Define the Apparent Disagreement
Two documents can differ because one is older, because they cover different settings or because one is a summary that omitted an important qualification. They may also disagree substantively. Do not silently merge their numbers, select the newer date or treat both as equally authoritative. Work out what each document actually supports.
This tutorial supplies a complete fictional comparison. Its local documents, dates and service facts are invented. It draws a reading distinction from two real references: the 2018 Sphere Handbook, printed pages 6-9, and Operationalising Sphere: A Practical Guide to Contextualisation, 2025, sections 2-4. The guide explains application; it is not a replacement edition of the Handbook.
Start With the Two-Document Packet
| Document | Fictional Contents and Limits |
|---|---|
| R1, Riverbend Waterpoint Planning Card, revision 1, June 2024 | A short local card based on the 2018 Handbook. It was prepared for a temporary open settlement. Its summary says to count users and install the number of waterpoints shown in a ratio. The card does not retain the ratio's flow and operating assumptions, definition of users or access qualifications. No technical sign-off is supplied. |
| R2, Riverbend Service Review Note, revision 2, October 2026 | A later local note citing the 2018 Handbook and 2025 contextualisation guide. It concerns existing neighborhood services and host and displaced households. It asks about actual delivery, users' access, maintenance and the response phase, but contains no field measurements or approved design. |
| Current question | The coordinator wants to know whether R1 is sufficient to authorize equipment purchase for the neighborhood service. |
| Current gaps | Water availability, service hours, quality, accessibility, population coverage and appropriate technical approval are not established. |
R2's later date does not establish that its factual claims are correct. R1's reference to a recognized handbook does not turn its incomplete summary into a design instruction. Both need checking against their original sources and the current task.
Compare Claims in Context
- Retrieve the exact cited edition and sections. Check the original, not another team's slide or search snippet. Confirm whether a later item revises the source or merely explains it.
- Separate normative aim, suggested action and measurement. Preserve the source's actual distinctions. Find the conditions attached to the numerical claim in R1 rather than treating a bare ratio as the whole recommendation.
- Compare populations, systems and response phases. R1's temporary-settlement setting differs from R2's neighborhood service question. Determine which assumptions transfer and which remain untested.
- Check local authority and obligations separately. A globally recognized reference does not itself establish the applicable legal requirements, service ownership or approval route. Retrieve those through the responsible owners.
- Write a resolution and a remaining-decision note. State what the comparison resolves, what it cannot resolve and the evidence and role needed next.
A Completed Resolution Note
Question: Does R1 provide enough support to approve a neighborhood waterpoint purchase?
Source comparison: R1 has reduced a context-dependent reference to a count and omitted important assumptions. R2 raises relevant questions, but its publication date and broader coverage do not verify current conditions. The 2025 guide supplements the application of the 2018 reference; it does not make the old local card a current technical design.
Resolution: Do not use R1's count as purchase approval. Retain it as a historical planning document with a clear limitation. Use the original reference and R2's question list to prepare the missing current evidence for the qualified service lead.
Next actions: The service owner establishes actual supply and operation information. Community engagement identifies who can and cannot use the service. The qualified WASH lead checks the applicable technical basis, including local requirements, before recommending the appropriate intervention. The authorized budget and procurement owners decide on purchasing through their actual procedures.
Still unresolved: No number of new installations, water-safety conclusion, complete cost estimate or approval follows from this comparison. The team needs to decide how to address current access problems while obtaining the required evidence through the responsible response arrangements.
Handle a Consequential Exception
Suppose the local service authority supplies a current requirement that appears stricter than the general source. Do not average the two or choose the easier figure. Record the exact authority, wording, scope and effective date, then give the apparent conflict to the qualified lead and responsible authority. A writer can explain the discrepancy without deciding the technical or legal interpretation.
Likewise, if the source is inaccessible, do not claim it was checked. Record the missing section, seek an authorized copy or an official equivalent and hold the affected conclusion. An available abstract can identify a source; it cannot supply omitted qualifications.
Transfer the Method Without Transferring the Answer
The UK Consultancy Playbook, version 1.1, is a useful example of commissioning guidance with a defined public-sector setting. It is not a water standard. In another assignment, keep a commissioning rule and a technical recommendation in separate columns even if both documents use the word “requirement.”
Use the standards-reading explanation to identify each statement's role, and the technical advice-note tutorial to communicate the result. The purpose is a traceable, bounded resolution, not a declaration that every source agrees.