Parking Lot Photometric Requirements — What Plan Reviewers Check

Parking lot lighting plans are rarely rejected because a reviewer dislikes a fixture cut sheet. They get rejected because the submittal does not clearly document how the site will perform after installation. Reviewers want to see visibility for drivers and pedestrians, a calculation method they can follow, and perimeter controls that keep the light on the site.

In practice, that means a parking lot photometric plan has to do more than show poles on a background. It has to tie the background, the fixture schedule, the point-by-point grid, and the jurisdiction criteria into one coherent package. If any of those pieces are missing, the reviewer is left to guess, and guesswork is what slows approvals down.

Below is what plan reviewers typically check first when a parking lot lighting package reaches the counter.

Start With the Jurisdiction Table

The first question is not whether the design “looks bright enough.” The first question is which standard governs the site. The current IES reference for roadway and parking-facility lighting is ANSI/IES RP-8-25, but cities frequently publish local thresholds on top of that baseline. A reviewer will compare your submitted values against the local table before they worry about anything else.

SeaTac is a good example. Its municipal code lists District 1 and 2 parking lots at no less than 0.5 fc, no more than 7.5 fc, with a maximum-to-minimum uniformity ratio of 15:1. District 3 and 4 parking lots are allowed to run lower, at 0.2 fc minimum and 3 fc maximum. If your plan only reports an average value, the reviewer still cannot confirm compliance with those thresholds.

This is why a permit-ready submittal should identify the governing standard directly in the plan set. It gives the reviewer a clear frame of reference and shows that the calculation package was built for the jurisdiction rather than copied from a manufacturer study.

Reviewers Check the Whole Site, Not Just the Average

Average illuminance is one data point. It is not the whole review. A parking lot can carry an acceptable average while still having dead zones at pedestrian routes, drive aisles, or lot edges. That is why most jurisdictions care about minimums and uniformity, not just the mean.

A reviewer will typically scan the calculation grid for three things:

• whether the grid covers the full paved and pedestrian scope of the project
• whether low points align with entries, exits, sidewalks, or crossing paths
• whether the maximum-to-minimum ratio stays within the published limit

The practical takeaway is simple: model the real use zones. Include the stall fields, but also the drive aisles, walk paths, access points, and the places where a reviewer expects users to make decisions. The plan should tell the full site story, not just the center of the lot.

Property Lines Get Their Own Review

Parking lot submittals are often approved or denied at the edge of the site. Reviewers pay close attention to property-line light trespass because complaints from adjacent parcels are predictable and politically visible. If the plan does not show the perimeter clearly, it invites comments even when the center of the lot performs well.

Bonney Lake, for example, limits rear and side property lines next to residential or rural uses to 0.1 fc. That kind of threshold changes how poles are spaced, how optics are selected, and whether shielding or lower mounting heights are required. It also means the grid cannot stop at the curb line. The perimeter has to be calculated and documented as part of the same package.

Reviewers want to see that the designer has treated the property edge as a real compliance condition. A clean permit set will usually show perimeter points, note the governing trespass limit, and align those values with the fixture schedule and pole layout.

Fixture Schedules and Mounting Data Matter

A calculation report without a clear fixture schedule is incomplete. Reviewers need to know what luminaire was modeled, how it is mounted, what distribution was used, and whether the submitted hardware matches the performance shown in the report. If the schedule is vague, the reviewer cannot tell whether the field installation will actually match the calculated result.

This is especially important on value-engineered projects where the fixture family may still be moving. The photometric package should identify the modeled luminaire, distribution, wattage, pole height, and aiming assumptions. If the design later shifts to a different fixture, the calculations need to be updated instead of relying on “equivalent” language.

The more precisely those schedule notes are tied to the site plan, the easier it is for the reviewer to approve the package without a clarification cycle.

Before You Submit

A strong parking lot photometric submittal reads like a technical record, not a sales sheet. It identifies the governing criteria, shows the full site grid, documents the property line, and ties every calculated result back to the actual fixture schedule.

Before filing, confirm that the package answers five questions clearly:

• Which code or standard governs the lot?
• What are the minimum, maximum, and uniformity targets?
• How is light controlled at every property edge?
• Which fixtures, mounting heights, and distributions were modeled?
• Does the permit set include a compliance summary a reviewer can read quickly?

If you need that package assembled for an active submittal, our parking lot photometric plan service is built around those exact review points. You can also request a quote if the site is already headed into plan check.