Census permit data measures authorizations—not cycle time

Authorization is the measured event

The Building Permits Survey is an official measure of residential construction authorized by building or zoning permits within its defined population. It helps readers compare housing authorization over time and across supported geographies. The event is not application submission, completeness review, plan-review start, correction, payment, inspection, certificate issuance, construction start, or completion.

A permitting system should label Census data with the housing-unit, structure, building, valuation, place, reference period, release, and method boundaries. Importing the series into a dashboard called permitting performance can misstate both the public data and the local workflow.

Survey estimates and local case records are different evidence

Census describes a mixed monthly and annual survey design and uses imputation in monthly estimates for nonresponders and places outside monthly collection. Those methods are appropriate to a statistical program, but they do not reconstruct a jurisdiction's individual permit cases. A local portal record may include more detail while covering a different population or classification.

Responsible analysis should preserve source, release, geography, universe, observed versus imputed status where published, revision, units, and exclusions. It should not join a national series to local cases by place name alone and then infer backlog, staffing, approval speed, housing delivery, or causation.

The buyer test keeps throughput metrics separate

Ask a civic analytics product to show the raw Census series and its own local operational measures side by side. For cycle time, the platform should define start and stop events, paused periods, resubmissions, withdrawals, project types, responsible departments, denominator, observation window, missing cases, and changes in process. None of those fields comes from a building-authorization count.

Then change a jurisdiction boundary, reporting period, or permit classification. The product should preserve the original source release and calculation rather than backfilling an apparently smooth trend. A comparison is useful only when the population and event definitions remain explicit.

BPS does not judge a permit program

The Census methodology does not determine whether a permit was legally sufficient, correctly reviewed, code compliant, issued on time, acted upon, inspected, completed, or connected to a particular portal. Nor can authorized units alone establish housing supply, construction activity, agency performance, or the effect of a policy.

Civic Permit Review treats BPS as official statistical context and local permit systems as separate administrative records. Program evaluation requires current local authority, case-level definitions, comparable populations, disclosed methods, qualified interpretation, and attention to privacy and public-record boundaries.

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.