Why this is a method and not a list of events
A “year in review” usually means a list of the year’s biggest events. Writing one for a real city requires care, because it is easy to repeat a half-remembered announcement or to count a plan as an accomplishment. This article therefore does not list particular events for any year. It describes how to build a review you can stand behind, using records that anyone can check. The rule throughout is simple: if you cannot verify an item in a primary source, leave it out.
Step 1: decide the scope
A review can cover everything or just one theme, such as housing, transportation or schools. Narrow reviews tend to be more accurate. Decide at the start:
- the exact dates covered (calendar year, fiscal year or school year, which are not the same);
- the geography (the city, the county or a neighborhood);
- the kinds of events included, such as votes, openings, funding awards and published data.
Fiscal years matter in particular. Many public bodies report on a fiscal year that does not match the calendar year, so figures from two sources may cover different periods.
Step 2: collect primary sources
Primary sources are the documents created by the people and bodies involved. Good starting points include:
- Meeting agendas and minutes of the city council, planning board, zoning board, school board and county board. How these bodies work is explained under city government and mayor and council.
- Adopted budgets and audits, the clearest record of what was funded. Background appears in material on municipal budgets.
- Ordinances and resolutions, which show what was formally enacted.
- State and federal data releases from agencies such as the US Census Bureau and the state departments of education, labor and community affairs.
- Press releases from agencies, used carefully as statements of what an agency wants known, not as independent confirmation.
- Local news reports, as a guide to what happened and who to ask. Older coverage can be found through newspaper archives.
Step 3: build a timeline
List each item with a date, the source, and a one-line description in neutral words. Keep a note of exactly where each came from. Good habits from research notes, such as recording the document title, date and page, make later fact checking much easier.
Step 4: sort by evidence level
Not every item deserves the same weight. A useful sort is:
- Happened and documented: a vote, a ribbon-cutting with an official record, a published dataset.
- Announced: a plan, pledge or proposal. Label it as such.
- Claimed: statements about results from a single party. Include only if attributed and qualified.
- Unverified: anything you can only recall or have seen secondhand. Leave it out.
Many reviews go wrong by blending categories two and one, treating an announced project as a finished one.
Step 5: check each number
Figures are the easiest place to make errors. For each number, confirm the source, the period it covers, and the definition used. Percentages need a base; a “doubling” from a small starting point may be small in absolute terms. Do not combine figures from sources that define a term differently. If two sources disagree, say so.
Step 6: add context and balance
A bare list of events can mislead. Add short context so readers can interpret what they see, and give space to differing views. If a project was celebrated by officials and criticized by residents, record both, attributed. Consider whether the year’s events are a trend or a one-off, a question that is hard to answer from a single year.
Step 7: leave out what you cannot verify
It is acceptable, and good practice, for a review to be short. It is better to include five confirmed items than twenty uncertain ones. State plainly that the list is not exhaustive and that readers should check current official sources for details, since dates, hours and programs change.
A note on the companion question
A related but different exercise is judging whether a year went well. That calls for a set of evaluation questions rather than a chronology, and it is a separate task from the factual compilation described here. Keep the two apart: first establish what happened, then decide what it means.