Warabandi Canal Water Turn Scheduler and Swap Ledger for Farmers
Build a tool that computes each farmer's canal water turn (warabandi) from landholding shares and travel time along the watercourse, sends turn reminders by SMS or WhatsApp, and records swaps and sales of turns in a shared ledger. Farmers on the same watercourse often argue about turns kept in memory and paper lists. The project is a real scheduling problem with a clear community of users.
Intermediate
A small team, or one strong student willing to learn something new.1 semester · 2 to 3 students
7 to ship
4 optional extrasSuggested stack
What you should ship
- A watercourse model with outlets, farms, landholding areas and travel time of water between farms
- A scheduler that turns land shares into weekly turn times, including the time allowance for water to reach each farm
- A rotation that shifts turn times week by week so night turns are shared fairly, if the community uses that rule
- Turn reminders by SMS or WhatsApp in Urdu with the start time and the neighbour before and after
- A swap and transfer ledger where both farmers confirm a change and the schedule updates
- A dispute view that shows the original schedule, every confirmed swap and the resulting turn
- A pilot with at least one real watercourse and its water users' association
If you have time left
- Integration of canal closure notices so schedules pause automatically
- A voice call reminder for farmers without smartphones
- An analysis of how swaps change effective water share over a season
- Support for tube-well water sharing alongside canal turns
The problem: the water turn is valuable and kept in memory
In the canal-irrigated plains of Punjab and Sindh, water from a canal outlet flows down a watercourse shared by many farmers. Under warabandi, each farmer gets a fixed time slot each week, in proportion to their land, to divert the whole flow onto their fields. A farmer with 10 acres might get several hours on Tuesday night; a neighbour with 3 acres gets less, an hour or so later. Turns move with sales of land, inheritance and informal swaps and sales between farmers.
Most of this lives in memory, a paper list held by a local official, or a phone call to a neighbour. Missing a turn at 2am means a week without water for that field. Disputes over turns are a common source of conflict, and rights are hard to prove.
What already exists and the gap
- Irrigation departments keep official warabandi records, often on paper or in office systems that farmers cannot see.
- Farm advisory apps in Pakistan cover weather, prices and crop advice, not water turns on a single watercourse.
- WhatsApp groups are how many farmer groups coordinate today, with no structured record.
The gap is a simple, shared and trusted schedule for one watercourse that computes turns correctly, reminds farmers in time and records every agreed change.
Inspiration
Design and practice of water allocation rules: lessons from warabandi in Pakistan's Punjab (Bandaragoda, IWMI Research Report 17, 1998) describes how warabandi was designed to share scarce water equitably by giving time in proportion to land, and the widening gap between that design and actual practice, including informal exchanges. This project gives the design a transparent digital form and records the informal practice instead of pretending it does not exist.
What you build
- Water users' association members set up the watercourse: outlets, farms in order along the channel, areas and the time it takes water to reach each farm.
- The scheduler produces the weekly turn table, including travel-time allowances, and rotates start times if the community wants night turns shared.
- Farmers get a reminder before their turn, in Urdu, by SMS or WhatsApp, with who has the water before and after them.
- Two farmers agreeing a swap confirm it from their phones or by a reply code, and the schedule and ledger update for everyone.
The technically interesting part
- Turning shares into times. Total weekly time is split by area, but water takes time to travel along the channel, and some schedules give allowances for filling and draining the channel. Model these rules as configuration, not hard-coded logic, because practice differs between watercourses.
- Fair rotation. If turns rotate weekly so the same farmer is not always stuck with a night turn, prove your rotation gives each farmer the same total over a cycle.
- An agreement ledger. Swaps and sales of turns need confirmation from both sides and must never change a third farmer's time without their agreement. Store an append-only history so the current schedule can always be explained.
- Low-tech access. Many farmers use basic phones. Reminders and swap confirmations must work over SMS, with short reply codes.
How to evaluate it
- Correctness: unit tests and property-based tests that every farmer's total time matches their share and that no two turns overlap.
- Pilot: run with one watercourse for at least four weeks; record missed turns, disputes and how many swaps were recorded.
- Usability: can farmers and the association secretary read the turn table and confirm a swap without help after a short demo?
- Comparison: compare your computed schedule with the existing paper schedule and explain every difference.
Suggested plan
- Weeks 1 to 3: field visit, interviews with farmers and an association secretary, collect one real schedule.
- Weeks 4 to 7: watercourse model, scheduler and tests.
- Weeks 8 to 10: web app, reminders and the swap ledger.
- Weeks 11 to 13: pilot and data collection.
- Weeks 14 to 15: report and demo.
Path to a product
Water users' associations, irrigation reform projects and NGOs working on water governance are natural partners. A simple, low-cost tool could be offered free to associations with support from development programmes. The project is also a strong example of turning a real-world rule system into software, which is exactly what product engineers do.
Scope warning
Do not try to change the official water allocation or replace the irrigation department's records; your tool records what the community agrees. Start with one watercourse and one set of rules. Keep money out of the app even if turns are sold informally.
Learn what you need on Sefism
- Full stack development roadmap: the web app, database and reminders.
- SQL and databases roadmap: modelling farms, turns and an append-only ledger.
- DSA and problem solving cheat sheet: the scheduling and interval logic.
- PostgreSQL Documentation: constraints that stop overlapping turns.
- UI/UX design roadmap: designing for low-literacy users and basic phones.
Get help with this idea
The hard part is getting a real schedule and the trust of a farmer group. Tauseef can help you plan the field visit, model the rules flexibly and keep the scope to one watercourse. If you are new here, create a free account first.
Ideas and guidance, not finished projects
These are project ideas and scoping guidance, published free for students to use as a starting point. I do not build, write, or sell final-year projects, and I do not complete coursework for anyone. Take an idea, make it yours, and build it.
Not sure this one fits you?
I help students pick an idea that matches their skills and their deadline, then scope it down until it is finishable. Guidance only, never done for you.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.