
Construction Draw Package: Why the Developer Is the Translation Layer


A construction draw package is the set of pay applications, invoices, lien waivers, change order logs, and balanced sources and uses a developer sends to release loan funds. The lender reads it against draw requirements and inspections, while your team reads it against cost to complete, committed cost, contingency, and the books. The developer sits between those two views and rebuilds the connection by hand every draw, often in a two-day window before the lender’s deadline. When that window slips a day or two, contractor payments slip with it.
Two Separate Realities
Most developers run two separate realities: the lender’s draw and their own project financials. They reconcile the two by hand every month, and they are the only ones who can.
The lender’s reality runs on draw requirements, inspections, approvals, and funded-to-date. Yours runs on the budget, commitments, cost to complete, contingency, and the enterprise resource planning (ERP) system.

Some teams assume the lender handles the hard part, but lenders manage approval. The developer still assembles the package, tracks compliance, collects waivers, and ties every funded dollar back to the books. For the lender’s side, see how lenders review a construction draw request.
“You are the translation layer,” Chris DeVito, Built’s GM of Owner and Developer Solutions, told developers in a Built webinar this fall. “You’re the one that assembles the package, chases the documents, reconciles all the numbers.” No system carries that work for you, so it lives in spreadsheets and memory.
Development CFOs and controllers feel this at month-end close. The lender’s funded-to-date says one number, and the general ledger says another. Closing that gap means matching draws, invoices, and retainage line by line across every active project.
Where Draw Status Disappears
Once a package leaves your team over email and text, draw status is gone. Nobody can see whether the lender opened it, flagged a missing waiver, or sent it to inspection, and every status question becomes another email.
On Tuesday, the team on a $31M multifamily project starts assembling the monthly draw from scratch because the lender needs it by Thursday. The project has 15 subcontractors across 10 trades, and all of them have billed.
The project accountant pulls pay apps from email, invoices from the ERP, and the change order log from a spreadsheet. Two subs sent revised pay apps. One approved change order is missing from the budget. By Wednesday night, the team is reconciling three sources that were never designed to agree.
Subcontractors feel the slip first. They’ve signed conditional lien waivers and are waiting on payment. Every unanswered status call costs goodwill with the trades you need on site next month.
Owner-developers see the same slip as carry and risk. A draw that funds two days late holds back contractor payments and strains the lender relationship.
What Goes in a Construction Draw Package
A construction draw package is the document set a developer submits to request the next release of construction loan funds. It proves the billed work is complete and the costs tie to the approved budget. It also protects lien rights and shows that every funding source balances to the requested amount.
Project accountants own this assembly. They match pay apps to invoices, confirm retainage, and chase missing waivers. Each manual match is a spot where the draw can drift from the books.
A complete package includes the following:
- Pay applications: Each sub’s and the general contractor’s pay app for the period, by line item.
- Invoices: Subcontractor and vendor invoices that match the pay apps and code to budget lines.
- Change order log: An updated log of approved, pending, and rejected change orders.
- Retainage: Retainage calculated on the American Institute of Architects (AIA) G702 summary from line-item work on the G703.
- Conditional lien waivers: Waivers from the general contractor and each sub covering this draw’s amount.
- Sources and uses: A statement that balances to the requested amount before submission, with no plug figures.
- Lender requirements: Deal-specific items from your loan agreement, such as inspection reports or insurance certificates.
Lien waiver forms and rules vary by state. Confirm the required forms and timing with your counsel before the first draw.
Sending One Draw to Several Funding Sources
To send one draw to several funding sources, build it once from a single project budget and give each source its own view. A senior lender, an equity partner, and a mezzanine lender all fund the same work. Each one needs its share, its line items, and its funded-to-date.
Separate spreadsheets per source mean every correction happens three times.
A better practice is a draw ticket: a cover sheet that sits on top of the complete package so it can be shared with each additional funding source. The ticket states what that source is being asked to fund, and the pay apps, invoices, and waivers underneath stay identical.

The usual objection is that every lender is different. Formats and required documents do vary by lender and deal, but the project record doesn’t. Map one record to each format, and the reconciliation becomes a repeatable step.
Connecting the Draw to Your ERP
Connecting the draw to your ERP means every funded dollar ties to an approved, coded transaction in your book of record. The ERP is that book of record. For most owner-developers, it’s Yardi, Sage Intacct, QuickBooks Online, or QuickBooks Desktop.
That’s why “we already have an ERP” doesn’t close the gap. The ERP tracks vendors, accounts, and payables, while the lender tracks draw lines, retainage, and funded-to-date by source. Someone reshapes one into the other every month, and that someone is usually your project accountant.
A clean connection follows three rules. Code invoices to the project budget before they post. Post only approved transactions downstream. Record each draw’s funding by source, so month-end close matches the lender’s funded-to-date.
This guide to accounting for construction loan draws covers the journal entries.
How Built Connects the Lender’s Draw to Your Books
Built connects the lender’s draw to your books through one project record that both the lender’s view and your ERP read from. Built is the AI operating system for real estate finance, serving lenders, owners, developers, and contractors across the full lifecycle. We take on the translation work, so your team reviews the draw instead of rebuilding it.
Now run the same Tuesday through Built. Invoices from all 15 subs arrive in one inbox, and the Job Cost Agent splits each pay app, assigns budget codes, and matches lien waivers for the project accountant to review. Discrepancies get flagged before approval instead of surfacing Wednesday night.
Documents collected at the payable stage, such as change order logs and cost reports, count toward the draw’s compliance requirements, so nobody chases the same document twice. The draw package then pulls together in minutes, and your lender gets it in the format it already uses.
Your team works from the following:
- Invoice coding: The Job Cost Agent turns a stacked pay app PDF into coded payables ready for review.
- Compliance before submission: Project and organization requirements are enforced before a draw moves.
- Source-linked amounts: When your lender runs its draws on Built, every amount read from your documents links back to its source, and any override is flagged as a human edit for both sides.
- Live budget position: Cost to complete, contingency, and committed cost stay current instead of waiting for month-end.
- Draw tickets: A cover sheet for the complete package that can go to equity and other funding sources.
Built is the front door to your ERP. It connects with Yardi, Sage Intacct, QuickBooks Online, and QuickBooks Desktop and pushes only approved, coded transactions downstream. Your project management tool, such as Procore, stays in place. Procore keeps the field work, and Built handles the money and the lender connection.
Built’s lender network puts the draw in front of the lender directly. Its 300+ lender clients include 14 of the top 25 U.S. lenders, and many owners first come to Built because a lender invited them onto the platform.
Payments matter to the trades too. On Built, 97.3% of subcontractor payments are delivered within 30 days, and the median lien waiver signature time is 23.9 hours. Those are the delays the subs in Tuesday’s scenario were calling about.
Switching mid-project is the last objection we hear. The median implementation for owners and general contractors is 42 days.
For development CFOs and controllers, the job shifts from assembling the draw to reviewing it. For a broader look at the category, read our guide to construction draw software for owners and developers.
Talk to Built About Your Next Draw
Bring your next draw to our team, and we’ll show you how it runs from one project record. We’ll map your budget, your funding sources, and your ERP. Your team can then stop rebuilding the draw from scratch every month.
Construction Draw Package FAQs
What Should a Construction Draw Package Include?
Most lenders expect AIA G702 and G703 pay applications, matching invoices, and conditional lien waivers. The package also needs an updated change order log and a sources and uses that balances to the requested amount. Many lenders add inspection results and insurance certificates. Your loan agreement sets the final list, so check it before the first draw.
How Do I Send One Draw to Equity and Mezzanine Lenders?
Build the draw once from a single project budget, then give each funding source its own view. A cover sheet for each source, often called a draw ticket, goes on top of the complete package and states what that source is being asked to fund. The underlying pay apps, invoices, and waivers stay the same.
What Happens If My Lender Finds Something Missing From My Draw Package?
The lender usually holds the draw, or funds only the documented portion, until the gap closes. Missing lien waivers and invoices that don’t match budget lines are common causes. Each round trip adds days, which delays contractor payments and can push the schedule.



