Uncertain Building Dimensions? Model Scenarios Before Locking a Lighting Plan

When building dimensions are uncertain, don't treat one assumed number as settled. Carry each unresolved measurement as its own labeled scenario with its source attached. Then test the same lighting decisions, like fixture placement or fixture type, in every scenario.

If a decision changes from one scenario to another, keep it provisional and verify that input before you lock the plan. This approach won't predict exact fixture counts or final light levels. It shows you which unknowns actually matter, so your measuring time goes where it changes the plan.

Treat Uncertain Dimensions as Scenarios, Not Settled Inputs

A dimension belongs in a lighting plan only when its value, source, and status travel with it. A useful record has four parts: the value, where it came from (a preliminary drawing, a survey, a field estimate), its status, and any conflict with another source.

Keep the status labels separate. Confirmed means someone measured it on site and wrote it down. Estimated means it came from a rough field check or an assumption. Conflicting means two sources disagree and neither has been checked yet. Don't merge these labels just to make the plan look finished.

Here is a simple example. The preliminary plan shows one width for a work zone. The facility manager's tape-measure estimate gives a different width. Instead of picking one, keep both. Scenario A uses the plan width, labeled "preliminary drawing, unverified." Scenario B uses the field estimate, labeled "estimated, conflicts with plan." Neither one replaces the other until the zone is measured.

Public lighting work uses this same idea. For roadway lighting, Maryland's design manual describes preliminary calculations based on existing conditions and a base plan. Those calculations are followed by field verification and documented measurements before the concept moves ahead. That manual covers roadways, not buildings. Still, the habit carries over: a concept stays preliminary while site information gets checked. The same labeling works for moving obstructions, too. If your site has overhead cranes, you can apply it when you map crane zones before layout review.

Set Scenario Bounds from the Evidence You Have

Build each scenario from a value or condition that already appears in project documents, field notes, or site records. Don't average conflicting values, and don't invent a low and high range that no source supports.

1. Gather every source for the dimension. Pull the drawings, survey sheets, field estimates, and annotated photos that mention it. Note who produced each one.
2. Make each distinct documented value its own case. If two sources disagree, you get two scenarios. An average creates a number no source supports, and it hides which source the plan really depends on.
3. Use a range only when project evidence sets both ends. A range works when documented conditions mark each limit. If only one end is documented, you don't have a range yet.
4. Mark unbounded unknowns as unresolved. Write down the measurement that would close the gap, such as "clear height above the storage area: not documented, needs on-site measurement."
5. Keep the source and assumptions in the scenario name. "Scenario B: field estimate, ceiling assumed open" can be checked later. "Scenario B" by itself can't.

Compare the Same Layout Decisions Across Scenarios

Pick one planning question, such as where a row of fixtures goes, and answer it the same way in every scenario. If the answer changes, that unknown is decision-changing. If it stays the same, it can wait.

Floor dimensions are only part of the test. For VA projects, VA guidance on coordinating luminaires ties interior luminaire layout to ceiling type and construction, plenum depths, diffusers, ceiling tracks, and ceiling-mounted objects. It also ties layout to furniture, casework, millwork, and equipment. These make good scenario inputs in other buildings as well, because an unconfirmed duct or rack could block a fixture position that looks clear on a floor plan.

Read each row as a question, not a prediction. A row only goes on the verification list if its scenarios actually gave you different answers for your project.

Formal sensitivity analysis follows the same logic in more detail. In a hospital emergency room lighting study, researchers varied luminaire type and wall reflectance in an examination room and luminaire angle in a treatment room. Then they examined how the lighting outputs responded. That study tested lighting inputs, not uncertain building dimensions. It does show the core move: change one input, hold the rest steady, and watch the result.

To run your lighting plan scenarios in software, DIALux evo's indoor lighting tools let you recreate a room from a floor plan, place luminaires in linear or grid arrangements, and calculate individual rooms. Save each scenario as its own room or project version so the results stay separate. For a quicker first pass, you can sketch the alternatives in our online lighting layout tool. When the question is fixture selection rather than position, using IES data in layout planning explains how photometric files feed those models.

Verify Decision-Changing Inputs Before Locking the Plan

Measure first the input whose scenarios gave different answers. Any input that didn't change a decision can stay labeled as an assumption until it does.

1. Rank unknowns by the comparison result. An input that changed a placement or selection decision goes to the top. No numeric risk score is needed: the test is whether the answer moved.
2. Verify that input on site and document it. Maryland's roadway-lighting manual follows a similar order and includes later site checks of proposed work to confirm the design can be built under current conditions.
3. Update the scenario set. Swap the resolved alternatives for the verified value, then rerun only the decisions that depended on it.
4. Lock stable decisions with their assumptions attached. A result that held across every scenario is ready to use. The dimensions behind it are still unconfirmed, so keep the assumption written next to the decision.
5. Reopen the comparison when new information conflicts. A revised drawing or a new field note that disagrees with a locked input sends the affected decision back to step 1.

Once the heights and areas behind fixture type and spacing are verified, you can re-check quantities with our guide to calculating warehouse fixture counts. For high-ceiling spaces, you can then compare options in our linear high bay lights and LED high bay lights collections. If the project needs photometric planning across several cases, our lighting design support page is the place to start.

FAQs

What should I do when the drawing and a field measurement disagree?

Keep both values in the plan as separate scenarios, each labeled with its source. Don't average them or quietly pick the one that looks more likely. If the two cases lead to different fixture decisions, measure that dimension on site before those decisions are final.

What if none of my scenarios change the layout?

Then no single unknown has to jump the line for verification. You can move forward with the decisions that held steady. Write the unconfirmed dimensions next to them, though, so a later drawing revision or field note can flag a conflict.

Can I choose fixtures before every dimension is confirmed?

You can settle a fixture choice that stayed the same across all of your documented scenarios. Keep quantity, mounting, and placement provisional anywhere the scenarios disagreed. Reassess the choice if a verified measurement falls outside the cases you modeled.

Does a scenario model predict how the finished space will look?

No. A scenario comparison shows whether an uncertainty changes a planning decision. It doesn't confirm installed light levels. Final results depend on verified dimensions, the actual fixtures and their photometric data, and the conditions in the space after installation.