Author: Di Tran

A budget answers, “What capacity may exist?” Approval answers, “What exact work did an authorized person agree to?” Confusing the two is one of the fastest ways to damage a project, a vendor relationship, and the truth of the ledger.

This distinction matters in construction, technology, marketing, equipment repair, professional services, and almost every project where real conditions can change. A contingency, allowance, reserve, or unspent budget is not automatically money owed. It is controlled capacity that may support a documented decision.

The operator’s rule

No extra work should become an approved extra merely because it seems useful, the budget can absorb it, or someone already started. Before work begins—except for minimum emergency stabilization—reconcile eight things in writing:

1. Trigger: What new condition, owner request, code issue, design conflict, or discovery caused the proposed change?
2. Original scope: What did the signed agreement already include?
3. Evidence: What photos, measurements, inspection notes, drawings, or records show the condition?
4. Revised scope: What exact labor, material, equipment, subcontractor work, and result are now proposed?
5. Credits: What original work, allowance, material, or labor will no longer be required?
6. Price: What are the quantities, rates, markup, taxes, and not-to-exceed total?
7. Time: What changes in schedule, access, inspection, occupancy, or downstream work?
8. Authority: Who may approve it, and where is the dated written approval?

A strong change record makes it possible to say yes quickly when the evidence is complete. It also makes a respectful no—or a request for missing information—less personal.

Why written scope protects both sides

The U.S. Small Business Administration’s government-contracting guidance illustrates a broader operating principle: specifications matter, inspections test the promised result, changes can affect price and schedule, and the contract governs how disagreements are handled. Private contracts differ, but the discipline of identifying the change and its consequences remains valuable.

Written control protects the owner from surprise charges and duplicate scope. It protects the vendor from doing requested work and later facing a memory dispute. It protects the project team from using the same contingency twice. Most importantly, it creates a record that a future reviewer can understand without reconstructing the story from text messages.

The three-ledger method

Keep three numbers visibly separate:

• Base contract: the approved original scope and price.
• Approved changes: executed changes that modify scope, price, or time.
• Unapproved requests: proposed or disputed items still awaiting evidence and authority.

Do not add an unapproved request to the amount due. Do not erase it either. Hold it with a clear status and next requirement.

Payment proof is not scope proof

The IRS explains that business records may need supporting documents such as invoices, receipts, paid bills, deposit records, and canceled checks. Those records can prove that money moved. They do not by themselves prove that a new scope was approved, that the work was complete, or that a charge was not already included elsewhere.

For each payment, preserve the payee, date, amount, project, approved scope reference, milestone, proof of receipt, and remaining balance. Keep proposed, approved, invoiced, paid, and finally accepted amounts separate.

A one-page change-control template

Change title and date
Condition or request that triggered the change
Original contract section and included allowance
Evidence reviewed
Revised work and exclusions
Deleted-work or allowance credits
Itemized price and not-to-exceed total
Schedule and inspection effect
Minimum emergency stabilization, if any
Approval authority, signature/date, and stop point

If a true emergency threatens people, property, or an active system, authorize only the minimum stabilization that the contract and circumstances permit. Document the condition immediately. Stabilization is not blanket approval for the entire permanent repair or any later price.

A hypothetical example

A project has a $15,000 contingency. A vendor discovers a condition and proposes $9,000 of additional work. The existence of the contingency does not approve the $9,000. The team still needs to determine what the base scope included, which work is genuinely additional, what original work should be credited, what evidence supports the quantities and price, who has authority, and what happens to the schedule.

If the validated net change is $4,500 and the authorized owner approves it in writing, then—and only then—does the approved-change ledger rise by $4,500. The remaining contingency is a separate management figure, not an invitation to spend.

Operator dignity

Good control is not hostility. It is respect made visible: respect for the owner’s money, the vendor’s labor, the project’s quality, and the future relationship. The best system makes accurate work easier to approve and incomplete work easier to repair.

Sources

• U.S. Small Business Administration — Governing Rules and Responsibilities
• IRS — What Kind of Records Should I Keep?

This is an operational education framework, not legal, accounting, tax, engineering, architectural, construction-management, or contract advice. The signed agreement, applicable law, licensed professionals, insurers, lenders, and counsel may control a specific project.