Multi-location lighting standards work best as two linked records. The first is a portfolio baseline that lists the requirements every covered site shares. The second is a site exception log that records where a ceiling, mounting, or task condition changes how one of those requirements applies.
This split lets you standardize lighting across multiple commercial locations without assuming one fixture or layout fits every building. It is a project-coordination template, not a technical or legal standard. A requirement stays shared only while its intended use is the same at each site. When a site condition changes that use, open an exception, record the evidence, and carry the resolved decision into that site's own specification or order.
Set Up a Portfolio Baseline and a Linked Site Exception Log
Build two records that point to each other, so a site difference can never quietly overwrite the shared requirement. The fields below are a suggested coordination format you can adapt to your own tracker or spreadsheet.
-
Portfolio baseline record (one per shared requirement)
- Project intent: what the requirement is meant to achieve in the space
- Covered sites: the locations the requirement is meant to apply to
- Shared requirement: the wording every site starts from
- Source and owner: where the requirement came from and who can change it
- Version: a revision number or date so later records can cite it
-
Site exception log (one entry per site condition)
- Exception ID: a unique reference, such as site code plus sequence number
- Site and area: the building and the specific room, zone, or bay
- Affected requirement: the baseline item and the version it was checked against
- Status: where the review stands right now
- Downstream document: the site specification or order that will carry the decision
The version link matters most. If the baseline changes later, each exception still shows which version it was reviewed against. That tells you which site decisions need a second look.
Federal renovation guidance shows why the site record exists. The VA Lighting Design Manual directs design teams on renovation projects to investigate and document pre-existing conditions and to take those findings into account in planning and design. That manual covers VA facilities, but the logic carries over: a site condition only shapes the design if someone records it. For high-ceiling bays where commercial fixtures are standardized, planning alternatives like linear high bay lights need an explicit exception record if existing deck structural attachments or mounting heights vary.
Does your team also collect building energy audit data? DOE's Audit Template tool offers standardized audit data entry, validation, and export, with support for local audit requirements. Keep it as a separate record next to your lighting exception log. It does not replace that log.
Use Ceiling, Mounting, and Task Conditions to Classify Requirements
Keep a requirement shared while a site's condition leaves its intended use unchanged. Flag it for site-specific review when ceiling, mounting, task use, or local rules could alter that use. A visible difference alone does not require a redesign, but it signals a check before moving forward.
| Site condition | Keep shared when | Flag for review and record |
|---|---|---|
| Ceiling | Height and construction match the baseline's assumption | Different height, ceiling type, or construction; record photos and measured height |
| Mounting | The available mounting method matches the common plan | Different structure or mounting method; record the actual condition, not assumed fit |
| Task or area use | The space serves the same purpose the requirement targets | A different task or use in the area; record the activity and the zone it covers |
| Local requirements | The jurisdiction's review is confirmed for this site | A different jurisdiction or unconfirmed rules; record the jurisdiction and the reviewer |
Treat this matrix as a planning test that sorts site conditions for review, not as an engineering rule. Ceiling conditions carry real design weight. The VA manual, for example, calls for coordinating interior luminaire layout with ceiling type, construction, and plenum depths in its projects. A ceiling that differs from the baseline assumption belongs in the log, even if the review later finds the shared requirement still works.
Task differences can hide inside one building. A single site may hold storage, picking, and packing areas, each with its own lighting question. Our mixed-task warehouse example shows how zones and task areas can be mapped before a layout review. When a flagged task or ceiling difference needs layout work, a site-specific lighting design review can address that site without changing the portfolio baseline.
Local rules cannot be assumed to be the same across the United States. This template does not decide code compliance. For each site, name the project jurisdiction and have the responsible design professional or authority having jurisdiction confirm what applies there.
Record the Evidence and Disposition for Each Exception
A good exception entry lets a reviewer who never visited the site see what differs, why it matters, and where the decision stands. Fill it in this order:
- Identify the item. Record the exception ID, site, area, affected baseline requirement, and the baseline version it was checked against.
- Describe the observed condition. State the ceiling, mounting, or task condition in plain terms, such as "open deck with no suspended grid in Bay 3."
- Attach the source. Link a labeled photo, survey note, or measurement, and note who captured it and when.
- State the project question. Write what the condition could change, such as "Does the shared mounting assumption still apply here?"
- Assign review and status. Name the reviewer, then mark the entry open or record the written disposition and its date.
Step 3 decides whether the entry holds up later. A note that says "ceiling is different" gives a reviewer nothing to act on. A labeled photo plus a measured height gives them something they can check. For a field-ready capture routine, our site survey photo checklist covers zone records, measurements, labeled photos, and access notes.
If evidence is missing, say so in the entry and leave it open. An exception with no source attached should not move to review.
Carry Resolved Site Decisions Into Project Documents
Move an exception into a site specification or order only after its disposition is recorded. Then link the two so the decision stays traceable in both directions. The status labels below are suggested names, not formal industry codes.
- Open. The item is logged but not decided. Keep it out of the specification or order as an approved item. If the document must go out, list it as an open decision.
- Resolved. The responsible reviewer has recorded the disposition, who made it, and when.
- Documented in project. Copy the exception ID and disposition into the affected site specification or order. Note that document's version, then add the document reference back into the log entry.
The visible result is a log entry that shows its status and names the exact site document and version that carries the decision. Anyone can follow that link from the order back to the evidence.
Keep the baseline and the site decision separate in those documents. A resolved exception changes one site's record, not the shared requirement. If the same exception keeps appearing across sites, send it to the baseline owner as a proposed revision with a new version number.
Clear records are also a design-document expectation. The VA manual states that lighting design documents should show clear, complete and correct information in its project context. When you send a site package out for pricing, a supplier-ready lighting RFQ can list the site's open decisions next to its resolved requirements. That way suppliers quote what is settled and flag what is still pending.
Keep each site disposition traceable in its own project document. That is what keeps multi-location lighting standards consistent without hiding real site differences. Before releasing purchase orders or work scopes, review your open log to verify that every flagged ceiling, mounting, or task condition has an approved disposition recorded.
FAQs
What should we do if a site changes after its exception is resolved?
Open a new exception entry that references the earlier one instead of editing the resolved record. The new entry captures the changed condition and its evidence. The original shows what was decided before. Any site document tied to the old decision should be reviewed and reissued with a new version.
How do we handle a condition we cannot observe yet?
Log the exception anyway and mark it open. Note what is missing, such as a ceiling area you can't access, and what evidence would close the gap. Do not assume the shared requirement applies until someone has captured and reviewed that evidence.
Does a portfolio lighting baseline prove that every site meets code?
No. A baseline records the requirements your organization wants shared. It does not decide which codes apply at a given address. Each site still needs review for its own jurisdiction by the responsible design professional or authority.
Can one site have several exceptions against the same requirement?
Yes. Give each distinct condition its own exception ID, even when they affect the same baseline item. For example, a ceiling difference and a task difference in separate zones may get different dispositions, and separate entries keep each decision traceable.
