How to prepare your first VSME report

1. Set the boundary before collecting numbers

Write down the reporting year, company name and sites. For our fictional example, a bakery reports on one company and two premises for a calendar year. Put those details at the top of the collection sheet so that the person supplying an invoice knows which period belongs in the report.

2. Assign ownership and evidence

Ask finance for utility and fuel records, HR for workforce information, and the operations lead for safety records. Give each request an owner and due date. A request for “electricity use in kWh for both sites for the reporting year, with invoices” is easier to answer than “send your carbon data”.

• Use consistent units before combining site totals.
• Check whether bills cover the full year or overlap.
• Keep the original record and the calculation used.
• Explain estimates and missing periods explicitly.

3. Review the answers together

Check the period, unit, source and reviewer for every material figure. In the bakery example, a bill for a third address should trigger a boundary question before it enters the total. Ask a second person to review figures that will be important to the recipient.

Do not confuse an unanswered question with a zero. Record why something does not apply, what is missing, or what estimation method was used.

4. Design and deliver

Use headings and tables that make the report easy to navigate. Include the reporting boundary and explain figures in plain language. Greener Ahead lets you work from templates, edit the document and share a report link. Check both the exported document and the recipient’s view before delivery.

5. Make next year easier

Keep a short log of collection problems and decisions. Record who owns each source for next year. Reuse the structure while reviewing each carried-forward answer; a new year needs its own evidence and approval.

Use handovers to keep preparation moving

Make the next action clear enough that a colleague can complete it without interpreting a broad request. At the start, confirm what “done” means for each handover. Evidence collection is done when the requested records and their exceptions have been supplied, not when someone has replied to an email.

Write an evidence request someone can answer

Example request: “Please provide purchased electricity in kWh for the bakery and shop for 1 January–31 December 2025. Include the supplier records and meter identifiers. List missing months and corrected bills separately. Do not include gas in the electricity total.”

The owner should return the sources as well as the total. A reviewer can then check the arithmetic and boundary independently. Store links or document identifiers in the register; use access-controlled storage for the actual records. Avoid circulating payroll or other personal records when an aggregate is sufficient.

Run a release rehearsal

Read the finished output as a recipient. Start at the reporting basis and trace one important number back to its source. In the electricity example, the displayed 48 MWh should reconcile to 48,000 kWh in the register. The narrative should say which sites and months are included.

Open the share link with the intended access level, or inspect the exact exported file. Check page breaks, table headings, units, links and attachments. Record the approved version and delivery date. A well-designed page is useful only if its numbers and access settings are correct.

• Does the final report agree with the approved data?
• Can the recipient understand exceptions without a follow-up call?
• Are sensitive working records excluded from the delivery?
• Is there a named contact for corrections and questions?