5 Signs Your Building's Project Documentation Will Fail an Audit

The audit nobody is ready for

Most building boards do not think about documentation audits until they are in one. It might be a financial audit triggered by a reserve study discrepancy. A dispute with a contractor that escalates to arbitration. A resident lawsuit challenging a special assessment. An insurance claim after project-related damage. Or a regulatory review prompted by a complaint.

In every case, the board is asked to produce a complete record of decisions, approvals, expenditures, and communications related to one or more capital projects. And in most cases, what they can produce falls far short of what is required.

A 2023 review by a large community association auditing firm found that 72% of buildings could not produce complete project documentation when requested during financial audits. The deficiencies were not dramatic — no one was hiding records. The records simply did not exist in a retrievable form, because no one had maintained them as an organized system.

Here are five warning signs that your building's project documentation would fail an audit — and what to do about each one.

Sign 1: Your decision record lives in meeting minutes alone

Meeting minutes are necessary but insufficient as a decision record. They capture that a vote occurred and typically record the outcome: "Motion to approve the roofing contract with ABC Roofing for $180,000 — approved 4-1."

What minutes rarely capture is the decision context — the discussion that preceded the vote, the alternatives considered, the conditions attached to the approval, and the specific scope of work being authorized. When an auditor or attorney needs to understand why the board chose Contractor A over Contractor B, or what specific work was included in the $180,000 approval, meeting minutes alone cannot answer those questions.

The fix

Maintain a separate decision log for capital projects that records not just the outcome but the rationale. For each significant decision, document:

• What was decided and the specific motion language
• What alternatives were considered and why they were rejected
• Any conditions or contingencies attached to the approval
• The supporting documents reviewed (bids, proposals, engineering reports)
• The vote count and any dissenting positions

This does not need to be elaborate. A simple log entry of three to five sentences per decision, linked to the relevant supporting documents, transforms your record from "we voted yes" to a defensible account of prudent governance.

Sign 2: You cannot produce a complete financial trail for any project over $50,000

An auditable financial trail for a capital project means you can trace every dollar from budget approval through vendor payment. Pull the records for your most recent major project and attempt this exercise:

Start with the original budget approval. Can you produce the board resolution or vote authorizing the expenditure? Can you produce the contract or proposal that established the price? For every payment made, can you match the payment to a specific invoice, and that invoice to approved work under the contract? For every change order, can you produce the board approval, the contractor's written request, and the cost documentation?

If any link in this chain is missing — if there are payments that do not match invoices, invoices that do not match approved scope, or change orders approved verbally but never documented — your financial trail has gaps that an auditor will flag.

The fix

Implement a project-level financial tracker before work begins, not after. For each project:

• Record the original approved budget with the authorizing vote
• Log every contract and amendment with board approval dates
• Match every invoice to specific contract line items or approved change orders
• Record every payment with the date, amount, check number or wire reference, and the invoice it satisfies
• Document any budget variances with explanations and board acknowledgment

The overhead of maintaining this record in real time is minimal — perhaps fifteen minutes per week on an active project. Reconstructing it after the fact, when an auditor requests it, takes days or weeks and invariably contains gaps that could have been prevented.

Sign 3: Key communications exist only in personal email accounts

This is the most common and most dangerous documentation gap. An auditor asks for the board's communication with the contractor regarding a disputed change order. The board president searches her email and finds part of the thread. The property manager searches his email and finds a different part. A former board member who managed the project day-to-day has moved to another state and is not returning calls.

The communications exist — scattered, incomplete, and practically irretrievable in any coherent form.

This problem is structural, not behavioral. Email was not designed for institutional record-keeping. When board members use personal email for project communications, the building's records are only as complete as the least organized board member's inbox. And when that board member leaves, the records leave with them.

The fix

Establish a project communication protocol at the start of every capital project. The protocol should specify:

A designated communication channel. All substantive communications with vendors, architects, engineers, and attorneys on the project should flow through a centralized system — not personal email accounts. Board members can still use email for individual communication, but project-related exchanges should be copied to or conducted through the central record.

What constitutes a substantive communication. Not every email needs archiving. Define categories that do: scope changes, schedule modifications, payment discussions, deficiency reports, and any instruction or approval given to a contractor.

Retention requirements. Project communications should be retained for at least the statute of limitations period in your jurisdiction — typically six to ten years for construction-related claims. If your records live in personal email accounts, you have no control over retention.

BoardRecord addresses this directly by providing a centralized project communication record that does not depend on any individual board member's email account. When a board member rotates off, the project record remains intact and accessible to their successor.

Sign 4: Document versions are uncontrolled

A building's engineering consultant submits a facade inspection report. The board discusses it and requests revisions. The consultant sends a revised report. The contractor's bid is based on the original report, not the revision. Six months into the project, a scope dispute arises because the contractor and the board are literally working from different documents.

This is a version control failure, and it is remarkably common in building board projects. Drawings get revised without clear notation. Specifications are updated in email attachments without version numbers. Contract amendments reference "the original scope" without attaching it.

An auditor reviewing your project documentation will look for document version control — evidence that the board knew which version of each document was current and that decisions were based on the correct version. If your document repository is a folder of files named "facade report," "facade report revised," "facade report FINAL," and "facade report FINAL v2," you have a version control problem.

The fix

Adopt a simple version control discipline for every project document:

• Name files with version numbers and dates. "2025-03-15 Facade Report v2.0" is unambiguous. "Facade Report revised" is not.
• Maintain a document register. A simple table listing every project document, its current version, the date of the most recent revision, and who issued it. When a new version is issued, update the register and note what changed.
• Archive superseded versions. Do not delete old versions — move them to an archive folder. The history of document revisions can be critical in a dispute. An auditor may need to see what the board was working from at a specific point in time.
• Confirm the working version in writing. When revised documents are issued, send a brief confirmation to all project participants: "The attached drawings (v3.0, dated April 2) supersede all previous versions and are now the basis for the project scope." This takes thirty seconds and eliminates ambiguity.

Sign 5: No one on the current board knows where the records are

Board turnover is natural and healthy. But when the board member who managed a two-year capital project finishes their term, the institutional knowledge of that project — where the documents are stored, how the contractor was selected, what disputes arose and how they were resolved — often leaves with them.

The warning sign is simple: ask your current board where the complete records for your last capital project are stored. If the answer involves phrases like "I think the former president has them," "they should be on the property manager's computer," or "we would need to ask the management company," your documentation has a continuity problem.

The fix

Create a project handoff protocol that is executed whenever a board member who managed a capital project completes their term:

• Centralize all project records in a location accessible to the full board, not in any individual's personal storage.
• Create a project summary memo that describes the project scope, timeline, key decisions, current status, outstanding issues, and the location of all project documents. This should be a two-to-three page document that gives an incoming board member enough context to manage ongoing work or respond to future inquiries.
• Transfer vendor relationships. The incoming board or property manager should be formally introduced to active project vendors with a clear statement of who the new point of contact is.
• Update access credentials. If any project-related accounts, portals, or systems require individual login credentials, update them during the transition.

BoardRecord was designed with board transitions in mind — maintaining a permanent, board-accessible project record that does not depend on any individual member's tenure. When the next audit arrives, the records are where they should be: organized, complete, and accessible to whoever is currently serving on the board.

The audit is not the point

The purpose of good project documentation is not to survive an audit, although it accomplishes that. The purpose is to give the board the information it needs to manage projects effectively, make defensible decisions, and protect the building's financial interests.

A board that maintains complete project documentation spends less time in disputes, negotiates better contracts, makes faster decisions, and provides more transparent governance to the residents it serves. The audit readiness is a side effect of good practice — not the goal itself.

Review your current project documentation against these five warning signs. For every sign that applies, implement the corresponding fix before your next capital project begins. The cost of prevention is measured in hours. The cost of remediation — after the audit notice arrives — is measured in dollars, legal fees, and board credibility.