ESG / Sustainability Dashboard organizes reporting periods, measurement definitions and the evidence behind observed results. Each period has an operating organization, responsible owner and source identity.
Follow-up actions in one list
Sustainability Reviewer independently approves the exact period revision when approval is required, retaining the reason and evidence reference.
Every feature works on the same records. Pick one to see the screen your team works in.
Give every reporting cycle an owner and a defined measurement basis.
ESG periods
| Number | Name | Period date | Definition | Owner | Revision | |
|---|---|---|---|---|---|---|
| ESG-79483 | January 2026 reporting period | 20 Oct | Fuel combustion emissions | Nadia Mehta | 750 | |
| ESG-41184 | February 2026 reporting period | 30 Oct | Fleet energy intensity | Nadia Mehta | 120 | |
| ESG-88612 | March 2026 reporting period | 22 Oct | Monthly facility electricity use | Amira Salcedo | 890 | |
| ESG-65189 | April 2026 reporting period | 27 Oct | Business travel activity | Amira Salcedo | 230 | |
| ESG-39368 | May 2026 reporting period | 19 Oct | Fuel combustion emissions | Jonas Chen | 210 |
Collect measured facts against the reporting period and retain their source references.
Approval conditions
| Parent | Sequence | Description | Quantity | Unit | Observed on | |
|---|---|---|---|---|---|---|
| May 2026 reporting period | 10 | Reno meter reading for September | 370 | kilowatt-hours | 02 Nov | |
| April 2026 reporting period | 60 | Portland water total for month | 200 | t CO2e | 16 Oct | |
| January 2026 reporting period | 50 | Phoenix recycling weight for Q3 | 50 | kg | 23 Oct | |
| February 2026 reporting period | 10 | Denver charging energy for August | 710 | m 3 | 02 Nov | |
| May 2026 reporting period | 10 | Boise gas consumption for month | 720 | percent | 21 Oct |
Check document verification and snapshot coverage before relying on a result.
Metric observations
| Metric name | Source | Snapshot | Period start | Period end | Numerator | |
|---|---|---|---|---|---|---|
| Reno site electricity, September | April 2026 reporting period | September refrigerant log | 13 Oct | 19 Oct | 310 | |
| Portland water use, September | July 2026 reporting period | September fleet charging export | 14 Oct | 16 Oct | 890 | |
| Phoenix waste diversion, Q3 | July 2026 reporting period | September refrigerant log | 16 Oct | 25 Oct | 720 | |
| Denver fleet energy, August | January 2026 reporting period | Third quarter waste ledger | 22 Oct | 28 Oct | 320 | |
| Boise natural gas, September | July 2026 reporting period | August fuel card extract | 23 Oct | 28 Oct | 100 |
Record an independent decision against the reporting revision and its evidence.
Approval conditions
| Source | Source revision | Reviewer | Decision | Evidence reference | Reason | |
|---|---|---|---|---|---|---|
| February 2026 reporting period | 500 | Kofi Laurent | Pending | utility-statement-091.pdf | Meter estimate replaced by actual | |
| July 2026 reporting period | 130 | Leila Voss | Pending | waste-ticket-092.pdf | Quarterly total reconciled | |
| January 2026 reporting period | 550 | Jonas Chen | Pending | charge-export-093.csv | Duplicate charge removed | |
| February 2026 reporting period | 410 | Nadia Mehta | Pending | survey-response-094.xlsx | Supplier coverage revised | |
| May 2026 reporting period | 760 | Amira Salcedo | Pending | meter-photo-095.jpg | Emission factor updated |
Read observed sustainability results with their unit, definition and reporting window.
Metric results
| Source | Metric | Run | Period start | Period end | Dimension key | |
|---|---|---|---|---|---|---|
| July 2026 reporting period | Water use per production unit | Monthly evidence review run | 03 Nov | 09 Nov | site:reno | |
| March 2026 reporting period | Scope 2 purchased electricity | Supplier survey validation run | 23 Oct | 01 Nov | site:portland | |
| August 2026 reporting period | Electricity use per occupied floor area | Water intensity recalculation | 02 Nov | 04 Nov | fleet:west | |
| August 2026 reporting period | Fleet energy per delivery mile | Emissions factor update run | 13 Oct | 21 Oct | supplier:packaging | |
| July 2026 reporting period | Supplier data coverage | Emissions factor update run | 03 Nov | 11 Nov | unit:manufacturing |
Assign unresolved reporting work and trace how the operating outcome was recorded.
Follow-up actions
| Title | Source | Assigned to | Due date | Status | Completed at | |
|---|---|---|---|---|---|---|
| Verify Reno meter gap | January 2026 reporting period | Kofi Laurent | 19 Oct | Open | ||
| Reconcile waste hauler totals | May 2026 reporting period | Jonas Chen | 27 Oct | In progress | ||
| Confirm fleet charging export | March 2026 reporting period | Priya Haddad | 28 Oct | Completed | 23 Oct | |
| Review supplier survey omissions | July 2026 reporting period | Jonas Chen | 25 Oct | Open | ||
| Update refrigerant service log | March 2026 reporting period | Kofi Laurent | 29 Oct | In progress |
Evidence to reviewed sustainability results ships ready to use. One step needs a named approval before the work moves on: Review reporting period (Sustainability Reviewer).
Set the organization, responsible owner and effective measurement definition.
Collect measured facts with their units, dates and source references.
Check source coverage and document verification before relying on the reporting case.
Sustainability Reviewer decides the exact revision when the agreed policy requires approval.
Read the measured values with their definition, unit and result state.
Give unresolved questions an owner and due date, then retain the resolution.
Open any follow-up action to see the roles that work on it, its process stages and its approvals on one page.
Source, Assigned to, Due date and Resolution.
Records linked to this follow-up action.
Each role sees what its permissions allow.
Every status change, in order.
Review reporting period, with who decides.
June 2026 reporting period · Open
When approval is required, review the exact source revision and retain the reason and evidence reference.
Signed in as Sustainability Reviewer
| Decision | Approver | |
|---|---|---|
| Review reporting periodSustainability Reviewer decides the exact revision when the agreed policy requires approval. | Sustainability Reviewer | |
| Approve ESG periods, metric definitions | Sustainability Reviewer |
Everyone opens ESG / Sustainability Dashboard to the work that is theirs. Pick a role to see what it starts with.
Prepare reporting periods and observations, inspect metric outcomes and coordinate the evidence needed for review.
This is the first screen this role sees.
Source snapshots · Sustainability Analyst
| Name | Source system | Coverage start | Coverage end | Captured at | Record count | |
|---|---|---|---|---|---|---|
| September electricity meter export | Facility meter portal | 15 Oct | 19 Oct | 25 Oct | 21 | |
| September water meter export | Waste hauler statement | 19 Oct | 21 Oct | 28 Oct | 3 | |
| Third quarter waste ledger | Fleet charging export | 15 Oct | 21 Oct | 26 Oct | 8 | |
| August fuel card extract | Supplier questionnaire | 26 Oct | 04 Nov | 13 Nov | 13 | |
| September refrigerant log | Utility billing feed | 02 Nov | 04 Nov | 06 Nov | 10 |
Maintain measurement definitions, field mappings and source coverage for the reporting team.
This is the first screen this role sees.
Source snapshots · Data Steward
| Name | Source system | Coverage start | Coverage end | Captured at | Record count | |
|---|---|---|---|---|---|---|
| September electricity meter export | Facility meter portal | 15 Oct | 19 Oct | 25 Oct | 21 | |
| September water meter export | Waste hauler statement | 19 Oct | 21 Oct | 28 Oct | 3 | |
| Third quarter waste ledger | Fleet charging export | 15 Oct | 21 Oct | 26 Oct | 8 | |
| August fuel card extract | Supplier questionnaire | 26 Oct | 04 Nov | 13 Nov | 13 | |
| September refrigerant log | Utility billing feed | 02 Nov | 04 Nov | 06 Nov | 10 |
Independently decide reporting revisions and review the measurement basis used by the team.
This is the first screen this role sees.
Source snapshots · Sustainability Reviewer
| Name | Source system | Coverage start | Coverage end | Captured at | Record count | |
|---|---|---|---|---|---|---|
| September electricity meter export | Facility meter portal | 15 Oct | 19 Oct | 25 Oct | 21 | |
| September water meter export | Waste hauler statement | 19 Oct | 21 Oct | 28 Oct | 3 | |
| Third quarter waste ledger | Fleet charging export | 15 Oct | 21 Oct | 26 Oct | 8 | |
| August fuel card extract | Supplier questionnaire | 26 Oct | 04 Nov | 13 Nov | 13 | |
| September refrigerant log | Utility billing feed | 02 Nov | 04 Nov | 06 Nov | 10 |
Resolve assigned follow-up work and retain the explanation of what was completed.
This is the first screen this role sees.
Follow-up actions · Action Owner
Read authorized measurements, decisions and execution evidence without altering the reporting outcome.
This is the first screen this role sees.
Operation runs · Auditor
Maintain organization, people and user access for the approved reporting scope.
Examine reporting readiness, measurement context and unresolved evidence questions.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Open | 43 | ||
| In progress | 26 | 60% | |
| Completed | 15 | 58% | |
| Cancelled | 7 | 47% |
Sample counts per stage
Which reporting cycles are collecting evidence, under analysis or ready for their next handoff?
Which reviewed values share a meaningful unit and measurement basis?
How do comparable measurements differ across reporting windows?
Which snapshots support the intended window and which need investigation?
Which documents have a verification outcome and responsible person?
Who decided which period revision and on what evidence?
Which unresolved tasks need attention from their assigned owner?
Which runs and numbered steps need an outcome check?
See how ESG / Sustainability Dashboard fits your kind of team.
Coordinate measured evidence and reporting ownership across operating teams.
Review observed sustainability measures alongside their production-period evidence.
Bring period ownership, reviewed measurements and unresolved actions into reporting meetings.
Each stage of evidence to reviewed sustainability results names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Prepare measurement context and trace review evidence with an assistant working in your scope.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 17 tablesStart with one team and one process, then add the rest once the basics are running.
Select a period and an observed metric whose source evidence can be inspected. Name the responsible analyst, data steward and independent reviewer. Agree which policy requires approval.
Admin sets organization and reporting access. Data Steward confirms the effective definition, metric version, unit and source mapping before collection begins.
Collect observations against the intended revision. Check a snapshot’s coverage and a supporting document’s reference. Include a partial window and a source fact belonging to another period.
Have the reviewer return a case with a useful reason, then decide the current corrected context. Inspect the operation run and steps before treating the effects as confirmed.
Assign the unresolved question with a due date and retain its resolution. Ask Auditor to explain the period decision, measured result and lifecycle change from the recorded evidence.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure ESG / Sustainability Dashboard for your business. Begin with a reporting period, an existing observed metric and accessible source evidence that an independent Sustainability Reviewer can inspect.
The Overview brings together KPI health, reviewed metric results by unit, monthly period activity, status mix, an observed emissions-intensity trend and overdue follow-up. Use the underlying records to examine a result's measurement and evidence context.
Give the period a recognizable name, date, owner and source identity. Select the operating organization and effective measurement definition so the team can interpret the collected facts consistently.
Keep its unit, reporting window and source reference available. Metric readings retain their snapshot, while persisted results retain the metric definition and operation run needed for follow-up.
When the agreed policy requires approval, an independent Sustainability Reviewer decides the exact period revision. The decision retains the reviewer, reason and evidence reference.
Compare the snapshot's coverage window with the reporting period and assign the unresolved question to the responsible person. A recent capture date alone does not establish complete coverage.
Inspect the recorded reason with the metric definition, source and operation context. Keep the result state visible during review and assign any unresolved source or interpretation question for follow-up.
Check the unit, definition version, dimension and measurement basis before comparing values. Data Steward should explain a changed denominator or aggregation method before the team treats the difference as a trend.
Inspect the existing operation run and numbered steps. Follow their input, output and receipt references to establish the actual effects before deciding what further action is needed.
Action Owner records progress, completion date and a useful resolution against the source period. The reporting team can then identify what changed and whether any related question remains unresolved.
Start free, then use Proto to change fields, steps and approvals before your team goes live.