Permit.com forecasts need jurisdiction-stage assumptions

Name the jurisdiction, record, and forecasted stage

Permit.com's official FAQ says its work can include zoning due diligence, permit submittals, agency coordination, comment resolution, final-issuance tracking, milestone tracking, and approval forecasting. Those statements establish documented service positioning. They do not establish the timeline for a particular project or give a private service authority over intake, completeness, plan review, hearing, inspection, payment, issuance, or appeal. Each forecast must identify the jurisdiction, department, application or case, permit or approval type, project scope, and precise stage whose timing is being estimated.

Define both ends of the interval. Submission, agency receipt, administrative completeness, routing, first review, comment issuance, applicant response, resubmittal, technical approval, fee payment, and permit issuance are different events. State whether the estimate uses calendar or business days and how holidays, agency pauses, applicant response, outside-agency review, hearings, and inspections are treated. A forecast to next review is not a forecast to issuance, and issuance is not permission for every later construction activity.

Preserve the cohort and assumptions behind the estimate

Historical evidence is useful only when the comparison cohort is declared. Record the jurisdictions, permit types, project types, scope bands, filing channels, observation period, start and end events, completed and open cases, exclusions, sample size, median or other statistic, and treatment of missing or corrected dates. If the estimate relies on staff experience or current agency communication instead of a measured cohort, label that basis directly rather than presenting it as a data-derived result.

List the project assumptions that materially affect timing: zoning status, entitlement path, plan completeness, code edition, required disciplines, valuation or work scope, accessibility or fire review, environmental or utility coordination, contractor credentials, fees, public notice, hearing schedule, and any named outside approval. Assign an owner to verify each assumption. A standardized rollout model can organize work across locations, but it should not erase local procedures or turn a national average into evidence for one municipality.

Version revisions against actual public events

A forecast should have a creation time, data cutoff, model or estimation method, assumptions version, expected interval or range, preparer, reviewer, and intended decision use. When an agency posts a comment, changes a hearing date, requests another discipline, accepts a resubmittal, or issues a decision, create a new forecast version and retain the prior one. Show which fact changed and how it affected the remaining interval. Do not backdate the revised estimate or overwrite the forecast against which a lease, construction, or opening decision was made.

Measure forecast performance with the same defined stage and population. Compare predicted and observed events, explain censored open cases, and separate agency time from applicant or third-party time. A dashboard status is evidence of what the service recorded, not proof of the authoritative agency state. Reconcile material milestones to a dated official receipt, portal record, notice, email, stamped document, or other controlling jurisdiction record before relying on them for downstream decisions.

Demonstrate three unlike jurisdiction paths

A buyer demonstration should use three synthetic locations: a ministerial tenant improvement, a project requiring discretionary zoning action, and a permit with multi-department technical review. Start each forecast from a named official event, show the comparable cohort and assumptions, pause one case for an applicant response, change one hearing date, add an outside-agency dependency, and issue a revision. Inspect who can change assumptions, what evidence supports each milestone, and whether actual dates remain distinct from estimates.

Civic Permit Review reviewed Permit.com's official FAQ on September 24, 2026. It supports the stated service scope, timeline variability, milestone tracking, forecasting, and no-guarantee boundary. It does not establish any jurisdiction's rule, application completeness, historical-data quality, configured method, timeline accuracy, agency backlog, approval date, fee, zoning result, code compliance, permit issuance, construction schedule, cost result, or customer outcome. Public officials retain decision authority, and project teams remain responsible for qualified legal, design, code, and construction review.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Civic Permit Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.