WIA-ENE-071 Phase 1 begins with requirement R1, Water Resource Assessment, and its first clause (R1.1) says what the assessment must cover: "all water sources (surface water, groundwater, non-conventional)." A watershed is the natural boundary within which these sources interact. Rain falling on a slope becomes streamflow, soil moisture or aquifer recharge. What a user withdraws in one reach changes what is available in the next, and a contaminant released upstream becomes a downstream problem. Treating the catchment as the unit of analysis keeps these linkages in view.
The standard asks for four things at this stage:
Conservation is not a separate topic in this structure. The same assessment that sizes supply also locates the land that produces and protects that supply.
A water balance accounts for water entering a defined area, water leaving it, and the change in storage. In its simplest annual form it can be written as follows.
precipitation - evapotranspiration - runoff/streamflow out - groundwater outflow
= change in storage (soil moisture, aquifers, reservoirs, snow)The standard does not prescribe a particular model. It requires that the scale fit the question. A seasonal reservoir release decision needs a monthly or finer time step. A long-term allocation plan can use annual totals, but it must still show how wet and dry years differ. The three scenarios named in R1.1 give the model its purpose:
The first success criterion, "demonstrated sustainable yield meeting projected demands," can only be argued from a balance that covers all three scenarios. A balance computed for average years alone would not support it.
R1.1 places three conservation concerns inside the hydrological assessment itself. Recharge zones are the areas where infiltration replenishes aquifers, typically permeable soils, fractured bedrock outcrops, alluvial fans and some floodplains. Paving, compaction or contamination there degrades supply that may be invisible at the surface. Critical habitats are the wetlands, riparian corridors, spawning reaches and springs whose loss cannot easily be repaired. Environmental flow requirements describe how much water, and with what seasonal pattern, a river or wetland needs to stay functional.
Treating environmental flow as a requirement fixes its place in the allocation sequence. The ecosystem is counted as a user whose needs are quantified before the remaining water is divided among sectors. This follows the Phase 1 objective of "Environmental Protection: Safeguard water resources and aquatic ecosystems while meeting human needs." It also explains why demand assessment, discussed in 4.5, comes after the hydrological assessment, not before it.
Quantity alone does not make a source usable. R1.2 requires a baseline for every source and every distribution point, an inventory of pollution sources and the pathways by which contaminants reach water, a check against applicable quality standards, and a description of seasonal and spatial variability.
The emphasis on pathways reflects how catchments work. Point discharges such as outfalls are easy to locate. Diffuse inputs, such as runoff carrying sediment and nutrients from fields or settlements, arrive across the whole land surface and are moved by storms. Groundwater contamination can lag its cause by years. A baseline taken only in a dry month will miss first-flush events, and one taken at a single station will miss tributary differences. The standard's wording on variability is therefore a sampling-design requirement as much as a reporting one.
| Assessment question | Watershed-scale interpretation |
|---|---|
| Where is baseline quality measured? | All sources and distribution points, including tributaries and groundwater |
| What threatens it? | Pollution sources and contamination pathways, whether point or diffuse |
| Is it acceptable? | Compliance with applicable water quality standards |
| Is one sample enough? | No. Seasonal and spatial variability must be characterized |
R1.3 requires current demand to be quantified "by sector (domestic, agricultural, industrial, environmental)." The environmental sector appears in the same list as the others, which connects directly to the environmental flows of 4.3. Projections must draw on population, economic and climate scenarios. The assessment must also look for "opportunities for demand reduction and efficiency improvement" and evaluate vulnerability to scarcity.
Demand in a watershed is geographically uneven. Irrigation may concentrate in one valley, industry along one river, and households in a downstream city. Comparing a catchment-wide supply total with a catchment-wide demand total can hide local shortfalls. Efficiency measures are also a form of conservation, because water saved by reducing losses is water that need not be withdrawn from the source. This is why the success criteria include an efficiency target for piped systems, as 4.11 shows.
Under R3.2, technical design must "incorporate nature-based solutions alongside conventional engineering," while ensuring "climate resilience and adaptive capacity" and planning for "scalability and future expansion." The wording is "alongside." The standard does not set green and grey infrastructure against each other. A realistic watershed design combines them. Typical nature-based measures include:
These measures sit beside intakes, treatment works, pipes and reservoirs, and each reduces the load on the others.
R3.3 adds safeguards. The plan must include an environmental impact assessment (EIA), a social impact assessment with gender analysis, mitigation and management plans, and compliance with the IFC Performance Standards and the Equator Principles. The Environmental and Social Management Plan (ESMP), listed under deliverable D2, is where these mitigation measures are written down for conservation works as well as for construction.
Requirement R2 treats participation as technical work with its own outputs. R2.1 calls for identifying all stakeholders "including marginalized and vulnerable groups," assessing their "interests, influence, and capacity," and mapping "power dynamics and potential conflicts." In a watershed those dynamics have a recognizable shape. Upstream land users decide how much sediment, nutrient load and flow reaches downstream users, but they may bear the cost of conservation while others receive the benefit. The map of stakeholders should make that asymmetry visible.
R2.2 requires inclusive consultation, with representation of women, indigenous peoples and marginalized communities. It also requires that the process "document stakeholder inputs and demonstrate how they inform decisions." R2.3 requires accessible complaint channels, fair and transparent procedures, public reporting of how grievances are resolved, and "non-retaliation for raising concerns." Those who live beside a river or spring often hold knowledge about floods, dry-season flows and contamination events that no gauge has recorded. The consultation record is a legitimate input to the baseline, alongside the instrument data.
R6.1 asks for indicators that cover "water quantity, quality, access, and ecosystem health," with defined monitoring locations, frequencies and methods. It also asks for a data management system that ensures "quality, accessibility, and security," and for integration of traditional monitoring with "sensors, remote sensing." In a catchment, remote sensing can show land-cover change across areas that field crews cannot visit often, while in-situ sensors give continuous series at fixed points. Neither replaces periodic field verification.
R6.2 sets the QA/QC discipline that makes the numbers trustworthy:
A drifting level sensor or a mishandled sample can produce a trend that is purely an artifact. R6.3 completes the loop with a theory of change linking activities to outcomes, baselines and targets for each key indicator, and independent third-party evaluation at key milestones.
Watersheds rarely coincide with administrative boundaries, so requirement R4 stresses coordination. R4.1 calls for roles, responsibilities and accountability to be defined, with "coordination mechanisms across agencies and jurisdictions" and multi-stakeholder bodies that have clear mandates. R4.2 requires a review of existing water laws, regulations and policies, identification of gaps and inconsistencies, development or revision of allocation and use permits, and enforcement mechanisms with penalties for non-compliance. R4.3 assesses technical, managerial and financial capacity and plans training and knowledge management.
In practice, source protection often fails at the seams. One authority regulates abstraction, another land use, a third discharges, and none is responsible for the whole system. The Phase 1 gap review is meant to surface exactly such mismatches before design work builds on them. The permit system is also what turns a water balance into an enforceable allocation.
Requirement R5 applies the same discipline to money. R5.1 asks for capital and operations-and-maintenance (O&M) estimates over the full project lifecycle, "typically 20-30 years," with contingencies. R5.2 requires cost-benefit analysis, an affordability check for users, a comparison of financing options, and tariff structures "balancing cost recovery and equity." R5.3 requires diversified revenue, reserve funds "for capital renewal and emergencies," and accountable financial management.
This matters for conservation because the benefits of protected recharge zones, restored riparian buffers and healthy wetlands accrue slowly and are easy to defer in favor of visible infrastructure. A lifecycle view makes it possible to compare the cost of maintaining natural assets with the cost of the treatment or replacement capacity that their loss would require. Reserve funds also protect against a common failure, in which watershed works are built and then not maintained.
Phase 1 ends in a defined set of deliverables, and the standard's quantitative success criteria show what a well-run catchment program is aiming for. The table below reproduces them.
| Criterion | Target |
|---|---|
| Water availability | Demonstrated sustainable yield meeting projected demands |
| Water quality | > 95% compliance with applicable standards |
| System efficiency | < 20% non-revenue water (piped systems) |
| Access | Universal access to basic service (> 20 liters/person/day) |
| Affordability | Basic service < 3% of household income |
| Reliability | > 90% uptime/availability |
| Financial sustainability | Full O&M cost recovery, adequate reserves |
| Stakeholder satisfaction | > 80% approval in user surveys |
The deliverables fall into four groups: assessment reports (D1), planning documents (D2), implementation tools (D3) and compliance documentation (D4). The watershed-relevant items are the Hydrological Assessment Report, the Water Quality Baseline Report, the Demand Assessment and Projection Report, the Water Resources Management Plan and the ESMP. The Regulatory Compliance Matrix in D4 maps each requirement to an implementation measure. An illustrative outline of how a team might organize such a matrix, using the requirement identifiers from this chapter, is shown below.
R1.1 Hydrological assessment -> Hydrological Assessment Report (D1)
R1.2 Water quality baseline -> Water Quality Baseline Report (D1)
R1.3 Demand assessment -> Demand Assessment and Projection Report (D1)
R3.2 Nature-based solutions -> Infrastructure Design Specifications (D2)
R3.3 Safeguards (EIA/SIA) -> ESMP (D2)
R6.1 Monitoring design -> Monitoring and Evaluation Plan (D3)A Certification Readiness Assessment, which is a gap analysis against the WIA-ENE-071 criteria, is the last D4 item. Treat it as a pre-check on whether the evidence above exists and is consistent, not as additional analysis.
This chapter read the Phase 1 requirements through the lens of the watershed. Assessment (R1) establishes what water exists, where it recharges, what it carries and who needs it, with environmental flow counted as a legitimate demand. Stakeholder engagement (R2) makes the upstream and downstream relationship explicit. Design (R3) pairs nature-based solutions with engineering under impact-assessment safeguards. Institutions (R4) and finance (R5) determine whether protection can be enforced and sustained across jurisdictions and over decades. Monitoring (R6) supplies the quality-controlled evidence that tells the program whether it is working.
Phase 1 is meant to run on a milestone schedule of roughly 24 weeks, from project initiation through baseline assessment, analysis, stakeholder validation and finalization. The critical path items are stakeholder buy-in, baseline data availability, legal and regulatory review, and funding for later phases. What leaves Phase 1 is a validated baseline, agreed objectives and a feasible plan. The next chapter moves to the transition the standard describes, in which the final review is signed off, knowledge is transferred to the Phase 2 team, and the plans developed here are put into operation.