Irth Solutions Alternatives for Damage Prevention and Locate Ticket Management

Why utilities and locate contractors start looking for an Irth alternative

The first pressure is volume pricing meeting a construction boom. Ticket counts are not something you control. A fibre build, a road programme or a wave of residential development lands in your territory and your ticket volume doubles without your revenue doubling. Software priced against tickets makes somebody else's construction schedule into your cost line, and finance notices.

The second pressure is the gap between a ticket system and a field operation. Tickets arrive, get screened, and get assigned. Then the real work happens: a locator drives somewhere, marks the ground, photographs it, and clears the ticket before a legal deadline. Whether that locator was routed efficiently, whether the photograph is good enough to defend a claim two years later, and whether the technician who is quietly twice as productive as everyone else is being learned from, are operational questions that a ticket management system was not designed to answer.

The third is what happens after a strike. A contractor hits a line, everyone insists they were marked correctly, and the entire dispute rests on evidence quality: the ticket, the screening decision, the positive response sent, the timestamps, the photographs and their location metadata. Assembling that packet from several systems while a claim is live is a bad way to spend a week.

What Irth Solutions genuinely does well

Be fair about the unglamorous part. One call ticket ingestion is a grind. There are many notification centres across North America, each with its own format, its own quirks and its own change schedule, and none of them coordinate with the others for your convenience. A vendor absorbing that work is providing real value precisely because it is tedious and permanent. Nobody builds a career on parsing ticket feeds, and nobody wants to explain to a regulator that a format change silently dropped tickets for a fortnight.

Positive response handling is the second genuinely valuable piece. Responding to a ticket within a statutory window is a legal obligation with real consequences, and a system that tracks deadlines, escalates before they are breached, and returns responses to the right centre in the right format is doing work that protects the business rather than merely organising it.

Irth also serves both utilities and locate contractors, and it has been in this specific market long enough to have met the edge cases. If you are a utility with straightforward operations in a limited footprint, this is a category where buying is clearly correct and building would be an eccentric decision.

Where it strains

• Screening logic ceilings. Every asset owner has its own rules about which tickets need a physical locate, which can be cleared by records, and which need escalation. Complex rules pushed into configuration screens become fragile.
• Routing and productivity. Assigning tickets efficiently across a territory with varying deadlines is an optimisation problem, and generic assignment leaves margin on the road.
• Evidence quality. Photograph capture, location metadata and completeness checks at the moment of marking determine whether a claim is defensible, and that is a field application problem more than a ticket problem.
• Integration with GIS and work management. Tickets should be screened against your actual asset records, and each seam between systems is yours to maintain.
• Client reporting for contractors. If you locate on behalf of several utilities, each wants its own service level reporting, and standard reporting rarely produces all of them.
• Per ticket or per user pricing. Costs that track volumes you do not control are uncomfortable in a business with fixed price locate contracts.

Your real options

Staying is right for most single utility buyers. If your footprint is one or two states, your screening rules are conventional, and you have no software team, replacing a working ticket platform introduces risk into a process where the failure mode is a damaged gas line. That framing should settle the question.

Switching vendors is reasonable when the pricing model or the service relationship has broken down. KorTerra and PelicanCorp are the obvious peers, each with its own strengths and its own geographic history, and utilities do move between them. Understand that switching does not change the underlying economics much, because everyone in this category prices against volume in some form.

The hybrid is the strong option for larger operators: keep ticket ingestion and positive response as a service, and build the screening, routing, field capture and analytics layer around it. That splits the problem exactly where the risk sits, since the tedious external interfaces stay with a vendor and the parts that determine your margin and your legal defence become yours.

When a custom build pays back

Build when locating is your business rather than your obligation. For a contract locating firm, margin is made in routing, technician productivity and clearing tickets before deadlines without overtime. Those are optimisation and workflow problems over your own data, and a few percent of improvement across a large ticket volume is a bigger number than the entire software budget. Nobody sells you your own routing advantage.

Build when evidence defensibility is your dominant risk. If you are an asset owner facing regular damage claims, a field application designed around what a claim needs, timestamped photographs with location metadata, mark documentation, and a complete chain from ticket receipt to response, is a direct reduction in loss. That is a specification you write, not one you shop for.

Build when you operate across many jurisdictions with different rules. Normalising screening and response obligations across states, so your operations team works one process rather than seven, is precisely the kind of internal advantage custom software creates.

Build when you locate for several utilities at once. Each client wants its own service level reporting, its own view of the same field work and its own definition of on time, and producing four versions of that by hand every month is a job that should not exist. Generating them from one dataset also means you can argue about performance with evidence rather than with recollection.

What you should not rebuild

Do not build ticket ingestion from every notification centre yourself. The formats change on schedules you do not control, the failure mode is silent, and a silent failure here means an unlocated dig site. This is the clearest example on this page of a component where the boring vendor service is worth every penny. Keep it, and treat it as an input to the system you own.

Migration reality

Two things make this migration unusual. First, positive response is a live legal interface, so it must be tested before cutover rather than after. Run the new system in parallel receiving the same tickets, generate responses without transmitting them, and compare against what the incumbent sent for at least a full month covering a busy period. Only then move transmission.

Second, ticket history is evidence. Claims arrive years after the work, so your archive of tickets, screening decisions, responses and photographs must survive the migration completely and remain searchable. Export everything, including images with their original metadata, into your own storage before you change anything, and confirm retention obligations with counsel rather than assuming a vendor default matches them.

Field retraining is the third cost and it is not small. Locators are productive because their process is automatic. Any new field application slows them for a period, so roll out by crew rather than all at once, start outside peak season if your region has one, and expect the first fortnight to look worse in the numbers before it looks better.

Cost bands and the verdict

Ticket management platforms are priced against tickets, users or assets depending on the vendor, so model the cost at the volume a construction boom would create rather than at today's average. On the build side, a focused operations layer covering screening rules, routing, field capture with defensible evidence and client reporting, sitting on top of a vendor ingestion service, runs roughly $60k to $150k over 12 to 18 weeks in our delivery experience. A fuller locate operations platform adding GIS integration, contractor management, claims handling and multi jurisdiction normalisation runs roughly $180k to $400k.

The verdict: stay if you are a single utility with a limited footprint and conventional rules, because the downside of getting this wrong is measured in struck lines rather than in inconvenience. Switch peers if the commercial relationship has failed, while accepting the economics are similar. Build the operations layer if you locate for a living, if damage claims are a material cost, or if you work across enough jurisdictions that normalising them is worth real money. Keep the ingestion service either way.