These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- ESG / Sustainability Dashboard
- Features
- Follow-up and execution history
Follow-up and execution history
Assign unresolved reporting work and trace how the operating outcome was recorded.
OverviewMy Follow-Up Actions×
ESG / Sustainability Dashboard · Follow-up and execution history
New
My Follow-Up Actions
Follow up actions
| Title | Source | Assigned to | Due date | Status | Completed at | |
|---|---|---|---|---|---|---|
| Open fua-259 | ESG-42345 | 11 Oct | Open | |||
| In progress fua-667 | ESG-19936 | 19 Oct | In progress | |||
| Completed fua-342 | ESG-90195 | 20 Oct | Completed | 15 Oct | ||
| Cancelled fua-269 | ESG-26389 | 17 Oct | Open | |||
| Open fua-357 | ESG-94924 | 21 Oct | In progress |
6 of 6 records
Open fua-259Follow up actions · FUA-80677
OpenSourceESG-42345
Due date11 Oct
ResolutionRSL-383
What you can do
Give the unresolved question an owner
A reporting review can leave work that needs a named person and a due date. Follow-up actions retain the source period, assigned person and current state. Action Owner records the resolution and completion date so the reporting team can see what was done after the original question was raised.
Execution history gives the analyst a different kind of follow-up. Operation runs retain the source revision, input hash and result reference. Their numbered steps carry input and output references, with external receipt details where applicable. Lifecycle history records the actor and change associated with the source period.
How the work is organized
- Assign the next action. Agree the responsible Action Owner and due date for an unresolved source or review question. The action title should identify the work clearly. Keep the source period attached so another person can understand why the action matters to the reporting cycle.
- Record the resolution. Action Owner records when open work is in progress, then marks it Completed with an explanation of what was resolved. When the responsible team cancels an action, retain the explanation. A completed label should be understandable alongside the resolution text and date.
- Inspect uncertain execution. Sustainability Analyst follows a failed or reconciliation-required run to its steps. Check the recorded inputs and outcomes before asking for more work. Auditor can inspect the lifecycle change with its actor, operation identity and source revision.
What to agree during setup
Agree who assigns follow-up and who can maintain it on behalf of the responsible person. Set expectations for the due date and resolution description. Sustainability Reviewer should know which outstanding actions affect the period under discussion and which belong to a later operating cycle.
Define the handoff for a failed step or an uncertain external receipt. Name the person who can check the authoritative source. Use the existing operation identity when investigating the attempt so the team does not confuse a repeated request with a new reporting task.
Check the handoff on an actual case
Use an April reporting period with partial source coverage. Assign a follow-up to the person obtaining the complete source evidence and give it an agreed due date. Action Owner records progress and later explains the evidence received in the resolution before marking the work Completed.
In a separate rehearsal, interrupt a review action before the outcome is confirmed. Sustainability Analyst finds the run and inspects the numbered steps. An Unknown or Failed step should remain part of the investigation until its actual effect is established from the appropriate evidence.
Ask Auditor to identify the source revision, actor and recorded lifecycle change for the successful case. Then inspect the unresolved run and its follow-up without changing either record. The team should be able to explain the difference between resolving a business question and confirming that an operation finished.
What your team sees
- My Follow-Up Actions — Assigned work with due date, state and resolution.
- Due Follow-Up Actions — Open or in-progress work due for attention.
- State Transition History — Recorded lifecycle changes with the actor and source revision.
Follow the work through
Follow Follow-up and execution checks, or return to Evidence collection and validation when the source evidence needs attention.
What it keeps track of
Data model- Follow up actions
- Assigned corrective and follow-up actions with due dates.
- ESG periods
- Measured web properties with lifecycle status and observed outcome fields.
- People
- Analysts, owners and reviewers belonging to an organization.
- Operation runs
- Workflow execution runs with frozen revision, input hash and result identity.
- Operation steps
- Numbered steps of an operation run with input/output and receipt state.
- State history
- Immutable lifecycle transition history for each source.
Who uses it
Permissions- Action Owner
- Resolves assigned work.
- Sustainability Analyst
- Investigates operation outcomes.
- Sustainability Reviewer
- Follows unresolved reporting questions.
- Auditor
- Reads the retained history.
- Admin
- Supports the agreed access scope.
Set up ESG / Sustainability Dashboard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.