1. Review Disciplines
20%Measures how many distinct review functions may be involved in the permit path.
- Building / structural review
- Planning or zoning dependency
- Fire or life-safety review
- Public works, utilities or other agency review
Alliance Permit Intelligence
A transparent way to measure permit complexity.
The Alliance Permit Complexity Score is a proposed 1–10 framework for comparing the administrative complexity of permitting across jurisdictions. The goal is to turn source-backed permit requirements into a consistent measurement — without pretending that one number can predict approval or replace local review.
✓Source-backed fields✓Versioned methodology✓No approval predictions
Methodology V1 Framework
Score the process layers that make permitting harder to administer.
The score should describe how many administrative steps, dependencies and filing requirements a project team must coordinate. It should not grade a jurisdiction as “good” or “bad.”
2. Forms & Documentation
20%Measures the volume and specialization of published intake requirements.
- Application forms and affidavits
- Professional seals or supporting documents
- Permit-type-specific schedules
- Supplemental calculations or product documentation
3. Registrations & Preconditions
15%Measures administrative prerequisites that must be satisfied before or during filing.
- Contractor registration
- Business or trade registration
- Owner/agent authorization
- Prerequisite approvals or account setup
4. Special Approvals
20%Measures additional approvals outside the ordinary building-permit intake.
- Historic, coastal, flood or environmental review
- Right-of-way or utility approvals
- Special zoning or development review
- Product, fire, health or specialty-agency approvals
5. Portal & Filing Workflow
15%Measures how much friction exists in the submission and tracking workflow.
- Single vs. multiple portals
- Online vs. paper/hybrid intake
- Electronic plan review availability
- Separate payment, resubmittal or inspection systems
6. Operational Complexity
10%A controlled future layer for verified Alliance operational data where a consistent sample exists.
- Correction-cycle frequency
- Administrative handoffs
- Observed resubmittal burden
- Other normalized operational indicators
Important: The percentages above define a proposed Version 1 framework for development. Alliance should lock definitions, test the scoring model against verified records, and document any changes before publishing comparative rankings.
How the Number Works
Normalize each dimension before calculating the 1–10 score.
Raw counts should not be added together blindly. Each dimension needs a defined 0–10 subscore using comparison-safe fields, then the weighted subscores can be combined.
Complexity Score = (Review × .20) + (Documents × .20) + (Registrations × .15) + (Special Approvals × .20) + (Portal Workflow × .15) + (Operational × .10)Publication Guardrails
✓
Minimum data completenessDo not score a jurisdiction if required dimensions are materially incomplete.
✓
Source traceabilityEach underlying field should retain an official source or clearly labeled evidence basis.
✓
Verification dateScores should show when the underlying record was last checked.
✓
Version controlMethodology changes should create a new version rather than silently changing historical meaning.
✓
No false precisionScores summarize administrative complexity; they are not promises about timing, approval or cost.
Score Interpretation
Use bands to communicate complexity without overclaiming.
Public reports can show the numeric score together with a plain-language band so the reader understands what the number represents.
1–2LowRelatively few administrative layers or special filing dependencies.
3–4Moderate-LowSome added documentation, registrations or review coordination.
5–6ModerateMultiple process layers requiring active permit administration.
7–8HighSubstantial coordination across forms, reviews, approvals or systems.
9–10Very HighDense administrative workflow with multiple dependencies and handoffs.
Data Requirements
Every published score should be reproducible from stored fields.
| Data element | Stored evidence | Scoring use | Publication rule |
|---|---|---|---|
| Review disciplines | Department/review list + official source | Review subscore | Verify first |
| Required forms/documents | Published checklist, application or agency guidance | Documentation subscore | Verify first |
| Registrations | Contractor/business registration source | Registration subscore | Verify first |
| Special approvals | Planning, fire, environmental, utility or specialty source | Special-approval subscore | Verify first |
| Portal workflow | Portal URLs, submission method, payment/review workflow | Portal subscore | Verify first |
| Operational data | Normalized Alliance records with a sufficient sample | Operational subscore | Sample required |
Verification & Change Control
A score should change only when the evidence changes.
When a portal, requirement, registration or approval dependency changes, the underlying field changes first — then the score can be recalculated.
Recommended Record Fields
Keep every score auditable.
score_version
dimension_subscores
source_ids
date_verified
verified_by
data_completeness
score_calculated_at
change_history_id
Frequently Asked Questions
Questions about the Permit Complexity Score.
What does the Alliance Permit Complexity Score measure?
It is designed to measure administrative permitting complexity: review disciplines, forms and documentation, registrations, special approvals, filing systems and other process factors. It is not a code-compliance score or an approval prediction.
Does a higher score mean a permit will be denied or delayed?
No. A higher score means the administrative path contains more layers or dependencies under the methodology. Actual timing and outcomes depend on the project, submitted documents, reviewers, agencies and other factors.
What sources support the score?
Alliance should use official jurisdiction and agency sources wherever practical and retain the source URL, verification date and change history behind the fields that contribute to a score.
Can Alliance change the methodology later?
Yes, but changes should be versioned. If definitions, weights or included dimensions change, the new version should be documented so readers can understand why scores may differ from an earlier release.
Turn permit data into a clearer project strategy.
Use Permit Intelligence to understand administrative complexity, then let Alliance research, prepare, file and track the permit workflow for your project.