Tender document control and version checklist

Download the original procurement pack from the official platform and preserve the buyer’s file names. Add a simple register with document name, buyer version or date, download time, owner and status. Working documents should reference the source version they answer.

Avoid circulating multiple attachments by email without a register. A team can otherwise price one specification while writing against another.

Review every buyer answer for effects on compliance, solution, price, contract risk and timetable. A clarification may alter the practical meaning of a requirement even when no replacement document is issued. Record the decision and notify each affected owner.

• Date and official source of the change
• Affected document, requirement and bid section
• Commercial or delivery impact
• Owner and confirmation that the change is implemented

Set a controlled content freeze before the official deadline. Check file names, formats, signatures, page limits, pricing totals and portal attachments against the compliance matrix. After upload, obtain and retain the platform receipt and a copy of exactly what was submitted.

If the buyer permits replacement before the deadline, define who may authorise it and verify that the platform has replaced rather than duplicated the relevant file.