Back to insightsREQCON insights
What a requirements register should contain before tender submission
Before submission, a requirements register should show the requirement, its source, status, owner, commercial or delivery impact, and the decision behind the planned response. It should make unresolved matters visible rather than hiding them in individual files.
Core fields
Include an identifier, requirement text, source reference, category, owner, and status.
Use a consistent status model so reviewers understand what still needs action.
Decision fields
Capture the proposed response, assumptions, exclusions, and links to clarifications.
Record the reason for each material decision so it can be reviewed later.
Submission review
Review open and high-impact entries as a team before submission.
Freeze the register together with the final tender package.