How Change Orders Turn an $80k HOA Project Into $110k

The $80k roof project that quietly became $110k

The board approved an $80,000 roof replacement in March. By August the final invoice reads $112,400, and nobody in the room can cleanly explain the extra $32,400. That is not fraud. That is six change orders, each signed on its own day, each individually reasonable, none of them ever laid back against the original scope or the dollar figure the board actually voted on.

This is the most common way capital project budgets blow up in community associations. The roof got there through decking that was 'worse than expected' ($8,200), a code upgrade the inspector required ($6,400), an added drip edge 'while we're up here' ($3,100), a substituted membrane ($5,800), extra dumpster hauls ($2,900), and a rush-labor premium after weather delays ($6,000). Every one landed as a separate email approval to a busy manager.

What a change order actually contains, and what it hides

A clean change order tells you three things: what changed, why, and how the price moves. The dangerous ones blur all three. 'Additional labor and materials for unforeseen conditions, $6,000' is not a change order you can defend to an owner. It has no unit basis, no comparison to the original contract line, and no note on whether the base bid already accounted for reasonable contingency.

Two categories hide inside that vagueness. The first is genuine unforeseen work: rotted decking you could not see until the old roof came off. The second is scope creep: additions that were foreseeable, or that the base bid arguably already covered, dressed up as new. Telling those apart requires reading the original contract every single time. That is the tedious step almost nobody does under deadline pressure.

Why scope creep goes unnoticed until the final invoice

Creep hides because the original contract and the change orders live in different places, arrive at different times, and get approved by a person who is doing eleven other things. The manager who reviewed the base bid in March is not holding its scope schedule in memory in August when change order five arrives by text asking for a same-day yes so the crew doesn't demobilize.

The vendor is not usually the villain here. The incentive structure just quietly favors them. Nobody is doing the boring arithmetic of running total versus authorized amount, so each addition feels small against the whole project, and 'we're already committed' pressure makes 'no' expensive. By the time anyone sums the change orders, the money is spent and the work is installed.

The guardrail: check every change against scope and authority

This is a checking task, not a judgment task, which is exactly why it belongs to an agent. A manager should not spend forty minutes re-reading a March contract to evaluate a Tuesday change order, but somebody has to, or the guardrail does not exist. The work is deterministic: compare the change order line against the contract scope, add it to the running total, hold that total against the authorized ceiling, and surface anything that doesn't reconcile.

At One Home Agent this is the pattern Victor Vendors handles: not signing anything, not negotiating anything, just doing the cross-check a human keeps skipping under pressure and flagging the two questions that matter before a signature happens. The manager still makes every call. The agent just makes sure the call is informed.

How the agent maps each change to scope and budget authority

1. 01

   Anchor the two references at contract signing

   When the base contract is executed, the agent captures the scope schedule and the board's approved dollar authorization (the exact figure and date from the minutes). These become the two fixed points every future change order is measured against.

2. 02

   Parse each incoming change order

   For every change order, the agent extracts what changed, the stated reason, and the dollar delta. Vague line items like 'additional materials, $6,000' get flagged as underspecified before they reach the manager, not after.

3. 03

   Test it against original scope

   The agent checks whether the change describes genuinely new work or something the base contract arguably already covered. 'Add drip edge' on a roof where the base scope included flashing and edge detail gets flagged as a possible double-charge, with the contract line quoted.

4. 04

   Update the running total against authority

   Each approved change adds to a running project total. The agent holds that total against the board's authorized ceiling and reports the gap: 'Approved authority $80,000. Committed to date $91,600. This change order would put you 14.5% over.'

5. 05

   Surface the decision, not the answer

   The agent hands the manager a one-screen summary: what's new, what may be creep, running total, and whether the ceiling is now breached. The manager negotiates, approves, or escalates. The agent never signs.

What triggers a required board re-vote

A re-vote is required when the running total exceeds the board's authorized amount, or when a change materially alters the scope the board approved, not when the manager feels nervous. Boards authorize a specific dollar figure and a specific scope. Once cumulative change orders push past that figure, the manager is spending money the board did not vote to spend, which is a governance problem, not just a budget one.

The uncomfortable part: a re-vote slows the job, and slowing the job costs real money and real annoyance. Some boards would rather ratify after the fact than pause a crew. That is a legitimate choice, but it should be a choice the board makes with the numbers in front of them, not a default that happens because nobody did the arithmetic in time. The guardrail's job is to make sure the ceiling breach is visible before the signature, not discovered at the final invoice.

The manager still owns the negotiation

“The agent should never negotiate a change order and never sign one. Its entire job is to hand the manager the two facts they don't have time to dig up: is this actually new work, and are we now over what the board voted to spend. The relationship with the contractor, the judgment call, the pushback, that stays human. We're removing the arithmetic, not the authority.”

Todd Paton, Partner, One Home Agent

This is where the line matters. Negotiating with a roofer who has a crew on the roof is a relationship and leverage exercise, and it belongs to the manager who knows that vendor. Deciding whether an $8,200 decking find is fair, or whether to eat a delay premium to keep the schedule, is judgment. None of that automates.

What automates is the part that makes the negotiation possible: walking in already knowing the base scope excluded decking, that the running total is now 14.5% over authority, and that two other line items look like double-charges. A manager armed with that has leverage. A manager approving by text at 4:47pm has none.

Put a guardrail desk on your next capital project