One path: an order comes in however the patron sent it, the office approves it before anything moves, it lands on a calendar by headgate, a rider delivers it offline in the field, and the result posts against that patron's water right. Nothing gets re-keyed, and nothing gets lost between the clipboard and the spreadsheet.
The lifecycle
Control
A water order system that simply collects requests moves the problem rather than solving it. The district decides what runs and when, and it needs to make that call with the whole week in view — which headgate is already loaded, who is near their limit, what the ditch can carry. Loamio puts the approval step in front of the schedule, on a calendar organised the way water is actually delivered.
Against the right
Orders are only meaningful next to the right they draw on. Loamio tracks that right as share count times acre-feet per share — the way the district issued it — so a patron's remaining water is computed, not estimated. When the board cuts acre-feet per share for a dry year, every balance recalculates from one number, and the curtailment view sorts every patron ok, near-limit, or over against the new cap.
Reconciliation
On the District plan, diversion readings pulled from state agency sources — CDSS in Colorado — sit alongside your own orders on the diversion structure. Current flow, today's diversion, and the seven-day total are in the same screen as what you scheduled, so the office reconciles against the state's figures without exporting anything or opening a second system.
Questions
It manages the full life of a water order — the order is taken however the patron sent it, the district approves before anything moves, it is scheduled by headgate, a rider delivers and records what was actually delivered, and the result posts against the patron's water right. The value is that it is one path, with nothing re-keyed between the request and the ledger.
Yes. Incoming orders are approved by the office before they enter a run, so the district keeps control of what gets scheduled. Approved orders appear on a calendar organised by headgate, making the week's load visible before it is committed rather than after.
No. Loamio records how each order arrived — app, phone, SMS, email, paper, or in person — as part of the order. A district whose patrons ring the secretary keeps working the way it does today and still ends up with one clean record, instead of app orders in a system and phone orders on sticky notes.
The rider records it as what it was — delivered, partial, or skipped, with a note if needed — from the headgate, offline. Recording a partial as a partial is what makes a dispute answerable months later, and it keeps season-to-date usage accurate rather than optimistic.
Yes, on the District plan. Diversion readings from state agency sources (CDSS in Colorado) sit next to your own orders on the diversion structure, so the office reconciles against the official record without leaving Loamio.
Related: Irrigation district software · Ditch rider software · Water district software · Hydraulic schematic · Loamio vs. Watervize
Next step
A 20-minute walk-through using your headgates and a real week of orders. We respond within one business day.
Book a demo