Why your AGM minutes shouldn't live in email

Somewhere in your inbox is a file called something like AGM_protocol_2022_final_v3_SIGNED.docx. Another version, possibly different, is in the previous manager’s inbox. A third was printed, signed, and put in a folder that moved offices in 2023. Between them, they are the legal memory of a building: what the owners decided, with what majority, about tens of thousands of euros of other people’s money.

Ask a simple question against that memory: what exactly did the assembly decide about the facade, and when? Now you are searching three inboxes for attachments, opening each protocol, and reading prose to find the resolution. If two versions disagree, you have a second, worse problem.

The failure here is treating decisions as documents. A decision is not prose. It is a record, and records want structure.

What an assembly decision actually is

Strip the ceremony away and every item an owners’ assembly votes on has the same five fields:

• The proposal. What was actually moved, in the exact wording voted on.
• The votes. For, against, abstained. In an owners’ community these are not simple counts: voting is per unit, and often weighted by ownership share, so “7 yes, 3 no” might be a rejection if the 3 hold the majority of shares.
• The outcome. Passed or rejected, and who announced it.
• The context. Which meeting, which agenda item, which date.
• The summary. What was resolved, in language a future reader can act on.

Minutes-as-a-Word-file flatten all of this into paragraphs. The votes, the one part most likely to be disputed later, become a sentence someone typed under pressure at 9 p.m. in a stuffy common room. This is exactly the argument we made about maintenance requests in what a structured ticket system looks like: the moment information has fields, prose is the wrong container.

The voting math is where trust is won or lost

Per-unit, share-weighted voting is unforgiving arithmetic. Unit 4 holds 62/1000ths, votes yes. Unit 9 holds 48/1000ths, is rented out, and the ballot must come from the owner, never the tenant. Two owners gave proxies to a neighbor. Three voted on paper from the room, one by written statement beforehand.

Do that in your head, live in the meeting, and every close vote becomes contestable afterwards. The owner who lost the vote will do the math at home, and if their result differs from your announcement, the dispute is no longer about the facade. It is about whether your records can be trusted at all.

Recording each ballot against the unit, with the weight attached and offline and proxy votes entered explicitly, turns the announcement into a computation anyone can check. Contestable becomes checkable, and checkable disputes die fast.

The register: numbered, chronological, append-only

Collecting decisions is only half the answer. The other half is how the collection behaves, and the right behavior is strict: every passed resolution enters a single per-building register, numbered consecutively, in chronological order, and nothing in it is ever edited or deleted. Made a mistake in entry 14? Entry 15 is the correction, saying so openly. The history of the mistake is part of the record.

This sounds pedantic until you see what it buys. An append-only register cannot be quietly rewritten, by anyone, which means nobody has to trust the manager’s good intentions. The record defends the honest manager as much as it constrains a dishonest one: when an owner claims “that is not what we voted,” the numbered entry with the ballot detail answers, and the conversation is over in a minute.

Germany turned this exact design into law: every managed community must keep a Beschluss-Sammlung, a consecutively numbered collection of resolutions, maintained promptly, with court decisions affecting the community entered alongside. But nothing about the design is German. It is simply what a trustworthy decision record looks like, and a manager in Zagreb, Vienna, or Warsaw benefits from it identically, statute or not.

Decisions between meetings belong in the same register

Not every decision waits for the annual meeting. Communities decide things by circulating a written resolution and collecting signatures, and these are precisely the decisions that vanish, because no meeting means no protocol, so the signed sheet ends up in a drawer, outside whatever filing discipline the meetings have.

The register fixes this by being the single home for passed resolutions, however they passed. A circular resolution gets its number in the same sequence, next to the assembly’s decisions. One place to look. No second, informal memory.

The register is what survives a handover

Managers change. When a building moves to a new manager, or your company loses a colleague, the inbox archive walks out the door. Forwarded threads and a hand-labeled folder of PDFs do not reconstruct ten years of governance; the new manager starts half-blind and rediscovers old decisions by stepping on them.

A register hands over as one artifact: the building’s complete decision history, numbered, with the voting evidence attached. It also prints. Owners are typically entitled to inspect the decision record, and buyers’ notaries, courts, and banks ask for extracts at the least convenient moments. From a register, that is an export. From inboxes, it is a lost weekend.

The pattern by now is probably familiar: informal channels feel free until the day you need the record, which is the same reason group chats quietly cap your capacity. Governance records just raise the stakes, because there the record is legally load-bearing.

Start with the next meeting

Nobody backfills ten years of protocols, and you do not need to. Start the register at the next assembly: agenda items in before the meeting, ballots recorded per unit as they are cast, outcomes announced from the computed result, resolutions numbered into the register the same evening. The old archive stays as it is, and every decision from now on is findable, checkable, and yours to hand over cleanly.

One resolution deserves to be first in the register, because it recurs every single year and moves the most money: the approval of the yearly budget. What that approval sets in motion, from monthly advances to the annual statement, is the owner accounting cycle, and it deserves its own article.