Moving a draw between funds: why every reclassification needs an audit trail
Classifications change. A draw entered as coordination in month five turns out, when the backup arrives in month seven, to be a design gap. Under many contracts that moves it from the contractor's fund to the owner's, and possibly onward to a claim against the design team. The move is legitimate. What is not legitimate is a move that leaves no trace.
An audit trail is the difference between a corrected record and a rewritten one. The corrected record shows the original entry, the change, and the reason. The rewritten record shows only the new state, and nobody can tell it was ever different.
What a reclassification actually does
Every reclassification moves money between parties. Contractor contingency to owner contingency raises the owner's cost and restores the contractor's fund. Owner contingency to contractor contingency does the reverse. Contingency to change order moves a cost from inside the GMP to a request that raises the contract sum. Change order to contingency absorbs a cost the owner was about to pay.
Because the move changes who pays, it changes the anticipated final cost, the shared savings pool, and the exhaustion date of each fund in one step. A reclassification in the last month of a project can change the closeout arithmetic by more than any single draw did during the job.
None of that makes reclassification wrong. Most moves are corrections as information improves. The problem is a move that cannot be seen afterward, because then the owner cannot distinguish a correction from a late adjustment made for someone's benefit.
What the trail should hold
Each reclassification should record the entry that moved, the fund and cause before, the fund and cause after, the date of the move, who made it, and the reason in one or two sentences with a link to the document that prompted it. The original entry stays visible. The new classification is an addition, not a replacement.
The reason field is the one that earns its keep. A move from coordination to design gap with the reason noting the RFI response that revealed the drawing conflict is a move the owner can defend to the architect's carrier two years later. The same move with no reason is an assertion.
Consider a fictional $40 million courthouse renovation where the owner's ledger recorded fourteen reclassifications over the project. Eleven moved draws from contractor contingency to design gap on the strength of RFI responses. At closeout the owner presented those eleven entries, each with its trail, to the design team. The conversation was about the facts, not about whether the owner had changed its story.
Who can make the move
On the contractor's side, reclassifications in the contractor's own log are the contractor's business. On the owner's side, the owner's ledger should have a small number of people who can change a classification and a record of which of them did. An owner's representative may propose. The owner's project lead may approve. Nobody should be able to do it without the change being logged under their name.
The contract may also speak to reclassification. Under most AIA A133 based agreements the owner's approval is required for changes to the contract sum, and a move from contingency to change order is such a change. A move between funds inside the GMP may need only notice. Check your contract for the line between the two.
The late move pattern
Watch for reclassifications that cluster in the last three pay applications. Some are genuine cleanup. Some are an attempt to shape the closeout balance. The owner cannot tell which from the move alone, but a trail that shows the original classification stood unchallenged for ten months makes the question easier to ask.
Keeping the history instead of the state
A spreadsheet keeps state. Change a cell and the old value is gone. A ledger keeps history. Change a classification and the old one stays, with the new one stacked on top. The report shows the current state. The audit shows everything.
Costwitness keeps every classification change as a dated entry with a before, an after, an author, and a reason, and shows reclassification counts by month so that late clusters are visible. The software keeps the trail. Whether a move was right is a question for the people who made it.
What to do this month
- Check whether your current contingency log keeps the prior classification when one is changed, and if it does not, add a change history column or sheet.
- List every reclassification made to date with its reason, and fill in any that have none while the people involved still remember.
- Agree who on the owner's side can change a classification and make sure their name is captured on each change.
Questions on this
Should the owner reclassify a draw without the contractor's agreement?
The owner's ledger records the owner's position, so the owner can classify a draw as it sees fit. What the owner cannot do unilaterally is change the contract sum. A disagreement should be recorded as a disagreement, with both classifications visible, until it is resolved or carried to closeout.
Does a reclassification change the pay application?
Only if the contractor restates the G703. A move inside the owner's ledger changes the owner's view and the anticipated final cost but not the certified amounts. A move that raises or lowers the contract sum needs a change order, and that does show on the next pay application.
How far back should the audit trail go?
To the first entry. The value of a trail is that it is complete. A trail that starts in month eight leaves the first seven months open to exactly the question it was meant to close.
In the product
Contingency ledger, Change order register, GMP baseline. Free tool: Change Order Exposure, Shared Savings Calculator.
Keep reading
Earlier: Where contingency hides in the pay application. Later: A monthly contingency routine for owners in four steps. 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.