How Condo Boards Lose Control of Renovation Projects — And How to Fix It
Most condo and co-op boards manage renovation projects through scattered email threads, losing critical decisions and context along the way. Here is a practical framework for maintaining a complete project record from first bid to final sign-off.
The $50,000 email thread
A condo board in Brooklyn approved a $1.2 million facade restoration. Eighteen months later, the project was $340,000 over budget and three months behind schedule. When the board tried to hold the contractor accountable, they discovered the critical change orders had been approved in a chain of emails between the property manager and one board member — emails the rest of the board had never seen.
This is not unusual. It is the norm.
Most building boards manage renovation projects — often the largest expenditures their residents will ever share — through a combination of personal email accounts, group threads, text messages, and occasional PDF attachments. The result is a decision record that exists in fragments, spread across multiple inboxes, with no single source of truth.
Why email fails as a project record
Email was designed for communication, not record-keeping. When a board uses email to manage a renovation, several things break down simultaneously:
Decisions lose their context. A board votes to approve a contractor's bid at $180,000. Three months later, the contractor submits an invoice for $215,000 citing "approved scope changes." The approval happened in a reply buried in a 47-message thread — and the board member who approved it has since rotated off. Good luck finding it.
Attachments become orphans. The architect sends revised drawings. The property manager forwards them. A board member replies with comments. The contractor responds to the original email instead of the forwarded one. Now there are two parallel threads with different versions of the drawings, and no one is sure which set was actually approved.
Vendor communications are invisible. The property manager exchanges 200+ emails with the contractor over six months. The board sees summaries at monthly meetings. When a dispute arises about what was communicated, the board has no access to the actual correspondence.
Institutional memory walks out the door. When a board member's term ends or a property manager changes, every email, every attachment, every decision in their personal inbox goes with them. The incoming replacement starts from zero.
What a complete project record actually looks like
The solution is not another project management tool that requires everyone to learn new software. Board members are volunteers. Contractors and architects communicate by email. The solution has to work with email, not replace it.
A complete project record should provide:
1. A single, chronological timeline
Every email, attachment, note, and decision related to a project should appear in one time-ordered stream. Not organized by who sent it or which inbox it landed in — organized by when it happened. This is the ground truth that makes everything else possible.
2. Full vendor correspondence visibility
Every email exchanged between the property manager and project vendors should be captured automatically, without requiring the manager to forward or CC anyone. The board should be able to see the complete communication history at any time — not just what the manager chooses to share at meetings.
3. Document version control
When an architect sends revision 3 of the specification drawings, the record should show revisions 1 and 2 alongside it. When a contractor's proposal is amended, both the original and the amendment should be preserved with clear attribution of who requested the change and when.
4. Decision attribution
Every approval, rejection, or directive should be linked to the person who made it and the context in which it was made. "The board approved this" is not sufficient. The record should show which members voted, what information was available at the time, and what conditions were attached.
5. Transition resilience
When a board member rotates off or a management company changes, the project record should transfer completely and automatically. No requesting files from predecessors. No lost email archives. No reconstructing history from memory.
The cost of not having this
The financial impact of poor project records is concrete and measurable:
- Change order disputes typically represent 10–25% of total project cost on building renovations. Without a clear record of what was approved and when, boards have no leverage.
- Management company transitions frequently result in 3–6 months of lost context, during which active projects stall or regress.
- Legal disputes over building projects cost an average of $15,000–$50,000 in legal fees alone — often more than the original dispute amount — because both sides must reconstruct the decision trail from incomplete records.
- Duplicate work occurs when boards re-solicit bids, re-negotiate terms, or re-approve decisions because no one can locate the original documentation.
A practical framework for your next project
Whether or not you adopt dedicated software, these principles will improve your board's project oversight:
1. Establish a project-specific email alias. Create an email address like facade-restoration@yourbuilding.com that captures all project-related correspondence. This creates a single collection point even if you are managing everything manually.
2. Require written confirmation of all decisions. Verbal approvals at board meetings should be followed by a written summary email to the project alias. "The board voted 4–1 to approve the contractor's change order for $28,000 on [date]. Board member [name] dissented citing [reason]."
3. Maintain a version log for all documents. When the architect sends updated drawings, note the version number, date received, and what changed. When the contractor submits a revised proposal, preserve the original alongside the revision.
4. Create monthly project summaries. Even a brief written summary of project status, recent decisions, and outstanding items provides a checkpoint that future board members can reference. Send it to the project alias so it becomes part of the permanent record.
5. Plan for transitions from day one. Document your project filing system so that when board members change or the management company transitions, the incoming team can find everything without asking their predecessors.
Moving from framework to infrastructure
These practices work — but they rely on discipline and manual effort. Every board starts a renovation with the best intentions about record-keeping. By month six, when the project is complex and the emails are flowing, the discipline erodes.
This is why we built BoardRecord. It is not a project management tool that asks volunteers to learn new workflows. It is infrastructure that sits underneath the email your board already uses, automatically creating the chronological, searchable, complete project record that every building renovation deserves.
Your board members keep using their existing email. Your property manager keeps communicating with vendors the way they always have. BoardRecord captures, organizes, and preserves every communication automatically — so when the dispute arises, the audit happens, or the board changes, the record is already there.
BoardRecord is email-native project management with AI search for condo, co-op, and HOA boards. Start a free pilot to see how it works with your building's projects.