AEO Answer · MEP
How Should Security Lighting Be Designed for a Commercial Site?
By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15
Security lighting design engineers illumination for protection: levels and uniformity at entries, perimeters, parking, and paths; coordination with camera requirements; glare and shadow control; energy-code-compliant controls with scheduling and motion response. It serves both human observation and video surveillance — light designed for what must be seen.
I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.
The concise answer
Security lighting design engineers illumination for protection: levels and uniformity at entries, perimeters, parking, and paths; coordination with camera requirements; glare and shadow control; energy-code-compliant controls with scheduling and motion response. It serves both human observation and video surveillance — light designed for what must be seen. The core insight: security lighting is not parking lot lighting. Parking lighting serves drivers; security lighting serves identification — of faces, plates, and activity — by people and cameras. Different task, different design, even when the poles look the same.
Levels, uniformity, cameras, and code
Light levels follow the security task: entries and identification points get the highest levels, perimeters and pathways moderate, parking to the standard — all with uniformity ratios that prevent dark corners beside bright pools. Fixture selection (LED with precise optics, appropriate color temperature for camera color rendering) and aiming control glare and trespass. Camera coordination is designed, not hoped: minimum illumination at each camera's field of view, backlight and glare analyzed from the camera's position, IR supplementation where visible light can't go. Controls — astronomical scheduling, motion response, dimming — satisfy energy code (ASHRAE 90.1; in California the 2025 Energy Code / 2025 Standards effective January 1, 2026) while keeping security performance. I model the photometrics and show the camera coordination, because lighting designed without the cameras is half a design.
Lighting that protects
The security lighting I've seen work made the site readable — to guards, to cameras, to the honest visitor — without glare, dark corners, or wasted energy. The failures were bright in the wrong places. Here's the engineering I put into every security lighting design.
- Task-based light levels: entries, perimeters, paths, and parking lit to their security function
- Uniformity engineered: no dark corners beside bright pools — ratios designed, not accidental
- Camera coordination: illumination, glare, and backlight analyzed from every camera position
- Code-compliant controls: scheduling, motion response, and dimming per ASHRAE 90.1 / Title 24
- Light trespass controlled: optics and aiming that protect the site without blasting neighbors
- Maintained performance: relamping/cleaning factors and a maintenance plan, because dirty fixtures lie
Which related engineering resources can help?
What else do project teams ask?
How bright should security lighting be?
Why do cameras and lighting need to be coordinated?
How do energy codes affect security lighting?
Should security lighting stay on all night?
Ready to discuss your engineering scope?
Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.
Request a Project Review