Build an Annual Report Evidence Register Before Writing the Narrative
An annual report can look polished while its claims, numbers and approvals remain difficult to verify. A simple evidence register gives each statement an owner, a source and a review status before copy and design begin.
What is an annual report evidence register?
It is a working list of statements the report might make, the evidence behind each one and the person authorised to confirm it. It can cover operating performance, projects, people, governance and sustainability claims. It is an editorial control tool, not an assurance opinion or a substitute for audited financial statements.
The IFRS Foundation’s Management Commentary page describes the purpose of a coherent narrative around factors affecting an entity’s prospects. If an organisation uses the GRI Standards, GRI 1 also emphasises traceability of reported information and a content index. These frameworks have different scopes; your legal, regulator, board and chosen reporting-standard requirements determine what your report must contain.
Give every material claim a review trail
A spreadsheet or shared document can work. The register needs enough detail to let the writer, finance team, subject owner and designer use the same approved version.
| Field | Question to answer |
|---|---|
| Draft claim | What exactly will readers be told? |
| Period and boundary | Which year, entity, site or project does it cover? |
| Source file and owner | Where is the original record and who confirms it? |
| Method or definition | How was a figure calculated, and is it comparable with last year? |
| Approval and status | Is the claim verified, qualified, pending or removed? |
| Report location | Where will the approved claim and any note appear? |
For formal GRI reporting, use the standard’s own content-index requirements rather than treating this working table as the required index. GRI’s Content Index Service explains that consistency, accessible reported information and required disclosures are separate checks.
Turn a broad statement into a checkable one
Illustrative wording: “We improved customer response times across the GCC.” The statement is too broad to review. Which channels, markets and period? What counts as a response, and does the comparison use the same definition?
A better draft might be: “For enquiries handled by our UAE service desk, median first response time fell from X to Y minutes between the two stated periods, using the same ticket-start definition.” The numbers here are placeholders, not Labeeb or client results. The owner must supply the underlying system export, exclusions, method and approval before any figure is published. If comparable data are unavailable, remove the numerical improvement claim or describe the service change without asserting an outcome.
Resolve evidence before layout locks the story
- Set the brief. Agree the audience, entities, reporting period, framework and approval path.
- Request source material. Gather approved financial statements, board-approved figures, project records, policy changes and relevant design assets through secure channels.
- Build and review the register. Flag claims whose evidence is missing or whose scope differs from the proposed headline.
- Draft with qualifications. State the metric boundary, comparator and material limitations near the claim. Keep the narrative consistent with tables and charts.
- Freeze approved copy and data. Give design and translation teams a controlled version. Recheck every chart label and translated numerical statement after layout.
- Perform final sign-off. The organisation’s authorised reviewers, auditors or legal advisers confirm matters within their remit; the writer or designer does not certify them.
Labeeb’s existing annual-report service can support the writing and design process after the organisation provides the verified inputs. For sequencing and handoffs, the already scheduled production-timeline guide will address a different question when it goes live.
Follow one claim from draft to approval
Suppose a UAE organisation wants to write, “Our training programme reached more employees this year.” That sentence combines a population, a period and a comparison, but none is defined. A useful register entry would make the decision visible before the sentence appears in a designed report.
Claim and boundary
“Employees who completed at least one approved course increased between the 2025 and 2026 reporting years.” Confirm whether contractors, new joiners and repeated courses are included.
Evidence and owner
Record the learning-system export date, report filters, headcount denominator and HR owner. Save a controlled copy of the source rather than relying on a screenshot in an email.
Decision and wording
If both years use the same definition and HR signs off, use the approved figures with their scope. If definitions changed, explain the break in comparability or remove the increase claim.
Illustration only: this is a fictional editorial example, not an assertion about any organisation’s training results. The register should retain the rejected wording and reason as well as the final approved sentence. This prevents an earlier, broader claim from reappearing in a chart caption or translation.
What should the team do when evidence is weak or inconsistent?
Missing source: mark the claim pending and name the person who can provide a primary record. A draft interview statement or marketing slide is not a substitute for an approved dataset. Conflicting totals: compare the reporting boundary, period, units and exclusions before choosing a number. Changed method: document the change and decide whether a year-on-year comparison is still defensible. Unverified case study: seek client permission and confirmation of the outcome before naming a customer or quoting results.
The point is to make the claim easier to explain to a reader, not simply to collect more files. A strong editor can turn a qualified or narrower fact into clear prose. A weak process hides uncertainty in confident language. For an annual report, unresolved figures should go to the organisation’s responsible finance, governance or legal reviewers; Labeeb’s writing team should not override their judgement.
If the organisation reports under the GRI Standards, follow the relevant GRI requirements and reporting principles for the disclosures it makes. If it uses IFRS Management Commentary, note that the revised 2025 Practice Statement is a separate framework focused on information relevant to investors. Neither source by itself determines every UAE or GCC entity’s legal annual-report obligations.
Need a report readers can follow and your team can verify?
Bring your reporting brief, prior report, source inventory and approval timetable. Labeeb can discuss narrative structure, editorial production, bilingual presentation and design scope. Your organisation remains responsible for the underlying data, formal disclosures and sign-off.
See Labeeb’s annual-report writing and design service for the available support.