Most year in reviews fail for the same reason: they include everything. A review that lists every project, every hire, and every client is a status report, not a story. The list below is the opposite — a filter. Use it to decide what earns a slot, then use the checklist at the end to collect it.
What are the core sections of a year in review?
Six sections cover almost every case: results, customers, product and operations, people, milestones, and what’s next. A seventh — what didn’t go to plan — is optional but makes the other six more believable.
The order matters. Results first, because that’s what people came for. People before milestones, because milestones are only interesting when you know who hit them. A short forward look last, so the audience leaves with something to do.
1. Results: the promise and the outcome
Start with the targets you set at the beginning of the year, then show where you landed. A number without a baseline is decoration. “Revenue grew 23%” means little; “$4.2M, up 23% against a $3.4M plan” means something.
Include:
- Two to four headline metrics with a year-over-year comparison.
- The plan you set in January, if you published one internally. Comparing against your own forecast is more credible than comparing against nothing.
- One metric that isn’t financial but still matters: retention, NPS, delivery time, safety incidents, uptime.
Leave out anything you can’t source. If two systems disagree on the customer count, pick the system of record and say which one you used.
2. Customers: names, numbers, and one story
A customer count is a statistic. A customer story is a reason to care. Include both, but keep the story short — three sentences, ideally in the customer’s own words.
- Net new customers, and how many you kept.
- One named customer, with permission, and what changed for them.
- One quote that sounds like a person, not a testimonial template.
- A segment or geography that grew, if it’s genuinely new.
If you can’t use a customer’s name, describe them precisely: “a 40-person logistics firm in Ohio” beats “a leading enterprise client.”
3. Product and operations: what actually shipped
List what shipped and when, not what’s in progress. The test is whether a customer could use it this year.
- Three to five releases with a one-line description each.
- Anything you retired or fixed at scale, if it removed a real pain point.
- Capacity or efficiency gains that changed how the team works.
Avoid feature names that only make sense internally. “Project Atlas” means nothing on screen; “single sign-on for every customer” does.
4. People: hires, promotions, and the moments that matter
This is the section most reviews under-invest in, and the one the audience remembers. Include:
- Headcount at the start and end of the year.
- Key hires and promotions, with names and roles.
- New offices, shifts, or teams that didn’t exist in January.
- Service anniversaries at five, ten, or fifteen years — these land harder than anything else in the video.
- One team that carried an unusual load, named explicitly.
Get consent before putting anyone on screen, and be careful with people who left. A video that quietly erases a departed colleague is noticed by everyone who worked with them.
5. Milestones and firsts
Milestones are the moments that mark the year as different from the last one. They work best when they’re specific and dated.
- First customer in a new market, first million in a product line, first profitable month.
- Certifications, audits, awards you actually received (name the body and the year).
- Physical milestones: a new facility, a new line, a ribbon cutting.
If a milestone needs a paragraph of explanation, it belongs in the follow-up email, not the video.
6. What didn’t go to plan
One or two sentences, no more. “We missed our hiring target by twelve roles, and it cost us in support response times” is enough. This section buys credibility for everything before it and signals that leadership is paying attention.
Don’t turn it into a confessional, and don’t blame a team by name. State the miss, state what changed, move on.
7. What’s next
End with two or three priorities for the coming year, phrased as commitments rather than wishes. “Ship the mobile app in Q2” is a commitment. “Continue to innovate” is not.
Tie one of them back to something that happened this year, so the year feels like a step rather than a reset.
What should you leave out?
Cut these even when someone senior asks for them:
| Tempting to include | Why to cut it |
|---|---|
| A month-by-month chronology | Nobody remembers a year as a calendar. Organize by theme. |
| Every department’s project list | It reads as an internal status report and doubles the length. |
| Vanity metrics without context | Impressions, page views, and “engagement” mean nothing without a goal. |
| Unattributed statistics from the internet | If you can’t link the source, don’t put it on screen. |
| Internal jokes and project codenames | They exclude everyone hired in the last six months. |
| Customers who haven’t approved their mention | One angry email undoes a year of goodwill. |
| Anything about next year’s layoffs or restructuring | Wrong venue. Bad year in review videos are remembered longer than good ones. |
The checklist
Hand this to each department head with a deadline. One row per item, one owner, no essays.
| Item | Owner | Where to find it | Include if |
|---|---|---|---|
| Revenue or bookings, actual vs. plan | Finance | Close, board deck | Always |
| Year-over-year change for each headline metric | Finance | Board deck | Always |
| Net new customers and retention | Sales, CS | CRM, billing | Always |
| One approved customer story or quote | CS, Marketing | Case study, interview | Almost always |
| Three to five shipped releases | Product | Release notes | Always |
| Headcount start and end | People | HR system | Always |
| Key hires and promotions | People | HR system | If any, and there always are |
| Service anniversaries (5, 10, 15 years) | People | HR system | If any |
| New offices, teams, or markets | Ops | Ops lead | If any |
| Two or three dated milestones | Everyone | Department heads | Always |
| One honest miss, with what changed | Leadership | Exec team | Recommended |
| Photo and video assets with consent | Marketing | Shared folder | Always |
| Two or three priorities for next year | Leadership | Planning docs | Always |
If a row has no owner after one round of asking, cut the item. Unclaimed content is usually content nobody needs.
How much of this fits in a video?
A 90-second video holds roughly a third of this list. Map each section to a time budget before you write anything:
| Section | Seconds in a 90-second cut | Treatment |
|---|---|---|
| Results | 25–30 | Two or three numbers, large on screen |
| Customers | 15–20 | One quote, one face, one number |
| Product | 15–20 | Fast cuts of the thing working |
| People | 20–25 | Names on screen, not just faces |
| Milestones | 10 | One or two title cards |
| What didn’t go to plan | 0–8 | Narrated, no visuals needed |
| What’s next | 10–15 | One line, held long enough to read |
The full list still matters — it feeds the email, the slide appendix, and next year’s planning. The video is the highlight, not the archive. For formats that fit a 90-second cut, see year in review video ideas; for the production sequence, see how to make a company year in review video.
FAQ
How many data points should a year in review have? As a rule of thumb, eight to twelve for a video and twenty to thirty for a written report. Past twelve, viewers stop distinguishing one number from the next.
Should we include a financial loss or a missed target? Yes, in one sentence with what changed as a result. Omitting an obvious miss makes the audience distrust the wins.
Do we need to include every department? No. Include every department that had a result worth showing. A department with nothing to report this year can appear in the people section instead of getting a segment.
How do we handle remote or field teams? Give them their own segment with real footage from their location, even if it’s phone footage. A video that only shows headquarters tells most of the company they weren’t part of the year.
Can we reuse this content for the board deck? Yes, and you should. Build the checklist once, then cut it three ways: video script, all-hands slides, and the written recap. The numbers stay the same; only the length changes.
Once the list is filled in, the video is mostly assembly. Talluma is building a tool that turns your numbers into an animated year-in-review video. It is not available yet. More about who we are.