Home / Tools / CPHEEO / Population Forecasting Calculator — 30-Year Design Horizon
CPHEEO Calculator

Population Forecasting Calculator — 30-Year Design Horizon

Project base-year population using all 4 CPHEEO methods and pick the highest rational forecast for water supply design.

📘 Read the full CPHEEO Chapter →

Every water supply project starts with population forecasting. The numbers drive everything downstream — treatment plant capacity, transmission main diameter, reservoir volume, pump power, tariff projections, and financial models. A 10-15% error at this stage compounds into wrong investment decisions that take 30 years to unwind.

CPHEEO Chapter 2 mandates four forecasting methods (arithmetical, geometric, incremental, logistic) and tells designers to pick the highest rational projection. This calculator runs all four in parallel so you see the spread at a glance — particularly useful when census data is thin or when you're preparing the feasibility-stage memo for a 20-village multi-village JJM scheme.

Based on the CPHEEO Manual on Water Supply and Treatment, published by the Central Public Health and Environmental Engineering Organisation, Ministry of Housing and Urban Affairs, Government of India.

What this calculator computes

  • Arithmetical forecast: suited to slow-growing mature cities with steady absolute increment
  • Geometric (compound) forecast: the realistic curve for rapidly growing tier-2/tier-3 cities and new towns
  • Incremental increase: compensates when growth itself is accelerating
  • Logistic curve: S-shape for saturating metros (Mumbai Island City, Kolkata) approaching ultimate density
  • Design population = max of the four — the highest rational projection per CPHEEO guidance

Calculator

Population Forecasting (30-year design horizon)

↓ Download Excel

Project the base-year population to the design year using all 4 CPHEEO methods. Use the highest rational forecast (typically geometric for growing cities, logistic for saturating metros).

Inputs
Base-year populationpersons
Average decadal increasepersons
From past census data
Average increment of increasepersons
For incremental method; set 0 if unknown
Decadal growth rate%
Decades to forecastdecades
3 decades = 30-year design period
Saturation population (logistic)persons
City's ultimate saturation based on land area × density
Outputs
Arithmetical forecast
86,000persons
P = P₀ + n × X
Geometric forecast
97,656persons
P = P₀ × (1 + r/100)^n
Incremental forecast
98,000persons
P = P₀ + n × X + n(n+1)/2 × Y
Logistic forecast
1,42,190persons
P = Ps / (1 + m × e^(-k × n)) (m, k from past data)
↪ Simplified: uses m = 1, k = 0.3 typical
Design population (highest rational)
1,42,190persons
max of the 4 methods
CPHEEO Reference Values
Design horizon30 years (3 decades)
Reassessment interval10 years
Method selectionGrowing cities → geometric · Saturating metros → logistic
Download the Excel version to keep a local copy with live formulas — change inputs in the sheet and outputs recompute automatically.

How to use the inputs

  • Enter the base-year population from the most recent census
  • Fill in the average decadal increase from past census data (3-5 readings preferred)
  • Set the growth rate — typical: 15-25% for mature metros, 25-40% for growing tier-1, 40-80% for IT corridors and new towns
  • Number of decades = 3 for a standard 30-year design horizon
  • Saturation population is land area × assumed ultimate density (400 persons/ha for medium-density Indian urban)

Worked example

Worked example — tier-3 municipal town
Base population (2024) = 50,000. Average decadal increase from past 3 censuses = 12,000. Decadal growth rate = 25%. Forecasting 30 years (3 decades). Arithmetical = 50,000 + 3 × 12,000 = 86,000. Geometric = 50,000 × (1.25)³ ≈ 97,700. Incremental ≈ 98,000. Logistic (Ps = 200,000) ≈ 138,600. Design population = 138,600 (logistic wins here because the town is nearing saturation relative to its land area). Design flow at 135 LPCD = 18.7 MLD.

Interpreting the results

Pick the maximum of the four forecasts as your design population — this is CPHEEO practice.

If the geometric method gives an unreasonably high number (e.g., 3x arithmetical), the city's land area may constrain that growth — revisit the saturation population and weight the logistic forecast more heavily. If arithmetical is highest (unusual), it often signals a forecast horizon that's too short and the geometric/incremental curves haven't yet compounded.

FAQs — using this calculator

Which forecast method should I pick as the design?
Per CPHEEO Chapter 2: the highest rational projection from the four methods. For growing Indian cities, geometric typically wins. For mature saturating metros, logistic often dominates. Always cross-check that the winning forecast is physically plausible — a forecast exceeding land-area × max-reasonable-density is not rational even if mathematically higher.
I only have 2 census data points — is that enough?
Technically possible but risky. CPHEEO recommends at least 3 past decadal readings; 5 or more is reliable. With only 2 points you can compute a growth rate but can't validate it across cycles. Supplement with NITI Aayog state urban population projections, municipal voter rolls, or NPR data.
Should I add floating population?
Yes — 10-30% addition is typical for Indian cities. Workers, students, tourists, daily commuters consume water the same as residents. Delhi +25%, Mumbai +20%, Bangalore +18% over permanent population. Ignoring floating population underestimates demand by 15-25%.
What saturation population should I use for the logistic method?
Saturation = Land area within ULB boundary × maximum reasonable density. Typical values: medium-density Indian urban = 400 persons/ha, dense old-city cores = 600-800/ha, sprawling tier-2 = 200-300/ha. For a 500 ha town, saturation ≈ 200,000 persons. This represents the ultimate ceiling the city can physically support.
How does forecasting change for JJM rural vs urban?
For single-village JJM schemes (population < 10,000), simple geometric with a conservative growth factor (1.5-2.0 × base over 30 years) is standard practice. Rural villages show less extreme growth than urban — 2-4% annual typical. The four-method comparison is overkill for a single village but essential for tier-2+ urban projects.
Why does CPHEEO require reassessment every 10 years?
Growth rates change — economic shocks, industrial policy changes, migration patterns, pandemics all distort trajectories. A 2014 forecast was likely too high post-demonetization; a 2018 forecast too low post-Covid. 10-year reassessment catches these structural changes and lets you rebalance design decisions before they compound into capacity crises.

Related calculators & references

Other CPHEEO Calculators

Water Demand & LPCD Calculator
Convert design population into MLD — average, peak, fire demand
Service Reservoir Sizing
Size ESR / GSR from daily demand
Rural JJM Scheme Sizer
End-to-end village scheme calculator

Indian Codes Referenced

IS 1172 — Rural Water Supply
55 LPCD rural standard
IS 10500 — Drinking Water Quality

Related pages on InfraLens

CPHEEO Ch. 2 — Full chapter
Clauses, practitioner notes, FAQs
All CPHEEO chapters
Handbook