A new fixture name doesn't tell you whether a proposal is a simple substitution or one of the lighting scope changes that needs wider review. To find out, compare the proposal with the approved project baseline. If the documented zones, intended tasks, mounting assumptions, coverage, and any other documented project requirements all stay the same, treat it as a candidate fixture-only substitution.
If any of those assumptions might change, ask for a project scope review before anyone approves or orders the fixture. If the proposal or the baseline is missing the details needed for a fair comparison, the question stays open until someone supplies them. Your project's own contract documents and requirements set the formal approval route.
Classify the proposal against the approved baseline
Use this screen as a first pass before approval. It gives you a preliminary classification, not a ruling on contract scope.
| Review result | What the comparison shows |
|---|---|
| Candidate fixture-only substitution | Model differs; documented zones, tasks, mounting, coverage, and other requirements unchanged |
| Possible scope change, review needed | One or more documented assumptions may change |
| Unresolved, pending information | Baseline or proposal lacks comparable details |
Each result points to a different next step. A candidate substitution moves to a written comparison and whatever substitution process your project documents require. A possible lighting scope change goes to the person or team who manages changes under your contract before any order is placed. An unresolved case needs a specific information request, and nothing should be approved while you wait for the answer.
Identify the approved lighting baseline
Your baseline is the set of current approved records that define the lighting work. Gather these records before you compare anything. For each assumption you plan to check, write down the document name or reference number.
- Lighting drawings or plans that show fixture locations, zones, and layout
- Specification sections that name the specified fixture and its required qualities
- Fixture or luminaire schedules that list types, mounting, and quantities
- Approved revisions, addenda, or bulletins that replaced earlier versions
- Control zone schedules or narratives, if your project has them
- Any other project record that states intended tasks or coverage for a space
Make sure each record is the current approved version and not an earlier draft. Every project names its documents a little differently, so use this list as a guide to where to look, not as a required set. Also find the contract section or procedure that governs substitutions on this project. On jobs with several buildings or phases, it helps to organize project records by zone, so each comparison points to the right sheet.
Compare the proposal's effects, not just its name
Fixture identity and fixture effects are separate questions. For each assumption your baseline documents, record three things: the approved condition, the condition stated in the proposal, and a status of unchanged, changed, or unknown.
A light fixture in a design record can do more than fill a model number. For example, the VA Lighting Design Manual focuses design on the tasks of each space, defines lighting control zones, and coordinates luminaire layout with furniture, casework, millwork, and equipment. Those requirements apply only to VA projects. Still, they show how a swap can reach past the product itself.
- Zones: Does the proposal keep fixtures in the same documented areas and control groups? If it regroups or adds fixtures, mark the item changed.
- Intended tasks: Does the proposal still serve the documented task areas? If the task is a bench, a rack face, or a label, check the task plane and not just the floor.
- Mounting assumptions: Compare the method, location, and height shown in the schedule or drawings with what the proposal states.
- Coverage: Look for changes in quantity, spacing, or layout. If the proposal doesn't show any, ask for a revised layout. Our commercial project support hub covers layout review and control checks.
- Other stated requirements: Compare any other item the baseline specifies, but only where it is actually documented.
Mark an item unknown when the proposal says nothing about it. A different model name doesn't prove a scope change on its own. Silence doesn't prove that nothing changed, either. Ask for the missing details before you mark the item unchanged.
Record the differences and request clarification
Put the comparison in writing before you treat the change as settled. Keep it short, so the approver can quickly see what stays the same, what may change, and what is still missing.
- The proposed fixture, identified exactly as the proposal names it
- The baseline references it replaces, such as the spec section, drawing number, or schedule tag
- Items confirmed unchanged, each with the document that confirms it
- Possible changes, each tied to the assumption it affects
- Unknowns, each with the specific information needed to resolve it
- Related-work, cost, or schedule effects, but only if the proposal or project documents identify them
Owner procedures show what a record like this can look like. Yale's July 2025 substitution procedure asks requests to name the product being replaced, along with its specification section and drawing references. It also asks for a comparison of significant qualities with deviations noted, and for any changes needed to other parts of the work, plus cost information. Similarly, the Illinois CDB construction documents call for an itemized comparison with the specified product. They also ask for information on schedule, coordination, other affected contracts, and cost. Each procedure applies only to its own projects.
Send any unresolved items back as a clarification request or a request for revised records. Then follow the substitution or change process your project documents set out. If an order is close to release, hold the affected lines using a bulk order release checklist until the comparison is settled.
FAQs
Can a different fixture model still count as a substitution?
Yes. A new model can still be a candidate fixture-only substitution if every documented project assumption stays the same, including zones, intended tasks, mounting, and coverage. The model change is where your review starts, not its conclusion. Whether the substitution is formally accepted depends on the process in your project's governing documents.
What should I do if the proposal leaves out key details?
Leave the classification open and ask for exactly what's missing. For example, you might need the mounting method, a revised layout, or confirmation that the documented zones stay the same. Approving a proposal before those gaps are filled can leave project expectations unclear for everyone involved.
Who makes the final call on substitution versus scope change?
The contract and project requirements for your specific job decide that. Procedures differ by owner, agency, and contract, so no single US process applies everywhere. The screen in this guide helps you prepare a clear request. It doesn't replace the decision of the person or body your documents name.
Does a scope review mean the cost or schedule will change?
No. A review only means a documented assumption may be affected. A cost, schedule, or related-work impact belongs in the record only when the proposal or project documents identify one. Whether either party is entitled to an adjustment depends on the governing contract.
