What a Tender Notice Actually Tells You

A tender notice looks like dry administrative text, and most reporters skim past it on the way to something more obviously newsworthy. That's a mistake. Read carefully, a tender notice tells you who is allowed to bid, what standard the work must meet, and — crucially — what the completed project is actually supposed to look like. Every later comparison against reality starts here.

The award publication that follows is the second document worth keeping on file. It names the successful bidder, the contract value, and usually a completion date. Kept side by side with the original tender, it lets you spot where the scope or cost has already shifted before a single shovel of earth has moved.

Following the paper past the announcement

Progress reports, where public bodies publish them, are the thread that connects the paperwork to the ground. They rarely arrive on a predictable schedule, so tracking a project means checking back periodically rather than expecting a single tidy update. When reports go quiet for an extended period, that gap is itself worth noting and asking about.

• Compare the tender's stated scope against what a progress report or site visit actually shows
• Note the dates of every document you gather, not just its content
• Keep a simple table linking each claim to its source, so a discrepancy is easy to point to later

Describing a gap fairly

Finding a mismatch between the record and the site is the easy part. Describing it accurately, without overstating what you actually know, is harder. A delay isn't automatically evidence of wrongdoing, and a cost increase can have an ordinary explanation. Before publishing, the responsible body deserves a proper opportunity to comment on what you've found, documented in the same careful way as everything else in the file.

Done this way, a tracking piece rests on a record anyone else could pull and check for themselves — which is, in the end, what makes it worth publishing.