Reading a statement of requirements: obligations, assumptions and acceptance tests.

Classify each statement as an obligation, an acceptance test or a question before you fill a compliance matrix. Separate mandatory eligibility, deliverables, preferences, dependencies and unclear wording. Internal labels do not change the buyer’s rules. This is one read in how to read a 400-page tender in a day.

Published: 16 September 2026 · By Andre · Reviewed by Bill · selrob

Takeaways

A preference is not a gate. A mandatory is not a scored nice-to-have. Read the buyer’s word, not your heading.
An acceptance test is the sentence that says how the buyer will decide the work is done.
A dependency on the buyer is not your deliverable. Track it. Do not mark it compliant.
Unclear wording stays unclear until the buyer answers. An internal assumption is not a status.

Which statements create an obligation, a test or a question?

Read every sentence in the statement of requirements as one of five things. Mandatory eligibility: you hold it at the time the pack requires, or the offer can be set aside; that hunt is mandatory criteria. Deliverables: work you must perform. Preferences: scored or “desirable” items that are not pass/fail. Dependencies: things the buyer or a third party must do before you can perform. Unclear wording: a sentence you cannot classify without inventing a meaning.

An obligation uses the buyer’s verb: must, shall, will provide, is required. An acceptance test names the measure, the sample, the period or the sign-off. A question is everything you would have to assume. Assumptions belong in a log and, where they affect conformity, in a clarification question. They do not belong in the compliance column.

What does the capability matrix still own?

Who delivers each line. This page classifies the sentence. The capability matrix names the roster. If you cannot name the person, you do not yet have a deliverable you can accept. Do not mark the requirement compliant because the sentence is clear.

Where do the rows go next?

Into the compliance matrix. Use that template’s field language: Requirement ID, Source Reference, Buyer Classification, Requirement Summary, Required Evidence, Response Owner, Internal Due, Compliance Status, Residual Uncertainty, Addendum Version. Buyer Classification is the buyer’s weight, not your internal tag. Writing “we treat this as a preference” on a sentence the pack calls mandatory does not move the gate.

Worked example

Annotated scope: Department of Regional Services pack

Hypothetical. The buyer, tender and figures are invented to show the fields in use; they are not a client result. Two-year records digitisation and service-desk services. RFT DRS-REC-2026.

Annotated statement of requirements, completed hypothetical example
SoR ID	Source	Buyer text (excerpt)	Kind	Obligation, test, or question	Internal label (not a status)
SoR-01	Conditions §3.1	The Respondent must hold current ISO/IEC 27001 certification at the closing time.	Mandatory eligibility	Obligation. Held at close, or the offer can be set aside.	Do not rewrite as “we can get it before kickoff.”
SoR-02	SoR §2.4	Digitise 120,000 physical files within six months of commencement. Acceptance: 99.5 percent capture accuracy on a random 1 percent sample drawn by the Principal.	Deliverable	Obligation (volume and time) plus acceptance test (99.5 percent / 1 percent sample / Principal draws).	Staffing the 120,000 is a capability-matrix row, not a classification change.
SoR-03	SoR §4.1	Preference will be given to Respondents that can demonstrate social-enterprise participation in the delivery team.	Preference	Not a gate. Scored only if the evaluation table gives it weight.	Absence is not non-conforming unless another clause says it is.
SoR-04	SoR §2.8	The Principal will provide an export from the legacy EDRMS within 20 business days of kickoff.	Dependency	Buyer obligation. Not a supplier deliverable. If late, your six-month clock on SoR-02 is at risk.	Do not mark Compliant. Log the dependency and the delay consequence.
SoR-05	SoR §5.3	Provide on-site support at each regional office as required.	Unclear	Question. Which offices. What “as required” means. Hours, notice, SLA, remote alternative.	Assumption “three offices, one day a month” is not compliance. Status stays Clarification Required.

Blank template

Blank annotation log

Statement of requirements annotation log, blank form
SoR ID	Source	Buyer text (excerpt)	Kind	Obligation, test, or question	Internal label (not a status)
SoR-			Mandatory / deliverable / preference / dependency / unclear
SoR-			Mandatory / deliverable / preference / dependency / unclear
SoR-			Mandatory / deliverable / preference / dependency / unclear

Into the matrix

Same rows in compliance-matrix field language

Hypothetical. The buyer, tender and figures are invented to show the fields in use; they are not a client result. SoR-05 remains unresolved. The internal assumption is recorded under Residual Uncertainty. Compliance Status is not Compliant.

Statement of requirements mapped to compliance-matrix fields, completed hypothetical example
Requirement ID	Source Ref	Buyer Classification	Requirement Summary	Required Evidence	Response Owner	Internal Due	Compliance Status	Residual Uncertainty	Addendum Ver
REQ-01	Conditions §3.1	Mandatory Condition	Hold current ISO/IEC 27001 at closing time	Valid certification schedule covering the delivery scope	Priya (CISO)	22 Sep 2026	Compliant	Certificate in date through 2027. Recertification does not overlap close.	v1.0
REQ-02	SoR §2.4	Scope Requirement	Digitise 120,000 files in six months; 99.5 percent accuracy on a 1 percent sample drawn by the Principal	Methodology, named capture leads, sample-handling procedure	David (Delivery)	29 Sep 2026	Drafting	Clock starts at commencement, which depends on SoR-04 export.	v1.0
REQ-03	SoR §4.1	Weighted Evaluation	Demonstrate social-enterprise participation in the delivery team if claiming the preference	Named participant and role, or leave the criterion unscored	Amira (BD)	24 Sep 2026	Partial / Exception	No social-enterprise partner on the roster. Not treated as a mandatory.	v1.0
REQ-04	SoR §2.8	Buyer dependency	Principal export from legacy EDRMS within 20 business days of kickoff	None from the supplier. Record the delay consequence on REQ-02.	David (Delivery)	22 Sep 2026	Not a supplier obligation	If the export is late, six-month digitisation cannot be held as written.	v1.0
REQ-05	SoR §5.3	Unclear: classification withheld	On-site support at each regional office as required	Cannot be named until the buyer defines offices, hours and “as required”	Elena (Bid lead)	Clarification cut-off	Clarification Required	Internal working assumption (three offices, one day a month) is not submitted as compliance. CQ-04 logged.	v1.0

What do you do with the sentence that will not resolve?

Leave it open. SoR-05 cannot be made compliant by writing a number in the bid team’s notebook. Ask the buyer, in the form the pack requires, which offices exist, what attendance means, and how “as required” is measured. Until that answer is in an addendum, the matrix says Clarification Required. If the cut-off passes with no answer, the second gate is whether you will price an undefined attendance obligation. That is a commercial call on undefined scope, not a classification you are entitled to finish yourself.

Keep reading

Elsewhere in this guide.

Book a call

Bring the last tender you regretted.

In 30 minutes we’ll show you the call selrob would have made, and the working behind it.

Book a call