A usable change process begins with a clear baseline.
A change can be measured only when the original agreement explains what was included. The baseline should identify drawings, specifications, room-by-room work, quantities, finish assumptions, allowances, alternates, exclusions, owner-supplied products, building obligations, schedule assumptions, and closeout. Vague phrases make it difficult to distinguish a change from work that should already be included.
Before mobilization, reconcile contradictions among the proposal, drawings, finish schedule, and verbal discussions. Date the governing documents and keep superseded versions out of active use. When the team starts from one current baseline, a later request or condition can be described against it without reconstructing the agreement from memory.
Identify why the change exists.
Changes commonly arise from an owner request, design revision, building or agency comment, product substitution, field dimension, code or professional requirement, damage, concealed condition, coordination conflict, quantity difference, or correction of incomplete information. Recording the reason matters because it influences responsibility, urgency, design review, and whether dependent work should pause.
A requested finish upgrade is different from hidden deterioration discovered after demolition. A clarified drawing is different from a changed layout. A product that becomes unavailable is different from a product ordered late. The change record should explain the event objectively and attach photographs, sketches, specifications, or correspondence needed for review.
Define a protocol for concealed conditions.
Existing buildings may hide damaged framing, corroded piping, unsafe wiring, uneven substrates, moisture, undocumented alterations, abandoned services, inaccessible connections, or assemblies that differ from available plans. Some conditions can be investigated before pricing; others become visible only after controlled opening or demolition.
The agreement should explain how the area is made safe, documented, evaluated, and protected while the response is developed. The proper architect, engineer, licensed trade, environmental professional, building representative, insurer, or other specialist may need to participate. The required response must be based on the property-specific facts and qualified review.
Keep allowances from becoming invisible changes.
An allowance is a placeholder for a defined item or scope awaiting selection or final information. It should state the amount, quantity, expected quality, whether labor is included, and how tax, delivery, markup, and differences are handled. When the final selection exceeds or falls below the allowance, the reconciliation should be documented even if no physical scope changed.
Track every allowance in one log showing the carried amount, approved selection, committed amount, expected variance, decision deadline, and procurement status. This keeps several small upgrades from appearing only at the end. If an allowance is too vague to describe what it buys, the scope needs further development before contracting.
Require a complete change proposal.
A change proposal should identify the related contract item, describe added and deleted work, list material and labor assumptions, show credits when applicable, state the amount, identify schedule effects, and explain any decision deadline. Supporting sketches, product data, photographs, subcontractor input, or breakdowns may be appropriate depending on complexity.
Price is only one part of the decision. A new fixture can affect rough work, wall depth, tile, cabinetry, power, approvals, lead time, and return visits. A deleted item can leave related costs in place. The team should evaluate the complete interface rather than treating every request as a single isolated task.
Update the forecast, not only the invoice.
Maintain a change log with proposed, under-review, approved, rejected, and completed statuses. The financial forecast should combine original contract value, approved additions and credits, pending exposure, allowance variance, owner purchases, payments, and expected final cost. The schedule forecast should show the cumulative effect of approved and unresolved changes.
Reviewing the log regularly allows the owner to make tradeoffs while options remain. A desired upgrade may be balanced by deferring another alternate. A long-lead change may be rejected or substituted to protect the completion date. Cost control is strongest when decisions occur before the field has only one expensive path left.
Close changes into the final project record.
Approved changes should flow into updated drawings, selection schedules, procurement logs, payment applications, punch lists, and closeout documents as appropriate. If the installed condition differs from the original record, the team should identify which document now governs operation, maintenance, warranty, and future work.
At completion, reconcile every change and allowance so no proposed item remains ambiguous. Confirm credits, outstanding work, final amounts, and related documents. A clean change record supports final payment discussions and gives the owner a more accurate history of what was actually built.
- Describe the reason and affected baseline
- Document added and deleted scope
- Show amount and schedule effect
- Obtain authorization
- Update cost and schedule forecasts
- Carry the decision into closeout records
Turn this guide into a working project record.
Begin with a short owner brief rather than leaving important details scattered across browser tabs or conversations. Record the complete property address and unit, legal or management contacts, current occupancy, affected rooms or commercial areas, desired result, elements that must remain, photographs, available drawings, known damage, previous alterations, target timing, and every document already received from the building or landlord. Date the brief and identify which information is confirmed, assumed, or still missing.
Next, separate decisions into four categories: confirmed base scope, owner selections still required, optional alternates, and conditions needing investigation. Give each open item a responsible person and a decision date tied to the work it controls. A product decision may affect rough locations or fabrication; a building comment may affect access or protection; a professional review may affect whether pricing can be fixed. Recording that dependency makes the consequence of delay visible before the field is waiting.
Create a responsibility matrix for design, filing, permits, building submissions, insurance, purchasing, delivery, licensed and specialty trades, protection, testing, patching, cleaning, inspections, punch list, and closeout. Use exact legal entities where contracts, permits, licenses, or insurance are involved. The matrix is not a substitute for professional advice; it is a way to expose responsibilities that otherwise fall between parties.
Finally, give the same project package to every contractor or consultant being evaluated. Issue clarifications consistently, retain prior versions, and keep one current decision log. Review official requirements near the time of the project because agency procedures, building requirements, products, and property conditions can change. A strong record helps the owner ask better questions, compare the same promise, and identify when more design, investigation, or qualified advice is needed before construction.
- Property and current-condition summary
- Base scope, alternates, and exclusions
- Selections and decision deadlines
- Building and agency requirements
- Professional and trade responsibility matrix
- Access, occupancy, and protection plan
- Budget and schedule assumptions
- Inspection, punch-list, and closeout list
Common project questions.
What is a construction change order?
A change order is written documentation modifying the agreed scope, price, schedule, or another contract term. It should describe the change, identify additions or credits, show time effects, and be authorized according to the agreement and applicable requirements.
Is an allowance the same as a change order?
No. An allowance is a temporary amount carried for a defined item or scope. Selecting above or below it may create a documented adjustment. A change order can address broader added, deleted, or revised work and schedule effects.
Who pays for a concealed condition?
Responsibility depends on the contract, available information, cause, property, and applicable law. The condition should be protected, documented, evaluated, and addressed through the agreed process; legal or professional advice may be appropriate.
Can a contractor proceed based on verbal approval?
The safest approach is to follow the written authorization procedure in the agreement. NYC consumer materials for applicable home-improvement work emphasize written change orders signed by the parties. Emergency protective measures may require a separate prompt documentation process.
Should a change order include schedule impact?
Yes. Even a small visible change can affect design, procurement, inspections, trade sequence, access, and return visits. The owner should understand time effects before authorizing whenever reasonably possible.
How can owners reduce change orders?
Develop scope, investigate existing conditions, coordinate drawings and products, review building requirements, assign responsibilities, and make decisions early. Changes cannot be eliminated, but ambiguity and late decisions can be reduced.
Primary sources and verification.
This guide is general planning information. Property-specific requirements should be confirmed with the responsible agency, building, design professional, licensed trade, insurer, attorney, or other qualified party.