An ePermitHub document handoff is not jurisdiction record custody

Name the authoritative record at every boundary

ePermitHub's official record supports a narrow capability statement: the platform provides document-management and plan-review workflows and can integrate with permitting and construction systems. The agency must still decide which system and object is authoritative for the application, plan package, revision, review comment, approval, and issued set. Preserve the jurisdiction record number, application type, parcel and address references, applicant, discipline, file identifier, source system, transfer identifier, received time, checksum, and custody state for every inbound document.

Do not rely on filename or folder position as identity. Applicants may reuse names, replace sheets, split one package into several files, combine disciplines, or upload a corrected document while another review is open. The record should distinguish submitted, quarantined, accepted for intake, routed for review, superseded, withdrawn, approved, issued, and archived versions. If a transfer fails or duplicates a file, both systems should expose the exception without silently selecting the latest visible copy as authoritative.

Keep review actions attached to the exact version

A markup, checklist result, comment, applicant response, resubmission, reviewer disposition, and approval must point to the exact sheet or document version on which the action occurred. Preserve author, role, time, discipline, comment identifier, cited requirement, affected location, status, response, and reviewer decision. Flattening annotations into a replacement PDF can make the visual package convenient while losing the sequence that explains why an issue was opened, changed, resolved, reopened, or carried forward.

Define how comments and approvals move between the plan-review environment and the permit system. A successful API call or plug-in status can prove transport, but not that the target record accepted every file and relationship correctly. Reconcile package counts, identifiers, versions, comment states, approval signatures, and exceptions. If a reviewer acts during an outage or in a local copy, the later synchronization should preserve the original action time, actual actor, and conflict decision rather than inventing one clean sequence.

Carry custody through issuance, retention, and disclosure

The approved plan set should be an explicit jurisdiction action, not an inferred status. Retain the approving authority, signature or seal where applicable, approval time, permit record, covered disciplines, approved file hashes, conditions, expiration or revision rules, and the exact set delivered to the applicant and field inspectors. Later field changes, deferred submittals, revisions, and as-built records should branch from that set with their own authority and effective status instead of overwriting it.

Test a same-name resubmission, partial package transfer, duplicate callback, malware quarantine, comment linked to a superseded sheet, approval while an integration is delayed, records hold, and public-record request covering both active and archived files. The agency should retrieve the complete governed history, apply access and redaction rules, preserve retention and legal holds, and show which copy was public, internal, sealed, or restricted. Vendor availability and export capability should be tested before they become the only practical path to the record.

Read the product claim within its evidence boundary

The ePermitHub page establishes current official positioning for digital plan-room, document-management, plan-review, and integration capabilities. It does not establish an agency's authoritative-system design, record completeness, version accuracy, review quality, approval authority, permit issuance, retention compliance, public-record response, privacy protection, accessibility, or recovery capability. Supported formats, integrations, signatures, export behavior, audit logs, retention features, security, and contracted responsibilities require jurisdiction-specific confirmation.

Civic Permit Review reviewed the official record on September 1, 2026. No dated material change after the August 31 successful-publication cutoff was established, so this is durable civic-system analysis rather than a current-intelligence event. Agencies should test one representative application with multiple revisions from intake through transfer, comments, resubmission, approval, issuance, field access, later revision, archive, export, and disclosure before treating a connected document status as the public record.

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.