A useful exception record separates the condition, evidence, material consequence, responsible party, lender decision, due date, and proof of resolution.
Define what counts as an exception
An exception is a condition that prevents the current draw or project record from aligning with the agreed baseline, reporting requirement, or lender control. It may involve unsupported billing, work that could not be observed, incomplete or inconsistent documents, stored-material evidence, an unapproved change, a budget shortfall, schedule variance, missing equity, permit or inspection status, a lien or payment concern, incomplete closeout, or another project-specific requirement.
Not every comment belongs in the exception register. Routine status, future reminders, technical observations, recommendations, scope limitations, and conditions requiring a lender decision should be labeled distinctly. The report can connect them, but the register should not turn every sentence into an equal-priority task.
Write the exception around the affected decision
Each record should identify the project, draw period, source document or observation, date first identified, current description, affected budget or scope item, evidence reviewed, material consequence, responsible party, requested response, next action, due date, and escalation path. The lender should be able to tell whether the item affects the current advance, a future advance, cost to complete, schedule, collateral, closeout, or only record completeness.
The technical consultant should state the basis and limitation of its observation without deciding matters reserved to the lender, borrower, design professional, contractor, counsel, title company, insurer, or other party. “Open” is not a conclusion. The record should explain what remains unproven and what information or action would allow the responsible decision-maker to disposition it.
Run more than one clock
First-identified age shows how long the underlying condition has remained unresolved. Current-response age shows how long the item has waited since the last meaningful action. Draw-cycle count shows recurrence. Due-date variance shows whether an agreed commitment has passed. Those clocks answer different questions and should not be reset merely because the wording changed or a new report was issued.
A paused clock should have a reason, such as awaiting design direction, contractor pricing, lender instruction, agency action, weather, access, testing, or a future construction milestone. The pause does not erase the condition. It explains why time is passing and who has authority to move the item.
Escalate repeated exceptions by pattern and consequence
A single late submittal may be administrative. Repeated incomplete draw packages, unsupported stored materials, unapproved changes, budget transfers, schedule slippage, missing lien evidence, or promised corrections that do not appear can indicate a control problem beyond the individual item. The reporting history should show frequency, related items, prior commitments, and whether the project response is improving.
Escalation thresholds should be agreed at kickoff and can consider funding impact, cost exposure, schedule consequence, health and safety, collateral protection, recurrence, age, inability to verify, or proximity to final completion. Escalation means prompt notice through the agreed path; it does not mean the consultant has declared a default or made the lender’s credit decision.
Close with evidence—or name the disposition
Potential closeout evidence may include a revised pay application, approved change, invoice, delivery record, photograph, reinspection, test result, updated schedule, permit record, design-professional response, budget transfer, equity evidence, lien or title documentation, contractor certification, or another item required by the lender. The right evidence depends on the exception, and receipt alone does not establish technical or legal sufficiency.
A record may be closed-verified, resolved by revised request, carried to a later draw, accepted by the lender, superseded by an approved baseline, transferred to closeout, withdrawn, or left open. The disposition should identify the date, evidence, responsible reviewer, and remaining qualification. That history protects the continuity of the monitoring record when staff, contractors, or loan administrators change.
Use aging to focus the draw conversation
The draw report should lead with current material exceptions and meaningful changes since the prior period, while the supporting register preserves the full history. A lender may need separate views for conditions affecting the current recommendation, long-aging project exposure, borrower or contractor response, and items approaching a contractual or project milestone.
Current OCC and FDIC guidance describes construction monitoring as a way to assess draw appropriateness, compare advances with progress and original cost, detect delay or overrun, and confirm adequate funds remain. A disciplined exception record supports that control by making unresolved evidence and decisions traceable from one draw to the next—without turning the consultant’s log into the loan agreement.
Primary sources
Sources and technical references.
Source review current as of September 1, 2026.