Construction draws: building a lender-ready package

Every builder financing a project knows the monthly rhythm: work gets done, the draw request goes in, and money arrives — or does not — depending on how convincing the package is. What is striking is how often draws are delayed not because the work is behind, but because the paperwork is. The concrete was poured on schedule; the statutory declaration was not.

This post walks through the mechanics of progress draws as they generally work on Canadian construction financing, and the package discipline that separates smooth funding from monthly fire drills. Loan agreements differ, and your lender’s requirements and your construction counsel govern — treat this as the operational map, not the terms.

How a draw schedule actually works

Construction lenders rarely advance a lump sum. They advance in draws against verified progress, keeping the loan balance roughly in step with the value in the ground. The draw schedule — monthly, or milestone-based on smaller projects — defines the cadence. Each draw is, in essence, an argument: here is the work completed since the last advance, here is what it cost, here is what remains, and here is the evidence.

The lender’s underwriting question never changes: is there enough undrawn loan left to finish the building? Every document in the package exists to answer some piece of that question.

What a complete package contains

Requirements vary by lender and project size, but a progress draw package generally assembles some combination of:

• A progress claim or draw request summarizing work completed in the period, usually broken down by budget line or cost code.
• An updated budget showing costs to date, the current draw, and — critically — cost to complete per line.
• Supporting invoices and payment certificates from trades and suppliers backing the claimed amounts.
• A statutory declaration (the CCDC 9A/9B forms are common) declaring that accounts for the previous draw have been paid, subject to holdback.
• A current lien search on title, confirming no claims of lien have been filed.
• A progress report from the lender’s quantity surveyor or cost consultant, where the loan requires independent verification.
• Insurance confirmations and any project-specific conditions the loan agreement carries.

None of these documents is difficult on its own. The difficulty is that they come from different people — the site team, accounting, the trades, the lawyer, the QS — and must all describe the same month consistently. A package where the progress claim and the budget disagree by one change order is a package that comes back with questions.

Where holdback meets the draw

In BC, the Builders Lien Act requires a 10% holdback on the value of work and materials, and the draw math has to respect it: lenders generally advance net of the required holdback, and the statutory declaration speaks to payments "subject to holdback." That means every draw implicitly updates a holdback ledger — what has been retained, per contract, and when the release windows open. Builders who track holdback as an afterthought discover the problem at the worst time: at release, when the ledger has to be reconstructed across a year of draws. The lien and holdback mechanics deserve their own discipline; our compliance hub covers the timelines in plain language.

Cost-to-complete is the number that decides

Experienced construction finance people read a draw package back to front: they go straight to cost-to-complete. Percent-complete flatters; cost-to-complete confesses. If the remaining budget on a line will not finish the work — because of a change order not yet reflected, a price escalation, or an optimistic original allowance — the gap surfaces here first, and lenders respond far better to a builder who surfaces it than to one whose numbers quietly stopped adding up.

That puts a premium on budget hygiene between draws: change orders priced and folded into the budget when approved, not at draw time; commitments tracked against lines; variances explained in the month they appear.

Making assembly repeatable

The teams that stop dreading draws all converge on the same operational shape. The budget, cost codes, invoices, change orders, and holdback ledger live in one system, updated as the work happens. The draw is then a report over live records, not a monthly reconstruction — the progress claim reads from the same lines the invoices were coded to, and the numbers agree because they were never separate.

OpSphere ProBuild is built for exactly this rhythm: budgets and cost codes, change orders that update contract value and budget in one motion, draw requests assembled against budget lines, loan tracking per project, and BC lien holdback ledgers with release-window countdowns. ProBuild is available today — and the monthly draw is one of the first workflows teams move onto it.