Status glossary

Permit words, translated carefully.

Local systems use different vocabularies. These definitions explain PermitProspect’s normalized display without overriding the issuing authority’s raw status.

01

Filed

The application or permit record was submitted to the issuing authority. Filed does not necessarily mean approved or issued.

The exact event varies by source. Review the jurisdiction’s field definition before treating a filing date as the start of construction.

02

Approved

The authority completed an approval step, but fee payment or a separate issuance step may still be required.

Some systems combine approval and issuance; others expose them separately.

03

Issued

The authority reports that the permit was issued or ready to issue under its local process.

Issue-date meaning can vary by permit program. It is not proof that physical work has begun.

04

Active

The source currently treats the permit as open or active under its status vocabulary.

An active status can include inspection, fee, or work stages. Use the source milestone when available.

05

Finaled or complete

The permitting workflow reached a final or completed state in the source system.

This usually makes the record less timely for installation work, although later service opportunities may still exist.

06

Expired

The permit passed its source-reported expiration date or was assigned an expired status.

Expiration does not prove that work stopped or never occurred. Renewals and extensions can exist as separate records.

07

Revoked or void

The issuing authority invalidated the permit or removed it from active status.

PermitProspect suppresses revoked records from lead alerts unless a source-specific reason justifies review.

08

Declared valuation or reported cost

A source-reported amount whose definition varies by jurisdiction and permit type; it is not verified final project cost.

PermitProspect keeps the jurisdiction-specific label and never fills a missing value with an estimate.

09

Direct trade match

A source code, permit type, or normalized work description explicitly matches an allowed term for the trade.

The stored result includes the rule, reason, confidence, and taxonomy version.

10

Adjacent trade signal

A permit event may create downstream demand for a trade that is not itself explicitly permitted.

Adjacent signals must explain their trigger and remain visually distinct from direct matches.