To plan parking lot pedestrian lighting, draw the routes people walk from parked cars to the building on their own layer of the site plan. Keep that layer separate from the stall and drive-aisle coverage. Then mark every crossing and possible obstruction, and compare the finished map with the proposed area-light positions before anyone finalizes them.

A layout built around vehicles shows where cars park and drive. It can miss the path a shopper takes between two parked SUVs to reach the front door. The worksheet below is a practical project tool, not a lighting standard. It ends with a list of the places that still need review for your specific project.
Map the Walking Routes from Parking to Entrances
Start with a copy of the site plan and add a separate layer that shows only people on foot. This can be tracing paper over a printout or a separate markup layer in a PDF or CAD file. Keep the vehicle lighting coverage off this layer so the walking routes stand on their own.
- Mark the destinations. Label every building entrance people use, such as the main door, staff door, deliveries, and any accessible entrance.
- Mark the origins. Outline each parking area, row, and drop-off zone where people leave their cars. Label accessible parking spaces separately.
- Draw the designated walkways. Use solid lines for sidewalks, striped walkways, and marked paths that the site already provides.
- Draw the routes people actually take. Use dashed lines wherever real foot traffic leaves the designated path, like a shortcut across stalls or straight across a drive aisle. Watch the lot at a busy time or ask staff where people walk.
- Break each route into segments. Start a new segment wherever a route changes direction or meets a vehicle aisle. Number them (A1, A2, B1) so you can mark crossings and review each one later.
- Connect accessible spaces to their entrances. Draw a line from each accessible space to the accessible entrance it serves.
That last step has its own guidance. The Access Board says accessible parking spaces must be located on the shortest accessible route to an accessible entrance, relative to other spaces in the same facility. Where parking serves multiple entrances, accessible spaces must be dispersed among the accessible entrances. This is an accessibility routing rule, not a lighting rule. Still, it tells you which route lines must appear on your layer before any light position gets reviewed.
If you have used a zone map for floodlight placement, this layer works in a similar way. You are defining the areas people move through before you judge where fixtures go.
Mark Crossings and Potential Obstructions
Every place where a walking route meets moving vehicles gets its own mark, and so does anything that may affect how a route or crossing gets reviewed. Put these marks on a second layer, or use a distinct color, so they don't blend into the route lines.
- Drive-aisle crossings: Mark each spot where a route segment crosses an internal aisle. Label them C1, C2, and so on, and note which segments they connect.
- Driveway and entry crossings: Mark where routes cross lot entrances, exits, or drive-through lanes.
- Roadway crossings: Flag any point where a route leaves the lot and crosses a public street. Keep these labeled differently from internal aisles, because different guidance applies.
- Parked-vehicle positions: Note rows where a route runs between, beside, or behind parked vehicles. Add a note if taller vehicles, such as vans or pickups, park there.
- Other site features: Mark landscaping, dumpster enclosures, signs, columns, cart corrals, and existing poles that sit along a route or near a crossing.

Treat each note as a condition to review, not as proof that the lighting falls short. A parked-car note tells the lighting reviewer where to look. It doesn't settle what that spot needs.
Roadway crossings have a documented review method. For uncontrolled crossings, the FHWA guide describes building a site base map and a crossing inventory that records crossing lighting and sight distance. That inventory covers items like overhead lighting and the visual clearance of the crossing. Use those items for your roadway crossing marks. FHWA wrote this guidance for crossings on roadways, so keep your internal aisle marks as worksheet notes for the project reviewer.
Compare the Route Map with Proposed Light Positions
Lay the route and crossing layers over the proposed lighting plan and work through them one mark at a time. You should end up with two lists: locations the proposal clearly considered and locations it leaves unresolved.
- Align the layers. Overlay the route map on the proposed plan at the same scale, matching building corners and curb lines.
- Review each route segment. For A1, A2, and the rest, note whether the proposal shows a light position that relates to that segment. Write "considered" or "unresolved" next to each number.
- Review each crossing and obstruction note. Give every C mark and every parked-vehicle or site-feature note the same label.
- Check roadway crosswalks for contrast. At crosswalks on a roadway, FHWA describes positive contrast as the goal, so drivers can pick out the pedestrian. It also advises placing luminaires in forward locations to avoid silhouetting pedestrians. Note whether the proposed positions sit in front of the crosswalk from the driver's view or behind it.
- Check poles against route lines. Mark any proposed pole that sits in a walking line, in a parking row, or next to a crossing.
- Send the unresolved list forward. Hand the list, with segment and crossing numbers, to the lighting designer or engineer on the project.
Step 5 has a useful reference point. In its parking guidance for military installations, the Army Transportation Engineering Agency recommends poles in protected islands or at stall junctions. Its ideal is center or side islands protected by raised curbs. When poles must go in parking rows, it places them at the junction between stalls to minimize obstruction. That guidance was written for military installations, but it gives you a clear question to ask about any pole on your overlay.
Keep the roadway crosswalk check in step 4 at roadway crosswalks. It doesn't set a numeric target, and it isn't a rule for internal lot routes.
Before you approve final positions: The overlay shows what the proposal considered. It can't tell you illumination levels, uniformity, or whether the layout meets local requirements. When the project needs those answers, get a photometric design and a review by the local authority before you sign off. No jurisdiction-specific rule is assumed in this worksheet.
For that next stage, our lighting simulation overview explains how we prepare 3D visuals and foot-candle charts from the building information you provide. If the proposal includes floodlights aimed toward walkways, our guide to floodlight beam control and glare covers aiming considerations. Once a designer assigns a fixture type to a segment, you can compare outdoor LED fixture categories or pathway lighting options against that segment's notes.
FAQs
Should I plan around the designated walkway or the route people actually take?
Plan around both. If people cut across stalls instead of using the sidewalk, a layout that only follows the sidewalk leaves the real route out of the review. Draw both lines, flag where they differ, and let the project team decide whether to address the observed route, change the site layout, or both.
Does FHWA crosswalk guidance apply to drive aisles inside a parking lot?
The FHWA sources used here cover crossings and crosswalks on roadways. They don't set a method for internal parking lot aisles. Use them for any route that crosses a public street, and treat internal aisle crossings as separate items for your lighting designer to evaluate.
Can a route overlay tell me whether my parking lot has enough light?
No. The overlay shows which walking segments and crossings a proposal accounts for. Light levels and uniformity come from a photometric calculation, and any local requirements depend on your jurisdiction. Use the overlay to make sure those later reviews cover every route.
What should I note when parked vehicles sit between a walkway and a drive aisle?
Record the row, the crossing or segment number it affects, and whether taller vehicles park there. That gives the reviewer a specific location to evaluate. The note flags a condition to look at. It doesn't confirm a visibility problem or prescribe a fix.