TransCore Alternatives: Tolling and Permitting Systems, Integrators, and Owning It In House

Why agencies start looking for a TransCore alternative

It usually starts with a change order. The legislature adjusts a fee schedule, a new permit class appears, an escalation rule for unpaid violations changes, or a court decision alters how notices must be worded. The agency needs the system updated, the request goes to the vendor, and the answer comes back as a priced change with a delivery date some months out. Nobody has done anything wrong. That is exactly how a services contract works. But an agency whose policy environment moves several times a year and whose systems move once a year feels the mismatch constantly.

The second trigger is a contract cycle. Long term system contracts come up for rebid, and rebid forces the question everyone avoided while operations were stable: what do we actually own here, and what happens if we choose a different vendor. The honest answer is frequently uncomfortable. The roadside equipment is one thing, the back office application is another, the data model is documented to varying degrees, and the customer service operation may be a staffed service rather than software at all. Untangling those before the procurement rather than during it is the difference between competition and a foregone conclusion.

The third trigger is public expectation. Residents compare a tolling account portal to their bank app and a permit application to any modern online form. When a haulier waits two days for a routing decision that a well built system could return in minutes, that is not a vendor failure so much as an architecture that predates the expectation. It still lands as complaints in the commissioner's inbox.

What TransCore genuinely does well

Tolling at scale is harder than it looks from outside. A lane has to read a transponder at highway speed in bad weather, capture plate images, associate a transaction with an account, hand off to interoperability partners in other jurisdictions, and do it millions of times with an error rate low enough to survive legal challenge. That end to end capability, roadside through back office, is a specialist discipline, and companies that have run it for decades carry knowledge you cannot hire quickly.

The second genuine strength is fluency in public delivery. Government procurement, bonding, prevailing wage rules, accessibility standards, records retention, audit expectations, and interoperability agreements are real constraints, and vendors who work in this market build for them by default. A software firm that has never delivered under a public contract discovers those requirements late and expensively.

Third, single point accountability. When lane hardware, transaction processing, and the back office come from one contract, there is one throat to hold when revenue goes missing. Agencies that unbundle gain flexibility and take on integration risk themselves, and for a small agency that trade is not automatically worth it.

Where the integrator model strains

The first strain is ownership. In a typical arrangement the agency has a licence and a service, not a codebase. That is fine until you want to change something quickly, integrate with a state system that did not exist when the contract was signed, or take your operation to a different provider. Every one of those becomes a negotiation. The cost is not really money, it is tempo: the agency's ability to respond to its own policy environment is set by a contract vehicle rather than by need.

The second is configuration ceiling. Back office systems built for many agencies carry the union of their requirements, exposed as settings. Your jurisdiction inevitably has a rule that is not a setting: a hardship deferral, a specific notice sequence, an exemption class, a reciprocal arrangement with a neighbouring authority. That is when workarounds start, usually as a spreadsheet maintained by one experienced staff member, and that spreadsheet becomes an operational dependency nobody has documented.

Third, reporting and revenue assurance. Agencies need to reconcile transactions to revenue, prove leakage is within tolerance, and answer legislative questions with numbers that hold up. If the answers require a vendor report request, you have handed away part of your oversight function. Direct query access to your own transaction data is a reasonable thing to insist on, and it is much easier to obtain during procurement than after.

Fourth, the customer experience gap. Violation processing, dispute handling, payment plans, and permit applications are policy heavy and public facing. They change often and they are judged against consumer software. Enterprise back offices are optimised for correctness and throughput rather than for a person on a phone at midnight trying to pay a notice before it escalates, and closing that gap through change orders is slow and expensive.

Who should stay exactly where they are

Stay if the roadside is the system. Transponder reads, image capture, classification, and interoperability messaging are safety adjacent, revenue critical, and standards bound, and there is no version of this where an agency writes that itself. Stay if you have no permanent internal technology capacity, because custom systems need an owner every year, not just in the build year. Stay if your procurement framework effectively requires a single prime contractor with performance bonding, since fighting that is a longer project than any software. And stay if the operation you are unhappy with is a staffed service, such as a customer service centre, because that is a people and process problem that different software will not solve on its own.

The realistic options

Rebidding is the first option, and done properly it is more powerful than it looks. Kapsch TrafficCom, Conduent, Neology, and Q-Free compete in this market, and a rebid with better terms can change your position substantially: data access rights, source code escrow, documented interfaces, an exit plan, and a separation between roadside and back office scope. Most of the pain agencies describe comes from contract terms, not from code quality.

The second option is unbundling. Keep roadside with a specialist, procure or build the back office separately. For oversize and overweight permitting there are dedicated products worth evaluating, including Bentley SUPERLOAD and ProMiles, which carry routing and bridge analysis capability that would be genuinely unwise to rebuild from scratch. Take the analysis engine, own the workflow around it.

The third option is a custom layer over the systems you keep. Public portals, permit intake and issuance workflow, violation lifecycle management, payment plan administration, exemption handling, and reporting can be built on top of an existing transaction system through its interfaces. You keep the revenue critical machinery and take ownership of the parts that follow policy.

When building pays back

Build when policy velocity exceeds contract velocity. If your fee schedules, permit classes, or escalation rules change more than once a year, and each change costs a priced change order and a multi month wait, the payback calculation is simple. Two or three years of change orders often exceeds the cost of owning the workflow layer outright.

Build when the public interface is the reputational risk. A permit portal that returns a decision in minutes, tells a haulier exactly why a route was refused, and lets them fix and resubmit is worth real money in reduced call volume and fewer escalations. That is a well understood build, not a research project.

Build when you need one view across systems that will never merge. Agencies run tolling, permitting, citations, and registration on different platforms from different eras, and the questions leadership asks cut across all of them. A reporting and case layer that reads from each is far cheaper than any consolidation programme, and it delivers in months rather than years.

Migration reality for public systems

Money in flight is the hard part. Open violations, active payment plans, disputed transactions, and permits in progress all have legal status, and none of them can be lost or duplicated in a cutover. Plan a parallel period covering at least one full billing and escalation cycle, and reconcile to the cent, because a discrepancy here is an audit finding rather than a bug.

Get your data out in a documented, readable form: transaction records, account and customer data, violation history with notice dates and delivery evidence, permit applications with decisions and the reasoning behind them, and payment records. Notice history matters enormously because the legal defensibility of an escalation rests on proving what was sent, when, and to which address. Retain the old system in readable form well past cutover, since disputes and public records requests reach back years. And budget seriously for staff retraining, since experienced clerks carry institutional knowledge that no configuration file records.

Cost bands

TransCore and its peers deliver through competitively procured contracts, so the number depends on scope, transaction volume, and whether operations staffing is included. There is no list price and comparisons across agencies are rarely like for like. On the custom side, using Digital Heroes delivery experience: a focused build covering permit intake, review workflow, issuance, and a public portal runs roughly $70k to $160k over 14 to 20 weeks. A full back office replacement covering accounts, violations, payments, notices, and reporting runs roughly $250k to $600k and up over nine to eighteen months, and payment card handling and hosting compliance add cost in any scenario. Public procurement time sits on top of all of it and is often the longest single line.

The verdict

Keep a specialist for the roadside and for high volume transaction processing, because that is genuinely their discipline and not yours. Use rebid to fix the terms that actually hurt: data access, documented interfaces, escrow, and a real exit plan. Build the layer where policy lives, which is permitting, violations workflow, and public self service, because those change with your legislature rather than with a vendor roadmap. The agencies that end up happiest are not the ones that replaced everything. They are the ones that stopped paying change orders for their own rules.