Sustainability action and evidence tracker
A useful sustainability action record tells a reviewer what was promised, what was delivered and what evidence supports the result. Those are separate questions. This editable tracker helps a coordinator keep them connected without turning a completed task into a claim that environmental or social performance improved.
The eight-page pack contains instructions, four reusable blank sheets and a three-page completed fictional case. Use the DOCX as a controlled working file or print the matching PDF. The PDF is not interactive. Neither file calculates results, validates dates, sends reminders or authorises a decision. Duplicate the action, evidence and review sheets as needed.
Download the editable sustainability action and evidence tracker (DOCX).
Download the print sustainability action and evidence tracker (PDF).
Define the action before updating its progress
Write the specific output, responsible owner, included site or population and first agreed due date. A pilot, an approved proposal and a roll-out are different outputs. Record the permission and resources on which the work depends. If those conditions are still missing, keep the action proposed or blocked rather than describing a hoped-for result as agreed work.
The result question belongs beside the output. For a quantitative review, specify the unit, population, period and denominator. For a qualitative review, describe the observation that would answer the question and its limits. These choices should make the future review possible; they should not be rewritten after the event simply to make the action appear successful.
The European Commission’s About EMAS page connects environmental objectives, implementation and evaluation of effectiveness. That environmental-management context supports keeping delivery and results distinct. This original tracker is not an EMAS form or registration process.
Give delivery and the result different states
Delivery states describe the promised work: Proposed, Agreed, In progress, Blocked, Delivered or Cancelled. Result-review states describe what can currently be said about the intended change: Not due, Awaiting evidence, Inconclusive, Reviewed within stated scope or Revisit required. The pack defines these as manual working conventions, not a certified rating system.
A team may deliver a trial while its result remains inconclusive. It may cancel an action for a recorded reason without achieving the intended benefit. An observed improvement can also be narrower than the ambition that motivated the work. Keep a short explanation beside the state so another reader does not have to infer the conclusion from a colour.
Use the review boundary sheet to identify which actions are included and the cut-off for the update. An index with one line per action is useful for navigation. It is not a substitute for the underlying action and evidence records, and the percentage of tasks delivered is not a percentage improvement in sustainability performance.
Keep the evidence specific enough to inspect
Give each item an evidence ID and exact version. Record its owner, controlled location, relevant page or row, covered population and period. State whether it is a source record, a summary, a calculation or an attributed account. A completion note may support that work happened while supplying no basis for an outcome comparison.
The evidence sheet asks what the item supports and what it leaves unresolved. If the source covers two sites while the action covers one, record that mismatch before using the totals. If a denominator changes, retain the definition and affected records. Do not remove a conflicting or superseded item merely because a better record arrives later.
Keep restricted material in its authorised location and use references in the tracker. The reviewer needs sufficient access to inspect the relevant evidence, but listing a file does not grant that access or permit wider circulation. Use role names where appropriate and avoid unnecessary personal details in a progress pack.
Follow a pilot through an unusable first comparison
The downloadable case is entirely fictional. Linden Parcel has two actions: A01 runs a reusable-crate pilot at West depot on route W; A02 prepares an East-depot proposal. A01 promises a completed pilot and indexed records, not a company-wide reduction. The result question concerns sleeves used per completed West route-W delivery over two specified September periods.
At the first review, A01 is delivered. Its baseline summary E01 covers both West and East, with 1,500 sleeves and 600 completed deliveries. The pilot record E03 covers West route W, with 576 sleeves and 480 deliveries. The arithmetic suggests rates of 2.5 and 1.2, but the populations differ. Reviewer V rejects the apparent 52% reduction as a West result and keeps the result review Inconclusive.
A later extract E02 supplies the intended baseline: 800 sleeves and 400 completed West route-W deliveries. The baseline rate is 2.0 and the pilot rate is 1.2. The difference is 40% of the baseline rate. Review RV02 records this as a lower observed sleeve rate for the two periods, after checking the route and count definitions.
The case does not establish that the crate trial caused that difference. It supplies no analysis of parcel mix or other changing conditions, no sleeve mass and no lifecycle assessment. The reviewed observation cannot become a claim about waste kilograms, avoided emissions, both depots or an approved roll-out. The earlier rejected comparison remains visible in RV01.
Preserve a date change without rewriting history
A02 needs an equipment-access description before its proposal can be completed. Its first due date was 7 October. Sponsor S agrees a revised date of 21 October in AP02, and the tracker retains both. At the 14 October cut-off, delivery remains Blocked and result review is Not due. The revised date does not erase the delay or turn the proposal into delivered work.
Use a new dated review or change record when scope, dates or evidence change. Identify the decision-maker and retained approval reference. A change in one action does not automatically change another action’s state. Where an earlier summary relied on corrected evidence, identify that summary and ask its owner to assess the effect.
Prepare a progress review that can be challenged
Before circulating a completed copy, choose a delivered action and trace its output. Then choose an examined result and reproduce the stated comparison or inspect the recorded qualitative test. Ask what would change the conclusion. Check that open dependencies have owners and dates, cancelled work has a reason, and superseded evidence is not being presented as current.
Use the corrective-action closure guide for investigating a process failure and testing a fix. Use the shared-actions guide when one task contributes to several issue decisions. This pack has a different practical job: reusable action, evidence and review sheets that keep a proposed result attached to its exact measurement scope. It does not replace either wider workflow.
Source: European Commission, About EMAS. Context shortened and paraphrased under CC BY 4.0. Checked 15 October 2026.
Version 1.0. Original Nitium Advisory forms, diagram and fictional case. This is a manual progress-recording aid. It supplies no assurance, certification, legal determination or permission to release a sustainability claim. Immediate operational concerns should use the appropriate escalation route rather than wait for the next tracker review.
Comments