If only one zone of your facility has changed, send a short request that names that zone and describes the change. Then label every other condition as verified, reported, or unknown. Note any links to nearby areas or shared controls, and ask the reviewer straight out whether your proposed boundary is enough.
Your boundary is a proposal. The reviewer sets the final scope. A formal permit or authority review follows your jurisdiction's rules, and the US has no single national process for it.
Prepare a Request for the Changed Zone
A good lighting review request tells the reviewer where to look, what changed, and what you assume about the rest of the site. It also asks one clear question about scope. Copy the fields below into an email or intake form and fill in what your team knows:
- Project and site: [Facility name, address, and any project or work order number]
- Changed zone: [Room number, area name, floor, gridline, or drawing sheet the reviewer can use to find it]
- What changed: [Layout, lighting equipment, use, or task change], [date of the change, if known]
- Conditions elsewhere: [Each relevant item outside the zone, tagged verified, reported, or unknown]
- Possible connections: [Shared controls, adjacent areas affected by the change, activities that cross the boundary, or "none known"]
- Scope question: "We propose limiting this review to [zone]. Is that boundary sufficient, or what other areas or information do you need?"
These fields are a suggested structure, not a required form. If your reviewer has its own intake sheet, put the same details into that sheet when planning commercial lighting updates.
Be specific about what kind of change it is. A physical change, like moved racks or swapped fixtures, is easy to describe. A change in use or tasks is easy to leave out because the room may look the same. Say a storage area became a packing station. Spell that out, because the new task may be the whole reason you need a review. Describe the change only. Don't add your own guess about the design fix or whether the space meets code. That call belongs to the reviewer.
Separate the Change From the Baseline
Keep the changed zone and the rest of the facility in separate columns. Give every unchanged item a status that matches what your team actually knows. Use the checklist below as a prep aid and keep the cells short.
| Condition | Changed zone | Rest of facility |
|---|---|---|
| Layout | What moved, opened, or closed | Verified / reported / unknown |
| Lighting | Fixtures added, removed, or replaced | Verified / reported / unknown |
| Use | Old use vs. new use | Verified / reported / unknown |
| Tasks | New or different work done there | Verified / reported / unknown |
| Information used | Site visit, photos, or drawings | Name and date of the record |
"Verified" should mean someone recently checked the condition. "Reported" means a team member says it hasn't changed but nobody confirmed it. "Unknown" is a fair label, and it beats a guess.
If an old lighting plan or as-built drawing informed your baseline, name it as the source you used, such as "[drawing title], [date]." That tells the reviewer where the information came from. It doesn't claim the drawing still matches the site.
Some project owners spell out this split in writing. For VA renovation projects, the VA Lighting Design Manual calls for documenting pre-existing conditions and clearly showing the interfaces between renovated and existing-to-remain areas on the drawings. Treat that as one owner's approach for its own projects. It isn't a rule for private facilities, but it shows why a clear changed-versus-unchanged line helps.
Flag Connections Beyond the Zone
List anything that might tie the changed zone to space outside it, and ask the reviewer whether each item changes the scope. You're disclosing, not deciding. A connection doesn't automatically mean the review has to grow.
- Shared lighting controls: Do the zone's lights share a switch, sensor, or schedule with another area? Name the other area. Ask whether it belongs in the review or whether the reviewer needs control details.
- Adjacent areas affected by the change: Did the change affect a corridor, doorway, or neighboring room, for example a new opening or a different traffic path? Ask whether that space should be added.
- Activities that cross the boundary: Do people or equipment now move between the zone and nearby space as part of the new task? Describe the path and ask whether it changes the review area.
- Unknown relationships: If you can't tell whether something is shared, mark it unknown. Then ask what information would settle the boundary question.
Control links can tie spaces together by design. The VA manual includes one case for its facilities. If a nourishment station is open, its overhead lighting is controlled with the adjacent area. That example is specific to VA projects. Still, it shows the kind of link worth mentioning so the reviewer can weigh it.
Outdoor sites raise the same question at their edges. Our guide to outdoor yard zone mapping shows how storage rows, access lanes, and boundaries can be split into separate zones with stated assumptions.
Choose the Review Route
Send advisory requests to your design or service contact. Send formal submissions to the authority with jurisdiction over your project. The two routes have different recipients and rules, so you can't swap one for the other.
- Design or service review: Send the request to the lighting designer, service provider, or internal facilities reviewer working on the project. Ask what intake information they need and whether they accept a zone-limited scope. If they ask for a photometric layout, our guide to project-ready photometric layouts explains how layouts fit into commercial project planning.
- Formal permit or authority review: Find out which jurisdiction covers the project. Then check that agency's current instructions, application, required materials, and recipient before you send anything. Requirements vary by locality, so don't reuse another jurisdiction's checklist.
Local processes can include steps you won't see in a private review. Take Multnomah County's Mid-County Lighting District process in Oregon. Applicants should have been referred by another agency. Before applying, they contact the County with the project location to see whether a lighting plan is already on file for the area. When an application is needed, the County asks for photometric calculations covering all the public streets required for that process. That process covers public streets in one district, not facility interiors. It shows why you should check the right agency's records and current steps first.
FAQs
What if we have no current record of the rest of the facility?
Tag those conditions as unknown and say so in the request. Then ask the reviewer whether a walkthrough, photos, or other records are needed before they can respond on scope. For outdoor wall-mounted areas, our wall pack replacement survey shows one way to record mounts, power, and controls with labeled photos.
Will a reviewer automatically accept a one-zone scope?
No. A one-zone boundary is your proposal. The reviewer may accept it, expand it, or ask for more information. A clear baseline and an honest list of connections give them what they need to decide.
Should the request include the lighting fix we have in mind?
Keep the request focused on what changed and how the space is used now. You can mention a preference if one exists, but present it as context, not a conclusion about design, performance, or code compliance. The reviewer evaluates those points.
What should we confirm before relying on a local submission route?
Confirm which agency has authority over the project and whether you need a referral first. Ask whether the agency already has a plan on file and which form and materials are current. Get the answers from that agency directly, since steps differ by jurisdiction.
