Most farms know what they made for the year. Fewer farms know what they made on Paddock 7. Almost no farms know what they made on Paddock 7 compared to Paddock 12 across three seasons running. The numbers exist. They just live in places where they can't talk to each other, so the question can't be answered without a week of someone's time.
This is a piece about paddock-level profit and loss — what it actually is, why most farms don't have it, what it changes when you do, and how to get there without rebuilding your records from scratch.
The short version: paddock-level P&L is the single most useful piece of analysis a farm can run that nobody is running. Once you have it, you stop guessing which blocks deserve the next round of investment, which ones to drop from the rotation, and which ones to lease out instead of farm. The question moves from “I think this paddock is a bit underwhelming” to “this paddock has had the worst gross margin three seasons running and the reason is fertiliser intensity.”
What paddock-level P&L actually is
Paddock-level P&L is a simple idea executed seriously: attribute every revenue line and every input cost on the farm to the paddock, block, mob, batch or compartment it came from or went on. Sum up by paddock. The number you get out is the gross margin (or net margin, depending on how much overhead you attribute) for that piece of land for that period.
The mechanics aren't complicated. Conceptually you need three things:
- A paddock identity for every parcel of land you treat as a separate accounting unit. A drawn polygon with a stable identifier.
- Input attribution at the point of work — every spray, every fertiliser application, every seed allocation, every irrigation event, every labour hour, every fuel charge tagged to the paddock it was applied to.
- Revenue attribution at the point of sale — every load, every animal, every contract tagged back to the paddock the produce came from.
Sum the inputs. Sum the revenue. Subtract. The difference is the paddock's contribution.
The number isn't perfect. Some costs — overhead, equipment depreciation, owner's labour — aren't easily attributed to one paddock. But the relative picture between paddocks is much more important than the absolute number, and the relative picture is what tells you where to invest, where to back off, and where the operation is silently subsidising land that isn't earning its keep.
Why most farms don't have it
The mechanics aren't hard. The reason almost no farms have a current, accurate paddock-level P&L isn't a will problem. It's a data-model problem.
Most farms run on systems that account at the enterprise level: cropping enterprise, livestock enterprise, mixed. The accounting software sees one big “fertiliser” expense for the season. The spray diary sees individual applications but doesn't see costs. The livestock register sees movements but doesn't see feed input. The accounting and the agronomy live in different worlds, and the bridge between them — the paddock identity that ties a fertiliser invoice to a specific block — isn't shared.
The result is that anyone trying to produce a per-paddock P&L has to do it by hand. Pull the cost data from accounting. Pull the application data from the spray diary. Reconcile the two — half the spray diary entries don't have a unit cost, so you back-fill them from the chemical invoices. Pull the yield data from the harvest log. Match yields to paddocks (which works for cropping, gets harder for livestock). Build a spreadsheet. Three weeks later you have an analysis that's already out of date because last week's spray hasn't been added yet.
It's not that nobody knows how to do it. It's that the time cost of doing it manually is so high that almost nobody bothers — and the analysis that does get done is usually for one season and then gets abandoned because it can't be maintained.
What changes when you have it
A few examples from operations who actually maintain paddock-level P&L:
Variable-rate input decisions become evidence-based. “Block 7 has the lowest yield-per-dollar-of-input three years running, and the soil tests show it has the highest baseline nitrogen — we're over-applying urea on it.” That's a different conversation from “I have a feeling about Block 7.”
Lease-vs-farm calls become defensible. When a paddock has consistently lost money compared to neighbours doing the same thing, the calculation of leasing it out instead of farming it stops being emotional and starts being numerical. Sometimes the right call is to keep farming it for non-financial reasons (long-term soil rebuild, rotation balance, contractor labour, sentiment). But you make that call knowing the financial cost rather than not knowing it.
Buyer programme participation becomes targetable. If you're considering enrolling a portion of the operation in a sustainable-sourcing premium programme, knowing the gross margin on the specific paddocks you'd enrol — including the additional compliance cost — tells you whether the premium is worth the overhead. Without paddock-level numbers, the answer is whole-operation; with them, it's portfolio-level.
Rotation decisions sharpen. “Wheat-canola rotation on the heavier blocks; barley on the lighter ones” stops being received wisdom and starts being a query against your own data — the kind of question a grain and broadacre operation should be able to answer from its own records.
Mob-paddock assignments become accountable. Feed cost per kilo gained, by mob, by paddock, by season. The decision about which paddock to move which mob to in early spring stops being “where we always put them” and starts being “where they put on weight cheapest last season” — the same discipline applied to a beef cattle operation's grazing rotation.
None of this is exotic analysis. It's the kind of operational insight a manufacturing plant treats as table stakes for every product line. Agriculture has historically been one of the last industries where it isn't.
What “real” paddock-level P&L requires
If you're evaluating whether a platform actually supports paddock-level P&L (not just claims to), three questions sort the genuine from the pretend:
- Where does the paddock identity come from, and does every system on the farm see it? If the spray diary calls it “Paddock 7” and the accounting calls it “South 12 — Block A,” there is no shared identity. Every system has to read from the same paddock register.
- Is input cost attached at the point of application, or back-filled from accounting? A platform that attaches costs at application is one that gives you an accurate paddock-level picture in real time. A platform that requires nightly reconciliation between accounting and applications is one that gives you a picture three weeks late, with errors.
- Does revenue come back to the paddock automatically when a load is sold? Cropping makes this relatively easy — the load came from a harvest block. Livestock is harder — the animal grazed three paddocks before sale. The right answer involves weighted attribution based on residency, not just “whichever paddock it was on when it left.”
A unified farm management platform that captures every record once and treats the paddock as the primary identity meets all three. A stitched-together collection of point tools meets none of them.
The honest caveats
Paddock-level P&L isn't a complete picture of the operation, and pretending it is can lead to bad calls.
Some costs are genuinely operation-wide. The owner's labour, the office overhead, the equipment depreciation, the consulting fees — some of these can be reasonably attributed across paddocks; others can't. Be explicit about which costs are attributed and which sit in an overhead pool.
Some paddocks earn non-financial returns. A windbreak block, a wildlife corridor, a regeneration paddock, a longer-term soil rebuild — these may show a poor short-term P&L while doing useful long-term work. The data tells you the cost; the judgement decides whether it's worth it.
One year isn't enough. A single season can be misleading because of weather, market timing, or one-off pest events. Three seasons is the minimum where patterns become meaningful.
Yields are messier than they look. Cropping yields off a harvest block are usually clean. Livestock weight gain by paddock is messier because animals move. Horticultural pack-out by block needs the packing shed to read the same block identity the field does. The data quality of the inputs decides the data quality of the analysis.
How to get there
If you're starting from scratch:
- Draw or import every paddock as a polygon, with a stable identifier you'll keep using. This is the foundation of everything that follows.
- Pick a platform where every operating record — spray, fertiliser, irrigation, treatment, labour, fuel — can be tagged to the paddock at the point of work. The capture-once model is what makes the analysis maintainable.
- Connect the accounting. Every chemical invoice, every fertiliser delivery, every contractor charge needs to land against the paddock that consumed it. Most operations get 70% of this from invoice-line tagging and the remaining 30% from monthly reconciliation.
- Tag every sale back to its source paddocks. For cropping, this is a single line on the harvest record. For livestock, this is the residency-weighted calculation.
- Run the analysis quarterly, not annually. A current paddock-level P&L is useful; a year-old one is history.
If you're maintaining a manual spreadsheet today and asking whether to switch to a platform that does this automatically — the question to ask is how many hours per month the spreadsheet costs you, and what decisions you'd have made differently with a number that was current instead of three weeks behind. Our calculator can help you put a figure on that.
The kicker
Paddock-level P&L isn't an advanced feature. It's the most basic question a farm should be able to answer about its own land: which piece earns its keep, which piece doesn't, and which piece is improving over time. The reason almost no farms can answer it isn't because the answer is hard. It's because the data lives in places that don't talk to each other.
Once it talks, the answer falls out as a side-effect of running the farm. And once you have the answer, the decisions you make next season are made with the lights on.
— The RedEarthOne team