Who Should Handle the Permit: Owner, Contractor or Designer?

Separate the roles before choosing a name

An application may involve an owner, an authorized representative, designers and contractors with different responsibilities. Start by asking what role the proposed applicant will occupy under the actual permit process. Do not agree to an owner-builder arrangement merely because it appears to simplify a contractor's paperwork.

Ask the authority for the current form and explanation applicable to the project. Alameda County's Alameda County: Permit Forms and Resources includes owner-builder and agent-authorization documents, illustrating that these are defined processes rather than casual labels. Read what you are being asked to sign and seek clarification when the responsibility is unclear.

Make an administrative responsibility chart

List who prepares application information, signs authorizations, submits plans, pays charges, monitors comments and receives issued documents. Assign backups for time-sensitive communication. The owner should know the permit number and retain access to the project record even when another person handles day-to-day administration.

Avoid an arrangement in which the designer assumes the contractor is monitoring the portal while the contractor assumes the owner is doing it. A named coordinator can track the file without pretending to perform the professional work of every contributor.

Coordinate design and construction responsibilities

Ask who is responsible for the technical content and who confirms that installed work matches the approved documents. San José's San José: Preapproved ADU and Site-Specific Application discusses applicant and vendor responsibilities in its specific program. Use the guidance for the relevant permit rather than treating one example as a universal rule.

If the contractor asks the owner to obtain the permit, request a clear explanation of the arrangement and its implications. Compare it with the agency's instructions and the proposed contract. The administrative convenience of one party should not leave the other unaware of a material responsibility.

Include inspection and correction tasks

The city's San José: Inspection Records and Scheduling describes scheduling and field-contact information. Identify who books the inspection, verifies readiness, meets the inspector, communicates corrections and provides completion evidence. These tasks continue after permit issuance and therefore need explicit ownership.

For a hypothetical equipment replacement, the owner may be willing to upload documents but unable to answer technical questions or be present during work hours. The proposed division of tasks should account for that reality. A small administrative saving may not be useful if it leaves no informed field contact for the inspection.

Choose a handover that survives personnel changes

Store the permit identification, submitted package, current status and correspondence in an owner-controlled project folder. If a contractor or designer leaves, document what was completed and what remains, then ask the authority how any applicant or representative change must be handled. Do not assume changing a portal email transfers every responsibility.

Before signing, your role chart should make the full path visible from application through final records. Read forms as substantive documents, not just obstacles to getting a permit. A clear division of work allows the owner to delegate practical administration while still understanding what each participant has agreed to do.

A role chart to attach to the proposal

Use separate rows for application preparation, technical design, owner authorization, agency payment, portal monitoring, issued-plan distribution, inspection readiness, site attendance, corrections and final-document delivery. Put a named person or company in each row. Where two parties share a task, explain the handoff rather than listing both and hoping they coordinate.

Ask the proposed applicant which responsibilities arise from the actual form or permit arrangement and which are simply contractual services. Read any owner declaration carefully. If its meaning is uncertain, obtain appropriate advice before signing; a contractor's preference for that arrangement does not answer the owner's responsibilities.

Test the chart against an ordinary interruption. If the coordinator is unavailable when a reviewer asks a question, who receives it and responds? If the installer finishes but a correction remains, who tracks it? These scenarios reveal gaps while the agreement can still be clarified. The chart does not alter statutory or professional duties, but it makes the practical work visible and reduces the chance that a necessary task falls between participants.

Keep signed authorizations and declarations in the owner's file, not only in the contractor's account. Record what each document covers and when it was signed. If the scope or representative changes, ask whether an update is needed. This makes delegation traceable and helps a replacement participant understand the existing arrangement without treating possession of a portal login as proof of every authority or responsibility on the project.