Automated Emission Factor Change Notices
Every night, WebRun checks Persefoni for updates to the emission factors applied to your footprint, calculates the revised impact on your Scope 1, 2, and 3 totals, logs the delta in Google Sheets, and drafts a stakeholder notice in Gmail explaining the change and its magnitude for your review before sending.
How do I track emission factor changes and notify stakeholders about their impact?
WebRun checks Persefoni nightly for emission factor updates, calculates the resulting change in your Scope 1, 2, and 3 totals, logs every revision with before-and-after values in Google Sheets, and drafts a plain-language stakeholder notice in Gmail. The notice waits for your review before anyone outside the team sees it.
- Every emission factor change is logged with full before-and-after detail for audit purposes
- Stakeholders are notified promptly so no one is surprised by revised totals at year-end
- The stakeholder notice is reviewed and approved by your team before it is sent
Built for carbon accounting teams · ESG auditors · sustainability managers · climate disclosure officers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.persefoni.comin a real browser with your saved login - no setup, no API keys. -
1
Persefoni - detect emission factor changes and calculate impact
persefoni.com
WebRun opens Persefoni to detect emission factor changes and calculate impact. - Open Persefoni and check the emission factor library for any updates applied since the last run
- Identify which emission factors have changed and which activity data categories they affect
- Calculate the resulting change in Scope 1, 2, and 3 totals and note the delta in tCO2e
Done when Each changed emission factor is identified with its affected categories and the resulting delta in total emissions.
-
2
Google Sheets - log the revision and delta
google.com
WebRun opens Google Sheets to log the revision and delta. - Open the emission factor revision log sheet
- Append a new row with the date, the factor name, the old value, the new value, the affected category, and the delta in tCO2e
- This log supports assurance-grade audit trails for your GHG inventory
Done when Each emission factor change is logged in Google Sheets with full before-and-after detail.
-
3
Gmail - draft stakeholder notice for review
gmail.com
WebRun opens Gmail to draft stakeholder notice for review. - Draft a plain-language notice email summarizing the emission factor updates and their impact on the reported footprint
- Address the draft to the sustainability lead and relevant stakeholders listed in your setup
- Leave the email as a draft for your review - do not send automatically
Done when A stakeholder notice draft is ready in Gmail summarizing the updates and footprint impact, awaiting your review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it send the notice to stakeholders automatically?
No. The stakeholder notice is drafted in Gmail and left for your review. You decide who receives it and approve the send yourself.
What if no emission factors changed overnight?
If no changes are detected in Persefoni, WebRun skips the log entry and the draft email and runs quietly until the next check.
Why does this matter for our auditor?
Auditors need a complete record of which emission factors were applied and when they changed. The Google Sheets log provides a dated, before-and-after revision trail that supports assurance-grade GHG reporting.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.