A website TOR should describe the problem the organisation is trying to solve, not only the pages it expects to receive. The more clearly the requirement explains audiences, content, functionality and operational expectations, the easier it is to evaluate proposals fairly.
Business objective and audiences
State why the website is being replaced or created, who uses it and which actions matter most. Examples include finding publications, applying for a service, making a booking, requesting a quotation or accessing supplier information.
Content and migration
Identify how much existing content must move, which documents or media are important, whether URLs must be preserved and who is responsible for rewriting or approving content.
Functional requirements
List forms, search, directories, ecommerce, booking, payments, multilingual content, user accounts, APIs and other integrations separately from general design requirements.
Technical and operational requirements
Include hosting, backups, security, accessibility, performance, analytics, environments, source-code or administrator access, documentation, training and the expected support period after launch.
Evaluation and acceptance
State submission requirements, evaluation criteria, project governance, UAT responsibilities and what will constitute acceptance. This reduces disagreement when a project reaches handover.