Lenders don't want narrative. They want documentation that shows the project is progressing as planned, that cost-to-complete is controlled, and that the risk profile hasn't changed since the last draw. Most monthly construction reports delivered by developers and GCs fail this test — not because the project is in trouble, but because the report doesn't speak to what the lender's construction inspector actually evaluates.
This is a developer-side guide. It's written for the owner or development manager who is responsible for producing the monthly report that goes to the construction lender and their inspector.
Who Reads Your Monthly Report (and What They're Looking For)
Your lender typically uses a third-party construction inspector — sometimes called a lender's inspector, owner's inspector, or construction monitor — to review each monthly draw request and project update. The inspector visits the site, compares field conditions to your reported percent complete, and produces their own report to the lender.
The inspector is evaluating three things:
- Schedule conformance. Is the project progressing at the rate implied by the draw amount? Is the reported schedule consistent with what they observed on site?
- Budget conformance. Is the draw amount supported by work in place? Are there cost overruns or open change orders that suggest the remaining budget is at risk?
- Risk flags. Are there open RFIs, change orders, subcontractor issues, or site conditions that suggest the project's cost-to-complete or schedule is at risk?
A monthly report that addresses all three clearly and specifically will move through the draw approval process in 3–5 business days. A report that the inspector has to chase for information, or that requires them to make inferences about schedule status, will slow down.
What to Include
Schedule status: not just percent complete
Reporting "35% complete" is not useful to a lender inspector. They need to know what was completed in the reporting period, what is in progress, and what is scheduled to start in the next period. Most importantly: if the project is behind schedule, they need to know by how many days, what caused it, and what the recovery plan is.
The most credible schedule reporting for lender purposes includes:
- Milestone dates: planned vs. actual for key milestones (structural completion, MEP rough-in, building envelope, substantial completion)
- Current projected substantial completion date
- Open delays by cause: weather days, RFI delays, owner-directed changes, subcontractor issues
- Any schedule recovery actions being taken
If your project is ahead of schedule, say so with the same specificity. Lenders notice when developers only report positive news vaguely and negative news with lots of explanation.
RFI status
Lender inspectors are increasingly sophisticated about RFI backlogs as a leading indicator of schedule risk. An open RFI backlog that's growing month over month suggests the architect or EOR response process is a bottleneck. A large number of open RFIs against critical-path activities is a direct schedule risk flag.
Include in your monthly report:
- Total RFIs submitted to date
- Open RFIs as of report date
- RFIs open against critical-path activities (if any)
- Average RFI response time in the period
If you have this data organized, the lender inspector's job is easier and their confidence in your project management is higher.
Change order status
All approved change orders, with descriptions and amounts. All pending or disputed change orders, with status. The net contract value after approved COs. The contingency balance remaining (if the contract provides for contingency).
Lenders are concerned about change orders that are not approved — unapproved COs sitting in negotiation represent a potential cost overrun. Document them honestly; an inspector who discovers an unapproved CO during a site visit that doesn't appear in your monthly report loses confidence in your reporting accuracy for the remainder of the project.
Subcontractor compliance
For projects with lien waiver requirements: status of lien waivers by trade, by pay period. Any subcontractor performance issues (late mobilization, undermanned crew, quality issues that have generated punch items) should be documented with the corrective action in place.
Daily log compliance
Some construction loans — particularly those with more active inspection requirements — want to see evidence that daily logs are being submitted on time. The ability to show a complete daily log record for every working day in the reporting period is a credibility marker. It tells the inspector that the project is being run with documentation discipline, not reconstructed at month end.
What Not to Include
Monthly reports that try to be comprehensive about everything they're doing right tend to bury the information lenders need. A construction lender's inspector reads 6–12 of these a month. Reports that are structured, specific about the things that matter, and honest about problems and resolutions get approved faster than reports that are narrative and promotional.
Avoid:
- Lengthy descriptions of work that was completed without connection to schedule or budget
- Photos without captions identifying what is shown and how it relates to reported progress
- Vague language about "minor issues being resolved" without specifics
- Optimistic schedule projections without documented basis
The Relationship Between Field Documentation and Draw Speed
The developers who receive draw approvals fastest are not necessarily the ones whose projects are going best — they're the ones whose reports are most organized. A project with a 2-week schedule delay that reports it clearly, with cause and recovery plan, gets approved faster than a project that appears to be on track but whose inspector can't verify percent complete against the field conditions because the documentation is incomplete.
The field documentation system — daily logs, RFI logs, schedule updates — is also the source data for the monthly lender report. GC teams that maintain organized real-time records don't need to compile a monthly report; it largely compiles itself from the documented record. Teams that are reconstructing the record monthly are not only slower but also more likely to produce reports that don't align with what the inspector observes on site.