The draw request is the most consequential document an owner receives during a custom build, and it is the document owners spend the least time reading carefully. By the third or fourth draw, most owners have stopped reconciling against the source invoices. By the eighth, they are signing on summary alone.
This is not laziness. The format of a typical draw request is not designed for owner review. It is designed for owner approval. The two are different.
What follows is a practical guide to reading a draw request the way someone competent in financial governance would read it. None of it requires construction expertise. All of it requires about thirty minutes per draw.
What a Draw Actually Is
A draw is a periodic billing from the contractor to the owner, covering costs incurred during a defined period. On a cost-plus project, a draw includes the actual costs of the work performed during that period, plus the contractor's management fee on those costs, less holdback retained, less any prior overpayments or credits.
The draw is not an invoice in the conventional sense. An invoice represents a fixed amount owed for a defined deliverable. A draw represents a running settlement against an evolving total. The same project will receive twenty or thirty draws across its lifecycle, each of which must reconcile against the project's actual costs and against every prior draw.
The reconciliation is what separates a clean draw from a problem draw. Most issues that surface in late-project audits are reconciliation errors that were present in the draws all along, but were never tested.
The Anatomy of a Clean Draw
A properly assembled draw package contains, at minimum, the following components:
| Component | Function |
|---|---|
| Cover Summary | Period covered, costs incurred, fee applied, holdback retained, prior payments, balance due. One page. |
| Invoice Register | Line-item list of every vendor invoice, with vendor, invoice number, date, amount, and obligation tie-in. |
| Source Invoices | Copies of every vendor invoice referenced. Without source documents, the register cannot be verified. |
| Holdback Calculation | Per-vendor holdback held this period, accumulated to date, releases occurring with statutory dates. |
| Tax Breakdown | Tax applied at correct jurisdictional rate, with cross-provincial trades flagged separately. |
| Signature Block | Contractor's certification that the draw is accurate, with date and signatory. |
If a draw arrives without the invoice register or without access to source invoices, it is not yet ready for review. It is ready for return. An owner has the right to receive the documentation that allows verification. Contractors operating with proper financial architecture expect to provide it. Contractors who are reluctant are the contractors whose books most need to be tested.
Five Verification Points
1. Source Invoice Match
Pick three to five line items from the draw's invoice register at random. Pull the corresponding source invoices. Verify that the vendor name, invoice number, invoice date, and pre-tax amount match exactly. Check that the invoice is addressed to the project and not to another job.
What failure looks like: the register shows an amount that does not match the source invoice. The invoice is addressed to a different project. The invoice number on the register does not appear on any document the contractor can produce. Any of these is a flag worth pausing the draw to resolve.
2. The Deposit-Deduction Trap
For any vendor with a substantial fixed-price contract - railings, cabinetry, countertops, custom millwork, structural steel - check whether a deposit was paid earlier in the project. If yes, when the final invoice for that vendor appears in a later draw, verify that the deposit has been deducted from the final billing.
What failure looks like: the vendor issues a final invoice for the full contract value. The contractor processes the invoice without checking whether the deposit was already paid. The owner is billed the same dollars twice, eighteen months apart, and nobody catches it because the two payments live in different draws.
"The deposit-deduction error is one of the most common reconciliation failures we see. It is almost never deliberate. It happens because accounts payable processes the final invoice as a standalone document - not as the final entry in a multi-payment sequence."
3. Holdback Calculation
Confirm the holdback rate matches the project's jurisdiction. In Quebec and Ontario, statutory holdback is 10%. Verify the calculation is on the pre-tax subtotal, not the grand total. Verify holdback is being held on every contracted vendor, not just some.
What failure looks like: holdback calculated on the post-tax amount (overstating the holdback). Holdback applied inconsistently across vendors. Holdback released on a vendor before the statutory waiting period has elapsed. Any of these creates exposure that is difficult to recover later.
4. Tax Jurisdiction
Verify that vendors are billing the correct tax rate for the project's jurisdiction. The most common error: an Ontario trade working on a Quebec project bills the full Quebec combined rate (14.975%) on its invoices, but does not have a Quebec tax registration. The Ontario trade should be billing only 5% GST in this scenario.
What failure looks like: the owner pays QST that the trade is not authorized to collect and not remitting to Revenu Quebec. The owner cannot recover this tax, and the trade may be operating in violation of provincial tax law. This pattern is common enough that we treat it as a default verification on any cross-provincial draw.
5. Cumulative vs. Period Totals
Verify that the cumulative project total at the bottom of the draw equals the prior cumulative total plus this period's draw. This sounds trivial. It is not. Cumulative totals carried forward across draws are one of the most common places for arithmetic drift to enter a project's financial record.
What failure looks like: the cumulative total on Draw 12 does not equal the cumulative total on Draw 11 plus the period total on Draw 12. The discrepancy is small, often a few hundred dollars, and gets carried forward indefinitely. By the end of the project, the cumulative total no longer reconciles to the sum of period draws. The error is now embedded.
The Deposit-Deduction Trap, In Detail
01 A custom residential project awarded a railing supplier a fixed-price contract. The supplier's standard practice was to invoice 25% on contract signing as a deposit. The deposit was paid on Draw 13, recorded against the deposit invoice number.
02 The work was fabricated, delivered, and installed eighteen months later. The supplier issued a final invoice for the full contract value, without deducting the deposit already paid.
03 The contractor's accounts payable team, processing the final invoice in isolation, would have paid it in full in Draw 28. The duplicate would have been invisible at the draw level - the deposit was eighteen months and fifteen draws earlier.
04 What caught it was the obligations register. The contracted value for the supplier was a known fixed dollar amount. When the final invoice was applied, the running balance went negative - structurally impossible.
05 The error was flagged before payment was released. The corrected draw was reissued with the deposit deducted. The supplier confirmed the correction. The project was made whole.
The structural lesson: the error was the supplier's. The architecture that caught it was the contractor's. A combined-ledger project would have paid in full and recovered only on later audit, if at all.
When to Pause a Draw
Owners are often reluctant to raise draw concerns because they do not want to damage the relationship with the contractor. This concern is legitimate, but the alternative is worse. Errors uncaught at the draw stage compound. Errors raised at the draw stage are usually corrected immediately, with no relationship damage if handled professionally.
Minor corrections (under $500, clerical): note them in writing, ask for confirmation in the next draw, do not pause payment. These are normal.
Material errors (over $500, or structural): pause the draw, request the corrected version, do not sign the original. A contractor who handles this professionally is the contractor you wanted. A contractor who resists correction is the contractor you needed to know about.
Pattern errors (the same type of error in multiple draws): escalate. Pattern errors are not clerical; they indicate a structural failure in the contractor's financial architecture. This is the moment to engage independent review.
"A contractor whose books are clean welcomes verification. A contractor whose books are not clean treats verification as an attack. The reaction is the data."
What This Costs You
Thirty minutes per draw. On a project with twenty-eight draws across two years, that is fourteen hours of total review time. The errors caught in those fourteen hours, on most projects we have seen, more than justify the time. On the projects where no errors are caught, the exercise still produces something useful: confidence in the contractor's financial discipline, grounded in evidence rather than trust.
This is, in our experience, the single highest-leverage activity an owner can perform on a custom build. It costs almost nothing. It produces information that no other activity produces. And it puts the owner in the right relationship with the project's financial reality.
LSPP Solutions provides draw audit and ongoing financial governance review for owners on active custom builds. We catch what the methodology was designed to hide.
Contact LSPP