Irrigation, Reservoirs & Scheduling
Irrigation: Data & Integrations
What is recorded, what it connects to and who can see it.
The module maintains 8 core entities and connects to 5 external sources. Everything is exportable in open formats and every instance of sharing requires explicit consent.
Data model
What the module records, and how it connects
These are the entities the module maintains. Because they are shared across the platform rather than owned by one screen, a record created here is available everywhere it is relevant.
- Irrigation zone
- Soil moisture reading
- Deficit calculation
- Irrigation event
- Reservoir
- Storage level
- Pump
- Energy record
Every entity carries a full audit trail and is exportable in open formats under the Farm Data Charter.
Integrations
What it connects to
Agrivencia integrates with authoritative sources rather than rebuilding them. Where no production interface exists, a documented user-mediated route is provided instead.
- Soil moisture sensor networks
- Met Office evapotranspiration data
- Irrigation controllers
- Abstraction licence records
- Energy monitoring systems
Integration availability, licensing and cost vary by source. The integration catalogue states the position for each one honestly, including where a commercial licence is required.
Detail
How the data is held
Irrigation scheduling based on soil moisture deficit and evapotranspiration rather than habit typically delivers substantial water and energy savings alongside better crop uniformity. This module runs the scheduling model, manages reservoir storage and refill, and appraises the capital case for winter storage against a summer abstraction licence that may not always be available.
Field studies of sensor and evapotranspiration-based scheduling consistently report water use efficiency gains in the range of 20 to 40 per cent alongside yield improvement. On-farm reservoir and irrigation grants have been available through the capital grant offers, and winter storage is increasingly the only route to secure summer water as abstraction is constrained.
Everything Irrigation records is written into the same platform data spine as every other module, which is why a single entry can satisfy an operational need, a scheme evidence requirement, an assurance clause and a carbon activity line at once. That is the whole design premise: the work is already being done, and it is the recording of it that is duplicated.
How we handle evidence
Where these figures come from
Agrivencia grades every figure it publishes. Primary legislation, official statistics and audit reports are treated as authoritative. Levy body and professional body data is treated as reliable. Commercial trackers and trade press are treated as indicative and labelled as such. Where sources conflict, the conflict is shown rather than resolved silently.
- Authoritative Legislation, statutory instruments, official scheme rules, national audit and public accounts reporting, departmental annual reports and accredited official statistics.
- Reliable Parliamentary committee evidence, peer-reviewed research, independent economic institutes and levy body analysis.
- Supporting Professional bodies, land agents, certification schemes and industry associations.
- Indicative Commercial market trackers and trade press, used for corroboration only and always labelled.
Payment rates, caps and windows in UK farm support change frequently and sometimes without notice. Nothing on this platform is a substitute for the current published scheme rules or for professional advice.
Questions answered
What people ask about Irrigation
Does this replace the software I already use?
Not necessarily. Agrivencia integrates with authoritative sources and mainstream packages rather than insisting on replacing them. Where an incumbent does one job well, the platform connects to it; where the job spans several systems and nobody does it, the platform does it.
Will it work where I have no signal?
Yes. Field capture in Irrigation is offline first, storing locally and synchronising when a connection returns. Only around a fifth of UK farms report reliable signal across the whole holding, so this is a design assumption rather than a feature.
What happens when the scheme rules change?
Scheme rules are held as data rather than code, so a rate change, a cap change or a window closure is a content update that takes effect the same day. The platform also alerts you to what the change does to your own position.
Who owns the data I put in?
You do. The Farm Data Charter gives you a complete export in open formats at any time, and every instance of data sharing requires an explicit, revocable consent that is visible in your account.
Does it work if I farm across a border?
Yes, and that is one of the main reasons the platform exists. A business with land in more than one nation sees one reconciled view rather than two portals, with obligations and deadlines from both administrations in a single calendar.
Can my agronomist or land agent use it too?
Yes. You grant scoped, time-limited access per holding and per module, and you can revoke it in one click. Advisers never get a shared password or a blanket view.
What is the biggest limitation of this module?
Sensor drift. Mitigated by scheduled recalibration. We would rather state that plainly than let you discover it after signing.
See Irrigation running on your own holding
Thirty minutes, using your parcels, your schemes and your enterprises rather than a sample farm. No obligation and no sales script — if it does not fit your business we will say so.
- Free tier available
- No card required
- Your data stays yours