A post-closing design change should reconnect revised scope, technical review, approvals, contract value, funding, schedule, and field verification.

Identify the change before evaluating it

Describe the original requirement, proposed revision, reason, initiating party, affected location or system, drawing and specification references, related RFI or submittal, contract-change status, work already performed, and decision deadline. Distinguish owner-directed scope, design development, error or omission, code or authority requirement, field condition, value engineering, substitution, contractor means and methods, tenant change, utility condition, and clarification that does not change scope.

Status needs a controlled vocabulary: identified, under technical review, pricing, pending owner decision, pending lender or program approval, authorized to proceed, executed, incorporated into documents, installed, tested, accepted, superseded, rejected, or withdrawn. “Approved” is incomplete without naming who approved what and for which purpose. A design professional’s technical acceptance, an owner’s direction, a contractor’s price agreement, and a lender’s funding decision are different acts.

Reconstruct the coordinated technical basis

Review the revised drawings, sketches, specifications, calculations, product data, narratives, and responses across every affected discipline. Test dimensions, loads, support, clearances, penetrations, drainage, fire and smoke protection, energy performance, accessibility, controls, acoustics, envelope continuity, finishes, equipment access, maintainability, testing, commissioning, warranties, and connections to completed or future work as applicable.

The change should preserve a traceable relationship to the project requirements and current code, permit, program, insurer, utility, authority, and client criteria within the scope of the responsible reviewers. HUD’s construction-change procedure, for example, calls for modified drawings and specifications, a design-professional statement, itemized cost support, and identified signatures. Other projects use different contracts and approvals, but a lender still benefits from seeing a coordinated technical package rather than a price-only change order.

Reconcile contract value and development funding separately

Show the contractor’s proposed and agreed value, labor and material basis where required, subcontractor support, markups, credits, allowances, contingency, prior work, taxes, insurance, bonds, general conditions, design and consultant cost, testing, permit fees, owner cost, and any effect outside the construction contract. Identify whether the amount is estimated, not-to-exceed, unit-price, time-and-material, pending, executed, disputed, or included elsewhere.

Then state the development-budget treatment and funding source. The change may use contractor contingency, owner contingency, allowance, budget savings, a transfer, additional equity, insurance, grant or program funds, or loan proceeds if permitted. The lender and governing documents determine eligibility. The monitoring record should prevent one saving from funding several changes and should keep pending exposure visible before formal execution catches up.

Carry time, procurement, and approvals with the cost

A change can add design duration, review cycles, permit revision, utility coordination, long-lead procurement, fabrication, mockup, access, demolition, rework, inspection, testing, commissioning, seasonal work, or closeout even when the contractor reports no extension. Compare the change with the current schedule logic, procurement register, area sequence, testing plan, occupancy milestones, and available float. Record the contractor’s time position and the reviewer’s current basis rather than assuming a zero-day change has no schedule consequence.

Work performed before technical, contractual, lender, or program approval creates a separate control issue. The FAR Changes clause, which applies to federal contracts rather than private loans, illustrates why written identification and modification matter when direction changes the work or time. On a private project, follow the actual contract and loan documents; for monitoring, keep unauthorized or anticipatory work visible and avoid treating it as accepted or fundable merely because it is installed.

Replace the baseline deliberately

Once accepted through the required project and lender path, update the drawing and specification log, contract sum, schedule of values, development budget, contingency, change log, procurement log, project schedule, permit or approval record, testing requirements, accessibility issue record, and remaining-cost analysis. Identify the effective document revision and date so the field observer, pay-application reviewer, borrower, equity partner, lender, and project team are not comparing current work with different baselines.

Superseded documents should remain available as history but not compete with the current construction set. Where cumulative sketches, bulletins, RFIs, submittals, and change orders have not been incorporated into a coordinated revision, the report should state that limitation. A list of executed changes does not prove the field team has one current buildable record.

Verify the change through installation and closeout

Follow the accepted change into procurement, submittal, fabrication, delivery, installation, observation, inspection, startup, testing, commissioning, punch work, warranties, record documents, and authority acceptance as applicable. Confirm that credits or deleted scope are reflected in the field and payment record as carefully as added work. If the change creates a new interface or performance criterion, carry that requirement into the relevant test and closeout evidence.

Close the monitoring item with an explicit disposition: accepted and incorporated, installed and verified within scope, superseded, rejected, carried as open, accepted with limitation, or transferred to final closeout. State remaining evidence and responsible party. The lender retains its credit and funding decision; KOW’s role is to keep the technical, cost, schedule, and document consequences connected so the revised completion picture can be evaluated on a current record.

Primary sources

Sources and technical references.

Source review current as of September 2, 2026.