From Grant Award to Groundbreaking: The Arizona Work Begins After Approval

Insights category: Government Relations

Winning a federal grant is a major accomplishment.

But it is not the finish line.

It starts a new phase of work. And the strongest implementation plans begin before the award, then get more detailed once the final terms are known.

Once the award arrives, your company still has to turn a written proposal into a working project: often across several Arizona cities, counties, agencies, utilities, contractors, and communities.

That is where many projects slow down.

A grant award may provide the money. It does not automatically provide the local approvals, construction schedule, public support, or operating plan needed to put that money to work.

For technology, broadband, infrastructure, and economic-development companies, the post-award period deserves the same attention as the application itself.

First, read the award as an operating document

Your Notice of Award, grant agreement, and related terms tell you what the funding can and cannot support.

Start by confirming:

• Scope: What activities, equipment, services, or construction were approved?

• Budget: Which costs are allowable, and is cost sharing required? If so, how much, from which sources, and in what form?

• Timeline: When does the period of performance begin and end?

• Milestones: What must be completed before the next payment or reporting deadline?

• Special conditions: Are environmental reviews, additional approvals, or extra reports required?

• Partners: Which organizations are responsible for portions of the work?

Think of the award like a set of building plans. You may have room to make normal adjustments, but you cannot quietly move the building to another lot or add three new floors without approval.

Federal financial assistance often carries requirements involving financial management, performance measurement, procurement, reporting, internal controls, and recordkeeping. Which provisions of 2 CFR Part 200 apply depends on the program, the recipient's legal status, agency regulations, and the award terms. For-profit recipients and subrecipients should confirm their applicable requirements rather than assume every provision applies the same way.

Your specific award may also include additional conditions. Use the award documents together with applicable statutes, regulations, and agency guidance, not general advice alone, to determine your obligations.

Build the Arizona team before the project needs one

A company based outside Arizona may know how to deliver the technology or construction work. It may not know which local office needs to be involved first.

That difference matters.

Depending on the project, your working group may need to include:

• Local government: City, town, county, or special district officials

• State partners: Agencies such as the Arizona Department of Transportation, Arizona Department of Environmental Quality, or Arizona Department of Water Resources, depending on the project

• Utilities: Electric, water, sewer, telecommunications, and right-of-way contacts

• Tribal governments: Where projects affect tribal lands, rights, resources, or historic properties of religious or cultural significance, including properties outside tribal lands. Coordinate with the responsible federal agency on any required government-to-government consultation.

• Implementation partners: Engineering firms, construction contractors, school districts, universities, workforce groups, or local nonprofits

• Community representatives: Residents, businesses, property owners, and other people affected by the work

For a transportation project, ADOT notes that federal infrastructure implementation requires state, local, and federal partnership. That same lesson applies beyond transportation.

A broadband company, for example, may have a strong network design but still need county coordination for road crossings, utility access, construction timing, and restoration requirements.

Create one master schedule, not five separate ones

Projects often have separate schedules for engineering, permitting, procurement, construction, grant reporting, and public communication.

That creates blind spots.

Instead, build one master schedule that shows how every piece connects.

The sequence below is illustrative. Some tasks can run in parallel; others have to wait on agency authorization, environmental review, property access, or permit approval.

For example:

1. Confirm award conditions and approved budget.

2. Verify site control, easements, and right-of-way.

3. Begin required environmental reviews.

4. Complete preliminary engineering and design.

5. Coordinate utilities and public agencies.

6. Obtain local and state permits.

7. Release bids or select contractors using required procedures.

8. Order long-lead equipment.

9. Begin construction.

10. Track performance, spending, and community impacts.

11. Complete closeout and continuing obligations.

The key is to identify the “gates.”

If environmental clearance is required before construction, that becomes a gate. If a local permit is needed before trenching, that becomes a gate. If equipment must meet grant-specific requirements, that becomes a gate.

Do not begin ground-disturbing work until the authorizations and clearances required for that work are in place. A groundbreaking ceremony is worth scheduling for when the project is genuinely ready, not simply because the award was announced.

Permitting is where Arizona details become real

Arizona is not one single permitting environment.

Requirements can change by location, land ownership, project type, and the agencies involved.

A project in unincorporated Pima County may follow a different path than one inside the City of Phoenix. A rural broadband installation may face different road, utility, and access questions than a technology facility near a major employment center.

Before construction, confirm whether your project needs:

• Local approvals: Zoning, site plans, building permits, grading, traffic control, or right-of-way permits

• Environmental approvals: Reviews tied to federal funding, water, stormwater, habitat, or cultural resources

• Utility coordination: Location, relocation, crossing, connection, and restoration plans

• Property rights: Easements, leases, access agreements, or rights-of-way

• Tribal coordination: Consultation or agreements where applicable

• Construction requirements: Safety, labor, domestic sourcing, wage, bonding, or contractor provisions tied to the award

Do not assume your engineering consultant or general contractor owns all of these responsibilities.

Assign an owner for each approval. Put the expected completion date in the master schedule. Then track the approval until it is documented.

Choose implementation partners for more than technical skill

Technical qualifications and compliance capacity matter, but selection has to follow the procurement method that applies to the project. Under sealed bidding, award generally goes to the lowest responsive and responsible bidder. Under competitive proposals, selection may weigh price and other disclosed evaluation factors.

So build the qualification and compliance requirements into the solicitation and evaluation process up front. Your contractors and partners need to understand the project's compliance obligations, documentation needs, and public setting.

Questions worth asking during selection:

• Have they worked on federally funded projects?

• Can they maintain complete invoices, payroll records, change orders, and subcontractor files?

• Do they understand the difference between a contractor and a subrecipient?

• Can they meet Arizona licensing, safety, and local permitting requirements?

• Do they have experience working around residents, businesses, roads, schools, or active facilities?

• Can they meet the schedule without cutting corners?

Federal procurement rules generally emphasize competition, documentation, conflicts of interest, and written procedures. Review 2 CFR §§ 200.317–200.327 before selecting partners.

If a contractor proposes a major change, pause before approving it. A change that seems minor, such as switching equipment, changing a route, or moving a facility, may affect the approved budget, project goals, environmental review, or grant conditions. Where 2 CFR § 200.308 applies, a change in scope or objectives needs prior written approval even if the budget does not change.

Keep the project tied to its original promises

Your approved project and award documents establish your commitments. Identify which application promises were actually incorporated into the award, then track those obligations from day one.

Those commitments may include:

• Miles of broadband installed

• Facilities completed

• Businesses or households served

• Jobs created or supported

• Training delivered

• Equipment deployed

• Safety, access, or performance improvements achieved

For example, if your approved award commits the project to serving a specific rural area, moving the project to a more convenient location may require prior written approval. If your approved performance measures include a certain number of participating businesses, create a system to document participation as the work progresses.

Under 2 CFR § 200.301, federal awards focus on measuring performance against approved goals and objectives.

The simple rule is this: spend money in a way that supports the approved purpose, and collect evidence that shows what the project accomplished.

Make reporting part of the weekly routine

Reporting should not be a frantic exercise at the end of each quarter.

The following is a suggested internal management rhythm. Formal submissions must follow the deadlines, formats, and requirements in your award.

• Weekly: Schedule, permitting, construction, and risk updates

• Monthly: Spending, invoices, cost share, contractor performance, and milestone review

• Quarterly or as required: Formal financial and performance reporting

• At major changes: Written review of scope, budget, timeline, and approval needs

Keep one organized record system for:

• The award and amendments

• Invoices and payment records

• Procurement files

• Contracts and subawards

• Timesheets and payroll records

• Permits and environmental documents

• Performance data

• Meeting notes and decisions

• Public notices and community feedback

• Change orders and approval letters

Confirm the applicable retention period before closing project files. Under 2 CFR § 200.334, the general rule is three years from submission of the final financial report, with exceptions that can require longer retention, such as unresolved audits, litigation, or certain property records.

Good records do more than prepare you for an audit. They help your team answer basic questions quickly: What was approved? What has been spent? What changed? Who approved it? What happens next?

Communicate before the bulldozers arrive

Communities do not experience your grant application.

They experience road closures, construction noise, utility work, changed traffic patterns, new equipment, and, in the best case, a useful improvement.

Tell people what is happening before they have to discover it themselves.

A practical communication plan should explain:

• Purpose: What the project will do

• Location: Where work will take place

• Timing: When work begins and how long it may last

• Impact: What residents and businesses should expect

• Access: Who to contact with questions or concerns

• Progress: What has been completed and what comes next

A broadband project, for instance, should explain why crews are working along a particular road, how driveways will be handled, and when pavement or landscaping will be restored.

Listening is part of execution.

A practical 90-day post-award checklist

During the first 90 days, or sooner where award deadlines require, aim to establish the following management systems, confirm applicable requirements, and identify unresolved approvals. Some environmental reviews, permits, and site-control issues may take longer; the goal is to identify those dependencies early and manage them deliberately.

1. Read: Review the full award, budget, timeline, and special conditions.

2. Assign: Name project, compliance, financial, and community leads.

3. Map: Identify Arizona agencies, local governments, utilities, partners, and affected communities.

4. Schedule: Build one master timeline with approval gates.

5. Verify: Confirm site control, permits, environmental requirements, and procurement rules.

6. Measure: Turn the incorporated application commitments into trackable performance measures.

7. Communicate: Begin regular updates before visible construction starts.

8. Escalate: Identify decisions that require federal or pass-through approval before acting.

Bonus thought: The groundbreaking is a checkpoint, not the finish line

A groundbreaking is worth celebrating.

But the real win is a project that stays on schedule, follows its commitments, serves the community it was designed to help, and can withstand review years later.

That takes more than technical talent. It takes local coordination and steady attention to how Arizona government actually works.

At Valadez & Associates, we help companies connect federal funding goals with Arizona-specific execution. Our work may include local government coordination, permitting strategy, stakeholder communication, and support for major capital projects. You can also learn more about our approach and review an example involving a major capital project in Pima County.

Federal funding can help build important things in Arizona.

The responsible next step is making sure the work is planned openly, coordinated locally, and delivered the way it was promised.