Construction Data Insights
The Tenders You Don't Win Are Still Data
Estimating teams spend most of their working year on jobs they will never win. Impact Plumbing now measures the part of that they can control: how fast a tender gets answered, how long since anyone touched it, and what the company keeps walking away from.

01
The challenge
Estimating is a volume business. Tenders arrive constantly, a fraction get qualified, fewer get submitted, and fewer again come back as work. Every commercial plumbing contractor runs at those odds. It's the cost of being in the market.
Which means the risk in an estimating department isn't losing a tender. It's losing one quietly. A tender that nobody followed up, that sat past its due date while everyone assumed someone else had it, that went cold and was never formally declined. Nothing in the numbers tells you that happened, because a tender you forgot and a tender you lost look identical at the end of the year.
Impact's director wanted the estimating team held to something. Not a win rate, which depends as much on who else bid, but turnaround and follow-up, which are entirely within the team's control. Nobody could see either. There was no record anywhere of when a tender was last actioned.
The annual view had a separate problem. Live tender reporting counts what sits in each bucket right now, which is exactly what a weekly meeting needs. It's the wrong shape for a year in review. As tenders move from qualified to submitted to won, the counts behind every earlier month move with them, so a financial year never settles. The team sat down to read a full year together and the top-line figures wouldn't reconcile against each other. The numbers weren't wrong. They just described today, not the year.
02
The solution
We stopped trying to make one report do two jobs.
The live report stays live, and still drives the weekly estimating meeting. Alongside it sits a locked version, frozen per financial year, where the numbers never move again. A year selector switches between the current year, last year and the one before, so a comparison takes a click instead of an argument about date ranges. The decision was deliberately unclever: half a day once a year to cut and lock the static copy, rather than engineering one report that tries to be both and fails at each.
The report leads with three labelled figures. Target, win rate, win rate required. Those are the numbers the business steers by, so they sit across the top where the weekly meeting reads them first, legible in a glance. The reports have been built alongside the business for years and keep being refined around what it needs to focus on next; this pass sharpened that further.
Each month the report is rendered to PDF and emailed out on the first business day after month end. That matters more than it sounds. A link points at a report that will have changed by the time anyone opens it, while a PDF is a fixed record of where the pipeline stood that morning, and a folder of them is a year you can compare against.
On the tender list itself, the status cards were replaced with the numbers the department actually runs on: how many tenders are outstanding, how many are overdue, and how many came in over the last seven and thirty days. Volume in, work in progress, and what's late.
Every tender now carries a last contacted date, stamped automatically with the author whenever a note is logged against it. It isn't a field anyone types into, because a field people maintain by hand is a field that lies. It's a real column written at the moment the note is created, which means the list can be sorted by it. Sort descending and the tenders nobody has touched in a month rise to the top.
Around that sit the smaller things that make a list usable: tender ID and revision number as visible columns, and an export of submitted tender notes to Excel for anyone who wants to work through them offline.
Two reports cover what the department gives away. A binning report breaks down disqualified tenders by sector and by client, so the business can see what it declines as a pattern rather than one decision at a time. A labour utilisation report shows where estimator hours are going, filtered to any single month across a two year window, with buttons for last week, last month, last quarter and the year to date.
03
The results
The weekly estimating meeting reads off the report from top to bottom. The figures at the top are legible, so the meeting starts with the position rather than with someone interpreting it.
Cold tenders surface by themselves. Sorting by last contacted turns "has anyone chased this?" from a question asked in a meeting into a column read before it.
The financial year holds still. A locked year can be quoted in a board pack, sent to an accountant, or compared against the year before, and it will say the same thing in six months as it does today.
Each month adds to a record instead of overwriting one. The monthly PDF means the company accumulates a series of fixed positions, so movement between months is measurable rather than remembered.
Estimating effort became visible. Hours against tenders, by month and by sector, alongside the binning report, means the cost of chasing a sector the company rarely wins is a number now.
The delivery journey
How the transformation took shape
01
The journey
The interesting argument on this one wasn't technical. It was whether a report should ever be asked to be both a live operational view and a historical record.
Making a single report do both is possible. It's also fragile, expensive to maintain and easy to get subtly wrong, and the failure mode is the worst kind: numbers that look fine and aren't. Reading a financial year that wouldn't reconcile made the decision easy. Keep the live report live, cut a locked copy once a year, and spend the saved effort on the things the department can act on.
The other decision worth recording is what to measure. Win rate is the obvious estimating metric and the least useful one to manage by, because it moves with who else bid and how hungry they were. Turnaround and follow-up belong entirely to the team. Measuring those, and making them visible on the list rather than buried in a monthly report, gives a manager something to have a conversation about on a Tuesday.
02
Implementation strategy
- Separate the live view from the historical record. A report that answers "where are we now" and a report that answers "what happened last year" are two different products, and a year that quietly rewrites itself can't be quoted.
- Measure what the team controls. Turnaround and follow-up are the estimating department's own behaviour. Win rate is a result, and results make for poor management conversations.
- Stamp facts, don't ask people to maintain them. Last contacted is written automatically when a note is logged, with its author, because any field a busy team updates by hand eventually stops being true.
- Make the report readable in a glance. Three labelled figures at the top beat a paragraph, because the header is read in a meeting, not at a desk.
- Send the snapshot as a file, not a link. A PDF is a fixed point in time. A link is whatever the report says when it's opened.
- Count what you decline. Disqualified tenders by sector and client show what a business walks away from as a pattern, which is a decision worth making on purpose.
03
Long-term impact
Win rate becomes a trend rather than an anecdote. With years that hold still and a monthly series behind them, the company can see whether it's getting better, and in which sectors, instead of arguing from the last job everyone remembers.
Bidding gets more selective on evidence. Estimator hours against a sector, sitting next to what the company declines and what it wins there, turns "should we keep chasing this work" into a question with numbers attached.
Accountability outlives any one manager. The follow-up numbers are on the page whoever chairs the meeting, so the standard doesn't leave with the person who set it.
And the record survives the system. The monthly PDFs are files the company holds, readable years from now regardless of what happens to the reporting platform they came from.