Tender requirements versus contract requirements: what should be tracked?
Track requirements that affect scope, price, risk, evidence, or delivery responsibility from tender through contract. Keep the tender source and the agreed contractual wording side by side so the team can see what changed before work starts.
Keep the two states distinct
Tender requirements describe what was requested; contract requirements describe what was agreed.
A requirement may be clarified, qualified, replaced, or excluded during negotiation, so neither state should overwrite the other.
Track the change path
Link clarifications, reservations, amendments, and contract clauses to the original tender requirement.
This creates an auditable decision trail for project, commercial, and site teams.
Carry forward operational obligations
Identify obligations that need proof during delivery, such as approvals, documentation, tests, and handovers.
Assign them before the project team receives the final requirement set.