Site Plan Review for Data Centers: What It Covers and How Long It Takes

Site plan review is the local government’s check that a specific development layout meets the zoning ordinance, subdivision rules, engineering standards and any conditions attached to an earlier approval. It comes after the land use question is settled. If a data center is a permitted use, site plan approval may be the main local decision; if the use needs a special exception or rezoning, the site plan must also match the plan and conditions approved at the hearing. The broader sequence is covered in the data center permitting process.

The distinction matters because review standards differ. In Loudoun County, Virginia, by-right data centers were approved administratively through the site plan process, while special exception applications require staff review and public hearings before the planning commission and board of supervisors.¹ In March 2025 the county’s board voted 7–2 to make data centers a special exception use in districts where they had been permitted by right, with a grandfathering window for applications submitted before February 12, 2025.¹ That one change moved data center approvals in the largest U.S. market from a technical track to a discretionary one. See zoning for data centers for how the paths compare.

Who decides varies. In many counties, staff approve site plans; in some Michigan communities, such as the City of Perry, the planning commission reviews the plan with staff comments and may approve, approve with conditions or deny it.⁹ Either way, the reviewer’s job is to apply written standards. As one township’s rules put it, a completeness check is not itself a decision on whether the plan complies.¹⁰

A data center site plan is a full civil engineering package, usually sealed by a licensed engineer. Local checklists differ, but most ask for the same core sheets.⁵

Data center plans add items that a warehouse plan would not: generator yards and fuel storage, substation or switchyard pads, transformer and chiller locations, security fencing and gates, and sometimes noise barriers. These elements drive many comments, because they sit near property lines and affect setbacks, fire access and screening. The ground truth for all of it is a current boundary and topographic survey, described in title review and ALTA surveys.

Pre-application meetings are worth the time. Michigan State University Extension notes that reviewing a very preliminary plan lets the developer address significant issues before the formal submittal, and that many communities charge a fee for the meeting while some do not.¹³ Some localities list it as an optional step, and others hold one on request.⁹¹⁰

After filing, a completeness check confirms the package has every required item. Technical review then routes the plans to each discipline. Comments come back as a letter, the engineer revises and responds point by point, and the cycle repeats until every comment is cleared. Final steps typically include posting performance bonds, recording easements and signing maintenance agreements for stormwater facilities.

Large, single-story buildings on big pads draw a predictable set of comments. Knowing them in advance lets the engineer design them out of the first submission.

• Fire apparatus access: The model fire code calls for access roads at least 20 feet wide with 13 feet 6 inches of vertical clearance, access within 150 feet of all portions of the first-story exterior wall (measured along an approved route), and a turnaround on dead ends longer than 150 feet.⁷ Local checklists add load ratings, such as 75,000 pounds in one Georgia county.¹¹ Security gates must be approved by the fire official.⁷
• Stormwater: Large roofs and paved yards produce a lot of runoff. Reviewers check detention sizing, outfalls and construction-phase controls. See stormwater management for data center campuses.
• Landscaping and screening: Buffers, berms and plant quantities are counted against the code. One county checklist, for example, requires an 8-foot buffer with a continuous hedge and one canopy tree per 50 linear feet along parking and drive areas.⁴
• Lighting: Photometric plans must show light levels at and beyond the property line; one county caps spill onto adjacent residential property at 0.5 footcandles.⁴
• Setbacks and noise: Fairfax County’s 2024 rules require new data centers to sit at least 200 feet from residential lots and call for noise studies before and after construction.⁸ Equipment yards near the property line are a frequent issue. See noise, setbacks and buffers.
• Transportation: Entrances, turn lanes and construction traffic routes, often tied to a traffic impact study.

Some states set deadlines for local site plan review. Virginia is the clearest example. Under its Code, a locality must act on a previously disapproved site plan within 30 days after it is corrected and resubmitted, and a resubmitted plan that is not approved or disapproved within the required period is deemed approved.² A September 2025 Fairfax County staff report describes 2025 legislation (HB 2660) that cut the first-submission review period from 60 days to 40 days and set 30 days for resubmissions.³ Many other states leave timing to local ordinance, so check the code where the site sits.

Statutory clocks measure the government’s time, not the project’s. The applicant’s revision time between rounds, outside agency reviews, utility approvals and bonding all add to the calendar. A large campus may also be split into a master plan and separate plans per building or phase, as discussed in phased vs. full build-out.

An approved site plan can protect a project from later ordinance changes, depending on state law. In Virginia, an approved final site plan is valid for at least five years, or longer if the approving agent sets a longer period, and later changes to local ordinances, maps or policies generally cannot adversely affect the developer’s right to build under it, subject to listed exceptions.¹⁴ Other states handle vesting differently, and some protect nothing until building permits issue or construction begins. This is a question for land use counsel.

Vesting matters more now because rules are moving. Loudoun’s 2025 change shows how quickly a by-right path can close, and its grandfathering came with limits: applications had to be diligently pursued, and an increase of more than 5% in a data center’s square footage counted as a substantial modification.¹ In September 2026 its board voted for a temporary pause on certain legislative applications for data centers and substations while new standards are written, with a formal resolution scheduled for October 20, 2026.¹⁵ Screening for these risks is covered in data center moratoriums and local restrictions.

1. 01Confirm the approval path in writing: by-right, special exception or rezoning, and who signs the plan.¹
2. 02Get the current checklist and fee schedule, and ask whether a pre-application meeting is offered or required.¹³
3. 03Order a boundary and topographic survey and a geotechnical investigation early; grading drives everything else.
4. 04Confirm whether the state or EPA issues construction stormwater coverage, and budget time for the SWPPP.⁶
5. 05Meet the fire marshal about access roads, gates and hydrant layout before fixing the building footprint.⁷
6. 06Check for data-center-specific setbacks, noise studies or height limits in the ordinance.⁸
7. 07Learn the review clocks and how long each prior data center plan in the jurisdiction actually took.

Site plan comments rarely kill a project, but they can shrink the usable footprint once fire lanes, buffers and ponds are drawn. That is why a site screen should test the layout against gross vs. buildable acreage before closing. If you want a second look at a parcel, you can get a site reviewed.