We’ve historically measured progress in public infrastructure by what we could build. Longer spans. Deeper foundations. More complex interchanges delivered on compressed timelines. Every generation of contractors has been more capable than the one before it, and every generation of software has promised to make that capability visible.
We never stopped to ask whether our decision-making kept pace with our ambition.
It hasn’t.
Right now, a program director somewhere is reviewing a status report assembled by hand from four different systems, about a project she is responsible for but cannot truly see. The schedule lives in one tool. The budget lives in another. The field updates arrive by email, if they arrive at all. She will spend the better part of a morning reconciling four versions of the truth before she can make one decision. The data exists. The insight doesn’t. And somewhere in that gap, a decision that needed to be made on Tuesday gets made on Thursday. Or not at all.
This is not a technology failure. It is a failure of intelligence architecture.
The lifecycle nobody sees whole
Here’s what makes that failure so expensive: it doesn’t happen once. It happens at every handoff.
- A historical bid pattern that should inform next quarter’s estimate sits untouched in a system nobody reopens after award.
- A contractor’s field data — the materials, the delays, the environmental conditions that actually shaped a project’s outcome — never makes its way back into how the next project is planned.
- An agency awards a contract with real confidence, then loses that same confidence six months later, because the tools that helped them choose a contractor have nothing to say about how to manage one.
Plan. Estimate. Bid. Build. Handoff. Five stages, and at every seam between them, information that could have made the next stage smarter simply stops moving.
Ask a program director where their portfolio actually stands, and you’ll get an honest answer: last month’s version of it. Ask an estimator whether this bid is smarter than the last one, and you’ll get a shrug: it’s within range. Ask a state DOT whether the dollars it’s distributing to local agencies are going where they’ll do the most good, and you’ll get a spreadsheet, not a forecast.
None of those are bad answers. They’re the best answers a fragmented system can give. That’s the problem.
Data isn’t the constraint. Trust in it is.
Ask most executives in this industry what’s stopping them from answering their hardest questions, and the honest ones will say data integrity, not data absence. The information has been collected for decades. Materials logs. Bid histories. Change orders. Compliance filings. What’s missing isn’t the record. It’s a reason to trust what the record says when it’s stitched together from systems that were never built to talk to each other.
That’s a harder problem than buying another dashboard, and it’s the one worth solving. Because once an agency can trust its own historical data enough to build on it, the questions change. Not “what happened on this project?” but “what does this project’s pattern tell us about the next fifteen?” Not “did we spend the money?” but “did we spend it on the corridors that needed it before they became emergencies?”
That shift — from records to forecast, from what we can report to what we can predict — is the actual opportunity in front of this industry. Not a better report. A different relationship with the record.
The connective tissue, not another platform
An intelligence layer for public infrastructure isn’t a new system to log into. It isn’t a dashboard with more tabs. It’s the connective tissue between what a contractor knows in the field and what an agency needs to decide in the office, in time for the decision to still matter.
When that layer exists:
- A project manager knows a critical path item is drifting three days before it becomes a problem, not three weeks after.
- An estimator sees a market signal before a bid comes in 40% over expectation, not after the award is already regretted.
- A program director sees a full portfolio, not last month’s snapshot reconstructed from four systems, but where things actually stand today.
- A state agency distributing IIJA dollars can tell you not just what a corridor cost last year, but what it’s likely to need next year, before a local partner has to ask.
That’s not a hypothetical. It’s what happens when fifty years of transaction history — the planning phase, the letting phase, the pre-bid and post-award record on both the contractor’s side and the agency’s — finally gets treated as an asset instead of an archive.
Infotech has sat inside that transaction record for half a century, as the official contractor behind AASHTOWare Project™ software development. We didn’t get there by telling agencies and contractors we know their business better than they do. We got there by earning the kind of trust that comes from showing up in the planning phase, the bidding phase, and every phase after, for longer than most of the people reading this have been in the industry.
That is the same infrastructure — the letting systems, the bidding events, the compliance records — that public agencies across the country already run on. The opportunity in front of us isn’t replacing any of that. It’s finally asking that record to do more than sit still: to tell an agency or a contractor not just what happened, but what’s likely to happen next. The domain expertise was never ours to claim. It’s yours. Our job is making sure it doesn’t go to waste the moment a project moves to its next stage.
What’s actually at stake
We have built extraordinary physical infrastructure in this country. Bridges that will outlast the people who approved them. Highway systems that reshaped how an entire economy moves. We have not yet built the intelligence layer to match it.
The organizations that figure this out over the next decade won’t just have better bid years or smoother handoffs. They’ll have a fundamentally different relationship with their own history, one where fifty years of data finally does what data is supposed to do, which is tell you something true about tomorrow.
The organizations that don’t will keep doing what the industry has always done well: building things. And they’ll keep making the decisions about those things the way we always have: a step behind, a system removed, and a Tuesday too late.
That gap is closing. The only question left is who closes it first.
Curious what an intelligence layer looks like in practice for your agency or your bid pipeline? Get in touch with our team →
Author
Shelly Nooner
Chief Product Officer
Shelly Nooner is Chief Product Officer at Infotech, where she oversees product strategy, engineering innovation, AI initiatives, and data-driven strategy for the public sector, including Infotech’s role as the official contractor for AASHTOWare Project™ software development. She brings over two decades of experience managing large-scale civil software teams, including 25 years at Trimble, and holds an Executive MBA (GMP33) from Harvard Business School.