Every builder who runs enough draws will eventually have one bounced. The difference between a builder who recovers in two days and one who loses a week of cash flow is what they do in the first 24 hours after the rejection lands. This is the playbook for triaging a returned draw, fixing the right things in the right order, resubmitting cleanly, and preventing the same rejection on the next package.
The first 24 hours determine the damage
When a lender returns a draw package, the clock starts on cash flow. Vendors who expected to be paid on the wire date now sit unpaid. Subs who were scheduled for the next phase may walk if their last invoice does not clear. Interest continues to accrue on the construction loan, and the builder absorbs whatever short-term financing is needed to keep the project moving. The wider the gap between rejection and resubmit, the more expensive the gap becomes.
Inside 24 hours of receiving the rejection, the builder needs to do three things. Read the rejection carefully and categorize every flagged item. Acknowledge the rejection with the loan officer, in writing, with a planned resubmit date. Begin the fixes on the highest-impact items first. Builders who skip the acknowledgment step and just rush to resubmit are the ones who damage the lender relationship even when they fix the package quickly.
Categorize every rejection before fixing any of it
Not all rejections are equal. Some are five-minute fixes. Some require new documentation that takes days to collect. Some require renegotiation with the lender on scope or interpretation. Triage the rejection into one of five categories before you touch the package.
| Category | Typical example | Fix time | Risk if ignored |
|---|---|---|---|
| Math | G702 line 4 does not match G703 column G total | 15 minutes | Low (mechanical fix) |
| Documentation | Missing prior-period unconditional waiver | 1 to 3 days (vendor turnaround) | Medium (delays wire) |
| Photo | Photo without project ID or line caption | 1 to 4 hours (re-shoot or recaption) | Low (re-shoot if needed) |
| Scope | Line item billed beyond budget without change order | 2 to 7 days (CO process) | High (forces scope conversation) |
| Validation | Inspector percent does not match billed percent | 1 to 5 days (re-inspection or re-bill) | High (lender trust impact) |
Math and photo fixes go first because they are fast and unblock the rest. Scope and validation issues go last because they require the lender to make a decision, and you want them deciding on the basis of an otherwise clean package, not one with three unresolved items.
The five most common rejection reasons in detail
G702 line 4 does not match G703 column G total
The cover-sheet completed-and-stored-to-date figure must equal the sum of column G on the continuation sheet. On 926 Stratford draw three, line 4 reads $213,400 and column G sums to $213,460. A $60 mismatch is enough to bounce the package. The fix is to recalculate column G from the underlying line items and update line 4 to match. Never adjust column G to match line 4; the line items are the source of truth, the cover sheet is the summary.
Missing prior-period unconditional waiver
Vendors billed on draw N must produce an unconditional waiver in the package for draw N+1. Builders who chase waivers reactively, after the next draw is already prepared, hit this rejection routinely. The fix on the current draw is a phone call to the vendor and a same-day waiver. The fix on future draws is to issue the unconditional waiver request the day the prior draw funds, not the day before the next one is submitted.
Photo without project identification
A photo of a framed wall is meaningless to a lender if it could be any project on any site. Lenders increasingly require photos with project ID, date, and a caption tying the photo to a specific G703 line. Smartphone photos with embedded EXIF metadata and GPS coordinates are usually enough. Photos pulled from a sub’s text message often are not. The fix is to re-shoot if the work is still visible, or to attach a written attestation from the site supervisor confirming the photo’s origin if it is not.
Scope creep on a budgeted line
A line item is billed at $52,000 against a scheduled value of $48,200. Either the line is overrun and needs a change order, or the bill is wrong. Lenders will not approve billing past the scheduled value without a written and signed change order on file. The fix is to choose. Either reduce the bill to the scheduled value and absorb the overrun until a change order is processed, or pause the draw and process the change order before resubmitting. Most lenders prefer the change order, because billing-then-fixing creates precedent that the lender does not want to set.
Inspector percent does not match billed percent
The lender’s inspector reports framing at 70% complete. The G703 bills framing at 85%. The lender bounces with a percent-complete flag. The fix is almost always to bill at the inspector’s number, not to argue. The inspector is the lender’s tiebreaker, and arguing about percent on a single draw burns trust the builder will need on the next ten draws. If the inspector is genuinely wrong and a re-inspection is justified, request it in writing with photo evidence, but bill conservatively in the meantime.
Resubmit without losing the relationship
The mechanical resubmit is straightforward. Fix the items, regenerate the package, send it back to the loan officer with a clear cover note. The relationship side is harder and more important. The loan officer just spent time on a package that did not approve. The next package needs to feel like the builder learned something, not like the builder just patched the immediate problem.
The cover note on a resubmit should be three short paragraphs. First, an acknowledgment that the original package had errors and a thank-you for the catch. Second, an itemized list of what was wrong and what was changed. Third, a sentence on what process change prevents this on future draws. That third paragraph is what separates builders the loan officer trusts from builders the loan officer scrutinizes.
When to call the loan officer directly
Email is the right channel for math fixes, photo recaptions, and missing waivers. The fix is mechanical, the rejection reason is unambiguous, and the loan officer does not need a conversation. Pick up the phone for scope issues, validation disputes, or any rejection where the underlying cause is not obvious from the rejection note.
On 926 Stratford, if the inspector reports framing at 70% and the builder believes 85% is correct, that is a phone call. The builder explains what the inspector may have missed (interior framing not visible from the exterior, a partial-day inspection, weather conditions during the visit) and asks for a re-inspection or a documented exception. Never argue this in writing first. Email creates a record that hardens the disagreement; phone creates a conversation that resolves it.
The second-rejection problem
A draw that gets rejected once is a math problem. A draw that gets rejected twice is a relationship problem. Loan committees notice second rejections. Some lenders escalate a second rejection to credit review; others put the builder on a heightened monitoring status that follows them across loans. A single second-rejection event can cost a builder 25 basis points on the next loan and lengthen approval cycles for the next two years.
The way to avoid a second rejection is to over-correct on the resubmit. If the rejection cited two missing waivers, send all of them in the resubmit, not just the two that were flagged. If the rejection cited a math error on line 4, audit lines 1 through 9 and confirm every reconciliation in writing in the cover note. The goal of the resubmit is not to clear the flagged items. The goal is to demonstrate that the package as a whole is now clean.
Preventing the same rejection on future draws
Every rejection is a process signal. A single rejection is bad luck. Two rejections of the same type across two builds is a process gap. The fix is upstream of the draw package itself.
For math rejections, the fix is to derive G702 line 4 from the G703 column G total automatically rather than typing it. For waiver rejections, the fix is to issue waiver requests at invoice payment, not at draw assembly. For photo rejections, the fix is to standardize photo capture (project ID, date, caption) at the moment of the photo, not at the moment of the draw. For scope rejections, the fix is to maintain a live change-order log that the draw package draws from, so a billed amount over the scheduled value is impossible without a corresponding change-order entry. For validation rejections, the fix is to bill what the inspector will see, which means matching the build percent to the visible work in place, not to the builder’s internal sense of progress.
Every one of these fixes is enforceable in software. A draw platform that ties G702 to G703 mathematically, that generates waiver requests from invoices, that timestamps photos against project and date, and that blocks a billed amount from exceeding the scheduled value without a change order on file, makes the rejection categories above structurally hard to produce. That is the version of the draw process where rejections become rare events rather than recurring ones.
A worked rejection on 926 Stratford
Run through a concrete example. The third draw on 926 Stratford is submitted on a Tuesday, requesting $43,560. The loan officer at First Community Bank reviews on Wednesday and returns the package Thursday morning with three flags. Line 4 on G702 reads $213,400 but column G sums to $213,460. The drywall sub billed on draw two has no unconditional waiver in the current package. Two photos of the framing line have no captions tying them to the line item.
By Thursday afternoon, the builder acknowledges the rejection in writing, commits to a Friday resubmit, and starts on the math fix. The math is recalculated from the underlying transactions; line 4 is corrected to $213,460, and the wire request increases by $60. The drywall sub is contacted Thursday afternoon for the unconditional waiver, which arrives Friday morning. The site supervisor revisits the project Thursday evening and re-shoots framing photos with line-item captions written on a whiteboard in the frame. By Friday at 11 a.m. the package is resubmitted with a cover note acknowledging the three errors and noting the process change for future draws (waivers requested at the moment of payment, not at draw assembly). The loan officer approves Friday afternoon. The wire clears Monday morning, three business days later than it would have on a clean first submit.
Total cost of the rejection: three business days of cash flow, one re-shoot site visit, one phone call to the drywall sub, and a slightly bruised relationship that will be repaired by the next clean draw. Total damage: minimal, because the builder triaged correctly and resubmitted within 72 hours. A builder who waited a week to resubmit, or who resubmitted without acknowledging the errors in writing, would have incurred a meaningfully larger cost on both cash flow and reputation.
The post-mortem after every rejection
Every rejection deserves a 30-minute post-mortem the week after the resubmit clears. Three questions, one document, archived to the project file.
First, what was the root cause? Not the symptom (math error) but the underlying gap (G702 line 4 was typed manually instead of derived). The symptom is what the lender flagged. The root cause is what made the symptom possible.
Second, what process change prevents the same root cause on future draws? For a manual-entry math error, the process change is to derive line 4 from the G703 column G total in the draw template, never type it. For a missing waiver, the process change is to issue waiver requests at invoice payment, with a checkbox on the payment workflow. For an unphotographed line, the process change is a weekly site photo schedule with a checklist tied to the active G703 lines.
Third, who owns the process change and when does it take effect? A process change without an owner is a wish. Assign the change to a specific person on the team, write the effective date, and confirm in the next draw cycle that the change is in place. Without this step, the same rejection will reappear on a future draw, and the lender will notice.
How to read a rejection as a relationship signal
Not every rejection is just a fix-and-resubmit. Some rejections are the lender testing whether the builder reacts professionally. A loan officer who flags a small $60 math error on a 32-line draw is signaling that the builder’s precision is being watched. The right response to that signal is a thoroughly clean resubmit, not a defensive cover note explaining why the error was minor.
Equally, a rejection on a fundamental gate (no inspector sign-off, scope creep without a change order) is the lender signaling that the project has drifted out of the originally underwritten envelope. The right response there is a phone call, an honest conversation about where the project actually stands, and a plan to bring the build back inside the envelope. Builders who try to paper over a fundamental gate failure with a cosmetic fix on the resubmit usually find the next draw bounced even harder, and sometimes find the loan moved to special servicing.
Treating each rejection as a signal, rather than as a setback, is what separates builders who improve their lender relationships over time from builders who slowly burn them down. The fix on the current draw matters less than the pattern over the next six. A clean six-draw stretch following a single rejection often leaves the relationship stronger than it was before, because the lender sees a builder who learns. A rejection followed by another rejection three draws later teaches the opposite lesson, and the loan officer responds in kind on the next application.