Utility Engineering Services Kickoff Checklist- ARUSI

A successful utility project does not start with drawings. 

It starts with clarity. 

Before a designer opens a CAD file, the project team needs to understand the site, the utilities, the approval path, the delivery schedule, and the real-world constraints that could affect construction. When those details are missing, utility engineering becomes reactive. Teams spend more time chasing records, revising drawings, resolving conflicts, and explaining delays. 

That is where a strong kickoff process matters. 

For Arizona infrastructure projects, the right kickoff checklist can help project owners, utility teams, developers, municipalities, and general contractors reduce confusion before it becomes expensive. It gives everyone a shared starting point and helps the engineering team move from assumptions to decisions. 

Why the kickoff stage shapes the entire utility design process 

Utility engineering services touch more than one drawing package. They affect routing, permitting, coordination, constructability, cost, schedule, and long-term maintenance. 

A rushed kickoff often creates predictable problems: 

• Existing utilities are not fully understood.  

• Survey data is incomplete or outdated.  

• Utility owners are brought in too late.  

• Jurisdictional requirements are unclear.  

• Design standards are missing.  

• Review timelines are too optimistic.  

• Project roles are not defined.  

These issues may look small early in the project. In the field, they can turn into redesign, construction delays, change orders, or approval bottlenecks. 

A disciplined kickoff helps prevent that. It creates a practical foundation for utility design, Electrical Distribution Engineering Design work, telecom planning, dry utility coordination, survey, CAD documentation, and permitting. 

Start with the project’s purpose, not just its scope 

Scope tells the engineering team what to produce. 

Purpose explains why the work matters. 

Before utility design begins, the project team should clarify what is driving the project. Is the goal to serve a new development? Relocate existing utilities? Expand broadband access? Improve reliability? Support EV charging infrastructure? Replace aging cable? Prepare for future growth? 

This context changes the design approach. 

A utility relocation project may focus on minimizing disruption. A broadband project may prioritize route feasibility, permitting, and long-term access. A public infrastructure project may require strict documentation, transparent review cycles, and clear compliance with agency standards. 

When the “why” is clear, the engineering team can make better decisions about routing, documentation, coordination, and design priorities. 

Confirm existing utility records before design begins 

Most utility design challenges start with incomplete information about what already exists. 

Before kickoff, project owners should gather every available record that may affect the site or corridor, including: 

• Existing utility maps  

• GIS files  

• Record drawings  

• Previous as-builts  

• Easement documents  

• Right-of-way information  

• Service point information  

• Utility owner records  

• Prior project documentation  

• Known conflicts or field issues  

These records do not replace field verification, but they give the engineering team a starting point. 

The goal is not to assume every record is perfect. The goal is to know what information exists, where the gaps are, and what needs to be verified before design decisions become fixed. 

Bring survey and field conditions into the conversation early 

Utility design is only as reliable as the site information behind it. 

For Arizona infrastructure projects, survey and field conditions can affect routing, trenching, pole placement, equipment locations, access, drainage, clearances, and permitting. A design that looks clean on paper may become difficult to build if the project team does not understand the actual corridor. 

Depending on the project, the kickoff should address: 

• Topographic survey needs  

• Visible utility features  

• Roads, curbs, sidewalks, and structures  

• Drainage features  

• Fences, walls, slopes, and access limits  

• Existing poles, cabinets, vaults, meters, and handholes  

• Property limits and easements  

• Field verification requirements  

Bringing survey into the process early helps the engineering team reduce assumptions. It also helps project owners understand what information must be collected before the design can move forward with confidence. 

Identify every approval authority before the first submittal 

Utility projects often involve more stakeholders than expected. 

A project may need input or approval from municipalities, county agencies, utility owners, private property owners, state agencies, tribal jurisdictions, transportation departments, telecom providers, electrical utilities, gas utilities, and internal owner teams. 

That list should be defined as early as possible. 

The kickoff should answer: 

• Who owns the existing infrastructure?  

• Who approves the design?  

• Who issues the permit?  

• Who reviews right-of-way impacts?  

• Who needs to inspect the work?  

• Who must approve changes?  

• Who has final acceptance authority?  

When approval authorities are identified late, project schedules get squeezed. Submittals may be incomplete. Comments may arrive after design decisions have already been made. Teams may have to revise drawings for requirements they could have known earlier. 

Good utility coordination starts by knowing who needs to be involved. 

Align on design standards, file formats, and deliverables 

A utility design package has to work for more than the design team. It has to work for reviewers, permit offices, utility owners, contractors, inspectors, and future maintenance teams. 

That means standards matter. 

At kickoff, the team should confirm: 

• Required CAD platform and file format  

• Utility owner drawing standards  

• Layer naming and symbology  

• Title block and sheet requirements  

• Design notes and standard details  

• Scale and sheet size  

• Submittal format  

• Revision tracking process  

• Required calculations or supporting documentation  

• Final closeout expectations  

These details may feel administrative, but they directly affect review speed and document quality. 

A clean, standards-aligned package is easier to review, easier to revise, and easier to use in the field. 

Build the communication rhythm before issues appear 

Utility projects move better when communication expectations are clear. 

At kickoff, the team should decide how updates, questions, comments, and revisions will be handled. This is especially important when multiple parties are involved, such as owners, utilities, designers, agencies, general contractors, and subcontractors. 

The team should define: 

• Main points of contact  

• Meeting schedule  

• Review deadlines  

• Comment tracking process  

• Escalation path  

• Submittal dates  

• Revision expectations  

• Response time expectations  

• Decision owners  

Fast communication matters, but speed alone is not enough. The communication also has to be precise. A quick answer that creates confusion is not helpful. A clear answer that arrives too late can still delay the project. 

The best kickoff process creates both speed and discipline. 

Utility engineering kickoff checklist 

Before utility design begins, project teams should confirm the following: 

1. Project purpose, scope, and delivery goals  

2. Site limits, corridor limits, and service area  

3. Existing utility records and available GIS data  

4. Previous as-builts, record drawings, and easement information  

5. Survey needs and field verification requirements  

6. Known utility conflicts or high-risk locations  

7. Utility owners and approval authorities  

8. Jurisdictional and permitting requirements  

9. Applicable utility standards and design criteria  

10. CAD standards, file formats, and deliverable expectations  

11. Review schedule, submittal milestones, and comment process  

12. Communication roles, escalation paths, and decision owners  

This checklist does not remove every project risk. Nothing does. But it helps project teams start with fewer blind spots and a stronger shared understanding. 

Better inputs create better outcomes 

Utility engineering is not just a technical task. It is a coordination discipline. 

The best design teams do more than produce drawings. They help owners understand what needs to be decided, what needs to be verified, what needs to be approved, and what could slow the project down if left unresolved. 

For Arizona infrastructure projects, that kind of discipline matters. Utility corridors are busy. Stakeholder requirements can be complex. Public and private projects often involve multiple approval paths. The cost of unclear information can be high. 

A strong kickoff helps the project team move with more confidence. 

It gives the engineering team the information needed to design with purpose. It gives project owners a clearer path to approvals. It gives contractors better documents to build from. And it helps everyone reduce the avoidable delays that come from missing inputs. 

ARUSI supports Utility Engineering, Coordination and Consulting, electrical distribution design, telecommunications design, transmission line design, CAD/drafting, survey, dry utility engineering, and design-build project support for infrastructure teams across Arizona and the Southwest. 

If your team is planning a utility project, bring ARUSI in before design starts. The earlier the right information is organized, the stronger the first submittal can be.