Use one commercial lighting project brief for the entire portfolio: start with a project index, then duplicate the same record for every phase, building, and zone. Mark each input as confirmed, estimated, assumed, or missing, and assign an owner and next action to anything uncertain. Submit the package for design review only when unresolved gaps cannot change the review or have an explicit owner and follow-up action.

What a Commercial Lighting Project Brief Should Include
A practical brief has two linked layers. The project-level index explains the goals, scope, phases, and naming conventions. The repeatable location record captures the evidence that varies from one building or zone to another. This is an adaptable intake structure, not a universal or regulated form.
| Record level | Fields to capture | Why it matters |
|---|---|---|
| Project-wide index | Project name and owner; contacts; stable building and zone naming map; scope and priorities; phases and target timing; operating or shutdown assumptions; requested design deliverable; project-wide controls, commissioning, and operations and maintenance expectations | Keeps shared decisions in one place and separates current, planned, future, and out-of-scope work. |
| Repeatable phase, building, and zone record | Phase and location path; plan or sketch reference; overview and detail photos; length and width; ceiling or mounting height in feet; task or activity; operating hours; existing fixture type, quantity, and visible wattage or label information; controls; relevant electrical notes; access constraints; priority; source and status; open questions | Prevents a portfolio average from hiding differences in layout, tasks, schedules, fixtures, controls, or access. |
Duplicate the second row for every in-scope location, including locations in different phases. An area-by-area inventory that records fixture type, quantity, wattage, and operating hours is a useful field practice, as shown in the FEMP lighting retrofit workbook. Keep location-linked luminaire and controls schedules cross-referenced to drawings and records so equipment and controls remain unambiguous, consistent with professional specification guidance.

Set Project-Wide Priorities, Phases, and Building Names
Normalize the portfolio before collecting site evidence. Create a project index with stable short names or IDs and use one path throughout the package: Project > Phase > Building > Zone. Treat that path as a project convention the owner, contractor, and design team can maintain, not as a required software or file format.
For each phase, list the included buildings and zones, target timing, access or shutdown assumptions, decision owner, and expected design-review deliverable. Mark current, planned, future, and out-of-scope work separately. Record the priorities that guide trade-offs, such as schedule, budget assumptions, controls preferences, special requirements, commissioning expectations, or operations and maintenance deliverables. These categories align with owner-requirements guidance for lighting systems, but the actual priorities remain project-specific.
Before gathering photos or measurements, test the index with a simple question: can someone identify the phase, building, and zone from any record without relying on local knowledge? If not, fix the naming map first. That small step prevents evidence from drifting between buildings as the project moves through phases.
Build One Complete Record for Every Building and Zone
Repeat a location-specific record for every in-scope building, zone, and phase. Do not infer missing facts from a similar building or a single fixture photo. Keep the source of every plan, measurement, fixture note, and controls observation visible.
Document the Space, Tasks, Schedule, and Access
Attach the latest plan, sketch, or marked-up drawing, along with overview and detail photos. Record the zone's length and width, ceiling or mounting height in feet, notable obstructions, mounting surfaces, and any access limitations. If dimensions are approximate, label them that way.
Describe what people do in the space, what must be visible, normal operating hours, occupancy or activity patterns, seasonal changes, and after-hours access needs. State the zone priority and any phase or shutdown constraint that could change the design question or field-verification plan. A practical survey should cover the space description, worker tasks, operating hours, current lighting, and controls, as outlined in the FEMP lighting checklist.
Record Existing Fixtures, Controls, and Electrical Information
Identify each existing fixture type, quantity, mounting location, visible wattage or label information, condition, and current disposition: retained, replaced, relocated, or unknown. Record switches, occupancy or daylight sensors, dimming, time schedules, and observed control behavior when present. Posted schedules may be overridden, so label the source and use qualified verification when actual behavior affects the review. DOE's controls evaluation protocol supports treating fixture inventory, wattage, quantities, operating hours, and control behavior as verifiable inputs rather than unsupported assumptions.
When relevant and available from labels, schedules, or qualified field records, document supply voltage, fixture wattage, total load, inrush current, sensor rating, and 0–10 V compatibility. These are documentation prompts for professional review, not proof of compatibility, load suitability, wiring requirements, or code compliance. Do not provide wiring instructions or an approval determination in the brief.
Label Plans, Photos, and Measurements So Every File Has a Home
Assign stable phase, building, and zone names before renaming or uploading evidence. Use the same location path in the brief, filenames, captions, measurement notes, and plan references. A descriptive label can include the location, phase or status, area, and view or equipment subject, but the exact syntax should fit the team's workflow.
For photos, identify the view or subject, such as an entry, fixture label, control device, obstruction, or mounting point. Connect each image to the relevant zone record. For each measurement or note, record who supplied it, the collection date, whether it is confirmed or approximate, and the plan or photo it supports. A utility checklist offers an example of descriptive photo naming, but its identifiers are not mandatory for unrelated projects.
Keep fixture and controls schedules linked to locations and cross-referenced to drawings. Before submission, trace one sample from the project index to its phase, building, zone, plan, photo, measurement, and open question. If any link is unclear, correct the record or label the gap before adding more files.
Match Verification Effort to Ceiling Height, Task, and Fixture Type
Use this qualitative matrix to prioritize the next field check. It does not select a fixture, calculate light levels, provide an installation method, or determine code compliance.
| Zone condition | Inputs to verify closely | Review consequence |
|---|---|---|
| Low or accessible ceiling with general circulation | Dimensions, fixture spacing, operating hours, and controls behavior | Missing basic layout or schedule information can leave the zone's review question undefined. |
| High-bay or high-mounted area | Mounting height and point, obstructions, access method, fixture label, voltage, wattage, and controls | Unclear access, labels, or mounting information should be assigned for closer field verification before review. |
| Task-focused area, such as production, inspection, storage picking, or office work | Specific task location, activity, work-plane height when known, operating schedule, existing fixture placement, and priority | A general room name may not describe the visual task or the information the design team needs to review. |
| Mixed fixture or control zone | Fixture types and quantities, documented circuits or control groups, sensor locations, and dimming details | Separate references or records may be needed before replacement scope or controls questions can be compared. |
This closer-attention guidance is a planning heuristic: higher or obstructed mounting points, demanding tasks, and mixed systems generally justify clearer plans, labels, photos, access notes, and controls records. Assign the next verification action rather than assigning a numeric score.
Mark Every Input and Decide Whether to Submit
Use one status for every decision-relevant field:
- Confirmed: supported by a current plan, label, observation, measurement, or qualified record.
- Estimated: an informed approximation with its source, date, owner, and consequence if it changes.
- Assumed: a working condition that still needs confirmation, with an owner and follow-up date.
- Missing: unavailable information with one concrete next action, such as measuring, taking a photograph, obtaining a plan, confirming controls behavior, or scheduling access.
Submit the normalized brief when every in-scope building, zone, and phase has a traceable record, the design question and priorities are clear, and remaining estimates or assumptions are explicitly owned. Pause and gather information when a gap could change zone boundaries, task coverage, mounting or access assumptions, fixture replacement scope, electrical or controls review, phase scope, or the requested deliverable. This is an intake decision, not a code approval, electrical sign-off, commissioning result, or guarantee that field conditions match the records.
When the package is complete, send it for qualified design support. If the next step also requires comparable contractor quantities, controls notes, and timing information, use this commercial lighting quote package checklist as an optional follow-up. Otherwise, gather only the specifically flagged inputs first, then submit the normalized brief.
Commercial Lighting Project Brief FAQ
What information does a lighting designer need for a multi-building commercial project?
The designer needs a project index plus location-specific records for each building, zone, and phase. The useful starting set includes plans, photos, dimensions, heights, tasks, operating hours, existing fixtures, controls, access constraints, priorities, sources, and uncertainties. A portfolio average cannot replace information tied to the actual location.
What should a commercial lighting project brief include?
It should include two linked layers: project-wide goals, phases, names, schedule assumptions, contacts, and deliverables, followed by consistent location records with a status and next action for each uncertain field. Start with the project index, then duplicate the location record.
How do I organize photos and measurements across multiple buildings?
Assign stable phase, building, and zone names first. Use that same path in filenames, captions, measurement notes, and plan references. Add a view or subject label to each photo and record the source, date, and status of every measurement or note.
When is a multi-building lighting brief ready for design review?
It is ready when each in-scope location is traceable and any unresolved item cannot change the review or has an explicit owner and follow-up action. If a missing plan, measurement, access detail, controls record, or priority could change scope, gather that item before submitting.