Build a tender checklist that survives an addendum

Split the tender into reviewable obligations. “Technical submission” is too broad to assign or close. “Submit the signed equipment compliance schedule using revision B” gives the owner a clear deliverable and gives the checker a clear basis for acceptance.

For each requirement, capture its identifier, source document and revision, relevant clause or page, response owner, checker, due date, proposed evidence and current status. Record whether it is mandatory, conditional or requires clarification. Keep the original wording available without copying the whole tender into the register.

A conditional requirement needs its condition recorded. If a manufacturer authorisation is required only for certain equipment, somebody must decide which offered items fall within that condition. Leaving the row blank is not a decision. Record the applicability assessment and who checked it.

The Department of Expenditure works manual addresses tender amendments and corrigenda in section 4.4. Its public procurement scope matters; a private EPC tender still needs to be read on its own terms.

An addendum should enter through one controlled intake point. The coordinator records when it was obtained, the official source, the documents it supersedes and the apparent impact. Each affected discipline then checks its own requirements. An acknowledgement proves receipt; it does not prove that the consequences were resolved.

Use three separate statuses for this review: impact assessment pending, response being revised, and verified against the amended requirement. This prevents “addendum circulated” from becoming shorthand for “addendum incorporated.” An amendment that appears administrative may still change the signatory, submission format or validity period.

The coordinator should also look across dependencies. A revised delivery requirement can change the programme, quotation validity, working capital assumption and exclusions. The technical owner cannot close those commercial consequences simply by replacing a specification sheet.

Take a fictional bid with 84 requirements. On Monday, 79 have been checked and five are open. Addendum three arrives on Tuesday and changes three requirements, including the security format. Two affected requirements were among the 79 marked complete.

The correct result is not 79 complete plus three new rows. Reopen the two existing requirements, preserve their earlier evidence and attach the amendment. The register now has 77 requirements complete and seven requiring work, assuming the third affected requirement was already open. This arithmetic only works because amendments update identifiable requirements rather than creating disconnected reminders.

Finance may need time to arrange a replacement instrument. The bid manager must see that dependency immediately. A green finance folder should not conceal a red submission requirement. If correction before the deadline is doubtful, escalate the bid decision while there is still time to act.

The person preparing a document should identify the requirement it satisfies. A checker then confirms the relevant content, signatures, validity and version. Submission introduces another set of risks: the wrong file, a missing attachment, a portal size limit or an upload that was never completed.

For material documents, use a second check after upload. Compare the uploaded file or portal acknowledgement with the approved file and its requirement identifier. Where the portal permits downloading the submitted package, retain that copy. Where it does not, preserve the available receipt and a controlled manifest of what was submitted.

Do not store portal passwords or sensitive banking details in the general checklist. Keep the evidence accessible to authorised reviewers and link to the appropriate controlled location. The objective is reliable review, not unrestricted access to every bid record.

A supplier certificate that will arrive late needs an owner, expected date and an assessment of whether the tender permits later submission. A proposed deviation needs an explicit commercial decision and the required disclosure. Neither should be hidden under “document awaited.”

Use an exception meeting to resolve a short list of consequential items. The meeting should distinguish a correctable document gap, an unresolved interpretation and a bid condition the company may be unwilling to accept. Only the first category is simply a document production problem.

Avoid inventing a universal escalation threshold based on the number of open items. One missing mandatory instrument can matter more than ten minor formatting corrections. Prioritise the consequence of the gap and the time needed to correct it. Obtain tender clarification through the prescribed channel where the requirement remains unclear.

A spreadsheet can handle this process if identifiers, version history and access are controlled. A tender platform becomes useful when several disciplines, repeated amendments or multiple simultaneous bids make manual reconciliation unreliable. The essential design is the same: one requirement can have several evidence versions, but only one current review conclusion.

Test the process with a deliberately changed requirement. Give the team an amendment after a document has been checked and see whether the owner is notified, the old approval is reopened and the submission manifest changes. Also try a replacement file with the same filename. A process that relies only on filenames is unlikely to catch that mistake.

Measure unresolved mandatory requirements and unassessed amendment impacts close to submission. Counting documents uploaded rewards activity without showing whether the bid is compliant. After submission, review any last-minute rework to identify where the impact assessment or internal deadline failed.

A strong checklist leaves the bid manager with a clear decision: the latest requirements have been met, approved exceptions have been disclosed, and unresolved items are understood. It also gives the delivery team a better handover if the bid succeeds.

1. Break the next tender into identifiable requirements with named owners and checkers.
2. Run every amendment through an impact review, including requirements already marked complete.
3. Resolve material exceptions against the actual tender conditions before the submission decision.
4. Freeze the submitted files, portal evidence and final requirement manifest together.