Writing a Nonprofit Annual Report

What the report is actually for

Most annual reports are produced because the organisation has always produced one. That is not a purpose, and it shows in the result: forty pages of photographs and adjectives that nobody outside the office reads.

A report earns its cost when it does one of three jobs. It gives donors a reason to give again, by showing what their money did. It gives funders evidence that you are a competent organisation worth backing, which matters when they are deciding between you and someone else. Or it gives your community and partners a shared account of what happened, which is useful when you need them to act.

Decide which of those three you are doing before you write a word. The structure, the length, the tone and the amount of financial detail all follow from that decision, and a report that tries to do all three at once usually reads as though it was written by a committee, because it was.

What is required and what is chosen

This confuses more boards than it should. In Canada, a registered charity must file an annual information return with the Canada Revenue Agency, and incorporated nonprofits have filing obligations under the legislation they are incorporated under, including financial statements and, in many cases, an annual meeting. Those are obligations with deadlines and consequences.

The annual report, the designed document with photographs and a message from the chair, is not required by anyone. It is a communications product you choose to make. That is good news: since nobody prescribes it, you can make it as short and as useful as you like, and you can put the effort into the parts your readers actually use.

Worth knowing: your filing is public. Anyone can look up a registered charity in the CRA charity listing and read what you reported, including revenue, expenditures and compensation bands. Funders do this. So a report that paints a picture your filing contradicts is worse than no report at all. Our guide to charity compliance in Canada covers the filing side in detail.

Decide the audience before the format

Pick the primary audience and write for them. The others will still read it, and a document with one clear reader in mind is more useful to everyone than one aimed at nobody in particular.

A structure that works

You do not need a novel structure. This one is common because it answers questions in the order readers ask them.

1. A short opening from the chair or executive director. Half a page. What the year was about, what changed, one honest acknowledgement. Not a list of thank-yous.
2. What you set out to do. The objectives you started the year with, stated plainly. This is the part most reports skip, and it is what makes everything after it meaningful.
3. What happened. Programs and activities, with numbers that have context and at least one thing that did not go to plan.
4. Who it was for and what changed for them. Outcomes where you have them, outputs where you do not, and a story that a real person consented to.
5. The finances. A summarised picture in plain language, with the full statements available on request or linked.
6. The people. Board, staff, volunteers, partners and funders, named accurately and spelled correctly.
7. What is next. Two or three specific commitments for the coming year, which become the objectives section of next year’s report.

That last connection is the one organisations miss. If this year’s report ends with commitments and next year’s report opens by reporting against them, you have created a chain of accountability that funders notice immediately.

“Report against what you said you would do. An account of activity with no stated intention behind it is a newsletter, not a report.”

The financial section people actually read

Two failures are common and opposite. Some reports reproduce the full audited statements, which almost nobody reads. Others show a single pie chart with no numbers attached, which tells the reader nothing and looks evasive.

The version that works is a summary with words around it. Total revenue and where it came from, total expenditure and what it went on, the result for the year, and two or three sentences explaining anything that would puzzle an outsider. A large one-time grant, a deficit taken deliberately from reserves, a jump in salary costs because a program grew: each needs a sentence. Without it, readers invent an explanation, and the one they invent is usually less flattering than the truth.

Impact without inventing numbers

The pressure to show impact produces a lot of invented arithmetic in this sector. Numbers get multiplied into social value, attendance becomes lives changed, and a reader with any experience discounts the whole document.

Be precise about what you are reporting. An output is what you did: sessions delivered, people served, meals provided. An outcome is what changed for them: a skill gained, housing secured, isolation reduced. Outputs are easy to count and weak evidence on their own. Outcomes are harder and much more persuasive, and you can only report them if you measured them.

If you did not measure outcomes this year, say what you did measure and commit to what you will measure next year. That is a stronger position than an impressive-sounding figure nobody can trace. Our guides to outcome measurement and impact reporting cover how to build that evidence without a research budget.

Stories, consent and dignity

One well-told story does more than a page of statistics, and it is also the part of the report most likely to cause harm if handled carelessly.

Get informed consent in writing, and make sure the person understands where the story will appear and for how long. Offer the option of a changed name or no photograph. Let them read what you wrote before it is published. And be clear that services do not depend on agreeing, which people will assume unless you say otherwise.

Write the person as a person, not as a case. The test is whether they would recognise themselves in the description and feel respected by it. A story that positions your organisation as the rescuer and the participant as grateful and passive is both inaccurate and unpleasant to read, and it is the default register of a surprising number of annual reports.

Saying what did not work

This is the single highest-return paragraph in an annual report, and almost nobody writes it.

Funders read a great many of these documents. They know that no year goes entirely to plan, so a report where everything succeeded reads as either incurious or unreliable. One honest paragraph about a program that underperformed, a target missed, or a difficult year for recruitment, followed by what you learned and changed, signals an organisation that can be trusted with information. It is the fastest way to become more credible than the reports sitting next to yours.

Keep it proportionate. This is not a confession, it is professional candour: what happened, why, what you did about it, and what is different now. Two hundred words is plenty. Boards are often nervous about it and are usually reassured by seeing the paragraph written rather than discussed in the abstract.

Format: web page, PDF or print

The practical answer for most organisations is a web page as the primary version, a PDF generated from the same content for people who ask, and a short print run only if there is a specific occasion for it. Whatever you produce, make it accessible: real headings, alt text on images, adequate contrast, and text that can be resized. A report your community cannot read is not a report.

Plain language, accessibility and translation

The audience for an annual report includes people who do not work in your sector, do not use its vocabulary, and are reading on a phone between other things. Every piece of internal shorthand you leave in costs you readers.

Cut the jargon that means nothing outside the office: capacity, leverage, stakeholder engagement, wraparound supports. Say what happened in the words a participant would use. Keep sentences short enough to read once. If a term genuinely has no plain equivalent, explain it the first time you use it and then use it consistently.

Accessibility is part of the same job. Real headings rather than large bold text, alt text on every image, contrast strong enough to read in sunlight, and a web version that works with a screen reader and at larger text sizes. If you publish a PDF, tag it properly rather than exporting a flattened design file.

Then ask which languages your community actually uses. If a meaningful share of the people you serve read another language more comfortably, a translated summary matters more than another page of English. In much of Canada that means French, and in many communities it means something else entirely. A short translated version reaches people that a long untranslated one never will.

A production timeline that holds

Annual reports run late because the work is assumed to start when the year ends. It should start during the year.

1. All year: collect as you go. A shared folder for photographs, consented stories, milestones and numbers. Fifteen minutes a month beats three weeks of archaeology.
2. Two months before publication: agree the audience and outline. Who it is for, how long it will be, what the three or four things you want understood are.
3. Six weeks out: draft the content. Written by one person, not assembled from departmental submissions, which is how reports lose their voice.
4. Four weeks out: finances and factual check. Numbers reconciled against the statements, every name and title verified, every figure traceable to a source.
5. Three weeks out: board review. One round, with a clear brief: check accuracy and risk, not style. Unmanaged board editing is the most common cause of delay.
6. Two weeks out: design and accessibility pass. Layout, alt text, contrast, and the web version built from the same content rather than as an afterthought.
7. Publication: distribute deliberately. With a plan for who receives it and what you want them to do, not a single email to everyone.

Who writes it and who signs it off

One writer, one approver, and a short list of people who check facts. That is the arrangement that produces a readable document on time.

The writer should be someone who can hold a consistent voice across the whole thing, which usually means a communications staff member, the executive director, or a contracted writer who interviews the team. Assembling sections written separately by each program manager produces exactly the document you would expect: seven tones, repeated background, and no argument running through it.

The board’s role is governance, not copy-editing. Give them a clear brief: confirm that the financial summary is accurate, that nothing creates legal or reputational risk, and that the commitments for next year are ones the board is prepared to stand behind. Style comments should be optional and collected in one round. Without that brief, a good draft can spend six weeks being smoothed into nothing.

The annual meeting and the report

If your organisation has members and holds an annual meeting, the report and the meeting are related but not the same. The meeting has requirements set by your governing legislation and bylaws: notice periods, the financial statements presented, elections, and any special resolutions. The report is the document that makes that meeting comprehensible to someone who has not sat in your board meetings all year.

Practically, that means two versions of the same material. Members receive what the bylaws require, including the financial statements in the form your legislation specifies. Everyone else receives the report. Trying to make one document satisfy both usually produces something too technical for the public and not compliant enough for the members.

Check the notice period before you set the publication date, since that is the constraint people discover late. If members must receive materials a set number of days before the meeting, the report timeline works backwards from that date, not from when the design will be finished.

If you are a very small organisation

An organisation with one or two staff and a volunteer board should not be producing a sixteen page designed document, and the sector’s habit of pretending otherwise wastes a great deal of scarce time.

The small version is two pages or one web page: what we set out to do, what we did, who it reached, what it cost and where the money came from, one story with consent, one thing we learned, and what we are doing next. Written in a day, published on your website, sent to your donors. It contains everything a funder needs to see and nothing that exists only to fill space.

That version also scales. Publish it every year and you build exactly the chain of accountability larger organisations spend thousands trying to demonstrate, because a reader can follow your commitments and results across several years on a single page each.

Keeping the cost sensible

An annual report can cost anything from staff time alone to a five figure design and print project. For most small and mid-sized organisations the sensible end is modest, and the money is better spent on the parts readers notice.

Photography is usually worth paying for, because authentic pictures of your own work are the one thing you cannot borrow, and stock images of other people’s communities undercut everything else in the document. Design is worth paying for once: a template you can reuse for several years costs a fraction of commissioning a new look annually. Printing is the line to cut first, since a web page reaches more people for less.

Getting it read

Publication is not distribution. A report that goes up on the website and into one all-list email has been published and largely not read.

Segment the send. Donors get a message about what their giving did, with a link to the story and the finances. Funders get a short note referencing the specific work they funded and the relevant page. Partners get what is relevant to the work you do together. Staff and volunteers should see it before anyone outside does, ideally with a note naming the parts that are about them.

Then keep using it. Pull the strongest paragraphs into social posts across the following weeks, quote the outcomes in applications, and reference the page in your next newsletter. The document was expensive to produce, and most organisations extract about a tenth of its value in the first week and none afterwards. Our playbook on nonprofit communications strategy covers how that fits into a year of communications rather than a single event.

Reusing it for the rest of the year

Everything in a good annual report has a second life. The impact section becomes the evidence base for grant applications. The financial summary becomes the sustainability narrative funders ask for. The story becomes a case study, a newsletter feature and a social post. The commitments become the objectives you report against next year.

Keep the underlying material in one place: the consented stories, the photographs and their permissions, the outcome data with its method, and the final approved text. A year later, when someone asks for a summary of last year’s work for an application due on Friday, that folder is the difference between an hour and a fortnight.

Make one more artefact while the material is fresh: a single page summarising the year in about three hundred words, with the two or three numbers you are most confident in and one sentence on what changed for participants. That page answers the background section of almost every grant application you will write in the next twelve months, and writing it once, carefully, in the same week the report is approved, is far better than reconstructing it under deadline pressure four months later.

Mistakes that make reports unreadable

Frequently asked questions

What goes into a nonprofit annual report?

A short opening from leadership, what you set out to do, what actually happened, who it was for and what changed for them, a plain language financial summary, the people and funders involved, and specific commitments for next year. Everything else is optional.

Is an annual report legally required in Canada?

The designed annual report is not. Registered charities must file an annual information return with the CRA, and incorporated nonprofits have filing and meeting obligations under their governing legislation. The report is a communications choice on top of those requirements.

How long should it be?

For most small and mid-sized organisations, eight to sixteen pages, or the web equivalent. Length should follow the audience and the material, and a shorter report that is read beats a longer one that is not.

When should we publish it?

Within a few months of your year end, aligned with your annual meeting if you hold one. Publishing six months late signals that the information was not important.

Should it be a PDF or a web page?

A web page as the primary version, because it is findable, readable on a phone and accessible, with a PDF generated from the same content for people who ask for a document. Print only where there is a specific occasion for it.

How much financial detail should we include?

A summary of revenue by source and expenditure by program, the surplus or deficit, and a sentence explaining anything unusual, with the full statements linked or available on request. Remember that a registered charity’s filing is public, so the report must be consistent with it.

Do we have to report things that went badly?

You are not required to, and it is the paragraph that most improves credibility with funders. Keep it proportionate: what happened, why, what you changed.

Can we use participant stories?

Only with informed written consent, with the option of anonymity, and after the person has read what you wrote. Make clear that services do not depend on agreeing.