Read the Kind of Statement Before Applying It
A technical reference may combine a desired condition, proposed actions, measures and practical qualifications. Copying one line into a checklist can sever those connections. First identify what kind of statement you are reading and the decision it can support.
The Sphere Handbook, fourth edition, 2018, printed pages 6-9, distinguishes these elements:
| Sphere Element | What It Does | What It Does Not Establish Alone |
|---|---|---|
| Minimum Standard | States a qualitative condition grounded in life with dignity. | A site-specific design or prescribed delivery method. |
| Key actions | Suggest practical ways to work toward the standard. | That every listed action is relevant everywhere. |
| Key indicators | Help assess whether the standard is being attained. | That a single measurement captures the whole condition. |
| Guidance notes | Support application with additional explanation and connections. | An optional substitute for understanding the relevant qualifications. |
Use Sphere's own labels when discussing its content. Another source may use “standard,” “recommendation” or “requirement” differently. Establish its actual authority rather than assuming that one vocabulary works across sources.
Separate the Standard From a Number
A quantity can be a measurement, planning input, target, observed result or limit. Find out which it is. Read its denominator, unit, population, reference period, assumptions and accompanying notes. A number copied without these details may answer a different question from the one you face.
Sphere's 2025 contextualisation guide, sections 1.6 and 2-4, distinguishes rights-based aims from contextual actions and targets. It also separates a constrained short-term target from actually attaining the standard. Meeting an interim target does not erase a shortfall.
This does not permit a team to relabel inadequate conditions as acceptable merely because its budget is small. Record the gap, affected people, consequences, responsible decisions and plan for improvement. The current local authority, technical roles and affected people need to be part of the applicable process.
Follow a Fictional Service Question
Riverbend is invented. After flooding, a team is considering whether to restore an existing water point or establish a temporary delivery arrangement. Its brief contains neither an assessed water-quality result nor a technical design. Residents have reported access difficulties, but the locations and affected groups still need to be established.
A useful reading note would separate:
- The service condition the team is trying to achieve.
- The relevant reference and exact section.
- Candidate actions and the local information needed to compare them.
- Evidence that could show progress, including whose access might be missed.
- The decision requiring technical or public-health authority.
An inappropriate transfer would be: “The handbook mentions a waterpoint ratio, so this settlement needs exactly the calculated number of taps.” That skips the reference's assumptions and the site's operating conditions. Counting fittings does not establish flow, reliability, quality, affordability or usable access. The appropriate lead must determine which details matter in the actual setting.
The alternative is not to abandon standards or demand a new form for every discussion. It is to explain why the selected action and evidence fit the purpose. A short annotated note may be enough for a planning conversation; it is not an engineering approval.
Compare With a Different Kind of Guidance
The UK Cabinet Office's Consultancy Playbook, version 1.1, September 2022, printed pages 5-6 and 20-22, concerns commissioning and managing consultancy in its public-sector context. Its advice on defining a problem and deliverables can inform how a client frames a specialist assignment. It does not set a humanitarian water-service condition or establish an NGO's local procurement law.
For Riverbend, the distinction is practical. A commissioning reference can help describe the question for a qualified adviser. A technical service reference can help frame the substantive condition to investigate. Neither one makes the other's decisions or proves that a proposed supplier has the necessary expertise.
Keep the Source and Its Limits Together
Record the source title, publisher, edition, exact heading or page, the point used and why it fits this setting. Keep missing site information visible. If two references differ, compare purpose, edition and scope before treating them as contradictory or simply choosing the more convenient statement.
Continue with reconciling technical guidance, then writing a technical advice note. The WASH starting-point guide helps locate appropriate specialist material. This page explains how to read external guidance; it creates no new OpenAid technical standard or certification.