Service Design

Ontario Dig Authority

Adding accountability to dig date changes, without adding work

How do you add accountability to a process the sector already values, without making it harder to use?

orange flag and painted markings beside a dig site

Scope

  • Research design
  • Internal staff survey & stakeholder
  • workshops
  • Customer co-design workshops
  • One-on-one user interviews
  • Journey mapping
  • Feature prioritization
  • Prototyping & design iteration
  • Usability testing & validation
  • Future-state roadmap

The Ontario Dig Authority (ODA), formerly Ontario One Call, runs Ontario’s underground infrastructure notification system.

Before anyone digs, they file a locate request, and utilities or their locate service providers mark buried lines within a set window. When a locator can’t make the date, they can renegotiate it with the excavator.

Challenge

Renegotiation is a valued, necessary tool for keeping construction moving in Ontario. But the way it was recorded only showed one side of the conversation. A UIO or LSP could change a ticket’s date in the system without any confirmation from the excavator. Excavators weren’t notified of the change and had no obligation to respond.

The result was disputes, thin documentation and no shared understanding of what silence meant. When a renegotiated locate led to a complaint, ODA had little more than a new date to go on, and had to piece events together by talking to both sides.

ODA asked Q30 to find out how renegotiation was actually playing out across the sector, and to design a better process.

When a complaint came in, ODA had little more than a new date to go on.

Our Response

The most important finding came early. The sector was highly satisfied with renegotiation and with ODA’s ticketing system. That’s rare in research like this. It meant the real risk wasn’t doing too little. It was doing too much.

So we set ourselves a clear brief: increase accountability on both sides, without adding friction. Instead of a new portal or a system overhaul, we designed one added step. The date only changes once both parties agree.

Excavators, who are often in the field, can accept or decline by email from their phone, with no login. Every request, response and reason is recorded in the service portal automatically. And the change will roll out in stages, so ODA learns before it enforces.

The real risk was in doing too much, not too little.

One missing step, found by listening

Listen to both sides of the conversation

A renegotiation involves the excavator, the locator and the utility. We ran 16 research sessions: 5 with ODA teams and 11 across the sector, from small landscapers to large contractors, urban locators to remote independents, and municipalities that both own infrastructure and dig. Because people were talking about their own regulator, we allowed for what they might not say.

ODA often only saw a renegotiation when something went wrong.

Before the redesign, a renegotiation was mostly invisible to ODA. Talking to every party showed us what was below the line.

Map where renegotiation breaks down

Five personas, journey maps and a pain point map traced a ticket from submission to dig. They found seven friction points: season-opening ticket floods, oversized ticket areas, contacts who aren’t decision-makers, and phone agreements that never get confirmed in writing. We prioritized them with ODA and its sector advisory committee.

Many problems start well before anyone renegotiates.

A simplified version of the pain point map. The shaded steps happened entirely outside OOC’s systems, so OOC couldn’t see them.

Design to guardrails, not features

We started by agreeing five guidelines with ODA: mutual consent, a clear meaning for silence, visible status, a fit with how each group works, and careful change management. Guardrails kept it light: no new logins, minimal change to members’ software, one or two taps to respond.

The new process has four steps: request, notify, decide, apply. With no response in three business days, the original date stands. Bulk requests go out as one email, and one request covers every utility on a ticket. We documented it in 21 wireframe screens and reviewed it with ODA’s compliance, operations and technical teams.

Nothing changes on the work date until the other side says yes.

One added step. Nothing changes on the work date until the other side says yes.

A phased rollout was put in place with a small number of initial users to capture feedback and make sure the technology loop worked as intended.

Learn before you enforce

We recommended three phases: a pilot with a hand-picked group, a tracking-only phase that builds evidence before enforcement, then full rollout. Success measures are set before the pilot, neutral interviews follow it, and new research six months after launch shows what to improve.

Results

Excavators will get a say before a work date moves, through a simple accept-or-decline email they can answer from the field.

Locators and utilities will have a clear rule for what silence means. ODA’s compliance team will have a full record of every request, response and reason, instead of rebuilding events after a complaint. Because the change builds on a system the sector already values, it adds accountability without adding work. ODA also has a phased rollout plan, with success measures and a review built in, to guide what comes next.

Let’s make something better together.