A Complete Permit Application: A Practical Submission Checklist

Choose the right checklist before producing documents

A remodel, new dwelling and ADU can require different information. Begin with the official project category, then ask the department to resolve uncertainty about the correct route. For unincorporated Alameda County, Alameda County: Permit Forms and Resources provides separate building and ADU checklists. Use the current list rather than a consultant's old generic packet.

Create a submission register from that list. Each row should name the document, responsible person, applicable version and completion status. Mark not applicable only when the basis is understood. A missing document and an intentionally inapplicable requirement are not the same thing.

Check consistency across the package

Compare the project address, owner information, scope description and drawing dates across forms. Confirm that the architectural layout matches the information used by the relevant consultants. If the design changed, ask whether all affected sheets and calculations were updated, not just the most visible floor plan.

A reviewer should not have to guess which of two conflicting versions represents the proposed work. Include a clear document index and remove superseded files from the submission set while retaining them in your internal archive. This is document control, not a substitute for professional design review.

Identify the dependencies that block completeness

The San Mateo County: Apply for a Permit process explains an initial completeness review before later review stages. San José's San José: Preapproved ADU and Site-Specific Application identifies site-specific documents for its program. These examples show why a completed drawing set may still be missing an authorization, clearance or other required item.

Ask which outside documents need early requests. Assign each to an owner and record the agency or provider involved. A checklist with every drawing marked complete can still conceal a missing third-party document that prevents the next step. Make those dependencies visible before the submission day.

Upload deliberately and preserve the receipt

Follow the portal's current file and submission instructions. Check the uploaded package after transfer, especially if files were replaced or split. Save the submission confirmation and the list of files sent. If the portal has a separate action to complete or submit the application, verify that it was performed rather than assuming upload alone sent it for review.

Hypothetically, a team uploads revised sheets but leaves the application in a draft state. The owner hears that plans were submitted, while the agency has nothing ready to review. A receipt and status check resolve that uncertainty immediately without blaming an unexplained agency delay.

Respond to completeness questions as a package

When the authority identifies missing items, log them and send a coordinated response following its instructions. If an item is unclear, ask a specific question before creating a document that may not answer it. Keep the owner informed about what remains with the project team and what is waiting on agency action.

Your final preflight should cover jurisdiction, project category, required forms, scope consistency, current drawings, identified outside documents, authorizations, fees or payment steps and submission confirmation. The goal is not a guarantee of approval. It is a package that accurately represents the project and allows substantive review without avoidable administrative confusion.

A preflight review another person can repeat

Have a team member who did not assemble the upload compare the submission register with the actual files. Check identifiers, revision dates and references between documents. This is an administrative consistency review, not a claim that a second owner check replaces the designer's technical quality control.

Ask the reviewer to open the files rather than merely count them. A file named structural calculations can contain an older version, and an application form can refer to a superseded scope. Identify unclear or missing items in a short exception list with an owner and required action. Avoid declaring the package complete while that list contains unexplained placeholders.

After upload, preserve the exact set and confirmation in a folder labeled with the submission date. If staff later ask which version was sent, you should be able to answer without reconstructing it from email attachments. For a resubmittal, repeat the same control and include the required response information. A repeatable preflight is worthwhile because it targets preventable confusion while leaving substantive design judgment and approval with the appropriate professionals and agency.

Keep the checklist version or download date with the submission record. If requirements change while a project is being prepared, ask which version applies rather than quietly combining old and new instructions. This makes later questions about a missing item easier to resolve and prevents the team from claiming completeness against a checklist nobody can identify.