Multi-site permitting: one process, many jurisdictions.

Why multi-site programs stall

Rarely because of a single hard permit. They stall because each site is managed as an independent one-off, so nothing is comparable, nobody knows which sites are actually at risk, and the same local requirement gets rediscovered in the fifth jurisdiction after it was already solved in the second. Program discipline, not heroics, is what fixes it.

Standardized intake

Every site enters the program the same way, with the same information captured in the same fields. That is what makes a fifteen-site portfolio reportable in one view instead of fifteen email threads.

• Site address, jurisdiction and confirmed reviewing agencies
• Scope type — new construction, conversion, TI, remodel, relocation
• Prototype version and any approved deviations
• Design team, general contractor and local trades of record
• Target milestone dates: submittal, permit, construction start, opening
• Landlord, lease and delivery-condition constraints affecting permitting

Prototype vs. local requirements

A national prototype set carries assumptions that don't hold everywhere: adopted code editions differ, energy compliance paths differ, accessibility requirements can be stricter at the state level, fire authority expectations vary, and local zoning may control signage, parking, drive-thru stacking, hours or facade materials. LPG performs a local delta analysis per site so the design team adapts the prototype once, deliberately, instead of reacting to correction comments.

• Adopted building, fire and energy code editions and local amendments
• State or local accessibility requirements exceeding the federal standard
• Zoning constraints on use, signage, parking and site circulation
• Fire authority requirements including sprinkler, alarm and access
• Health department requirements for food service prototypes
• Utility provider requirements and connection lead times

The permit matrix

Each site gets a matrix identifying every required permit and approval, the reviewing agency, prerequisites, whether it can run in parallel, the documents required and who owns them. This is what turns 'we're waiting on permits' into a specific, actionable status.

• Zoning, use approval and site plan requirements
• Building permit plus mechanical, electrical and plumbing trades
• Fire alarm, sprinkler, hood suppression and gas permits
• Health, sign, right-of-way and site-work permits
• Utility applications and their lead times
• Business licensing, TCO and final CO requirements

Portfolio tracking and reporting

Program reporting should answer three questions at a glance: where is every site, what is each site waiting on, and which sites threaten an opening date. LPG reports at the portfolio level with per-site detail underneath, on a cadence that matches the client's development meeting rhythm.

• Status by site and by permit, not just by project
• Review cycle count and current pending-with-agency items
• Open comments and who owns each response
• Milestone variance against target dates
• Risk flags with the specific dependency driving them

Escalation and issue management

Sites stop moving for identifiable reasons — an unanswered comment, an unassigned document, a licensing gap, a utility application waiting on a fee, a jurisdiction requiring a meeting. Program management means those are surfaced with an owner and a next action rather than sitting inside a status column, and that the client hears about them early.

Institutional knowledge as an asset

The real compounding value in a multi-site program is what the program learns. Jurisdictional requirements, reviewer expectations, submittal mechanics and recurring comment patterns get captured per jurisdiction, so the tenth site in a state is easier than the first. LPG maintains that knowledge as part of the program rather than in individual inboxes.