29. Output requirements. The Statement of Service Requirements (SSR) must express the desired outputs of the service being procured with the minimum of prescription of the solution required to deliver it. Unnecessary detail should be avoided. The SSR must make the clearest statement regarding the nature and scope of possible changes to the requirement - or the operational context in which the service is to be delivered - over the course of the contract. This is especially important if the intention is to allocate some or all of the risk associated with the change to the private sector (i.e. through a service requirement that incorporates flexibility).
30. Prioritisation. It is extremely helpful to the Bidder and can simplify/shorten the analysis/negotiation period to provide simple prioritisation of the individual requirements in the SSR. The conventional labels of "Essential", "Highly Desirable" and "Desirable" may suffice.
31. Performance Standards or Targets. If possible, performance indicators should be included in the SSR for each requirement This helps drafting by demonstrating to the Users that quantifiable output requirements have been defined and shows the Bidders what the likely low level service performance measures are likely to be. They are also key to the production of an effective Acceptance plan.