¿NECESITAS AYUDA? ☎ +1(855)688 7879 Hora: 6 a.m.-6 p.m. (PST)

Commercial Lighting Changes After Approval: Record What Must Be Rechecked

A practical method for post-approval lighting revisions: compare against the approved baseline, map affected checks, and build a traceable revision record.
Decision-flow diagram for comparing a proposed commercial lighting change with approved documents, tracing affected assumptions, and recording affected, unaffected, or unresolved checks.
Share
In this article
  1. Trace the Change Against the Approved Baseline
  2. Recheck Scope and Documents Touched by the Change
  3. Build a Revision Record Before the Change Proceeds
  4. FAQs
  5. Which version counts as the approved baseline when drawings conflict?
  6. Does a small change reopen the whole lighting plan?
  7. Who decides whether a revision affects code or permit approval?
  8. Can affected fixtures be ordered while the revision is still pending?

When an approved commercial lighting plan changes, recheck only what the change touches. First, compare the proposed revision with the latest approved drawings, schedules, and specifications. Then trace which assumptions depend on the changed item, reopen those decisions, and keep the rest closed when the record shows they are unaffected.

Decision-flow diagram for comparing a proposed commercial lighting change with approved documents, tracing affected assumptions, and recording affected, unaffected, or unresolved checks.

The prompts below are conditional, not a universal checklist. Use them to build a revision record that shows what changed, who reviewed it, and what is still open.

Trace the Change Against the Approved Baseline

Start by naming the baseline: the controlled drawing, fixture schedule, or specification, plus its approved revision number. Then write the change in before-and-after terms so every reviewer shares the exact delta to evaluate. For example, "Type A at grid C-4, Rev 2" becomes "Type A at grid C-6, proposed."

Change Assumptions to revisit if affected Reviewer or route
Fixture location or layout Spacing, coverage, and zone assumptions tied to the moved fixtures Project lighting designer
Product or configuration Schedule line, documented characteristics the design relied on, control conditions Lighting designer or specifier
Control or electrical interface Control zones, device locations, driver and control fit, circuiting Responsible qualified electrical professional

The table maps dependencies, not results. A row only applies when the approved documents actually rely on that assumption.

Fixture moves. A moved fixture can affect the layout assumptions for its zone, even when the product stays the same. Do not assume the old layout results still hold for the new position. Send the affected zone back to the layout reviewer, and consider whether the move needs a professional photometric layout instead of a sketch update. If the move also changes what you know about the space, refresh the zone's site survey records before the reviewer starts.

Wide warehouse aisle with high-bay lights aligned above the work area, showing the spatial context considered when a fixture move may affect layout assumptions.

Product or configuration swaps. Compare the approved schedule line with the substitute's current documentation. Check only the characteristics the design depended on, and check control conditions when the design depends on them. Commissioning guidance notes that equipment substitutions should be approved by the lighting designer, with design changes and their impacts recorded in the Basis of Design. If the substitute is one of our fixtures, pull the spec sheet for the exact SKU, for example through our warehouse lighting fixtures pages, and compare it line by line with the schedule.

Control or electrical interfaces. Route any affected interface to the responsible qualified reviewer instead of resolving it in the field. On VA construction projects, VA lighting coordination checks include luminaire layout, control-device location and sensor performance, driver compatibility with control devices, and coordinating circuiting with control zones and devices. That list belongs to VA projects. It works as a scoped example, not a rule for every commercial job.

If a change affects circuit design or may alter code or permit approval, do not release it on the previous approval alone. The responsible qualified professional should assess it and confirm the applicable requirements with the project jurisdiction or authority having jurisdiction (AHJ) as needed.

If the trace sends you back to site inputs or fixture comparison, our commercial lighting planning guide covers those earlier steps.

Recheck Scope and Documents Touched by the Change

Quantity and scope changes spread through paperwork, not just the plan view. Trace the changed numbers into each record that encodes them, and flag only the records that depend on the revision.

  • Quantities and phases: Compare revised counts, affected areas, or phases with the approved scope and fixture schedule.
  • Controlled documents: List each drawing, schedule, or specification that carries the changed assumption, with its current revision and owner.
  • Procurement records: Check purchase orders, release lines, or submittals only where the changed quantities or items appear in them.
  • Budget and schedule records: Flag them for review when the change touches cost or timing. Record an impact only when project evidence shows one.
  • Remaining dependent decisions: Note any decision built on the old scope, such as a phased delivery plan, and mark whether it needs revision, review, or no change.

Documents whose assumptions did not change stay closed. Downstream effects you cannot settle yet should be listed as open items, not quietly assumed resolved. Before any affected order lines move forward, run them through a bulk order release checklist against the revised quantities.

Build a Revision Record Before the Change Proceeds

A usable record lets someone who missed the meeting see what changed, who checked it, and what is still pending. Build it in this order and adapt the field names to your project's own workflow.

  1. Baseline and change. Record the project and revision identifiers, the approved baseline document and its revision, and the proposed change in before-and-after terms.
  2. Dependency and document trace. List affected assumptions and confirmed unaffected items in separate columns. Give the reason for each and link the drawing, schedule, specification, or other record behind it.
  3. Reviewer and evidence per check. For each affected check, name the responsible reviewer and the evidence or document they consulted. One general owner for the whole change is not enough.
  4. Disposition and open items. Record each check's status, decision, and date or revision reference. Carry unresolved questions and approvals forward, and mark the change as pending, held, or cleared under your project's process.

Keep one rule firm: the previous approval is not a disposition for the revised design. An item counts as unaffected only when the record shows why. An item nobody has reviewed yet stays open.

Some projects define this route formally. For VA projects, written deviation requests and approval follow a set path. The architect/engineer (A/E) submits the request to the contracting officer (CO) and AHJ through the project manager (PM) or contracting officer's representative (COR). The request includes the reason and a technical narrative. It also includes deviation drawings and lighting and engineering calculations when applicable, cost and schedule impact estimates, and supporting documents when applicable. The manual treats the deviation as approved only after the A/E receives written approval signed by the CO and AHJ. Other commercial projects may use different routes.

Who owns which record also varies by project. WBDG describes commissioning documentation as a historical record of key decisions, with documentation responsibilities designated in the Owner's Project Requirements. Where your project has that document, check it to see who maintains the revision record.

FAQs

Which version counts as the approved baseline when drawings conflict?

Use the version your project's controlled approval record identifies as approved, with its revision number. A newer markup or an emailed schedule does not replace it until it goes through the same approval process. When two versions conflict, record both and have the document owner confirm which one controls before tracing the change.

Does a small change reopen the whole lighting plan?

No. A limited revision reopens only the decisions that depend on the changed item. A single swapped fixture type, for example, may affect its schedule line and related control conditions while leaving unrelated zones closed. Those zones stay closed only when the record shows they do not depend on the change.

Who decides whether a revision affects code or permit approval?

That call belongs to the responsible qualified professionals and the authority having jurisdiction for the project's location. Requirements vary by jurisdiction and adopted codes, so no single nationwide procedure applies. Identify the jurisdiction first, then route the question through that project's review process.

Can affected fixtures be ordered while the revision is still pending?

Holding the affected order lines until their checks have a recorded disposition keeps procurement aligned with the reviewed design. Lines the record shows are unaffected can continue under the existing approval. Anything still marked pending or held should stay out of the release.

More to Read

One or Two Lighting Control Zones? Base the Choice on Different Schedules Oct 10, 2026 One or Two Lighting Control Zones? Base the Choice on Different SchedulesA planning guide for commercial facilities: group areas that share a control response, and split only where a schedule or task needs... When a Commercial Lighting Upgrade Should Keep Some Existing Fixtures Oct 10, 2026 When a Commercial Lighting Upgrade Should Keep Some Existing FixturesAn area-by-area guide to retaining existing commercial fixtures, with a keep, replace, or verify-first table, shared-control checks, and records to collect. Commercial Exterior Lights Near Glass: Reduce Window Reflections Before Adding Output Oct 10, 2026 Commercial Exterior Lights Near Glass: Reduce Window Reflections Before Adding OutputA troubleshooting path for window glare from site lights: find candidate fixtures from the indoor view, test aim against coverage, then review...

Escribir un comentario

Tenga en cuenta que los comentarios se tienen que aprobar antes de que se publiquen.