Why Photometric Plans Get Rejected at Plan Check

Photometric plans are usually rejected for technical completeness, not for aesthetics. A reviewer is asking a narrow question: does this package prove that the installed lighting will meet the governing requirements? If the answer is incomplete, the plan comes back with comments.

The good news is that most rejections follow the same patterns. Once you know where review friction occurs, it becomes easier to structure the package the way a plan checker expects to read it.

The Plan Never States the Governing Criteria

A photometric report that shows numbers without a code reference forces the reviewer to do the interpretation. That is the fastest route to a correction notice. The current IES reference for parking and circulation work is ANSI/IES RP-8-25, but many jurisdictions layer their own maintained thresholds, uniformity ratios, shielding rules, or property-line limits on top of that baseline.

If a package does not identify the applicable jurisdiction criteria directly in the set, the reviewer has no quick way to confirm whether the calculations are acceptable. Strong submittals solve that problem with a short compliance note that names the governing section and summarizes the values being checked.

The Fixture Information Is Incomplete

A calculation report is only credible if the fixture schedule tells the reviewer what was modeled. Missing distribution types, vague wattage descriptions, or incomplete mounting notes make it impossible to compare the drawing set to the calculation package.

This is especially common on projects where the design team starts with a generic manufacturer study and then swaps fixtures late. The reviewer will flag that inconsistency because there is no documented basis for the final performance. A permit-ready set should identify the luminaire family, distribution, wattage, mounting height, and any shielding or aiming assumptions used in the model.

There Is No Property-Line Analysis

Reviewers expect the lighting designer to prove that the site works at the edge as well as the center. Many rejection comments are triggered by missing perimeter values rather than by the main grid itself. If the calculations stop inside the parking field or canopy area, the submittal is incomplete.

Municipal codes often publish explicit trespass limits. Bonney Lake, for instance, limits rear and side property lines adjacent to residential or rural uses to 0.1 fc. That kind of requirement has to be shown in the package with actual property-line points. Without it, the reviewer is left to assume the edge condition has not been checked.

The Package Mixes Average, Minimum, and Uniformity

Another common failure point is treating the average illumination value as the only measure of compliance. Reviewers usually care more about minimums and uniformity because those metrics reveal dark zones and uneven lighting. A plan can show a respectable average and still fail the actual standard.

SeaTac’s parking-lot table illustrates the issue. District 1 and 2 lots require at least 0.5 fc, no more than 7.5 fc, and a maximum-to-minimum ratio of 15:1. A package that reports only an average does not answer the question the reviewer is actually asking.

The solution is not more graphics. It is cleaner reporting. The plan should state the minimum, maximum, average, and ratio in one place and make it easy to compare those values against the published requirement.

The Background and the Report Do Not Match

Reviewers also reject plans when the site background, pole layout, and calculation report are not coordinated. A fixture shown on the drawing but omitted from the report, or a report generated from an outdated background, immediately raises trust issues. Once that happens, even the correct parts of the package are scrutinized more heavily.

Good packages remove that ambiguity. The pole and fixture tags on the plan align with the schedule. The calculation grid covers the same scope shown on the background. The compliance summary references the exact fixture family and mounting heights shown in the drawing set. In other words, the package reads as one document rather than four separate attachments.

How to Reduce Rejection Risk

The fastest way to reduce plan-check comments is to think like the reviewer. Give them a technical record they can verify quickly: the governing criteria, a coordinated fixture schedule, a full-site calculation grid, property-line values, and a concise compliance summary. When those elements are aligned, review becomes administrative rather than investigative.

If your team is trying to avoid a second review cycle, start with the live service documentation or send your project details for a permit-ready package built around plan-check expectations.