Building Board Compliance Files That Hold Up

The owner says they never received the letter. Another director is certain it was sent. The photo is somewhere in a personal mobile phone, the draft notice is in an old Word file, and the spreadsheet says only: “follow up”. That is the point at which building board compliance files becomes more than an administrative task. Your corporation needs a record that lets the board answer calmly, with dates, documents and a clear sequence.

Start with the notice itself. The following is general wording a board can adapt to its declaration, rules and the facts at hand.

> Subject: Compliance request for [unit number] > > Dear [unit owner name], > > The corporation has observed [brief factual description of the concern] at or relating to your unit on [date and time]. The supporting record includes [photograph, inspection note or other record]. > > The corporation requests that this matter be corrected by [date]. This request is made with reference to [the relevant declaration provision, rule or by-law]. Depending on the circumstances, the corporation may also rely on sections 117 and 119 of the Condominium Act, 1998. > > Please provide any response or relevant information by [date]. If the matter is not resolved, the board will review the record and consider its next steps under the declaration and applicable law. Where permitted by the declaration's indemnification provisions, the corporation may seek recovery of reasonable related costs. > > Sincerely, > > [Name], for the board of directors

That letter is not a substitute for legal advice, and it should not be sent as a formality. Its value comes from the file behind it: what was observed, what rule applies, when the owner was notified, and what happened next.

What belongs in a board compliance file

A useful file is not a pile of correspondence. It is a chronological account that another director can understand without relying on memory. If a secretary resigns, a new director joins, or a CAT Notice of Case arrives, the corporation should not have to reconstruct the story from several inboxes.

Begin with the source document. Save the relevant declaration provision, rule or by-law, with the version and effective date. A rule that was amended after an incident is not necessarily the rule that applied at the time. Keep the board's authority clear as well. Section 17(3) of the Condominium Act, 1998 requires directors and officers to act honestly and in good faith, exercising the care, diligence and skill that a reasonably prudent person would exercise in comparable circumstances. A careful record supports that discipline.

Then keep the factual evidence. This may include dated photographs, an inspection note, a complaint received by the corporation, correspondence, or a contractor's record. Label each item by incident date, not merely by upload date. If a photograph was taken on Tuesday but added to the folder two weeks later, both dates can matter.

The file should also show each communication step: the first compliance letter, the delivery method, proof or record of delivery, the owner's response, and any follow-up. Finally, include the board decision. A short minute or written decision should record what the board reviewed, the action approved, and the next review date. Section 55 governs records that owners may inspect, so the board should also consider record keeping and privacy while assembling the file.

Building board compliance files without selective enforcement gaps

Selective enforcement allegations often expose a process problem rather than one bad letter. The question is rarely just whether a particular owner was contacted. It is whether the corporation can show a consistent basis for acting.

Consistency does not mean every situation receives identical treatment. A repeated safety concern may justify a faster response than a first minor breach. An owner who promptly corrects an issue may need no further escalation. What matters is that the file records the reason for the difference.

Use the same basic intake questions each time: What was observed? When and where? Which provision may apply? What evidence exists? Has the owner been given an opportunity to respond? What is the next date the board will review the matter? This turns a director's good intentions into a repeatable process.

A simple compliance register can help the board see patterns across units, but it should point to the supporting file rather than replace it. A row reading “parking issue - closed” is not enough when the owner asks what was alleged, which notice was sent, or why the corporation considered the matter resolved.

Avoid writing conclusions into the evidence record. “Vehicle observed occupying visitor space at 8:10 pm” is a fact. “Owner deliberately ignored the rules” is an interpretation and may be unnecessary. Clear factual language makes the board's position easier to review and less likely to become personal.

The old folder system breaks at handover

Shared drives, spreadsheets, email and Word templates can work for a small corporation, until they do not. The usual weaknesses are mundane: photos remain on a director's mobile phone, an email is sent from a personal account, a template is overwritten, or an escalation date passes during a busy month.

The cost is not simply untidy administration. Directors lose evenings looking for material. The board may send a second letter without knowing the first was delivered. A departing treasurer may hold the only complete thread. If a dispute reaches the Condominium Authority Tribunal, the corporation may need to organise its evidence while responding to deadlines and filing stages that can total $200.

A better process separates four things that are often mixed together: evidence, communications, owner responses and board decisions. Each should be connected, but each should retain its own date and source. This makes it possible to see the record as the board saw it at the time, rather than as someone remembers it months later.

Set an escalation rhythm before the second notice

The first letter should not be the last planned action. At the time it is sent, set the review date and identify what would change the board's next step. For many matters, a 30-day review is enough. Others may need 60- or 90-day checks, particularly where correction takes time or the issue recurs.

At each review, record one of three outcomes in plain language: resolved, awaiting information, or escalation considered. If escalation is considered, identify why. The owner may not have responded; evidence may show the issue continues; or a response may raise a question requiring counsel's input.

Section 132 addresses rule enforcement, while section 134 provides a court enforcement route in appropriate circumstances. Those provisions do not remove the need for judgement. The declaration, the facts, the corporation's prior steps and legal advice where needed will govern. The board's job is to preserve a reliable account before anyone asks for it.

A practical file structure for volunteer boards

Use one reference number for every matter, such as 2026-014, and place it on the evidence, letters and board notes. Create a folder or record with the unit number, incident date, relevant provision and current status. Keep original evidence alongside a brief incident log, rather than pasting everything into a running email chain.

For each notice, record the final version sent, who authorised it, the delivery channel, the sent date and the delivery result. If the owner responds by mobile phone, make a dated note of what was said and any commitment made. Do not rely on a director's recollection at the next meeting.

YardRule is designed around this practical sequence for Ontario condominium corporations: GPS- and time-stamped photo capture, compliance-letter templates, delivery tracking, owner response records, escalation reminders, meeting packs and an append-only history that cannot be edited from inside the app. It is available at $49 per month for up to 25 units, or $99 per month for up to 100 units. Boards can use the full product for 30 days without a card, and if they stop paying, their record remains readable and exportable.

The software does not decide whether a breach occurred or what legal step to take. It keeps the record, so the board can make those decisions with the relevant material in front of it.

Before your next compliance letter goes out, ask one practical question: could a director who was not involved explain this file from beginning to end? If the answer is no, start with the incident date, the applicable provision and the delivery record. That small discipline is often what makes the better file.

This article and its sample wording are general information, not legal advice. Your corporation's declaration and counsel govern. For related practical material, consult YardRule's Ontario condominium compliance guides.