Annual Report Planning Checklist

An annual report should do more than document a year.

A city can finish dozens of projects, serve thousands of residents, and manage a substantial budget—and still publish a report that leaves readers wondering what actually changed.

The problem is rarely a shortage of information. More often, it is a shortage of decisions made early enough: Who is this report for? What can the evidence support? What deserves the most space? Who owns each number? And what happens when the final draft reaches five departments with five different priorities?

A useful annual report connects resources, work, and outcomes in a way readers can verify. It is part accountability document, part public explanation, and part institutional record.

This Harbor Creative planning guide is designed for municipal communications teams, counties, public agencies, nonprofits, and other organizations producing a public-facing annual report. It provides a practical project framework, sample requests, and a release checklist—not a substitute for audited financial statements, legal disclosures, or professional accounting advice.

First, decide what kind of report you are producing.

The word annual report can refer to different deliverables. Identifying the right one at kickoff prevents confusion over requirements, audiences, and approvals.

These categories can overlap, but they are not interchangeable. The Government Finance Officers Association (GFOA) recommends accessible popular financial reporting as a supplement to—not a replacement for—comprehensive financial reporting. A PAFR seeking a GFOA award must satisfy the program's specific eligibility requirements, including consistency with the ACFR. See the GFOA PAFR eligibility guidance.

Planning decision: Identify the report type, reporting period, intended audience, legal or program requirements, and final approval authority before designing a page.

1. Start with the story the evidence can tell.

Do not begin with a table of contents copied from last year's publication. Begin with three questions:

1. What changed during the reporting period? Think service levels, infrastructure, programs, finances, community conditions, and operational challenges.
2. What evidence shows that change? Identify verified measures, approved financial figures, completed milestones, and documented examples.
3. Why should a reader care? Explain how the work affected access, reliability, safety, cost, opportunity, or quality of service—without claiming outcomes the evidence cannot establish.

A useful framing statement might be:

“This report explains what we committed to, what we delivered, what the numbers show, and where work remains.”

That last phrase matters. Public trust is better served by acknowledging a delayed project or an unmet goal than by treating every activity as an unquestioned success.

The GFOA's guidance on performance measures recommends tracking and communicating measures that cover finances, service delivery, program outcomes, and community conditions. A report can therefore move beyond a list of activities toward evidence of results.

Activity is not the same as impact

Consider these fictional illustrative examples:

• Activity: “We resurfaced 12 miles of roadway.” This describes work completed.
• Output: “Twelve miles reopened after construction.” This describes a deliverable.
• Outcome: “Average travel time on the corridor fell by 8%.” This is an outcome claim that requires a documented baseline, consistent measurement, and careful interpretation.

Not every program can credibly demonstrate a causal outcome. Use precise language: “was associated with,” “we observed,” or “the measure changed” when causation has not been established.

2. Create the reporting brief before collecting content.

A two-page brief can prevent weeks of revisions. Agree on these fields with the sponsor and core team.

Do not confuse an internal production target with an external deadline. For example, GFOA's PAFR award eligibility includes a six-month submission window after fiscal year-end; that is a program-specific condition, not a universal annual-report publication law.

3. Build a source-of-truth inventory.

Most reporting delays begin when data arrives in incompatible formats—or when two departments use the same label for different measures.

Create a single inventory for every important claim and chart. Suggested columns:

A chart without a clear definition can mislead even when every number is mathematically correct.

Six questions to ask about every metric

• Is the reporting period consistent with the rest of the report?
• Is the denominator clear, especially for rates and percentages?
• Are comparisons like-for-like, or did the definition change?
• Are estimates, preliminary figures, and audited figures clearly distinguished?
• Does the source owner agree with the interpretation?
• Can a reviewer reproduce the number from the cited source?

For financial reporting, do not independently rework audited figures into attractive graphics without finance-team reconciliation. GFOA advises that popular financial reports use data derived from the ACFR and the same accounting basis. https://www.gfoa.org/materials/popular-reporting-of-financial-information

4. Design the structure around reader questions.

A good report should let readers skim for the overview and then go deeper into the evidence. One flexible structure for a public-facing organizational report is:

1. The year at a glance. A short opening, the reporting period, and a handful of verified headline measures.
2. What we set out to do. Strategic goals, priorities, and the starting context.
3. What we delivered. Selected service, program, or project results, with supporting evidence.
4. What the numbers tell us. Trends, targets, finances, and explanations of significant changes.
5. People and places. Specific stories that illuminate a verified result, with permissions and context.
6. What needs work. Challenges, missed targets, constraints, and corrective actions.
7. What's next. Approved priorities and future milestones, clearly distinguished from completed work.
8. Methods and sources. Definitions, boundaries, references, and links to detailed statements.

An ACFR has its own accounting and presentation requirements; this sample structure is not an ACFR template. Consult applicable GASB requirements and the GFOA ACFR criteria for formal financial reporting.

5. Make numbers understandable without changing their meaning.

Charts should answer a question, not decorate a spread.

A useful chart title states what is being measured and over what period: “Median permit review time, FY 2024–FY 2026” is better than “Our Progress.”

Show units and sources. Use comparable scales. Explain unusual spikes. If a number is preliminary, label it. If the reporting method changed, show a note rather than pretending the trend is uninterrupted.

A fictional example: explain the change

Weak presentation: “Customer satisfaction: 91%.”

Stronger presentation: “In the 2026 survey, 91% of responding service users selected ‘satisfied’ or ‘very satisfied’ (n = 420). The survey was voluntary, so results may not represent every service user.”

All numbers in this example are invented for demonstration. Do not use them as real government performance data.

A strong report also distinguishes spending from outcomes. A project may be on budget but behind schedule; a program may serve more people while its wait time increases. Readers deserve both sides.

6. Use stories to add context—not to replace evidence.

A photograph, resident quote, or project vignette can help a reader understand why a measure matters. But one compelling story is not proof of system-wide performance.

Choose examples that are representative, documented, and approved. Confirm image rights, consent, attribution, location details, and privacy considerations. Avoid implying that a staged photograph depicts an actual project.

A practical story brief contains:

• Context: What problem or need existed?
• Response: What did the organization actually do?
• Evidence: What verified change or deliverable can be shown?
• Limitations: What is not yet known or completed?
• Human perspective: Whose experience helps explain the work, and do you have permission to publish it?

For a public-sector report, strong visual storytelling can include annotated before-and-after images, simple project maps, timeline diagrams, and carefully sourced photographs. All must be accurate and accessible.

7. Plan accessibility before the design is approved.

A polished PDF is not automatically an accessible publication.

The federal Section508.gov PDF guidance encourages a digital-first approach and explains why HTML may be more accessible and mobile-friendly than PDF. If PDF is necessary, plan document structure from the source file: headings, meaningful reading order, tagged content, real text, descriptive links, table headers, text alternatives for meaningful images, and adequate contrast.

For complex charts, provide the underlying values in an accessible table or an equivalent textual explanation. For a downloadable PDF, test its tags, reading order, language, links, and assistive-technology experience rather than relying only on a visual inspection. See Section508.gov's tag guidance and PDF testing resources.

If translations, alternate formats, or language access are appropriate, budget for qualified review. An inaccessible report that looks beautiful on a designer's monitor is not finished.

Applicability note: Federal Section 508 obligations and state/local accessibility obligations are not identical. Verify the requirements that apply to the specific organization and publication.

8. Give every approval a clear owner.

Annual reports can stall when everyone is invited to comment but no one is accountable for deciding.

Use a simple approval map:

Set a single consolidated review window for each draft. Require comments to identify the issue, proposed correction, and responsible approver. Freeze verified figures before final layout whenever possible; changes after the freeze should trigger a documented recheck of related charts, captions, and summaries.

An illustrative 12-week production calendar

This is a planning example, not an official deadline or a promise that every organization can complete an annual report in 12 weeks.

Formal financial reporting may depend on audit completion and external deadlines, so build the schedule backward from those constraints. Add contingency time for unresolved numbers and executive approvals.

9. Think beyond the PDF launch.

The publication should have a stable home: a report landing page that states the year, reporting scope, summary findings, and links to accessible formats and supporting documents.

A sensible distribution plan may include an accessible HTML overview, downloadable report, email announcement, social excerpts, public meeting presentation, internal staff version, and printed copies where useful.

Use short excerpts to direct readers to the complete report. Do not let a promotional post omit important qualifications or transform a cautious finding into a sweeping claim.

Measure what readers actually do: can they find the report, understand the key measures, locate the underlying financial statements, and submit questions? Downloads and pageviews help describe reach, but do not prove comprehension.

Archive the approved final version, supporting data, permission records, source files, and correction log under the organization's retention policy. If a significant error is discovered, document the correction and update every affected format.

The Harbor Annual Report Planning Checklist

Use these checkpoints from kickoff through publication. This is Harbor's original project-management checklist, informed by the linked guidance—not an official GFOA award checklist or regulatory compliance assessment.

A. Purpose and scope

• Report type and intended use are documented.
• Reporting period and included entities/programs are defined.
• Primary readers and their information needs are identified.
• Applicable reporting, funding, award, and publication requirements are checked.
• A sponsor and final approval authority are named.
• Publication date, formats, budget, and contingency are approved.

B. Evidence and financial integrity

• A master content and data inventory exists.
• Each key metric has a source, definition, period, and owner.
• Comparisons use compatible definitions and periods.
• Finance has verified financial figures and audit status.
• Estimates, preliminary data, and exclusions are disclosed.
• Claims about outcomes do not overstate causation.
• Important challenges and missed targets are not omitted.
• Every chart can be traced back to an approved source.

C. Writing and editorial

• The opening answers what changed and why it matters.
• Headings help readers find information quickly.
• Activities, outputs, and outcomes are clearly distinguished.
• Jargon, unexplained acronyms, and promotional exaggeration are removed.
• Stories and quotations are fact-checked and authorized.
• Future plans are distinguished from completed results.
• Sources, methods, and limitations are easy to locate.

D. Design and accessibility

• The design works on mobile and in print where applicable.
• Charts include labels, units, dates, and sources.
• Color is not the only way meaning is communicated.
• Images have appropriate rights, captions, and text alternatives.
• Headings, tables, links, and reading order are accessible.
• PDF accessibility is tested if a PDF is distributed.
• Alternate languages or formats are addressed where appropriate.

E. Reviews and release

• Department leads have approved operational facts.
• Finance and data owners have approved relevant figures.
• Privacy, legal, records, and compliance checks are completed where needed.
• Corrections are consolidated and resolved by accountable owners.
• A final independent proofread is completed.
• Every format matches the approved version.
• A stable public report page and distribution plan are ready.
• Source files, approvals, and final versions are archived.
• A process exists for questions and post-publication corrections.

Copy-and-use departmental content request

Send this request at the start of the reporting cycle. Adapt the fields to your organization's actual reporting requirements.

Subject: Annual report content request — [department] — due [date]

We're preparing the [organization] annual report for [reporting period]. Please submit your department's verified information by [deadline] using the fields below. We want to show what changed, what the evidence supports, and where work remains.

1. Key results: List up to three important completed activities or outcomes, with dates and a sentence explaining why each matters.

2. Supporting measures: For each number, provide the source, definition, reporting period, comparison or target, and the person who can verify it.

3. Challenges or changes: Identify delays, unmet targets, scope changes, or important limitations that should be explained.

4. Story and imagery: Suggest one documented project or human-centered example. Include captions, dates, locations, rights/consent status, and available high-resolution files.

5. Next period: List approved upcoming priorities and distinguish firm commitments from proposed work.

6. Reviewer: Name the person who will verify the final draft and the best contact for follow-up.

Please do not submit unverified estimates as final figures. If a number is preliminary or unavailable, label it clearly. Our team will consolidate responses into one editorial draft for review.

The final reader test

Before publishing, hand the near-final report to someone who was not part of the production team. Give them five minutes to answer:

1. What were the organization's most important accomplishments—and how do you know?
2. What did not go as planned?
3. Where can you find the financial information or source behind a major claim?
4. What will the organization focus on next?
5. Can you access the report and understand its charts on the device or format you use?

If they cannot answer, revisit the structure before changing the cover design.

A better annual report begins long before the first layout.

The strongest annual reports are not necessarily the longest or most elaborate. They are the ones that respect the reader's time, connect claims to evidence, and make the organization accountable for both achievements and unfinished work.

Start with the reporting brief. Build the evidence inventory. Agree on review authority. Then create the narrative and design around what can be verified.

That is how an annual report becomes a useful public document—not simply a record that another year has ended.

Research and further reading

• GFOA — Popular Reporting of Financial Information: distinctions between comprehensive and popular reporting, data consistency, clarity, and timing recommendations.
• GFOA — Popular Annual Financial Reporting Award Program: program purpose and evaluation criteria.
• GFOA — PAFR Award Eligibility: specific award eligibility, reporting basis, and disclosure expectations.
• GFOA — ACFR Award Criteria and Checklists: formal financial-report evaluation criteria.
• GFOA — Performance Measures: guidance on monitoring and communicating service and financial results.
• Section508.gov — Create Accessible PDFs: digital-first guidance and PDF accessibility resources.
• Section508.gov — Common PDF Tags: structure for headings, lists, images, and tables.
• GRI Standards: optional reference for organizations undertaking sustainability/impact reporting under that framework, not a general requirement for all annual reports.

Editorial note: This guide is educational project-planning content. Report-specific accounting, auditing, accessibility, legal, and disclosure requirements must be verified by the appropriate professionals and governing bodies. Illustrative schedules and examples are not real performance data or mandated timelines.