Monitoring the whole farm water system: bore, pump, tanks and troughs
One dry trough is rarely a trough problem. If you want to monitor the whole farm water system, not just a tank, you have to watch the path the water actually takes: out of the bore or dam, through the pump, up to the header tank, down to the stock tanks and troughs. Most guides, including our own water tank level monitoring guide, cover a single tank well. The real farm risk is the system: the bore draws down, the pump fails silently, the header tank drains overnight, a trough empties in a hot week. Each failure starts at one stage and shows up two stages later, usually as thirsty stock. Here is how to watch the whole path, what each stage tells you, and how to layer the alerts so the urgent ones interrupt you and the slow ones wait politely.
Why single-tank monitoring misses the real risk
A level sensor on one tank is a big step up from a dipstick, and if you only fit one sensor it is the right first move. But farm water failures are chain failures. The bore draws down over a dry month, so the pump starts sucking air and trips. The tank the pump feeds stops filling, but it holds two days of water, so nothing looks wrong. Two days later the troughs at the far end go dry on a 40 degree afternoon, and now it is an emergency involving a water cart. The tank sensor, on its own, told you the middle of that story. The bore and the pump told the start of it, days earlier, when it was still a cheap fix.
The point of whole-system monitoring is to hear the start of the story. Every stage upstream of the failure you can see gives you lead time, and on a farm, lead time is the difference between a service call and a livestock problem.
Map the water path: source, pump, storage, stock
Every property is different in the details and identical in the shape. Water comes from a source: a bore, a dam, a river licence, a roof. A pump moves it, often powered by mains at the shed, a generator, or a solar controller in a paddock. It lands in storage: usually a header tank up on a rise doing the pressure work, sometimes feeding smaller stock tanks below it. Gravity or a second pump then delivers it to the stock end: poly lines, float valves and troughs, which is the only part of the system the animals care about.
Draw that map for your own place before you buy anything. Ten minutes with a pen tells you where the single points of failure are, which stages already announce their problems, and which fail in complete silence. On most farms the silent ones are the pump and the bore, and the loud one, the trough full of bellowing cattle, is the last to know.
What to watch at each stage, and why
The source: bore or dam level. A bore that draws down faster than it recovers is the earliest warning the whole system gets, and running a bore pump dry is one of the more expensive mistakes on a property. A level reading in the bore column, or a simple dam level sensor, turns "the bore seems slow lately" into a number you can watch across a season. This is the slowest-moving signal on the farm, and that is exactly its value: it is drought and demand made visible weeks early.
The pump: run-state and power. Pumps fail silently. A tripped breaker, a dead pressure switch, a generator out of fuel: none of them make a sound you can hear from the house. Watching whether the pump is actually running, and whether it has power, catches the most common silent failure on rural properties within minutes instead of days. We cover this end of the system in detail in generator and pump failure alerts for remote farms. The killer combination is pump state plus tank level: a pump reporting off while the tank it feeds is falling is a fault, full stop, and the system can tell you so without you interpreting anything.
The storage: header and stock tank levels. The header tank is the heart of the map, because its level reflects both directions. Falling with the pump off: supply problem. Falling fast with the pump on: a burst line or a stuck float downstream. Overflowing: a failed valve. Fit a proper level sensor here first, one that reads the actual level rather than a full-or-empty switch. If you want to understand what the sensor is doing, our interactive explainer on how tank level sensors work lets you compare ultrasonic, pressure and float readings on the same tank.
The stock end: troughs. The trough is the last point before an animal goes without, so it is where slow problems become urgent ones. Trough monitoring is less about precision and more about speed: is there water in it right now, and is it refilling after the mob drinks? A stock trough water level sensor in the paddocks that are furthest from the house, or carrying the most head, buys you the hours that matter on a hot day.
Power and signal are part of the water system
Two quiet dependencies sit underneath everything above, and they fail too. The first is power: paddock sensors and repeaters run on batteries and small panels, and a flat battery turns a monitoring point into a blind spot. Size the power for years rather than months, use solar where the sun does the maintenance for you, and make sure every device reports its own battery level so the system warns you before it goes dark. Our guide to solar power for remote tank and farm sensors covers panel sizing and placement.
The second is signal. None of this requires mobile coverage at the tank, the trough or the bore: the sensors carry their readings over a long-range low-power radio to one receiver at the house or shed, and only that one point needs internet. If the whole property has no reliable connection at all, a satellite uplink at the receiver does the job, which we cover in satellite water tank monitoring where there is no signal. Treat connectivity like a water line: one path, mapped, with a known failure mode, and an alert when it goes quiet.
Layer the alerts: not everything deserves your attention at 2am
A system that watches ten points will generate more information than a system that watches one, and if all of it arrives as urgent pings you will mute it within a month. The fix is layers. An empty trough at 2pm in January is an emergency: it should push to your phone and keep pushing until someone acknowledges it. A header tank declining a little faster than last week is a maintenance flag: it belongs in a daily summary you read with a coffee. Sort every alert into one of these before you switch it on:
- Act now. Trough empty or falling fast in heat, pump off when it should be running, header tank in freefall, storage below the level that covers a delivery delay. Push notification or text, immediately, to more than one person if stock are involved.
- Act this week. Slow decline with no obvious cause, bore recovery trending down, a tank that is not refilling to full overnight the way it used to. Daily digest.
- Act eventually. Sensor battery below threshold, a reading that looks noisy, seasonal usage creeping up year on year. Weekly summary, or a note on the dashboard.
- Silence itself. Any sensor that has not reported for a few hours gets its own alert. On a system you rely on, no news is not good news; no news is a dead battery, a failed radio or a cockatoo-chewed cable.
The layering is what makes whole-system monitoring livable. The urgent channel stays quiet enough that when it does go off, you move.
Start with one tank, grow on the same platform
None of this means buying ten sensors on day one. The sensible path is the one the hardware already supports: start with a single level sensor on the header tank, plus the receiver and the alerting, and live with it for a season. That first step does most of the setup work: the receiver, the radio path and the alert channels are built once and shared by everything that comes later. From there, each addition is just another sensor joining a network that already exists: the pump next, because it is the most common silent failure, then the troughs in the paddocks that scare you most, then the bore.
This is also why it pays to choose gear that grows, rather than a sealed single-purpose tank gadget: the platform question matters more than the first sensor. Our tank monitoring guide walks through the full system for anyone starting from scratch, and if you are weighing up what the pieces cost, the honest answer is qualitative: it is one-off hardware you own, the radio path carries no per-sensor fees, and the cost picture for Australian properties scales with the number of points you watch and the distances between them, not with the volume of water.
The bottom line
Monitor the system, not the tank. Map the path your water takes from source to pump to storage to stock, put a sensor at each stage that can fail silently, and let one receiver and one dashboard carry the lot. Layer the alerts so an empty trough interrupts your afternoon and a slow bore shows up in your morning summary. Start with the header tank, grow one sensor at a time, and every stage you add buys you lead time upstream of the failure you would otherwise have discovered as a dry trough. The farms that get caught out are almost never the ones with no monitoring; they are the ones watching a single number in the middle of a chain.
FAQ
Where this comes from
The primary sources behind the above, so you can check any of it yourself rather than take our word for it:
- Internet of things, the general idea behind a set of connected sensors reporting to one dashboard.
- Telemetry, on getting readings from the far end of a property back to the house.
- Level sensors, on how tank, bore and trough levels are actually measured.
- LoRaWAN, the long-range radio these sensors commonly report over.
What should I monitor first on a farm water system?
Start with the storage that hurts most when it fails, which on most farms is the header tank or the main stock tank. It sits in the middle of the system, so its level reflects problems on both sides: if the pump or bore fails the level falls with no fill, and if a pipe or trough valve fails downstream the level falls faster than normal use. One sensor there catches more failures than a sensor anywhere else, and you can add the pump, the troughs and the bore as the next steps.
How do I know my pump has failed before a tank runs dry?
Watch the pump itself, not just the water. A run-state or power sensor on the pump tells you it has stopped, tripped or lost supply within minutes. Paired with a tank level sensor, the pattern is unmistakable: the pump reports off while the tank level is falling when it should be filling. Without pump monitoring you only find out when the tank has already drained, which can be a day or more after the pump actually stopped.
Can one system watch the bore, the pump, the tanks and the troughs together?
Yes, and that is the right way to build it. Each point gets its own small sensor, every sensor reports over the same long-range low-power radio to one receiver on the property, and everything lands on one dashboard with one set of alerts. You do not need separate apps for the bore, the pump and the tanks, and each extra sensor you add reuses the receiver and the alerting you already own.
Which water alerts are urgent and which can wait?
Anything that means stock could run out of water soon is urgent: an empty or fast-falling trough in hot weather, a pump that has stopped while it should be running, a header tank in freefall. Those should push to your phone immediately. A slow decline over days, a bore recovering more slowly than usual, or a sensor battery getting low are maintenance flags: they belong in a daily summary or a quiet notification. If every alert is treated as urgent you will start ignoring them, and the one that mattered gets missed.
Do I need mobile signal at every tank, trough and bore?
No. The sensors send their readings over a long-range low-power radio to a single receiver somewhere on the property that has power and internet, so the paddock end needs no signal at all. If the whole property has no reliable mobile or fixed internet, a satellite uplink at the receiver carries the readings out instead. Signal is solved once, at one point, not at every sensor.
Does whole-system monitoring cost much more than monitoring one tank?
The step up is smaller than most people expect. The receiver, the alerting and the dashboard are built once and shared by every sensor, so the first tank carries most of the setup and each extra point is just another sensor. It is one-off hardware you own, and the radio path has no ongoing fee per sensor. Costs scale with how many points you watch and how far apart they are, not with how much water flows through the system.
Want a hand mapping your own water path and picking the first sensor? Tell us where the water comes from, where the pump and header tank sit, and which trough worries you most on a hot week. We will lay out a starting point that grows with the property, no upsell to gear you do not need. Tell us about your setup.