Specification and acceptance

A specification turns the need card into something suppliers can price and users can inspect at delivery. “Excellent quality” gives neither party a performance threshold. Naming one model without a reason may exclude workable alternatives. Start with the required outcome, then state the conditions under which performance is expected, how it will be measured, and who accepts it. CIPS guidance emphasizes clear requirements, outputs, and declared evaluation and acceptance criteria that allow credible, comparable bids . The organization and applicable law determine the actual document rules.

A functional specification has three layers. First describe use: “Staff scan double-sided A4 documents at a reception desk.” Second define performance under stated test conditions: a page rate, reading accuracy, and peak period. Third set interfaces and operating needs: file compatibility, space and power limits, user training, warranty, and support. Do not invent numbers merely to fill a blank field. Ask about workload and peaks, then test whether the supply market can meet the target. A threshold unrelated to the need can raise cost or exclude useful competition.

Separate mandatory requirements from preferences before issuing the request. A mandatory condition addresses a material inability to use the output or a verified obligation; it must be tested consistently for all bidders. A preference adds value and can be weighted instead of acting as an undisclosed exclusion. Record a reason, verification method, verification time, and approver for each condition. File compatibility might be shown by a sample test at acceptance. A supplier's assertion alone may be insufficient when failure would be costly. Ease of use needs a common task and described rating method, rather than a panel's different impression of each product.

Remove wording that could create disputes. “Deliver quickly” does not identify the start event or destination. “Within 15 working days after the approved order to the organization's warehouse” is testable if the decision owner confirms it and the market can reasonably comply. “99% availability” needs a measurement period, exclusions, and a data source. “Installation included” needs a site and a defined completion event. Review the draft with the user, technical team, receiving staff, and contract owner; each may find a different constraint. If ambiguity appears after release, issue and record the same clarification to all eligible bidders under the organization's process rather than privately favoring one.

Make a brief acceptance table linking each requirement to visible evidence. On delivery check quantity and identity, then test functions on an appropriate sample or every unit depending on risk. Record defects, corrective responsibility, and a recheck date. Physical receipt is not final acceptance: boxes may arrive without the promised function. The specialist documents exceptions and sends decisions about remedies, deductions, or scope changes to the authorized role. A prior criterion also protects the supplier against a new demand introduced only after award.