Loading your page…
Project planning resources
A project can have several legitimate application numbers because different authorities and owners control different work. Build one approval register, then connect each record to its scope, documents and next decision. That makes it possible to distinguish a received application from a reviewed plan, an issued permit and permission to begin work.
For owners, operators and project teams preparing a decision or handoff. Apply the checklist to the actual property, route, agreement and reviewing authority.
Request a project reviewAdministrative completeness and technical approval are separate milestones.
Select the category matching the actual work. Obtain the owner's signatures and representation documents. Where the utility owner must apply, deliver the coordinated package to its authorized submitter rather than substituting the contractor or drawing preparer.
Check naming, format, signatures, seals and required attachments. Reconcile construction-value information with the scope. Assign portal tasks and fee notices to a responsible person, and confirm the application was actually submitted rather than left as a draft.
Record intake acceptance, substantive review, comments, plan approval and permit issuance separately. Track fees, release holds, expiration dates and extensions or required restarts. A portal notification should produce a clear next action.
The register should explain the connection, not just list office names.
Coordinate site and building packages and their shared geometry. Sequence landlord or other private review before it forces late redesign, while keeping private approval separate from government authorization.
Assign specialty fire-system planning and permits alongside the building set. Connect the actual menu and food process to equipment and facility design. Reconcile pool and pool-house submissions with a common site and operating model.
For each application number, record the scope, authority, plan revision, open conditions and responsible person. When one review changes a shared element, notify and revise the related submissions rather than letting approved versions diverge.
Keep the initial inquiry brief. Detailed or confidential records can be exchanged through an appropriate channel after the assignment is defined.
Collect the site or route, operating description, design scope, authority checklists, owner authorization, current application numbers and any private-owner or utility criteria.
An approval register showing the authority or owner, application type, responsible submitter, plan issue, required inputs, current status, dependency, next action and expiration or release condition.
Do not begin affected work because a portal says received or because one reviewer approved a drawing. Resolve issuance conditions, private access, specialty approvals and any start-of-work requirements with the responsible parties.
Before you begin
Collect the site or route, operating description, design scope, authority checklists, owner authorization, current application numbers and any private-owner or utility criteria.
An approval register showing the authority or owner, application type, responsible submitter, plan issue, required inputs, current status, dependency, next action and expiration or release condition.
No. It helps organize the project questions and responsibilities. The actual scope, qualified professionals, property and asset owners, and reviewing authorities determine the applicable requirements and approval sequence. Confirm current instructions before submitting.
Source check ·
Use the linked authority’s current instructions for your actual property, use and work. Agency procedures can change; a source check is not a project approval.
An example showing separate application, document and payment requirements before a package enters review.
An example of the utility-owner and authorized-representative roles in a roadway application.
Your next step
Start with what you know. We’ll help define the path ahead.