Contingency draws without backup: flag them, do not block them
Most contingency draws arrive thin. A line on the pay application, a sentence in the contractor's monthly narrative, sometimes an email. The invoice, the subcontractor change request, the photo of the condition, all of that tends to follow weeks later, if the owner asks.
The owner has two ways to handle this. Refuse to recognize the draw until the backup shows up, or record the draw with a flag that says the backup is missing. The second is almost always better, and the reason is about what each approach does to the project.
Why blocking costs more than it saves
Under most AIA A133 based agreements the contractor has a right to draw its own contingency with notice, and the owner's approval is limited to certain cases. Refusing to acknowledge a draw that the contract permits puts the owner on the wrong side of the agreement. Check your contract, but in most cases the owner's remedy is review, not veto.
Even where the owner has a consent right, withholding it over missing paperwork tends to stall the field. The subcontractor who did the rework still expects to be paid. The contractor starts holding work until the draw is cleared. The owner gets the backup eventually, and also gets a delay claim.
The owner's real interest is not in stopping the draw. It is in making sure the draw is properly classified, properly sized, and properly supported before closeout. None of that requires stopping it today.
What a flag does that a block does not
A flag is a record. It says: on this date, this draw was entered, with this stated cause, and the following documents were not provided. The draw is recognized in the owner's ledger. The gap is visible next to it. Nothing about the pay application changes.
The flag persists until someone closes it. That means the missing invoice is still missing in month nine if it was missing in month four, and the monthly report says so. A contractor who knows the owner keeps an open flag list will usually clear it, because the list goes to the board and the lender.
At closeout the flag list becomes the audit agenda. Every draw still flagged is a draw the owner can ask to see substantiated under its audit rights. Draws that were blocked and then argued about in the field leave no such trail.
A fictional illustration
On a fictional $22 million recreation center, the owner's representative flagged nineteen contingency draws over the project for missing backup. Fourteen were cleared within two pay cycles once the contractor saw the list in the monthly report. Three were cleared at closeout. Two were reclassified after review, because the backup showed the cause was a design gap rather than a coordination miss. None of them delayed the work.
What counts as backup
The standard varies by draw size and cause. For a small coordination draw, a subcontractor change request and a short description is often enough. For a large draw citing unforeseen conditions, the owner should expect photos, a field report, the relevant drawing sheet, and the subcontractor's pricing.
The owner's record should say what was expected and what was received, not just yes or no. A draw with a subcontractor quote but no field report is better supported than one with a sentence, and the flag should reflect that. Partial backup is a partial flag.
Running the flag list
The flag list should be short enough to read and old enough to matter. Sort it by age. A flag from last month is a reminder. A flag from six months ago is a question the contractor has been avoiding. Both belong in the report, with the age shown.
Costwitness attaches a backup status to every contingency draw and carries unresolved flags forward month to month until a document is linked. The software keeps the list. Deciding whether a document is good enough remains a judgment the owner's team makes.
What to do this month
- Go through the contingency draws on the last pay application and mark each as supported, partially supported, or not supported.
- Write down, for each cause category, what backup the owner expects to see.
- Add an open flag list, sorted by age, to the monthly owner report and send it to the contractor before the report goes out.
Questions on this
Does flagging a draw mean the owner has accepted it?
No. Recording a draw in the owner's ledger means the owner knows it happened. The flag records that the owner's review is not complete. The owner's right to dispute the cause or the amount later stays intact, and the flag is the evidence that the question was raised.
What if the contractor never provides backup?
Then the flag stays open to closeout, and the owner raises it under its audit rights. Under most AIA A133 based agreements the owner can review the contractor's records for costs charged to the work. A draw with no backup at audit is the contractor's problem to explain. Check your contract for the audit clause.
Should owner contingency draws be flagged the same way?
Owner contingency draws are change orders, so they should not be signed without backup in the first place. The flag approach is for the contractor's fund, where the owner is reviewing rather than approving.
In the product
Contingency ledger, Monthly owner report, Change order register. Free tool: Pre-GMP Readiness Score, Contingency Runway.
Keep reading
Earlier: Owner contingency inside or outside the GMP: what the choice changes. Later: What happens when the contractor's contingency runs out. All articles on contingency.
See the two funds on a project like yours.
Thirty minutes on a call. The twin drawdown chart on a fictional project at your GMP size, and the month the fund runs out.