San Diego permit use needs inspection and expiration evidence
San Diego Information Bulletin 117 ties permit utilization and continued validity to specific timing and inspection conditions for covered building permits. Owners and reviewers need to distinguish an inspection request, a qualifying completed inspection, an approved extension, final-only eligibility and actual permit closure.
Editorial figure by Civic Permit Review. Source context: City of San Diego Information Bulletin 117.
Prove each permit-validity state with its own event
| Control record | Evidence to retain | What it does not establish |
|---|---|---|
| Applicability | Jurisdiction, permit class, scope, issuance date, governing code and bulletin version | That this rule applies to every San Diego approval |
| Initial utilization | Substantial-work evidence, required inspection type, completed inspection date, result and inspector record | That scheduling or requesting an inspection is enough |
| Continued activity | Subsequent required inspections, work pauses, suspension start, field evidence and status review | That an initial utilization event prevents later expiration |
| Extension or final-only path | Timely request, qualifying facts, formal approval, new deadline, final-only eligibility and conditions | That a request or fee grants the extension |
| Expiration and closure | Determination, stop-work notice, new permit or renewal path, final inspection, approval and closure date | That expired, finaled and closed are interchangeable |
Confirm that Bulletin 117 governs the permit
The direct answer is to apply the one-year utilization rule only after confirming that the City of San Diego bulletin covers the permit class and facts. Bulletin 117 describes covered building-permit timing, inspection, suspension, expiration, extension and final-only pathways. Store the jurisdiction, project, permit number and class, work scope, issue date, governing code and bulletin version, amendments, and responsible reviewer before calculating a deadline. [1]
Do not export the San Diego rule to another jurisdiction, another approval type, or a permit excluded by the bulletin. A system label such as issued or active may not encode the applicable class, extensions or historical authority. This article does not determine whether any permit is covered, valid, utilized or eligible for relief; the official permit record and City determination control. [1]
Use a completed qualifying inspection as utilization evidence
Bulletin 117 says a covered permit generally must be utilized within one year after issuance unless an extension is granted, and it connects utilization to substantial work validated by a required inspection. It also says storm-water, status, preconstruction and customer-request inspections do not qualify for that purpose. Capture the required inspection type, request and completion separately, work observed, date, result, inspector record and link to the permit scope. [1]
An inspection request, calendar appointment, canceled visit, partial field note or unrelated inspection should not automatically change utilization status. Define which completed inspection the authority treated as qualifying and preserve the evidence as received. If the record is ambiguous, keep the permit in review rather than calculating an unsupported active-until date. The bulletin describes the policy; it does not validate the project’s field work. [1]
Separate utilization, suspension and project expiration
Initial utilization is not the same as perpetual validity. The bulletin describes a separate 180-day suspension or abandonment rule and project-duration limits, including longer multiyear periods for described project classes. Build a chronology of every required inspection, substantial-work event, pause, resumption, notice and official status change. Preserve the exact date and authority for each transition. [1]
Do not infer continued activity from invoices, contractor presence, material delivery or an unqualified inspection type. Conversely, a gap in an internal schedule is not by itself an official expiration. Flag approaching boundaries for human review and retain the City’s decision. Applicable code, permit conditions and exceptions can govern facts beyond the bulletin summary.
Keep requests, approvals, final work and closure distinct
An extension request should have its filing date, basis, supporting evidence, fee where applicable, reviewer, decision, conditions and revised deadline. A request does not become an approved extension merely because it was submitted. Likewise, a final-only pathway, completed final inspection, final approval, permit finaling and administrative closure are separate events. The bulletin also describes stop-work consequences when required final approval is absent. [1]
Civic Permit Review reviewed the exact City page on October 7, 2026; it identifies the bulletin as April 2026 and no post-October 6 development was established. Unknowns include formal code applicability, permit class, substantial work, inspection qualification, suspension, extension eligibility or approval, final-only conditions, stop-work direction, final inspection and closure. Resolve them through the official permit file and City authority. [1]
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.