The AGM packet you dread, and how it becomes routine

Every self-managed board has a specific week they dread. It’s the week before the AGM. Someone — usually the president or the secretary — is trying to assemble a coherent packet out of a year of scattered decisions, half-remembered incidents, and PDFs in three different Dropbox folders.

The packet is due seven days before the meeting. It’s Tuesday. The president has 40 open threads in their inbox and no clear picture of what actually happened this year.

This is the standard AGM prep experience, and it’s the reason most boards budget a full weekend for the AGM packet. It doesn’t have to be this way.

What the AGM packet actually needs to contain

Depending on jurisdiction, the specifics vary, but the operational content is broadly similar across HOA and strata AGMs:

• The prior year’s minutes. Board meetings, special meetings, any resolutions passed.
• The president’s report. A narrative of what happened.
• The treasurer’s report. Financial statements, budget vs actual, reserve fund status.
• Capital projects update. What was done, what’s in progress, what’s coming.
• Bylaw or rule changes. With the required vote.
• Election materials. For the incoming board.
• Notice items. Anything the bylaws or law require.

The last three are administrative — they’re always painful, but they’re bounded. You know exactly what’s required, you know the format, you know the deadline.

The first four are where the scramble happens. Each of them requires you to reconstruct a year of activity from memory and archives, and each of them is where boards routinely spend 6 to 12 hours per report.

The specific reason it’s painful

The pattern of AGM prep in most self-managed buildings:

• Open a blank document.
• Try to remember what happened in the first quarter.
• Search inbox for “roof” to reconstruct the roof project.
• Realize the roofer sent three quotes but only one is in email, the other two were texts.
• Ask the treasurer what the reserve fund did this year.
• Get back “let me check with the accountant.”
• Wait three days.
• Continue trying to remember what happened in the second quarter.

Repeat for the remaining quarters. Extrapolate to the treasurer, the maintenance chair, and the parking committee.

The result is a packet that’s technically complete but reads like it was written in one sitting under pressure. Because it was.

What changes when the log is the source of truth

Now consider the same building, having kept a real log for a year. Every decision, every service visit, every resident report, every capital-project milestone, every vendor exchange has been captured as a log entry with a date, an owner, and attached documents.

The AGM prep for that building looks different:

• The president’s report is a summary of the year’s log entries. Not a summary written from memory — a summary written from a filtered view of the actual record. “In Q1 we had 14 issues reported, 12 resolved and 2 rolled over to Q2.” Numbers, not narrative-only.
• The capital projects update is a filter on log entries tagged to the capital project. The roof project has a page. Every quote, every meeting, every vendor exchange, every decision on it — visible in one scroll. The update is written by looking at that page, not by searching four inboxes.
• The equipment status appendix — if your building includes one — is generated from the equipment records. “Boiler #1: serviced twice this year, no faults. Elevator: 4 service calls, one warranty repair.” Facts from the log.
• The complaints summary is generated from the issues log. How many complaints. How they broke down by category. How long they took to resolve. Not to expose specific residents — the aggregate is what matters for governance.
• The vendor summary — helpful for boards evaluating whether to change vendors — is generated from the vendor pages. “This year we used [plumber] 6 times, average response time 4 hours, total spend $8,400. [Roofer] 2 times for the ongoing project.”

None of these reports require you to remember anything. They require you to filter the log.

Why the year-round record beats the month-of scramble

The best AGM packet isn’t the one written the week before the meeting. It’s the one written continuously over 12 months and assembled the week before the meeting.

This is the same insight teachers have about textbooks and students have about note-taking: the person who takes ongoing notes on the material understands it better than the person who cram-reads at the end. The AGM packet is the exam. The log is the notes.

The corollary is that if your board only starts logging in March because the AGM is in June, the log won’t help this AGM — but it will transform the next one. Every year the log gets better.

What “good AGM prep” actually looks like in practice

The AGM prep process for a board that has been logging for a year:

Eight weeks out. Open the log. Read the year’s entries in the “Announcements” or “Decisions” filter. Draft the president’s report narrative from the material. Two hours.

Six weeks out. Ask the treasurer to prepare the financial report. They already have the raw numbers because they’ve been attaching invoices to log entries all year. Half a day for their own review, not a week of reconstruction.

Four weeks out. Send the draft packet to the whole board. Get comments. Adjust. Attach the compliance documents (annual inspections, insurance certificate, tax filing) that live in the manuals library.

Two weeks out. Send the finalized packet to residents at the statutory notice window. Post it on the resident portal so anyone who lost the email can find it.

AGM week. Print copies for the meeting. Show up prepared.

Total prep time: maybe 15 hours across the whole board. Not 60. Not the “we lost our lives for a week.” A real, manageable project.

What the residents see

The AGM packet is also a signal to residents. A packet that’s complete, coherent, and citing specific facts creates a very different meeting than a packet that’s clearly assembled at the last minute.

Owners can see when a board is on top of things. They ask better questions. They vote based on the actual state of the building rather than their gut sense of “how things are going.” The board gets better feedback because the residents have better information.

None of this is dramatic. It’s just what a building looks like when the record is real.

Where BuildingHQ fits

BuildingHQ is designed around the log-as-spine idea, which turns AGM prep into a filtering exercise. Log entries can be tagged and filtered. Equipment and vendor pages produce natural appendices. Procedures for recurring events (like AGM prep itself) live in the library, so next year’s president follows the same steps.

The specific “AGM prep procedure” write-up is one of the highest- leverage procedures a board can write — you write it once, and every subsequent year is a follow-along. Take an evening; write down the sequence you actually used this year (however painful); save it as a procedure. Next year, your job is to click through it.

If your AGM is in the fall, start now. The log you build over the next few months makes the packet you produce next year a fundamentally different document.