Procedures aren't for this board — they're for next year's

The reason boards resist writing procedures is that they don’t need them. The board that’s currently on knows how the boiler works, who to call for the elevator, and what sequence of buttons to press when the fire panel throws a fault code. Writing it down feels like busy- work — an official version of what everyone already knows.

That framing is exactly why every self-managed building is one board turnover away from a preventable disaster.

Procedures aren’t documentation of what the current board already knows. They’re an insurance policy for the next board, who won’t know any of it.

What “everyone knows” actually looks like when it fails

A small strata council in a Vancouver neighborhood — three floors, 32 units, self-managed for six years. The president had been on the board for four of those six. She was the person who knew how the boiler worked, who to call when the elevator was down, and what to do when the fire panel went into a “supervisory” state after a storm.

In April, she was diagnosed with a serious illness. Two weeks later, she resigned from the board. The vice-president, who’d been on for a year, took over. Within a month:

• The boiler pilot went out on a Sunday. The new president called a plumber who charged an emergency fee for the wrong service. The correct action — reset sequence documented in a photo on the outgoing president’s phone — was unknown.
• The elevator went out. The board called the elevator company they thought was under contract; it turned out the contract had been switched to a different company eight months earlier and never formally handed off. Two-hour delay.
• The fire panel threw a supervisory. Nobody on the current board knew whether to call the alarm company (yes) or the fire department (no). They called the fire department. Awkward conversation, $600 false-alarm fee.

None of these events were catastrophic. Together, in the first month of the new president’s term, they cost the strata about $3,500 and a real hit to the board’s confidence. All of them would have been avoided by three specific write-ups the outgoing president had in her head and never wrote down.

She wasn’t at fault. She’d been meaning to write them for years. Nobody had made it easy.

What a procedure is (and what it’s not)

A procedure is not a policy. A procedure is not the bylaws. A procedure is not the AGM package. A procedure is a specific, sequenced, step-by-step write-up of “how this building does this one recurring or emergency task.”

Good procedures are:

• Short. Under 500 words for a routine one; under 1,000 for a complex one. If it’s longer, split it.
• Written to be followed at 3 AM by a stranger. Not a summary the board can nod at. Actual steps a new board member with a flashlight could execute.
• Attached to the equipment or the situation. The boiler startup procedure lives on the boiler’s page. The lobby-door failure procedure lives on the lobby-door page. Nobody has to know where to look.
• Photos and diagrams where it matters. A photo of the specific valve to turn is worth 200 words.
• Dated and versioned. So the current board knows the last revision year and can flag anything that’s out of date.

Good procedures are not:

• Aspirational. “The board should aim to inspect the roof twice annually” is a policy, not a procedure.
• General. “How to respond to emergencies” as a single document is useless. “How to respond to a burst pipe on floor 3” is a procedure.
• Legal boilerplate. Bylaws are for governance. Procedures are for operations.

The procedures every small building should have

Not everything needs a written procedure. Most one-off tasks don’t; the manuals cover routine equipment operation. What benefits most from procedures is the intersection of “recurring” and “board- specific” — the things this particular building does in a specific way that isn’t obvious from the manual.

A starter list for most small buildings:

• Boiler startup and reset. After a power loss, after a seasonal shutoff, after a fault code. Includes the specific sequence and what to look for.
• Elevator entrapment. Who to call first (elevator company before fire department in most jurisdictions), what to tell the trapped resident, how to open the outer door if instructed.
• Fire panel event. Trouble, supervisory, and alarm — three different responses. What each looks like, who to call.
• Burst pipe. Where the main shutoff is (with a photo). Who to call. How to check for damage in the unit above and below.
• Roof access. How to access safely. Who has keys. When it’s appropriate (never in a storm).
• Lockout — resident locked out of unit. The board’s policy (do we help? use a specific locksmith?) plus the actual procedure.
• Annual fire prep. The pre-inspection checklist the building goes through so the actual inspection is a formality.
• AGM prep. The 8-week backward calendar that ends at a well-organized AGM packet. (More on this in a future post.)

Every one of these is a single-page write-up that saves a future board an emergency Google search.

How to build them without making it homework

The mistake most boards make is scheduling a “procedures day” — setting aside a full board meeting to write down eight documents at once. It never works. The board runs out of energy, the drafts are poor, and half of them get filed and never revisited.

The good version is the opposite: write procedures as they come up, in real time.

• After every incident, write the procedure. The elevator was down for two hours because you called the wrong company? Write the elevator-entrapment procedure that same week, before the memory fades. Fifteen minutes of writing prevents the next two-hour delay.
• Convert manuals into procedures for the specific building. The boiler manual has a startup procedure. Copy the steps that actually matter for your specific boiler, add the photos, drop the parts that don’t apply, save it.
• Have the outgoing board write one on their way out. Rotating presidents can write a procedure on the specific thing they handled most often. That’s the highest-leverage handoff possible.
• Let the manuals link out. Every procedure references the manuals it draws from, so someone reading the procedure at 3 AM can jump into the manual page for the underlying detail.

Six procedures written over six months is a real library. Twelve is transformative.

The hidden benefit

The board that writes procedures doesn’t just protect the next board. It also becomes better at its own job.

The process of writing a procedure forces you to think through the task step by step. Half the time you discover a gap — “wait, does anybody actually know what happens if we don’t get the backflow tested in time?” — that would have been a real problem if it had come up under time pressure.

Procedures also make it easier to delegate. A board member who’s never handled a specific task can pick up the procedure, follow it, and get a right result. Delegation stops being a training exercise and becomes just handing over a piece of paper.

Finally, procedures make hiring or working with vendors more predictable. When you can send a new plumber a one-page write-up of “how this building handles a burst pipe response,” the plumber gets useful in an hour, not a quarter.

Where BuildingHQ fits

The product has a first-class procedures surface (we sometimes call them runbooks internally, but users don’t need to know that). Each procedure is a Markdown document with steps, attached photos, and links to the equipment or manuals it references. Every procedure is deep-linkable — you can send a vendor the URL to “section 3 of the boiler-startup procedure” without giving them access to anything else.

Procedures show up next to the manuals in the library, and each is searchable from every screen. When a board member is standing in front of the fire panel at 11pm, “fire panel supervisory” as a search returns the procedure in one keystroke.

If your board is one turnover away from starting over, start writing one procedure a month. Sign up free; six procedures at the end of six months is more than most self- managed buildings ever have.

Next year’s board will thank you. So will this year’s, the next time the boiler resets on a Sunday.