The tender submission checklist: what to check before you send

Run the checks in the order that can disqualify you

Most teams review a bid in the order they wrote it, which means the prose gets three passes and the lodgement rules get none. Invert it. The checks that can end the bid cost the least time and carry the most risk, so they go first and they get done by someone who did not write the response.

A second reader matters more here than anywhere else in the process. The person who filled a form is the worst person to check whether it was the right form, because they already believe it was.

• Mechanics: format, file naming, size caps, the portal, the deadline and its time zone.
• Forms: every returnable schedule present, in the issued format, filled where required and signed by someone authorised.
• Addenda: every one acknowledged, and every requirement they changed re-answered.
• Evidence: current at the closing date, in the bidding entity’s name, at or above the level the pack demands.
• Response: limits respected, every claim supported, nothing left as a placeholder.

Returnable schedules: return what you were given

Buyers evaluate schedules side by side, often against a scoring sheet that follows the form’s own numbering. A rebuilt form breaks that comparison, and packs frequently say in plain words that altering a schedule makes an offer non-conforming.

Where a section genuinely does not apply, write "not applicable" and say why in one line, rather than removing it. A missing section reads as an omission; a marked one reads as a decision.

Check the signature block separately. Who is authorised to sign, whether a witness is required, whether a scanned signature is accepted and whether the entity name on the form matches the entity that holds the insurances. These are trivial to fix on the day and impossible to fix afterwards.

Addenda are binding, and they arrive after you started

Addenda change scope, deadlines, evaluation criteria and mandatory conditions. The buyer publishes them, records who downloaded them, and assumes every bidder incorporated them. There is no allowance for a bidder who was already drafting.

The practical failure is subtler than missing one. A team downloads the addendum, notes the new closing date, and does not go back through the requirements matrix to see which rows changed. Mark the changed rows explicitly and re-answer them, rather than reading the addendum once and trusting memory.

If your matrix carries the document and page for each row, an addendum becomes a diff you can work through in twenty minutes. If it does not, it becomes a re-read of the whole pack.

Evidence: current, correct entity, right level

Expiry is the obvious one and still the most common. The test is not whether a certificate is valid today, it is whether it is valid at the closing date and, where the pack requires cover for the contract term, beyond it. A certificate expiring inside the evaluation window invites a clarification you do not want to be having.

The name is the quiet one. Group structures mean insurances are often held by a parent or a related entity while the bid is submitted by an operating company. If the certificate names a different legal entity than the tenderer, expect to be asked, and have the answer ready.

The level is arithmetic. The pack states a minimum; the certificate states a limit. Compare them directly rather than assuming the policy you renewed last year still clears the bar, because the bar moves between tenders.

Where a document’s provenance matters — a certificate received by email, a licence forwarded by a subcontractor — it is worth checking that the file is what it claims to be before it goes in your name. Stipple’s document check reports tampering signals, provenance and issue dates. It tells you about the file; it does not tell you whether the buyer will accept it.

Limits, and the claims inside the words

Page and word limits are enforced unevenly but they are enforced. Where a limit is stated per criterion rather than per document, count per criterion. Where the pack says text beyond the limit will not be read, assume it will not be read.

The second check is harder and matters more. Go through the response and mark every factual claim: certifications held, years of experience, projects delivered, staff numbers, turnover, response times. For each one, name the document that proves it. Anything you cannot evidence either gets evidenced or gets rewritten into a claim you can stand behind.

Two things are worth checking mechanically before submission. Text reused from an earlier bid or a template may overlap material already published on the web, which reads badly if a buyer notices. And where a buyer runs submissions through an AI-writing detector, prose that reads as generated is a risk whether or not it was. Stipple checks both, and neither result is a compliance judgement — they tell you what a reader might see before the reader sees it.

Lodgement: the deadline is not when you think

A closing time stated as 2:00 pm is stated in a specific time zone, and Australian tenders routinely close in a state that is not yours, in a month when daylight saving applies to one of you and not the other. Convert it explicitly and write the converted time on the plan.

Portals impose their own rules: total upload size, per-file size, accepted file types, whether a ZIP is allowed, whether each schedule must be a separate named file. These are trivial rules that take an hour to satisfy and cannot be satisfied in the final ten minutes with a large file and a slow connection.

Submit early enough that a failure is recoverable. The measured pattern in our tender research is that closings cluster heavily on one weekday. Aim to lodge the day before, and treat the deadline as the point by which a failed upload must already have been retried.