ProjectDox upload completion is not permit acceptance

The guide preserves a useful sequence of administrative states

Milpitas's official ePlan Review guide tells an applicant to upload required drawings and documents and then use an Upload Complete - Notify Jurisdiction action. It says the resulting sample status is Prescreen, meaning a permit technician is reviewing the application and uploaded documents. If information is missing, the project can return as Prescreen corrections. Only after a staff completeness determination does the guide describe creating the permit record and calculating fees.

That sequence supports a narrow and durable conclusion: upload completion records an applicant action and jurisdiction notification, not the public authority's acceptance of completeness, technical approval, permit issuance, or construction authorization. The guide later separates fee calculation, payment receipt, staff assignment, comments, review completion, approval, and final fees. A portal should expose those distinctions in plain language rather than using a generic complete badge.

Preserve the file set and the status actor

Each transition should identify the project and jurisdiction, applicant, permit or review type, file names and folders, document type, revision, upload checksum, uploader, upload and notification timestamps, required-document checklist version, prescreen reviewer, comments, missing-item disposition, and the rule or procedure in effect. If a file is replaced, preserve the earlier version and show which review cycle and comments it informed.

The actor matters as much as the label. Applicant-declared upload completion, automated transfer success, staff receipt, administrative completeness, fee assessment, plan-review finding, approval, and issuance are decisions or events owned by different roles and systems. A portal message should name which event occurred and what it permits next. Payment should remain a separate record; a paid fee does not establish a complete application, approved design, or issued permit.

Treat the document's age as a material evidence gap

The guide carries a September 4, 2018 date. The City continues to host the PDF at the registered URL, but availability is not proof that every screen, product version, department procedure, fee sequence, or terminology remains current in 2026. Civic Permit Review did not locate a revision date on the reviewed record or independently confirm the live applicant workflow. Readers should not use this article as current filing instruction for Milpitas or another jurisdiction.

A current implementation record would identify the responsible department, supported permit populations, portal and back-office product versions, effective date, current applicant instructions, accessibility status, support path, retention rule, migrated-record boundary, and superseded materials. The city or provider can close the gap by publishing or linking a current dated guide and an archive marker for obsolete versions. Until then, the article uses the 2018 source only to analyze status semantics.

Test the handoff with incomplete and revised submissions

A jurisdiction evaluating an electronic plan-review workflow should test a missing required document, wrong folder, unsupported file, interrupted upload, duplicate version, applicant team-member change, prescreen return, revised drawing, paid fee, technical-review comment, approval, and withdrawal. The public view and staff record should agree on the current state while retaining who changed it, when, under which procedure, and what evidence supports the next action.

Civic Permit Review reviewed the registered Milpitas PDF on September 5, 2026. The official historical record supports the state sequence described above, but it does not establish the city's current portal behavior, current rule, accessibility, file acceptance, application completeness, fee, technical review, approval, issuance, code compliance, legal status, or outcome. The source is therefore classified as an evidence gap rather than a verified post-cutoff development or clean current procedure.

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.