Permitting speed is now a screening factor. Most tier-3 cities still answer it with a handshake.
In the Site Selectors Guild's March 2026 Pulse Check, 29% of respondents identified business environment and regulatory climate as a leading factor eliminating sites from consideration. Another 22% selected speed to market. These are elimination factors, not preference factors. A site that cannot demonstrate a bounded approval path gets removed before the shortlist conversation starts.
The direction has been consistent for three cycles. In 2024, 82% of selectors identified development-ready sites with sufficient infrastructure as the top driver of industrial facility locations. DCI's 2025 summary described speed and certainty in permitting and power delivery as increasingly valuable. The percentages aren't directly comparable across years, because the surveys used different constructs. The weight assigned to regulatory predictability has risen anyway.
A site selector screening 15 communities against a 90-day construction-start requirement cannot do anything with "we're easy to work with." What they can screen is this: by-right M-2 site plan, staff-level review, 14-day completeness determination, Planning Commission consent agenda at next monthly meeting, no council action required, eight industrial site plans approved in the last 36 months with a median elapsed time of 47 days from complete application to approval.
An approval-path table is the document that produces that answer.
Does your regulatory structure actually qualify as an advantage?
Being a small jurisdiction does not make you fast. The Development Approvals Index from the NAIOP Research Foundation, which examined 30 jurisdictions across 16 states, found no notable relationship between jurisdiction population and approval performance. Fairfax County, Virginia, population over 1.1 million, ranked first.
A tier-3 city holds a documentable speed advantage when three conditions are present at once:
- The industrial uses most likely to be recruited (manufacturing, warehousing, distribution, food processing) are permitted by right or through a single discretionary approval in the zoning districts where your viable sites sit.
- The approval chain is short: one reviewing body, or a staff-level decision with no required hearing.
- You have recent industrial cases, approved within the last three years, whose elapsed times you can cite.
If your most marketable industrial site requires a rezoning, a conditional-use permit, and a subsequent site-plan approval, each before a different body meeting on a different monthly cycle, your regulatory structure is not a speed advantage. It may still be a predictability advantage, if you can document the full sequence and its actual duration. But do the self-assessment first. A director who invests 40 hours building an approval-path table for a process that takes eight months has documented a liability. That's useful information, and it tells you what to fix. It also changes the purpose of the exercise, and you should know that going in.
Start here. Pull the zoning ordinance for the district where your best industrial site sits. List every use category a manufacturing or distribution prospect might fall under. For each one: is this by right, conditional use, special use, or does it require a rezoning? How many bodies must act? How many hearings are required? If you can't answer those questions from the ordinance text without calling the planning director, your first problem is legibility, and it precedes the speed question.
What the approval-path table contains
The deliverable maps every realistic industrial project scenario to its regulatory pathway, approving bodies, hearing requirements, meeting cadences, and documented actual timelines. Format is part of the deliverable. Selectors need to extract a timeline for a specific use in a specific district; they are not reading a general description of your planning process. Build it as a standalone document, one page, two at most, that a selector can pull during a screening call or attach to an RFI response without extracting it from a larger package. Post it where desktop screening will find it. Embedded on page 34 of a community profile, it won't be found.
Several municipalities publish pieces of this. Stanton, Tennessee publishes separate estimated timelines for site plans (four to six weeks), variances and special uses (five to seven weeks), and rezonings (eight to 12 weeks), identifying the reviewing bodies and meeting cadences for each. Countryside, Illinois maps its rezoning, variance, and special-use paths from submission through staff review, public notice, Planning and Zoning Commission hearing (first Tuesday), and City Council action (fourth Wednesday), stating a minimum of approximately two months. Select Tennessee's certified-sites template requires a documented permitting process, timeline, and fee schedule as a certification criterion.
None of these combines all the fields a selector needs in one artifact. Here is what the complete table requires, column by column.
Project scenario and zoning district. Each row is a use-and-district combination: general manufacturing in M-1, food processing in M-2, warehouse/distribution in I-1, heavy industrial in I-2. Use your ordinance's own categories. A prospect looking at a specific site in a specific district should find their row without interpretation.
Entitlement path. By right with administrative site-plan review. By right with Planning Commission site-plan review. Conditional use. Special use. Variance required. Rezoning required. Each carries different bodies, different hearing requirements, and different timelines. Collapsing them into one "typical" duration is how most cities end up overstating their regulatory speed without intending to.
Every approving body, in sequence. Staff review. Planning Commission, and here distinguish whether the commission's role is recommendation or final decision. Board of Zoning Appeals. City Council. List each body with its function: completeness review, technical review, recommendation, or final action. Fairfax County's process overview shows why the distinction is worth a column. For rezonings and special exceptions, the Planning Commission recommends and the Board of Supervisors decides, with the Board hearing scheduled four to five weeks after the Commission. A table listing only "Planning Commission approval" understates that path by at least a month.
Meeting cadence and agenda-deadline exposure. Monthly, biweekly, or as-needed. The specific meeting date (first Tuesday, third Thursday). The submission deadline for making a given meeting's agenda. The real calendar risk sits here. A monthly commission with a 21-day advance submission deadline means a project that misses the deadline by one day waits an additional 30 days. Countryside's flowchart warns explicitly that unpaid hearing-notification costs can push a case to the following month. Triggers that specific belong in the table.
Public notice requirements. Which entitlement paths require published notice, mailed notice to adjacent owners, or posted notice on the site. The notice period, typically 15 to 30 days before the hearing. Whether the notice period can run concurrently with staff review or must follow it.
Documented actual timelines from recent industrial projects. This column separates a useful table from a restatement of your ordinance. Pull the last five to eight industrial approvals from Planning Commission minutes and planning department records. For each, record application acceptance date, hearing date or dates, decision date, and total elapsed days. If the project required multiple approvals (conditional use followed by site plan), record the full sequence. Statutory maximums and published estimates are what cities put in brochures; selectors discount them. Actual project timelines are the number they will use.
Parallel permits in separate lanes. Building permit, grading permit, fire marshal review, utility connection approval, and any state or federal environmental permits run as separate tracks. Tennessee's Department of Environment and Conservation publishes an industrial permitting matrix with columns for permit type, application timing, regulated activity, public notice, and issuance timetable. Air construction permits require 90-day advance submission for minor sources and carry a 115-day statutory issuance period. Those timelines run parallel to local land-use approvals, and the table should show them, with local and state/federal lanes visually separated so the reader can tell what the city controls from what it doesn't. The separation matters in both directions. A response quoting only the local 45-day site-plan timeline reads as evasion the moment the selector asks about air permits or stormwater discharge. A response lumping local and state tracks into a single "approximately six months" gives the city no credit for the speed it actually controls. State each lane with its own documented duration and application-timing requirements, and identify the dependencies: where a state permit must issue before a local approval can, or the reverse.
Quantifying appeal exposure
Most approval-path documents end at the decision. A selector evaluating timeline risk also needs to know what happens if the approval is challenged.
Standing. Who can appeal varies by state and by decision type. North Carolina permits judicial review by the applicant, property-interest holders, persons suffering special damages, qualifying associations, and specified governmental parties. Receiving adjacent-owner notice does not by itself establish standing. Oregon requires a petitioner to the Land Use Board of Appeals (LUBA) to have appeared before the local government during the proceeding. Virginia permits appeal by an aggrieved person, a term with its own case-law definition. State the actual standing categories under your state's enabling act.
Filing window. Representative deadlines in the statutes reviewed run 21 to 30 days from the decision. Oregon's notice of intent to appeal to LUBA is due within 21 days. North Carolina's petition for review is generally due within 30 days. Virginia allows 30 days for both BZA appeal and subsequent judicial review.
Stay effect. Whether an appeal freezes the project or allows construction to proceed under the existing approval. Virginia's administrative appeal to the BZA automatically stays further proceedings unless the zoning administrator certifies imminent peril. Oregon's LUBA appeal does not automatically stay the local decision. For a prospect with a construction-start date, that distinction is the difference between a 90-day hold and none. Make it a yes/no field.
Potential duration. Oregon's statutory sequence (21 days to file, 21 days for record transmittal, 77 days for LUBA's order) produces a maximum of approximately 119 days from local decision to LUBA ruling, before any further judicial review. Virginia directs only that the circuit court hear the matter "as promptly as practicable," with no fixed deadline. State the statutory sequence and, where you have it, the typical actual duration from your jurisdiction's recent experience. If no industrial approval in your city has been appealed in the last decade, say that. It's a data point.
Community opposition as a permitting risk factor
The 2026 Guild Pulse Check found 69% of respondents rating increasing NIMBYism as a four or five on a five-point barrier scale. Only 12% selected community sentiment as a current leading elimination factor, below utilities, sites, workforce, regulatory climate, speed, financial feasibility, scalability, and building availability.
Selectors treat opposition as a source of delay and political risk, and they screen for it through the regulatory structure rather than through sentiment. The questions are operational. Does the entitlement path require a public hearing? What is the notice radius? Has a similar project been approved recently without organized opposition? Is the site buffered from residential uses?
The table handles this by making the exposure visible. A by-right use with staff-level site-plan review and no required hearing carries near-zero community-opposition exposure inside the entitlement process. A conditional-use permit requiring a public hearing with 500-foot mailed notice to adjacent residential parcels carries material exposure. State which paths require hearings, what the notice requirements are, and what the adjacent land uses are for each site. That is what a selector can evaluate.
Where to find the data
Ordinance text gives you the entitlement paths, the approving bodies, and the hearing requirements. Planning Commission and City Council meeting minutes give you the actual project timelines: application acceptance dates, hearing dates, votes, conditions imposed. Planning department project files give you completeness-review durations and the gap between submission and acceptance. Your city attorney, or the state enabling statute directly, gives you the appeal standing categories, filing deadlines, and stay provisions.
Recent actual industrial timelines is the column most directors will struggle to fill, because many tier-3 cities haven't approved an industrial project in several years. If your last five industrial approvals span a decade, that's a thin evidence base, and the table should say so rather than present old cases as current performance. Absent any recent industrial approvals, you can document commercial or institutional projects that followed the same entitlement path, labeled as such. A selector will notice the distinction whether or not you flag it.
Maintaining the table
A table built in August 2026 starts losing accuracy the first time a meeting schedule changes, a staff position turns over, an ordinance amendment alters an entitlement path, or a new project produces an actual timeline that shifts the distribution. Give it a version date and a review trigger. At minimum, update after every industrial approval, every ordinance amendment affecting industrial districts, and every change in meeting cadence or staffing.
The approval-path table is the specific artifact that gets a permitting answer to rung 3: documented, authorized path based on adopted procedures and recent performance, prepared before a prospect arrives. Rung 4 — a project-specific determination of exact use, emissions profile, discharge, hazardous materials, operating hours, and construction phasing — requires a live prospect's inputs and cannot be pre-built.
In Issue 3 of The Playbook I placed the advance-preparation ceiling for permitting answers at rung 3 on a six-level commitment ladder. The table is what gets you there. A director who can hand a selector one page showing that a manufacturing use in the M-2 district is by right, requires staff-level site-plan review with a 14-day completeness determination and Planning Commission consent-agenda placement at the next monthly meeting, with eight recent industrial approvals averaging 47 days and no appeals filed in the last five years, has answered the permitting question at a level most competing cities will not match. The selector doesn't need to call the planning director. The answer is in the table, dated, sourced from project records, and verifiable against public minutes.
The screening starts before the RFI arrives. The table has to exist before then.
- Guild NIMBYism screening methods: A June 2026 Guild conference account describes consultants examining media coverage, sensitive neighboring uses, and activist activity during RFP, site-visit, and finalist stages as part of community-risk evaluation.
- State site-certification permitting fields: Select Tennessee, SiteOhio, Virginia VBRSP, and California's Business Ready Sites program each require different permitting and entitlement documentation, and Virginia's tiered system distinguishes sites where construction can begin in 12–18 months from those needing only land-disturbance permits.
- South Dakota's RFI response guidance: The state's published guidance says a community may receive as little as one day to assemble a response and recommends keeping roughly 90% of the material prepared in advance, with no more than 10 pages per community.
- NAIOP's approvals benchmarking effort: The Research Foundation's preliminary 30-jurisdiction index measures transparency, accountability, and consistency in plan review and permitting rather than full entitlement elapsed time, and its authors noted that broader representation is needed for robust trend analysis.