How to use PaddIQ

Every page, what it's for, and how to get the most out of it. If you only read one section, read Getting started — the rest follows from it.

Something wrong, or a question? In the app, open the menu → Send feedback: it brings the page you were on and a screenshot if you add one. Or email us: admin@paddiqag.com — we'll get back to you.

🚜Getting started — the workflow

PaddIQ runs on one idea: every operation on every paddock is a Field Record, and everything else — the map, the fert plan, the P&L — is computed from those records times your prices. Nothing is typed twice, so nothing disagrees.

How to use it

The Getting started checklist (sidebar) runs in this order, each step making the next one work: 1 paddocks → 2 region → 3 connect John Deere and sync (fills the product library, finds the machines) → 4 machinery (Add all from John Deere, build rigs) → 5 run the import wizard again so every pass gets its rig's cost (fert down the tube that went on with a seeding pass is $0 on purpose and isn't counted as missing a cost) → 6 prices → 7 plan (optional) → 8 review.
Want to look around first? Try the demo farm (the home page, or the sign-in screen — paddiqag.com/demo): the real app on one made-up wheatbelt paddock (Windmill — the home page's paddock), with a short tour of its yield maps, zones, N rate and margins. No account; everything happens in that browser tab only — nothing is saved, nothing reaches the cloud or John Deere, and your own farm on the same browser is never touched. Exit demo puts you back where you were.
Set up your farm: Import → Farm Setup, or draw paddocks straight onto the Farm Map (Add paddock/boundary).
Three more first-day steps the checklist doesn't tick off: (1) Pick your season — the season picker at the top of the sidebar sets which year every page shows; start on the season you're in, and add earlier seasons when you import their records. (2) Check your boundaries — open the Farm Map and look at each paddock's shape against the satellite: a boundary pulled from John Deere or a shapefile can be an old field, include a road or miss a corner, and every hectare figure, rate and margin is worked from that shape. Redraw any that are wrong (Draw a boundary on the Farm Map, or import the right shapefile). (3) Bring in your soil tests — Import Soil Tests takes the lab's CSV or Excel, a PDF report or a photo of it; the fert recommendations and the nutrient balance use them, and without one PaddIQ falls back to typical values and says so.
Settings → Data → Backup & sync → Check this device's storage: how full this browser's small store is (about 5 MB), whether the large store (IndexedDB) is working, and the biggest items — so you can look before a save fails rather than after.
A paddock that John Deere stores in several separate pieces is read as one paddock with every piece counted. Holes (scrub, dams, cut-outs) are only the rings that sit inside a piece.
Spray diary times: a pass imported from Operations Center carries its start and finish times onto the record (More details). Wind, temperature, humidity, nozzle and batch numbers are yours to record — PaddIQ never fills them from a weather model.
Pricing → Fill from PaddIQ defaults: a sheet of every row in this season's Pricing that the PaddIQ default list can price — products, grain, seed, fuel and oil, contractor rates, overheads — with what you have now and the default beside it. Tick what you want, nothing already priced is touched, and each filled row carries a PaddIQ chip until you type your own price over it. The defaults are indicative figures, not quotes.
Field Records search: type a product, paddock, pass type, date, note, operator or machine and only the paddocks with a match stay on the page, opened to show them. It understands the same slang and loose spelling the assistant does — gly, Treflan, excirel — and a machine matches by the name John Deere recorded, the rig or fleet on the pass, or the machine the pass is counted to. The Excel, PDF and Spray diary buttons run the very same search and filters, so a file holds exactly what the page lists.
Editing a pass: anything that stops it saving is said under the box it belongs to — a product line with no rate, a missing date, a finished pass with no rig — in red; amber is a heads-up that doesn’t stop Save. Press Save while something is red and every box shows its message and the page goes to the first.
When the search finds nothing it offers what you probably meant — names from this season's passes spelled close to what you typed, each with how many passes it finds (tap one to search it) — and, if the words do match passes that a pass-type, done / planned or machine filter is hiding, “N matches with the filters off · Show all”. Inventory’s and Pricing’s product searches do the same: a typo or a nickname (“treflan”) offers the product it probably meant, with Clear search.
Boxes that check what you type: a rate, a price or a paddock's hectares says under the box what's wrong (letters, a negative, a 0 where 0 means nothing) and what happens to it — the saved figure stays until you type a real one. The same goes for every price and amount box in Pricing (freight, levies, grain prices, overheads, leases, fuel, deliveries, invoice lines) and Machinery (a machine's figures, running cost and cost split, a job's $/ha). A paddock's hectares are never saved as 0 from a blank box any more. Every camera button (a place's photo, a batch sticker, a product label, a part scan) has “Upload a photo instead” beside it, for when the camera is blocked or the device has none; “Use my location” says why it couldn't and lets you tap the spot on the map instead.
Where to export: Field Records has Excel, PDF and Spray diary buttons beside the filters (they export what the filters show — the spray diary carries times, wind, temperature, humidity, Delta T, nozzle, pressure, spray quality and batch numbers per product); Harvest → Paddocks has Excel; Satellite Yield has Excel once this season is estimated; Nutrition → Summary has Excel; Stock on hand has both; Import → Export has the season plan PDF and paddock data; Planning → Costs & orders has one Export button listing the Order list, Paddocks and Margin what-if (Excel) and the Season plan PDF; Pricing, Maintenance and Financials keep their buttons.
Every export is a PaddIQ-branded file: Excel (a title block with the farm and date above the table) or a print window with the PaddIQ logo that saves as PDF. Nothing exports as CSV any more.
Rigs follow the product: an in-season fert pass defaults to the spreading rig, but when every product on it is a liquid (L/ha) it takes the spraying default instead — Flexi-N goes on the boom. A planned pass still on the default rig switches when its products change; a rig you picked yourself, or an actual pass, is never changed for you.
✨ Ask PaddIQ: when it stages changes, press Approve on the batch or just reply "approve" ("discard" throws them away). It never writes anything itself. It can stage more than records now — a product price, a contractor rate, an overhead, a machine's purchase price or work rate, a paddock's target yield or planned crop, and stock in, out or a count at a place — each shown as before → after. Members can only stage edits in the areas their team row says they can edit.
✨ Ask PaddIQ can read your invoices and purchase log: "what did I last pay for Transform?" answers from Pricing → Invoices and the purchases logged on a product, with the supplier and invoice number.
✨ Ask PaddIQ reads your fleets properly: each fleet's members with their share and role (worker or support), its $/ha and how it is worked out, and what it did this season (passes, hectares, $) — it used to see every fleet as empty. It also reads Pricing → Overheads as $ per hectare (it was told they were whole-season dollars), and an overhead change it stages reads “$/ha”.
✨ Ask PaddIQ answers how-to questions too ("how do I match paddocks to an imported boundary?") from this guide, naming the screen to go to.
✨ Ask PaddIQ can cost a pass at a contractor rate: "log the aerial spray on all canola at the aerial rate" stages the records with the contractor as the cost source, and the $ lands in Financials' Contractor bucket — the same as picking the contractor in a record's cost-source dropdown.
✨ Ask PaddIQ keeps your conversations: History at the foot of the panel lists the last 30, reopens one to read or continue it, and × deletes one. Staged cards in an old conversation show as expired — nothing old can be approved; ask again and it stages afresh. Your conversations are yours alone: they are kept on your device and in your own account, and nobody else — not the farm owner, not anyone else on the team — can open them. (Until October 2026 saved conversations were shared with the whole team; each one has been moved to the person who asked its questions, and any that could not be matched stay with the farm owner — History says so once.)
✨ Ask PaddIQ follows your team permissions when it READS, not only when it stages changes: if the farm owner has hidden a tab for you in Settings → Team (Financials, Pricing, Field Records, Planning, Inventory or Machinery), it can't answer from that tab either and says so; with both Pricing and Financials hidden, dollar figures are left out of the answers it can give.
Getting started: the checklist in the sidebar can be hidden with its × once the farm is running. The steps stay on this page, and it comes back for an account with nothing set up.
✨ Ask PaddIQ: press ■ Stop while it is answering and what it has written so far stays in the thread. You can keep typing while it works — the message waits and goes as soon as it finishes.
✨ Ask PaddIQ (the round button, bottom right): ask about paddocks, records, nutrient balance, stock, rain or margins in plain words. It reads the same numbers the screens show — every figure comes from your data, never a guess — and it can stage record changes ('add Metsulfuron to the planned knockdown on every wheat paddock on lupin stubble'): you see the list and press Approve before anything is written. Your question and the data it reads go to Anthropic's API; each account has a monthly allowance shown at the foot of the panel (document and photo reading draw on the same allowance, and there is a limit for everyone together each month), and questions are logged so the answers can be improved. If an answer is wrong or comes back empty, press the ! beside it to send that question to the PaddIQ admin.
New account? Paddocks come first: on the Farm Map press Import from John Deere and every paddock is created from its field (named Farm:Field) with its boundary and area, and Deere's farms become your farm list in Settings → Farm & Paddocks with each paddock under its farm, or upload a boundary file or draw them. The Getting-started guide's first button does this for you. Operations and map layers need paddocks to land on.
Get your operations in: connect John Deere (Import → John Deere) for a live sync, drop Excel/CSV exports or PDF field reports on Import → Manual / PDF (John Deere Operations Center reports today; other exporters can be added as sources), or add records by hand in Field Records.
Set your prices: Pricing tab — chemicals, fertilisers, seed, grain prices, overheads, fuel. Everything you imported is waiting there at $0 until you price it.
Check Financials: profit per paddock appears as soon as records + prices exist.
Plan next season: Planning walks four steps — Crops, Fertiliser, Programs and Costs & orders — with a strip at the top saying how far each has got and what to do next.
Cards list by crop, newest first. “Add a tank mix…” on a card opens the farm's saved mixes scoped to the card's crop — mixes tagged with that crop, untagged ones, Fallow-tagged and knockdown/summer sprays — with the same search, crop/purpose filters and sort as the Tank mixes section (search matches every word against the mix's name, its products, its purpose and its crop tags; Sort: A–Z is the default, and Sort: purpose puts a header over each purpose); “Show mixes tagged for other crops” at the bottom lifts the scope, and a second tab lists mixes used on the boom that are not saved yet — with its own search and Sort: A–Z or most passes. “New tank mix” in that sheet builds one from your saved products, saves it to the library tagged with the crop, and adds it straight away. A fertiliser pass (and a spray carrying liquid N) has one switch, Rates from the Nutrition plan: on, each paddock takes the rate of the matching line in your ACCEPTED Nutrition plan (same product, same timing) and the typed rate is used only where a paddock has no plan line; off, the typed rate wins (the plan line still merges in). Each product then shows where its rates came from — “plan: 55–90 kg/ha on 12 of 14 paddocks · 2 use 80 typed”. The rates are read when you apply the card; change the plan in Nutrition, then re-apply (the card shows “Changed since applied”). Passes no longer re-rate by themselves when Nutrition opens, and the plan is the same on every device. Crop types: every crop picker reads one list — PaddIQ's built-in crops (plus Hay, Pasture, Fallow and No Crop), the crops PaddIQ's library has added, and your own. “＋ Add a crop type…” in any picker (or Settings → Crop types) adds one for the whole farm, in its own colour, and queues it for PaddIQ's library. A crop you add carries no nutrition maths (removal, default yield, water ceiling) until the library reviews it — the pickers, balance and recommender say so rather than guess. Tank mixes (under the Cropping Cards list) is the farm-wide library — search it (name, product, purpose or crop), filter it by crop or purpose and sort A–Z, by purpose (with a header over each purpose), crop, cost/ha or recently changed; the search also narrows “mixes used on the boom”, which sorts by most passes or A–Z. Each mix: name, purpose, timing (where it sits in the season, defaulted from the purpose), crops it is for, products and rates, water rate, notes, cost/ha at the season you are planning, and how many card passes were made from it (withholding periods are on each spray record, from the label tables — not on the mix). Delete (red) asks first; card passes made from the mix keep their copies. Show mixes used on the boom lists every distinct mix the records have applied — passes, hectares, last date — one tap to save. Passes imported from John Deere group under the Operations Center mix name, with the water rate they ran at, so one mix is one row whatever the boom's per-pass jitter; records imported before this was read pick it up the next time you run Import → John Deere (or Sync) for that season. Read mixes from John Deere (shown when connected) brings the Operations Center tank-mix DEFINITIONS into the library — each component at the rate you set plus the water rate — matched by Deere's id, then by name; a mix you have edited here keeps your edits, and re-reading updates the rest. A card block made from a mix is a COPY that remembers its source: editing the mix never moves a card by itself; the block shows “mix changed since” (a new water rate counts) with a re-copy button, and the mix’s Re-apply pushes it into every block made from it — products, water rate, and the timing too unless you moved the block to another timing since. Actual records are never touched. The tank-mix builder opens as a sheet: on a computer your product library sits beside the mix; on a phone a switch shows one at a time — Mix (3) | Add products — and each line is the product, then its rate, unit and $/ha. “Use these products” puts them on the pass (or the mix you are editing). It can also start from a mix the boom used in a past season (grouped as the Tank mixes list groups them, at the rates you meant), from a saved mix, and — from a card's pass only — “Save as tank mix…” keeps a copy in the library too (it is not offered while you are editing or creating a library mix, where it used to make a duplicate). Generate card builds each spray pass from that season's commonest mix on the crop the same way — the Operations Center mix name, each product at its meant rate (0.67 L/ha, not one paddock's 0.6687), water and Boomspray left out of the products, the water rate on the pass. Rates on a card or in a mix are per hectare (L/ha, mL/ha, kg/ha, g/ha, t/ha); an older line saved as “L” or “kg” shows “per pass? set per ha” — every cost and order reads it as per hectare.

Tips & tricks

The order matters less than you'd think — you can import three old seasons first and price them later. Income and costs show $0 until prices exist, never made-up numbers.
Anything marked with an amber ⚠ or $0 is PaddIQ telling you it needs a price or a setting — it never silently invents one.
Put PaddIQ on your phone like an app: iPhone — open paddiqag.com in Safari, tap Share (the square with an arrow), then Add to Home Screen. Android — open it in Chrome, tap the ⋮ menu, then Add to Home screen or Install app. It opens full-screen with the PaddIQ icon, same sign-in, same data. Help → PaddIQ on your phone shows the steps for the phone you are holding.
On a phone the main pages live in the bottom bar (Map / Records / Weather / Planning); More opens everything else.
The Getting started strip in the sidebar counts six setup steps (paddocks, region, prices, machinery, operations, plan) for the active season and links to the next one. It disappears on its own once all six are done; a step ticks as soon as the page it points to has any real data.

📱PaddIQ on your phone

PaddIQ installs to your phone's home screen like an app — no app store. It opens full-screen with the PaddIQ icon, signs in to the same account and shows the same data.

On this device

iPhone or iPad (Safari)

Open paddiqag.com in Safari — it has to be Safari, not Chrome or a link inside another app.
Tap the Share button (the square with an arrow, bottom of the screen).
Scroll the list and tap Add to Home Screen, then Add.

Android (Chrome)

Open paddiqag.com in Chrome.
Tap the ⋮ menu (top right).
Tap Add to Home screen (on some phones Install app), then Add.

How to use it

iPhone or iPad: open paddiqag.com in Safari — it has to be Safari, not Chrome or a link inside another app. Tap the Share button (the square with an arrow, bottom of the screen), scroll the list, tap Add to Home Screen, then Add.
Android: open paddiqag.com in Chrome, tap the ⋮ menu (top right), then Add to Home screen (on some phones Install app), then Add.
Your data is safe either way: everything syncs to your account (when you come back to PaddIQ after using another app it fetches only what changed on your other devices, at most once a minute; Sync fetches everything), and the home-screen app signs in to the same account. On an iPhone the home-screen app keeps its own copy on the phone, separate from Safari's — so after installing, open it and let it sync once, and from then on use one or the other for entering records rather than both.

Tips & tricks

Opened from your phone, this section shows only the steps for the phone you are holding — and says so if PaddIQ is already running from your home screen.
On a phone the main pages live in the bottom bar (Map / Records / Weather / Planning); More opens everything else.

🗺️Home — Farm Map

Your whole farm on satellite imagery, colour-coded by crop, with overlays for profit/loss, season progress, nutrients, soil sites and NDVI.

How to use it

Add paddock/boundary → draw point-by-point on the map, or upload a shapefile/KML. Un-arable areas (rocks, dams, timber) can be cut out so areas stay honest.
Uploading boundaries is checked first. A yield map, as-applied map or other machine export is recognised and refused with a note saying what the file looks like — they are all just a .zip from John Deere, and one dropped in here used to replace every paddock boundary on the farm. If you already have boundaries, you are asked whether to Add and update (keeps any paddock the file does not mention) or Replace all.
Constraints (Layers → Constraints): a zones-style map of where inside each paddock the trouble is. Four seasons of peak growth, every pixel scored against its OWN paddock that year, then averaged — so a corner behind in every year, wet and dry alike, is the ground rather than the weather. It reads one farm at a time, at the finest Sentinel-2 pixel that fits the farm (10 or 20 m on most farms), because a pixel any coarser averages a salt patch together with the good country beside it until neither shows. Slower than the backtest; several minutes is normal, and it is kept on file afterwards — reopen the tab and it draws straight away, with Read the imagery again when you want it rebuilt.
The Constraints list gives hectares as well as a percentage, because gypsum, lime and ripping are quoted per hectare. Hectares are counted at the pixel size the imagery was actually read at (the line under the list says which — 20 m pixels are 0.04 ha each); hover a figure for the sum. A layer kept on file from before 7 October 2026 counted them at the wrong pixel size (on most farms about 2.8 times too few); it now shows the right figure without reading the imagery again. It finds underperformance, never a cause — sodicity, salt, compaction, non-wetting sand, an old sheep camp and a tree line all look the same from orbit. Walk the patch, and take a soil test where it is worst.
The 🗺 Layers button holds everything the map shows: paddock colouring (Crop, Profit/Loss, Season Progress, Nutrients), the basemap (Satellite / Street / Hybrid) and overlays (NDVI, Soil sites). The panel stays open while you flick between views.
Round buttons on the map's edge: Measure (📏) and My location (📍) — on a phone they also include Soil sites and NDVI.
💰 Gross margin map (Layers → Overlays): every paddock with a John Deere yield map is coloured cell by cell — yield × grain price (less levies/freight) minus this season's direct costs, with as-applied maps spreading their record's cost by the rate applied at each spot and everything else flat. A paddock with costs but no yield map (fallow, sprayed out, hand-entered harvest) is painted flat at its Financials income less costs, so a paddock that lost money still shows red; paddocks whose income is still a projection are left off. White is break-even, red loses, green earns. Two scales: Farm $ (loss and profit sides each stretched to the farm's own spread) or Within paddock (white = that paddock's mean, so its good and poor ground show even when the whole paddock is in profit). Hover any spot for the sum behind it — yield × price, each mapped pass at its rate, the flat costs, and the margin; tap to pin it on a phone. Tap a paddock for its mean, range and the hectares below break-even. The map's mean reconciles to the paddock's Financials margin.
🧪 Nutrients colour mode IS the applied-nutrient map: kg/ha of N, P, K, S, Zn, Mn or Cu applied at every spot this season, built the first time you pick the mode (paddocks with no as-applied map keep their flat season-total colour); the chips pick the nutrient. Same colour scale as NDVI (white → green → blue → red = light → heavy); farm-wide scale by default, and tapping a paddock stretches that paddock to its own range so its pattern shows (the legend says which scale is showing). Each fertiliser pass is converted with the same product nutrient contents the nutrient balance uses, and spread by the rate its John Deere map recorded at that spot (a pass with no map is flat; outside a map's coverage that pass added nothing). Hover for the passes behind a spot with the kg each contributed; tap a paddock for mean, range and total kg per nutrient and the list of passes (▮ mapped, ▯ flat and why). Herbicide passes add nothing and aren't listed.
📈 Multi-year margin (Layers → Overlays): every season's margin map averaged cell by cell, in nominal dollars with each real season counting once. Chips pick All years, Cereal, Canola or Lupin/legume — a paddock only shows in a group for the years it grew that crop, and is blank in a group it never grew. Hover a spot for the years behind it (2023 Wheat $412 · 2024 Canola $610 · … → average); tap a paddock for its average per crop group. Building it reads every year's layers, so the first switch-on takes a few seconds.
A dark pill with a spinner appears above the tab bar whenever something is working in the background — imagery loading, a John Deere layer coming down, a margin map building, a season syncing. It says what is happening and survives moving between pages, so a long job is never a blank screen.
Send feedback (sidebar) takes a suggestion or a bug with a screenshot, and now a sample data file — a soil lab’s export, a yield file, a PDF in a format PaddIQ cannot read yet. Up to five files, 25 MB each; only you and PaddIQ’s admin can open them, and they are used to make that format work.
Poor signal or none: PaddIQ keeps its own code on the device, so the app opens and works on a weak connection or none at all — everything you type is saved to the phone first and syncs when the signal returns. A small chip at the top says “Offline · 3 unsent” (tap it for the full line); back in range it says “Syncing…”, then “Synced”. What opens with no signal: the farm map and the main tabs (Records, Weather & season, Planning, Machinery, Inventory, Lists, Settings, Import, Financials, Pricing, the spray diary and this guide), once PaddIQ has been opened online on that device since its last update — it keeps them in the background, except on Data Saver. A tool inside a screen that you have never used on that device since the update (a map tool, a wizard) may say it needs a connection the first time. What needs the network whatever you do: new satellite imagery and the satellite estimate, the forecast and rain radar, John Deere, Ask PaddIQ, and the background map pictures you haven't already looked at (your paddock boundaries still draw) — each of those screens says “needs a connection” and loads again by itself when you're back. Zone Studio says so too (kept layers and yield maps still work; a new satellite read waits), and Pricing's invoice reader reads a PDF or a CSV / Excel list on the phone with no signal — only a photo needs a connection. While it reads it says the step (“reading page 2 of 5”). Signing in for the first time on a device also needs signal. If the app ever will not open at all, it is usually a sign-in problem rather than the app itself.
Signed out by itself: if your sign-in runs out (the phone was asleep for days, or you changed your password on another device), PaddIQ keeps everything — the sign-in screen says “You were signed out” and how many changes are waiting, and the screen you were on stays open behind it with anything half-typed. The sign-in box stays on top until you sign in (Escape doesn’t close it, so nothing behind it closes either). Sign in with the same account and you carry on where you were; the waiting changes send straight away and a note says so. An open pass in Records, a half-typed Ask PaddIQ question, a price-list or invoice review in Pricing and a half-entered Add stock in Inventory are also kept through a reload: reopen the pass and it offers “Unsaved changes kept from …” — Restore or Discard. If someone else signs in on that device instead, they are asked first and never see or send your changes.
The date scroller sits above the round buttons on a phone and steps through every clear satellite pass — drag it or tap a dot. It follows whichever layer is showing: the whole farm when nothing is selected, and that paddock's own dates once you tap one. Tapping a paddock keeps the map clear; the ℹ button below the scroller brings up that paddock's details and puts them away again.
On a phone the top bar is contextual (Ops-Center-style): tap a paddock and it becomes that paddock's layer picker — any pass, harvest map, or its latest NDVI (freshest image under 5% cloud, dated), newest first. A paddock opens on its most recent mapped pass (on a computer too); pick another, or “— pick a layer —” for none, and that paddock keeps your pick until you reload the page; yield layers add measure chips (Yield / Moisture / Protein / Starch / Oil / …) under the bar — Protein shows whenever the map's John Deere file has a protein column (HarvestLab names it “CrdPrPrcnt”; starch is “StrchPrcnt”), and a header with no protein sensor leaves its passes blank, never 0. Canola oil % gets an Oil chip too (John Deere names the column “OIL”); a canola map fetched before 6 November 2026 gets it when you fetch it again. A map fetched before 28 October 2026 gets its Protein and Starch chips when you fetch it again. The legend sits on the map's right edge, like Operations Center's: a small stepped colour bar, highest at the top (the end classes read “4.2+” and “< 1.9”, so a monitor-error cell never makes the top range read 4.2–188.9). Tap it for the full table — each colour's range, hectares and share — with the map's tools under it; tap its heading (▾, it stays at the top while the panel scrolls) to fold it back. “›” shrinks the legend to a small tab on the edge showing the measure, the map's average and unit (“‹ Yield 3.22 t/ha”); tap the tab to bring it back. This device remembers tab, bar or open. On a yield map the open legend carries “🛠 Yield map tools →”, which opens it in the layers studio (Planning → Imagery & VRT → Zones, on that paddock and layer), where grain-flow delay correction (each header’s monitor lag found from its opposite-direction passes and its readings moved back — on new fetches, or Fetch again; a best fit at the edge of what PaddIQ checks, −8 or +20 s, isn’t a reliable answer and isn’t applied, and the ends of each pass keep a value, never a blank; the header check and monitor-error count say whether they were worked out after or without it), the two-header check (compare, even out, match weighed tonnes, fetch again for exact seams), the pass check (each pass compared with the passes beside it and with itself 60 m further along — when passes differ more than the ground does it says why: travel direction, the headers, part-width passes or moisture; Even out the passes moves each one toward its neighbours, offered only when it is shown to work on ground it wasn't worked out on; the map's tonnes stay the same and Undo puts it back), monitor-error cleaning, the map’s statistics (average, median, spread, mapped hectares against the paddock, hectares in each of the map's colour classes — the same classes and colours as the picture) and a CSV export of every cell live; Equipment stays in the map's legend, and so does Smoothed — the picture averaged over about 1½ pass widths, like John Deere's contour map; it only changes the picture (statistics, zones and prescriptions use the logged cells) and is remembered on this device (also Settings → Maps). On Equal area colours no middle class is narrower than 5% of the paddock average. 🔎 Diagnose this map (under the statistics) lists every column of the map's John Deere file and says plainly whether it carried protein — “Protein found”, “The file has a protein column … but PaddIQ didn't save it” (⟳ Fetch this map again, at the same detail, saves it) or “No protein column in this file — John Deere's export for this operation didn't include it”; only then ⬆ Fetch at full detail (about 40–80 MB) checks John Deere's bigger per-sensor file, and a map that gets protein that way keeps fetching at full detail. A pass marked “(no map)” has no John Deere map on this device yet: “⬇ Fetch N missing maps from John Deere” in the picker (on a computer, the button beside Jobs) asks John Deere for that paddock’s maps there and then — maps for passes brought in through the John Deere wizard are not fetched by themselves. Picking a “(no map)” pass, or clicking it in the Jobs list, fetches it the same way. While maps are already coming in, picking a pass that still says “Fetching…” puts that map first: its paddock starts straight away, even when other paddocks are waiting, and that map is the next one downloaded and drawn. Its row says “fetching this one first…”, the paddock’s other maps follow, and the map shows by itself when it lands — unless you have picked something else meanwhile. It can’t make John Deere build the file any faster. John Deere builds each map file when asked (usually 1–5 minutes): PaddIQ keeps checking for up to 15 minutes while the app is open, on any page. The spinning line at the bottom says what it is doing — “John Deere map: W8 harvest map · John Deere building it · 2m 04s”, then asking for the file, downloading 1.2 of 3.4 MB, reading the file, drawing 3/8, saving — and on the Map page a “Maps · 2 coming in” message shows the same; Details lists each paddock: waiting for John Deere, downloading, drawing, ready ✓ or why it didn't come in. If nothing moves for 6 minutes, or the connection drops while the app is in the background, it asks John Deere again once by itself (“asked again”); if that stalls too it stops and says so, with Try again, on whatever page you are on. Switching to another app and back is fine — time away doesn't count, and a download the phone cut off is asked for again when you come back. When a map lands, “E2 harvest map ready — View” opens it (it goes after 15 seconds). If the app was closed mid-wait, the map offers “Fetch now” next time; it never restarts by itself. Every message like these stacks in one place — bottom right on a computer, bottom left above the tabs on a phone — newest on top, clear of the map's legend and buttons. Turn Soil sites on and the bar swaps to the analyte picker. ✕ returns to season + view.
🌾 Two headers on one yield map: when a harvest was cut by two (or more) headers, the yield layer's legend card says which reads higher and by how much — measured where their passes ran side by side, not from whole-paddock averages (two headers usually cut different ground). Even them out scales each header to the paddock's combined level with the map's total tonnes unchanged; Match weighed tonnes also sets the map's average to the paddock's correction tonnes (scales or docket weight) when its harvest record has them; Undo shows the map as logged. A gap over 30% is no longer refused: the Headers section (Zones → the yield map) checks it — side-by-side cells compared, one dry-mass yield column, one crop, side-by-side moisture — and says whether it is calibration; a correction saved before that, over 30%, is kept but turned off (“Apply it anyway” paints it). A machine name on under 2% of the map is a few stray readings, not a header: it is listed, never counted, and left as logged; one header logged under two spellings or by name in one file and VIN in another counts once. Equipment colours the map by which header cut each strip, like Operations Center. The logged readings are never changed, and the harvest record's yield is untouched — the correction affects the map and what is built from it (productivity, stability, zones, margin map). A map fetched before 20 Oct 2026 offers Fetch again to check headers first (the same John Deere download as before).
🗺 A yield map opens big (Planning → Imagery & VRT → Zones → a paddock → its yield map): on a computer the map fills the left of the window, the whole paddock in view, and the tools sit in their own column on the right — Legend, Layers (Yield, Moisture, Protein, Starch… and Equipment), Paddock tonnes, Corrections, Missing readings, Statistics, From John Deere — scrolling on their own. On a phone the map is on top and the tools open one section at a time underneath. Paddock tonnes: the map's total (average × mapped hectares) beside the weighed tonnes; type the weighed total and Save — it goes on the paddock's harvest records (the same Weighed / delivered tonnes box; two records split it by area), and Corrections → 5 Weighed tonnes makes the map's average match it. The weighed t/ha is the total ÷ the hectares HARVESTED on all the paddock's harvest records (shown under it); when those hectares and the map's mapped hectares are more than 25% apart it says so — check the harvest record's area — and (in Corrections → Weighed tonnes) lets you divide by the mapped hectares instead; with no area on any record it uses the mapped hectares and says so. A scale of more than 50% either way is refused (that is a wrong total or a wrong area, not the monitor); a scale saved before that rule is kept but not painted, with the reason. CORRECTIONS (since 28 October 2026): everything you can correct on the map, in the order it is applied — 1 Grain-flow delay → 2 Headers → 3 Passes → 4 Monitor errors → 5 Weighed tonnes (each row's numbers are worked on the map after the rows above it). Every row has the same shape: what PaddIQ found (tap “How PaddIQ found it” for the evidence), Off · Auto · Manual, and in Manual a slider with Auto's value marked ▲ under it. Moving a slider switches the row to Manual and shows the map and its Statistics with it a moment later (“Preview — not saved”); Save keeps it, Cancel forgets it, Undo puts back what the row had before. On a phone each row is one line with its verdict — tap to open. 1 Grain-flow delay: Auto finds each header's monitor lag from its opposite-direction passes (and applies it only when the best fit is clear and inside −8 to +20 s); Manual sets it in SECONDS, −8 to +30 s in half-seconds, with the metres it means at the map's speed beside it (“+6 s ≈ 11 m at 6.8 km/h”) — seconds because grain takes a fixed time from the cutter bar to the sensor. Each reading moves along its own pass, never across a pass end (the last seconds of a pass take the nearest shifted value). Under the slider the pass-end fit: a small curve of how well readings over the same ground on opposite-direction passes agree at every setting — the same score Auto decides on — with your setting, Auto's and the best fit marked, so you can see the best fit rather than eyeball it. A delay moves readings in time order, which only John Deere's file has (PaddIQ keeps the map's cells, not the timed readings), so changing it fetches the same files from John Deere again and the picture updates after; a hand setting is kept for every later fetch. 2 Headers, for two headers that disagree: Auto evens them where they ran side by side, the map's tonnes kept (with the weighed scale on as well, that is “Match weighed tonnes” — both facts used, neither header assumed right; past 30% Auto evens only then, or when the checks say it is calibration); Manual is Trust <header> (that header stays as logged and the other is scaled to it — for a header checked against a weighbridge recently; with weighed tonnes it says how far that lands from them) or each header's own slider. PaddIQ doesn't offer moving only one header to hit the weighed total: that loads all the error onto one header. Above the choices, the checks: how many cells were compared side by side, the yield column, the crop, and the headers' moisture side by side in percentage points (only cells where both logged a reading; a 0 is no reading). Dry yield is already moisture-corrected, so a moisture sensor d points out moves dry yield by only about d% — the check fails only when the moisture gap could explain a real part (a quarter or more) of the yield gap; otherwise it says the gap is the monitors' mass-flow calibration. A header that logged no moisture is named and not checked. Under them, coverage: how many hectares of cells hold a reading, how much the map fills between passes, and how much of the paddock has no data — a John Deere point export logs the cell under the header's GPS point, not the whole front, so most of the map is filled from the readings beside it (a header correction reaches those cells through the readings they were filled from); under 70% of the harvested area mapped, it lists what to check in Operations Center. The Equipment view colours every mapped cell by the header of the nearest readings, grey where no header reading reaches. One row per header, by your name for it (tap ✎ to rename it; a header John Deere logged only as a number — “Header 1” — is matched to John Deere's own per-machine averages on the harvest record and offered as “Looks like S790 — name it that” when the pairing is clear — a header that is a machine in Machinery is renamed there; a header John Deere gave just a number is named on that map only — John Deere may number headers per file, so “1” on another paddock can be another machine; any other header keeps the name on every map. A number named farm-wide before 28 Oct is still shown, marked “named on another map — check”), with its cells, hectares, average and tonnes; Only this header shows its cells alone — its readings and every cell filled from them, split the way the Equipment view splits the map, so the two headers' views together cover it (the rest greyed); move its slider (−50% to +50%, half-percent steps) or type a % and the map, the averages and the gap between the headers update before you Save. Each header's slider marks Auto's % ▲, so you can see it and fine-tune from it; Off shows the map without a header correction. While you fine-tune, ☐ Keep paddock tonnes (on unless you started from Trust) moves all headers by one more scale so the map's total doesn't change. Settings that put the headers more than 30% apart are allowed but flagged. Picking a choice applies it straight away — the line under the choices says what is on (each header's factor), and if a choice didn't save on the device it says so. Undo puts back the correction you had before. The picture paints every cell the map counts as mapped (within about 10 m of a reading) on every choice, so passes don't show white between them; the colour classes are worked again from each picture's own readings (equal area), so a header correction shows as the stripes evening out while a whole-map scale changes the legend's numbers, not the colours. On a computer the map's column is only as wide as the fitted paddock needs, so a tall paddock sits right beside the tools. 3 Passes: Auto is the pass check's own correction (offered only when it is shown to work on ground it wasn't worked out on); Manual applies 0–100% of each pass's worked-out factor, the map's tonnes kept. 4 Monitor errors: Auto takes out readings far from the rest of the map and readings unlike the cells round them — and, since 28 October 2026, readings unlike the ones either side of them ALONG their own pass, which is what catches dropouts on a 1-a-second John Deere file whose passes sit far apart in the cells (a run of three or more low readings together — a headland, a turn, poor ground — stays). A map cleaned before then keeps its old rule and says so, with “Use today's rule”. Manual moves the far-from-the-rest limit (2 to 8 robust standard deviations; Auto is 4) and shows how many readings it takes out as you drag. 5 Weighed tonnes: Auto scales the map so its average is the weighed t/ha (refused beyond ±50%); Manual scales every cell by your own %, −50 to +50. Back from Zone Studio's Correct this yield map, Back without changes puts every row back as it was. None of it changes the logged readings or the harvest record's yield.
Where the hectares come from (a yield map's Paddock tonnes): when the harvest records and the map are more than 25% apart in hectares, a card opens under the warning listing EVERY harvest record of the paddock for the season — its date, crop, the area as it is stored (an area of its own, or blank = the whole paddock — and the area the paddock had when the record was made, if that was very different), John Deere's own logged area, its weighed tonnes, and where it came from (the John Deere operation, and whether it is one this map was built from). Each is marked ✓ Counted with its hectares, or Not counted with why: a different crop on a map cut by crop, still planned, hay or straw, this map's operation filed under another paddock, or filed in the season either side. Operations the map is built from that have no harvest record are listed too, with the reason from this device's last John Deere sync (for example: taken for a pass already on file). One-tap fixes, each asking first and with Undo: Set its harvested area to the mapped hectares (only the record's harvested area changes — the area frozen when it was made, its cost and yield stay); Count this record (puts the map's crop on it); Move the weighed tonnes onto all records (split by area). The Harvested / Mapped choice is kept while the page is open, and a scale saved with Mapped keeps it. The harvest record sheet shows the same list, read only, with Open the yield map, when its paddock's records and map are that far apart.
🧪 Protein gaps — and canola Oil gaps — are estimated automatically: when one header logged protein (or oil) and the other didn't, or the sensor skipped passes, PaddIQ estimates the gaps the first time the map comes in or opens — from the passes beside them and the yield under them — and checks itself by hiding real passes first. If the check passes, the estimates show hatched; if not, the card says “estimates not reliable here” and why, and protein stays as logged. Undo on the protein card turns it off for that map for good. Raw (the map's legend, and the Farm Map's docked legend) shows only the cells with a reading — the gaps between passes and any missing protein left blank, so you can see the true coverage; Estimated brings the filled cells back. Averages and statistics are always the readings. Zone Studio's yield × protein analysis reads the protein map by itself, with the estimates (unless your maps are on Raw).
🎨 One colour scale on every map: yield, protein, starch, moisture, wet mass, speed, elevation, applied, target and prescription rates, zones, soil brightness and redness, radiometrics, productivity and soil-test values all run dark red (low) → yellow → dark green (high), in the same classes as the yield map (Settings → Maps: equal area by default, or smooth). Kept on their own colours: NDVI and other satellite imagery; the gross-margin map and the Farm Map's profit colours (white at break-even, red a loss, green a profit); Equipment (one colour per header); the yield × protein classes; crop colours; and status colours (seeded / not, tissue-test status).
🧪 A measure only one header logged (protein from a header with a protein sensor, beside one without): Yield map tools says so — “Protein logged by 1 of 2 headers — 48% of the harvested area has no reading” — and offers Fill the gaps. PaddIQ estimates each missing cell from the protein on the passes beside it and the yield logged under it (both headers log yield; the header correction and cleaning you chose are used), by regression kriging. Before drawing anything it checks itself: it hides up to 14 real protein passes one at a time, predicts them from the rest, and tells you the typical miss beside what the paddock average would miss (“Estimated passes checked by hiding 14 real ones: typical miss 0.3% protein (paddock average would miss by 0.8%)”). It only fills if it beats the paddock average clearly; cells more than two passes from any reading stay empty. Estimated passes are drawn lighter with white hatching — Measured only / Filled flips between them — and the Farm Map's Protein layer then says “includes estimated protein”. How this is worked out shows the method, the trend and every method's score. Undo shows protein as logged. The logged readings are never changed, and estimates never reach the harvest record's protein, the learning record, shared data or zones.
🎨 Map colours: yield, protein, moisture and as-applied rate maps are painted in seven solid colours — dark red (lowest) through a clear yellow (middle) to dark green (highest) — with a stepped legend that gives each colour's range, hectares and share of the mapped area, highest at the top. By default each colour covers about the same area (equal area, the usual yield-map split); Settings → Maps can split them in equal steps of value instead, or in fixed bands around the paddock average (within 5%, 5–15%, 15–25% and over 25% below or above — the same colour means the same % of average on every map), or switch back to the smooth red → yellow → green ramp. The choice is kept on that device; your maps and their numbers are unchanged either way — only the colouring. Yield layers in the zone studio follow the same choice. Satellite imagery keeps its own scale, and a stepped-rate map (a VRT with a few set rates) keeps one colour per rate.
Measure tool (📏): tap points on the map for running distance; three or more points also show the enclosed area in hectares. Right-click (or ↩ Undo) removes the last point.
Click any paddock for its details: crop, variety, area, season numbers, nutrients applied / planned (N, P, K, S; hover the heading for which products counted, and an amber line names any fertiliser that matched no analysis in your product library), this season's jobs with each John Deere map beside its record (a map whose file names no product is named from that day's record and says so), and the rotation history read from the seeding records of the last three seasons.
The ⋯ menu holds the Setup guide, boundary export (Shapefile / KML / GeoJSON — for an agronomist, contractor or another platform) and Clear all boundaries.

Tips & tricks

NDVI (Layers → Overlays) loads the latest satellite image for the whole farm on the high-contrast red → blue scale, stretched to 2–98% of the farm. Click a paddock and the layer clips to it and re-stretches to that paddock's own range so in-crop differences show; click more paddocks to add them to the set (a block reads on one scale), click one again to drop it (the legend reads the range and the paddocks; clear the selection for farm-wide). With NDVI off, clicking the selected paddock again deselects it. ‹ › step through earlier images. For the full imagery toolkit go to Planning → Imagery & VRT → Imagery.
Paddock areas update when you redraw a boundary, but existing Field Records keep the area they were created with — history doesn't rewrite itself.

🚜John Deere connection

Links your John Deere account so PaddIQ pulls boundaries and operations straight from Operations Center — no more USB or file exports.

How to use it

Import → John Deere → Connect John Deere. You sign in on John Deere's own page and approve access — PaddIQ never sees your password.
Click Enable access next to your organisation, tick it on John Deere's page, and you're connected. This is a one-time setup per device.
⟳ Sync John Deere is the one button that does the lot: refreshes farm data, imports new operations (clean ones silently; anything needing your call stages behind the Review banner), and downloads every map that is new, or unfinished on this device. The banner's ⟳ Sync — new and unfinished maps does the same without the farm-data refresh. The specialist buttons (Load farm data, wizard import, layer backfill, Redraw in HD) live under Advanced.
The wizard import (Advanced) opens EVERY new operation in the Reconciliation Wizard — product matching, rig costs and duplicate protection all apply.
On the Farm Map, ➕ Add paddock/boundary → Import from John Deere pulls all boundaries and auto-matches them to your paddocks; anything unmatched appears in the assign list for a manual match.
PaddIQ syncs with John Deere only when you tap Sync — nothing happens on its own when the app opens (since 28 Oct 2026; before that it synced itself up to twice a day). The banner on Import says how long ago this device last synced — "John Deere last synced 2 days ago" — with ⟳ Sync — new and unfinished maps, and the Farm Map shows the same note with Sync when it has been 12 hours or more. On a tap, new operations import by themselves when everything about them is certain; the banner shows what happened, with a Review button when some need your call. Review opens the wizard on just the flagged ops — 'Show everything' widens it to every new op from that sync. The sync only writes to your current paddocks: operations on fields John Deere still holds but that are archived in PaddIQ, or not in your paddock list at all (a block you no longer farm, a neighbour's job), are held back and counted on the banner. A paddock that was merged or reshaped still takes operations from seasons before the merge, under its own name — that is its history, and the merged paddock reads it. A field that IS one of your paddocks under another name in Operations Center (“Home 01” there, “01” here) is listed under the banner — “John Deere fields not matched to a paddock”, with how many passes wait: pick the paddock and press Match, and PaddIQ remembers it on every device and for your team, so every later sync (press ⟳ Sync now) brings its passes in on that paddock. A field the boundary import already linked to a paddock is matched by John Deere's field id on its own. Matched fields are listed with Unmatch; a match never moves passes already in Field Records. The wizard holds the same fields back, with the same Match to paddock list and an Include them button when the work was yours; a field not yet in your paddock list is added to it when its operations are imported, so they show in Field Records. On a brand-new farm with no paddocks yet, nothing is held back and nothing is imported on its own: the first sync sends every operation to the wizard, and the paddocks are listed as you import them. Undo on the banner takes back everything the last sync wrote on its own: records it added are deleted and plans it marked done go back to plans.
Maps download only when you tap Sync (⟳ Sync — new and unfinished maps on the banner, Sync on the Farm Map's note, or ⟳ Sync John Deere). That is on purpose: PaddIQ's licence with John Deere doesn't let it fetch from Operations Center on its own — no checking in the background, no fetching on a timer, nothing you didn't start. Opening a paddock or Zone Studio shows the maps already on this device or in your cloud; a map that is in neither says so, and a tap on it fetches it. On a Sync tap, PaddIQ looks at the operations list it has just read and asks John Deere for every yield, as-applied and seeding map this device doesn't have, and every one that is unfinished: a harvest that grew after its map came down (the header was still cutting), a job split over several operations where the map holds only some (a second header, a second day), a map that covers far less ground than John Deere logged for the job, and a fetch that failed or stalled. Maps are fetched three at a time; the pill at the bottom reads "Maps: 3 of 7 — W8 harvest map: downloading 12 of 40 MB", and a note says what came in at the end ("Maps: 4 new · 2 completed · 1 failed — Try again"). A map John Deere couldn't produce is not asked for again until John Deere changes that operation, and a map that is still short after John Deere's own hectares have been fetched once is left alone until John Deere's hectares grow. The setting on the John Deere card (this device only): When I tap Sync, also download new and unfinished maps — on by default — and Ask first when it's more than 10 maps or 300 MB (the size is an estimate; John Deere doesn't say until it sends the file), with Download / Skip this time. When this device's storage is nearly full PaddIQ says so instead of starting. Keep PaddIQ open until the maps are in: a web app can't download once it's closed. If the page is reloaded mid-way, the unfinished maps are listed on the Map page with Fetch now — they never restart on their own.
John Deere has more on this job: John Deere keeps a harvest (or a long spray or seeding job) as one operation and grows it as each run comes off the machine. A sync while the header is still cutting brings in what it has so far — 1.9 ha of a 130 ha paddock. The next tap of Sync compares every record John Deere wrote with the same operation now, and the wizard lists each one that has grown: "1.9 → 130.5 ha, 1.97 → 2.03 t/ha — Update", ticked. Update changes only John Deere's figures — the area, the monitor's yield, each product's rate, the day it finished, fuel and hours. A yield you typed or got from weighed tonnes, the tonnes, grade, protein and the record's own date are never touched, and neither is anything you changed by hand. Costs stay at the prices frozen when the record was made: the bigger job costs more at those prices, nothing is repriced. Undo puts the records back. A record imported within two hours of John Deere's last change to the job says "Job still running when imported — will update on Sync" on the yield map's Where the hectares come from card until a sync sees the job finished.
🚩 Mark a point (the round button column) — one button for flags and hazards alike. Drop a flag or note for yourself, mark rocks, rock piles and stumps, or mark what a pilot needs: powerlines and single-wire lines, poles, towers, houses, sheds, silos, treelines, fences, roads and stock routes, dams, watercourses, airstrips, loading sites, beehives, livestock, sensitive areas and no-spray buffer zones. Anything shown with ⚠ goes to the spray contractor in an export; the rest stay yours. “Something else” lets you name your own. A point takes one tap, a line several along it, an area several around it, then Done. Touch anything you have marked and it tells you what it is, the note you attached and the day you marked it; tap it to edit or remove it. The switch at the top of the picker hides everything on the map at once, “Drop where I am” puts a marker on your GPS position without tapping, and List shows everything you have marked — drag a row's grip to reorder it, tap it to edit, or remove it. Dragging a grip in the type list puts the ones you use most at the top, the swatch beside it changes that type's colour everywhere — map, printed page and legend — and the switch on the right turns that type off on the map without deleting anything. Point markers fly a flag whose pole base sits on the spot, so the flag never covers what it marks; an unconfirmed one flies a dashed flag. When you export a farm map you choose which kinds of marker go on it, so a spray contractor gets the hazards without your rock piles and flags. Give a height where you know it, and tick it off once you have confirmed it on the ground — the export says which ones are unconfirmed.
✈️ Export farm map (⋯ menu): tick the farms you want, pick a format, and it combines them into one map. The Shapefile bundle is what an aerial operator's guidance system wants — boundaries, hazard lines and hazard points as separate layers (a shapefile can only hold one shape type), plus a KML for Google Earth and a read-me. All in WGS84 lat/long. KML on its own is the easiest thing to send someone who just wants to look.
Map layers: Planning → Zones → Get John Deere layers pulls a paddock's yield and as-applied maps (fetched once, instant afterwards); Field Records → Map view shows them per paddock in season order.
One harvest, one map per crop: John Deere logs one operation per header (and per day), so a paddock cut by two headers is two files. Get John Deere layers — the farm-wide one on Import and the one on each paddock in Zones — joins every header and day of a season's harvest into one whole-paddock map ("20/11/25 · Yield (2 headers) — 2.2 t/ha"), and every seeding run into one seeding map. When the files show two crops on the paddock (canola beside wheat), the harvest is saved as one map per crop instead ("Yield · Canola" and "Yield · Wheat"); a crop under 2% of the points is a header clipping the next paddock and is left out. Older maps fetched one header at a time show "⚠ 1 of 2 parts" and a Merge button, and an older map that holds two crops shows "⚠ 2 crops in one map" and Split by crop: each fetches that season again from John Deere, and the old maps are hidden (never deleted) once the whole or one-crop map has saved. A yield map whose column is wet mass or grain volume says so ("⚠ wet mass, not dry"). Maps with two crops, wet mass or volume are left out of yield productivity, stability and the margin map, and the margin panel lists them. A layer opened on a device that does not have it (and has no cloud copy) is fetched the same way the sweep fetches it — every header's file, at your Yield detail setting.
The import wizard opens on ⚠ Needs input — the operations it cannot commit without a decision from you. The All pill shows everything including the ones that need nothing, and the other pills narrow to low confidence, fuzzy product names or date issues.
First season, in order: bring the operations in (the John Deere import is also what finds your machines), build your rigs from those machines, then run the import wizard once more. Records freeze their machinery cost on the day they are created, so passes imported before the rigs existed came in at no cost and only a re-run fixes them. Planning shows the Getting-started guide’s next step as one line above its plan strip until the farm is set up (an established farm — rigs and a season of 60+ passes — never sees it).
Suggestions come from PaddIQ's shared library: common chemicals, fertilisers and crop varieties. They appear as you type and the John Deere importer matches names against them, but nothing from that list enters your own library, prices or records until you pick it. Anything you add yourself stays yours, and is offered to PaddIQ as a candidate for the shared list — if enough farms add the same product, it becomes a suggestion for everyone.
A paddock showing no crop after an import: John Deere does not always name the crop on a seeding operation, and the app otherwise reads the crop from the variety — which needs that variety in your library. The paddock panel asks once, with the variety it was sown with; picking the crop sets the season AND adds the variety to your library, so every other paddock sown with it fills in by itself. Imports also teach the library whenever Deere does name the crop.
Hover any open map layer (a seeding, spray, spread or yield map) and the value under the cursor reads out — seed rate, applied rate, yield — in the layer's own unit, taken from the recorded data rather than sampled back out of the colours. Click to hold the reading, click again or pan to clear it.
Yield detail (Import → John Deere): Standard is the default — the same yield columns at one reading per second, about 5 MB a paddock. Full detail keeps every sensor reading (40–80 MB a paddock, 1.5–2.5 GB a farm-year) and is worth it only for fine zone work. A first fetch on a big farm takes a while either way; the progress line shows layers done, MB pulled and elapsed time, and the run survives moving between pages.

Tips & tricks

The connection lives on the device you connected — connect once per computer/phone you use.
Long fetches show a progress bar with a per-paddock roll call (D1 8/8 ✓ …) and a small spinner pill bottom-right — you can keep using the app while it runs; the pill means it's still working.
Re-running either import is safe: unchanged boundaries are skipped and the wizard recognises operations it has already written.
Boundary imports update paddock areas (with a confirm step) — past seasons keep the areas their records were created with.

🗂Import — Bring in old records

One place to fill in your history from wherever it lives: your own spreadsheets in any layout (sprays, seeding, fertiliser, harvest yields, crop history), another program's CSV export (Agworld, AgLogic, FieldView and the like), or a CBH / LoadNet delivery sheet. PaddIQ works out what each file is, shows every record as it will be stored, and writes nothing until you press Bring in. A whole import can be undone. Files are read on your phone or computer — nothing is sent anywhere.

How to use it

Import → Bring in old records → Choose files (or drop them on the box). Excel (.xlsx, .xls) and CSV. You can pick several at once; every sheet of a workbook is read.
Each sheet gets a line saying what it looks like — "Looks like spray records for 2021 — 46 rows, 12 paddocks". If that's wrong, change "This sheet is" (passes, seeding, harvest results, grain deliveries, crop history) or leave the sheet out.
Columns: every column of the sheet and what PaddIQ took it to be — sure (the heading is a name it knows), likely, or check this (worked out from what's in the column). Change any of them; pick "skip this column" for one you don't want. Titles above the table, one product per row, or Product 1 / Rate 1 / Product 2 across the row all work.
Before you bring them in: paddock names PaddIQ couldn't place ("Hom 04 — did you mean Home 04?") — pick the paddock or leave those rows out; products that aren't in your library — kept under the file's name unless you pick one of yours (nothing is added to your library or Pricing); and, for rows with no date, which season they belong to.
The list: every record by season, as it will be saved. Tap one to see it beside the row in your file. Chips say what needs a look: already on file (the same paddock, a day either side, the same products and rates — left out unless you tick it), fills the harvest record, no cost in file, archived paddock.
Press Bring in N records. They show in Field Records with "Added by you (Old records: the file's name)". Past imports lists every file brought in this way, with Undo.

Tips & tricks

Costs: a price in the file (a $/L or $/kg column, a $/ha or a $ total) is kept on each product at that time. No price in the file → the record says "no cost in file" and keeps $0 — never today's price. Old records don't say which of your machines did the job, so these passes read "No machinery cost recorded" (not "no cost source") and Machinery → Needs attention leaves them out; open one and pick a rig if you want machinery in that season's margin. A machinery or contractor $/ha column in the file is kept as the pass's machinery cost.
Spray diary: an imported spray carries only what the file wrote — start and finish times, wind, direction, temperature, humidity, nozzle, operator. Nothing is filled in from a weather model, and a row with no date is saved as "date unknown" rather than given a made-up one.
Season: a season or year column wins; otherwise the date's year — except a harvest dated January or February, which belongs to the season before. A season you didn't have yet is added to the season picker.
Harvest results and CBH sheets fill the BLANK figures on a harvest record already on file (yield, protein, grade, moisture, screenings, site, delivered tonnes); figures already there are kept and listed, unless you switch on "use the file's". A paddock with no harvest record gets one.
CBH / LoadNet (one row per truck): each paddock's loads are added up — delivered tonnes (kept as docket tonnes, the check on your header), protein, moisture and screenings weighted by each load's tonnes, and the grade that carried the most tonnes (every grade's tonnes kept). That delivered protein is what Zone Studio's protein check reads. Loads with no paddock on them wait for you to pick the paddock or leave them out.
Crop history (a paddock column and one column per year): fills the crop for paddock-seasons that have none; a crop already set is kept and shown.
Undo this import (red, under Past imports): removes the records it added, puts harvest figures back to what they were and clears crop history it set. Anything edited since the import is kept as it is now. Your account's change history keeps a copy either way.
Not read here yet: photos and PDFs of paper records (coming next), and yield or as-applied maps from other programs. Boundaries (shapefile, GeoJSON, KML) go on the Farm Map → Add paddock/boundary. A paddock in the file that isn't in PaddIQ isn't created — add it in Farm Setup first, or pick the paddock it is.

📥Import — Manual / PDF files and John Deere

Turns Operations Center exports (PDF field reports or Excel/CSV) into Field Records. Four file types: Seeding, Applications, Harvest, Tillage. The Harvest tab also takes ANY results spreadsheet (your own yield/protein/grade sheet, a CBH download): Import a results sheet shows every column and row for checking — which paddock each row matched, the yield it will use (a t/ha column, else correction tonnes ÷ area, else total ÷ area) — then loads protein, grade, moisture, oil, screenings and hay onto the paddocks; yields already on file are kept unless you tick Replace. Correction tonnes are weighed tonnes — scales or docket weight — and are kept on each paddock's harvest record along with where they came from, because they are the only figure that can check the header: its yield map and the John Deere yield are both the same monitor. A column called just "net weight" is kept but not labelled scales or docket; header tonnes are never treated as correction tonnes. Protein, grade and moisture now reach the recommender even on a paddock with no yield recorded yet. Correction tonnes (on the Harvest tab, under the total): enter each crop's season weighed tonnes — scales or docket — for when loads were not split by paddock, and PaddIQ sets it against what the paddock records add up to. It says whether that is a clean header check (every paddock's yield came from the monitor), only indicative (a mix), or no check at all (the paddock yields were already worked out from weighed tonnes). Within 5% is green, 5–15% amber, beyond that red. The gap is shown, never applied. Headers against each other (just below it): where two headers cut the same crop in one paddock, John Deere keeps each one’s own average. One paddock can’t separate calibration from which end each header cut, but across many paddocks the ground averages out and calibration doesn’t — so each pair gets a 95% range from its shared paddocks and a verdict: together (under 7% either way), worth checking, calibration difference, or can’t tell yet. It says the headers disagree, never which is right — only correction tonnes do that. For seasons imported before this, re-run Import → John Deere: it adds each header’s figure to the harvests already on file without changing any yield. If you've connected your John Deere account, the John Deere tab imports the same data with no files at all.

How to use it

🌾 Harvest tab → Harvest records: every harvested (and still to harvest) paddock of the season, one row each — one row per crop on a paddock sown to two crops, and one row for a paddock two headers cut. Each row is that paddock's harvest record: date (⚠ when it's after today; “JD 26 Oct · Use it” when John Deere logged it on another day), t/ha, hectares harvested, weighed / delivered tonnes, the yield map's t/ha (⚖ when the map is matched to the weighed tonnes), protein, moisture, screenings, oil (canola), grade (the grades you've priced in Pricing), receival site, hay and straw tonnes (onto the harvest record, priced from Pricing — crop Hay), income $/ha and margin $/ha (hover for where each came from; “set price” when the grade or crop has no price). On a computer a box saves when you leave it, and Enter or Tab goes to the next paddock's same box (Shift goes back). On a phone each paddock is a card — tap it for the same boxes. Edits go onto the harvest record itself (the one Field Records opens), with your name as the editor; on a paddock with two headers, the facts go on both records and weighed tonnes are shared by area. A paddock with no harvest record yet gets one on the first box you fill, dated mid-November or today, whichever is earlier, until you set the date. Under the table: tonnes, t/ha, protein and income per crop — the same totals as the headline at the top. Tonnes are each paddock's weighed tonnes where you have them, else its t/ha × its harvested hectares — the same tonnes Financials and the harvest record price (since 28 October 2026). Income $/ha and margin $/ha are over the paddock's hectares, the area its season's costs are over. The 📊 Excel button exports this table as it stands: one row per paddock per crop with every column above, tonnes and their basis (“55.8 t weighed”, “2.02 t/ha × 27.61 ha harvested”), income, costs and margin in $ and $/ha with how each was worked out, and a By crop sheet of the totals. Hay comes from the Hay box. The yield map's t/ha is not in the export (it is read from each map as the table paints).
The John Deere wizard always writes to the season the data was fetched for, shown in its title — never to whatever another open window has selected. If they differ it says so at the top. And no operation dated two or more years from the season can be written into it at all: it’s refused with a note, and nothing for that paddock is written.
What type a pass comes in as — the same rule in the John Deere wizard, the background sync and PDF Quick Import: a pass with ANY chemical in the tank (herbicide, fungicide, insecticide or adjuvant) is a Spray — on the spray rig and in the spray diary — even with Flexi N, UAN or 32-0-0 in it; the fert's nutrients still count from its products. A pass of liquid N alone stays a fert pass (costed on the boom, as liquid fert always is). A product counts as a chemical when the chem library or your own list says so, or its name does ("Prosaro", "fungicide"); a product an import once filed under Fertilisers in Pricing does not overrule its name. A type you picked before for the same John Deere work name still holds for topdress or spread, but never turns a pass with a chemical into a fert pass, and is never DTT: fert down the tube is decided by the seeding pass itself — within 2 days of it, on the seeding machine — never remembered from a work name, so a Flexi N topdress weeks after seeding never comes in as DTT on the seeding pass — change that pass's type on its card if you need to. Passes imported before 13 Oct keep their type: Settings → Data Health lists fert passes with a chemical in them.
In the John Deere wizard, picking an operation type on an undecided card fills in every other undecided card in the same run with the same John Deere work name — pick Spray once for "Post emerg broadleaf" and the rest follow. Cards already sorted, or set by hand, are never changed. Paddocks you have already confirmed stay as written; later paddocks arrive filled in. The choice is also remembered for future imports.
How the import picks each pass's cost source, first that fits: the rig you picked before for that machine (and that work type), John Deere's work type naming one rig's implement ("Tillage: Ripper"), the rig holding the machine John Deere recorded ("2M 8270R" sits in one spray rig → that rig), a pick an older import remembered, the only rig for the job, a rig whose name looks like the machine — and only then the job's default fleet. Liquid fertiliser (every product in L/ha) is a spraying job: it goes to the spray rigs and fleets, never the spreader. Every wizard card says why under its cost source; a default-fleet pick is amber — a guess (the machine sits in no rig, or in two). The background sync still writes those guesses so no hectares go missing, and flags them: the sync banner counts them, Field Records shows "· guess" on the chip (and a "Default fleet — a guess" filter), and Machinery → Rigs → Needs attention lists them with "Put N on a rig". Pick a source yourself and the other cards in the run with the same machine and job take it (cards you set by hand are left alone); the next import remembers it for that machine — keyed on the machine, so a change in Deere's implement list doesn't lose it. Only your own picks are remembered — a pick the import made by itself never is. The cost source list also offers manual-rate fleets and Pricing → Contractor rates (the contractor bills it, machinery $0). Fert down the tube that rides on the paddock's seeding pass says so and shows no $/ha — it saves at $0. A PDF Quick Import picks the rig the same way from the report's machine name.
One pass per John Deere operation. Deere records one operation per machine, and each becomes its own Field Record with its own hectares, machine and operator — two sprayers on one paddock with the same mix on the same day are two passes, and a paddock cut by two headers gets one harvest record per header (the larger header's record also lists every header's yield for the header comparison). The import knows a pass it already has by Deere's own operation id; passes imported before this change are matched the old way. A pass of the same shape on file only counts as "already imported" within a couple of days of it (three for seeding), so a second Urea topdress or a re-sow weeks later comes in as its own pass. Operations older imports skipped because they looked like a pass already on file are never written on their own: the sync holds them (its banner says "may be a second pass") and the wizard shows each one parked with an amber note naming the pass on file — choose Bring in, Later, or Skip if it is the same pass. A harvest by a different header than the one on file is not a question: it is another header on the same harvest, brought in as its own record ("Another header on this paddock's harvest — S760, 86 ha"); only the same header over about the same area and time is held. A pass John Deere logged twice — same day, same products, area within 3%, one side a machine with no name such as "Tractor" — reads "Likely the same pass recorded twice" with Skip already picked, and "Skip all" answers every one on the paddock or in the run; nothing is skipped until you confirm the paddock. The same goes for an operation with the same products at the same rates as a pass already on the paddock within a day — whether that pass was typed in, came from a PDF report or an older import under another type: it reads "Already on file — Skip suggested" (Approve all skips it, keeping the one on file), or, when John Deere names a different machine for each, "your call" and it waits for you. Harvest passes carry John Deere's own date (a Deere file has none: mid-November, never later than today), and the Date issues filter lists any pass dated after today. A harvest pass is costed when it is saved by your default Harvest fleet (else your harvest crew) — each header's record on its own hectares; the card says which and at what $/ha. On a phone each operation is one line (type, date, hectares, machine, how sure) with its answer already picked — tap it for products and cost source; notices are one line until tapped; Back and Confirm paddock stay at the bottom, above the tab bar, and the Ask PaddIQ button moves up out of their way. The ticked answer on a card is only your choice — nothing is written until you tap Confirm paddock. Clean → next issue sits with Approve all in the page. Nothing on file is changed by this, and duplicate checks never call two different John Deere operations copies of each other.
Drop each file on its card. PDFs and spreadsheets both work — the card shows what it found (paddocks, applications, yields).
Choose your path: the Reconciliation Wizard walks paddock-by-paddock and lets you match passes to plans, pick cost sources (rig, fleet or contractor rate) and fix product matching. Quick Import (PDF reports) writes everything in one go. Spreadsheets always go through the wizard — the old "(v28 legacy)" Import button is gone; it wrote seeding, spray and tillage where nothing in PaddIQ reads them.
In the wizard, unmatched products import under their JD name and are added to Pricing at $0 — nothing is ever dropped. Use “+ Add as new product” or map them to library products you already have.
Seed varieties register themselves in your library and appear in Pricing → Seed Prices automatically.
PaddIQ's library: every variety picker has a 'From PaddIQ's library' group and the product picker's search shows 'PaddIQ library' rows — the master set an admin keeps. Pick one and it joins your own list that instant; until you pick it, nothing is written to your farm. Anything you add yourself goes to a separate queue the admin sees with a count of how many accounts entered the same name, and can promote to the master set.
Re-importing the same file is safe: existing records are recognised and skipped. A PDF report's Quick Import replaces only what an earlier import of that same report wrote, on the paddocks in the file, for the kinds of pass in the file. A pass already in from John Deere (the sync or the wizard) is never deleted — the PDF's copy of it is skipped and listed under Parser Notes, and the next sync skips a pass a PDF already brought in. Two copies count as one pass when they are on the same paddock, the same kind of pass, within 2 days (seeding 3) and, for a spray or fert pass, share a product — and one pass on file stands for ONE pass in the file (the one on the same machine first): a second spray of the same mix the next day is written, or for the sync held for Review, never hidden by the first. Fert that John Deere already put on the seeding pass (fert down the tube, recorded with the seeding) is not written a second time: Parser Notes lists it as “already on the seeding pass”. The machine the report names under Equipment is read in full ("Tractor A 400R", not "Tractor").

Tips & tricks

Fert applied the same day as seeding (MAP down the tube) bundles into the seeding record — one pass, one machinery cost. When it comes in as its own DTT pass (the seeding was imported earlier), it is written at $0 machinery and linked to the seeding pass it went down with — the same rig, the same fleet, a rig in that fleet, or the same John Deere machine — so the seeder is never charged twice, whether the seeding was costed to a rig or a fleet. Only fert on the SEEDING machine counts: John Deere names the machine on every operation, and fert on the seeding tractor (the tractor alone, or with its bar) in the seeding window is down the tube, while Flexi N the sprayer put on the same paddock the same days stays a sprayer pass on the spray rig. An operation is never taken for a pass on file that names a different machine — older imports did that, and filed the seeder's Flexi N under the sprayer; such an operation now waits in Import → John Deere → Review instead of being hidden, and Machinery → Rigs → Needs attention lists the ones already on file.
Each card has Delete imported — removes every record that file type brought in for the season (manual records untouched). Cleanest way to start a season over.
Machine costs are snapshotted at import, and a pass keeps that $/ha. Passes that came in at $0 machinery (a rig with no costs yet) are listed in Machinery → Rigs → Needs attention under “$0 machinery”: “Cost these” shows each pass's $ before and after, costs the ones you leave ticked at their rig's or fleet's rate today, keeps the old figure on each pass and can be undone. Don't delete and re-import to re-cost — that loses operators, spray conditions, notes and plan links.
Paddocks in the file that don't exist yet are created automatically under the right farm.
Import has seven tabs: Bring in old records (where Import opens), Manual / PDF, John Deere, Harvest, Tissue Tests, Farm Setup and Backup & Restore. On a phone they sit in rows of three, all in view (Bring in old records reads Old records, Backup & Restore reads Backup); the open one is green. A small dot on John Deere means it is not connected on this device yet — connect it and the dot goes.
Delete season data sits closed at the bottom of the Manual / PDF tab. Open it for per-season buttons: planned only, all records, or everything (records, prices, targets, rainfall) from this device and the cloud. Every button confirms, and Delete everything makes you type the year.

📋Field Records

The single source of truth: every seeding, spray, fert pass and harvest on every paddock, with a cost per hectare frozen onto each record.

How to use it

Who added and who changed each pass: every pass added or changed from 27 Oct 2026 carries the account that did it — signed in, never typed — as a line under the pass: “Added by Jo · yesterday”, “Imported from John Deere by Jo · 2h ago”, “Edited by Sam · 5 min ago” (the exact time and email when you hover). A spray pass reads “Entered by”: that is who put it in PaddIQ; the Operator on the pass is still who did the job, as typed, and is never filled from the account. Open a pass for its History (tap to unfold): each change newest first — who, when and what (“area 40 → 38 · products”) — then how it was added. A name is the team member's name in Settings → Team, else the part of the email before the @. Passes from before then show no line and their History reads “Added before tracking” — nothing is filled in after the fact. A change PaddIQ makes by itself — a repair or sync (a John Deere area repair, the weather fill, a background John Deere import matching a plan), or the Fert Plan keeping its passes in step when you open it (a planned seed rate put right, a pre-seed pass moved to the seeding date, DTT folded onto the seeding pass) — is listed in History as “PaddIQ”, marked automatic, and does not change the “Edited by” line: opening a page never makes you the editor of a pass. A planned seeding pass the Fert Plan adds by itself reads “Added by PaddIQ”. Changing a product, rate or line on the Fert Plan is your edit and names you. The same line shows on the Fert Plan's product lines (the pass the line is on), Inventory stock moves and maintenance logs, machine maintenance records and daily checks. The spray diary PDF is unchanged — “Entered by” is on screen only.
A seeding pass that sowed several varieties keeps each one at its own rate and area — the card shows every variety, and seed is costed variety by variety at its own price. On the record, “+ another variety” adds a row. Passes imported before September 2026 came in as one joined name at an averaged rate; they show split into their varieties with the average rate and a note, until you type the real rates or re-run Import → John Deere for that season — the import now adds each variety’s own rate and area, and each header’s yield, to records already on file, without creating or duplicating anything. The background sync does the same for the current season.
A pass's row in the list is one line: date · type · products and rates · the part of the paddock it covered (“31.4 of 32 ha”, only when partial) · what pays for it · $/ha and $ total (since 28 October 2026 — Liam: “all quite cluttered”). A plan adds PLANNED (or OVERDUE, ⚠ stale) and its ✓ actual / ✕ buttons; a pass made from a plan carries one 📋 (click it to put the pass back to planned, when that is allowed); a seeding pass with fert bundled in says “+ fert”. The only compliance chip on a row is a problem: “⚠ plantback …” when a herbicide on that pass is short of its plantback for the crop the paddock is planned or sown to (the paddock's plantback pill's own check), and “⚠ WHP not clear” on a harvest dated inside a product's withholding period. Everything else — the withholding and grazing pills below, the N P K S the pass puts on, whether John Deere matched it to a plan, the bundled fert and the area — is in the opened pass, at the top, under Withholding · Plantback · Nutrients · Plan · Area. Nothing was removed; it moved.
An opened pass shows what it puts on as N P K S pills (kg/ha from its products at the recorded rates — the same conversion the nutrient balance uses); the paddock card’s pills are the season’s total against the plan. Withholding periods: every opened spray and fert record shows a pill read from the APVMA label of each product — “WHP harvest 14 d · clear 26 Sep” (counted in your own calendar days; until October 2026 the clear date showed a day early in WA), and grazing where the label gives one — for the paddock’s crop, from the record’s date. Tap it for the label’s own words. A harvest record shows whether the paddock was clear on the day, or which product still had days to run; the Harvest tab shows the same on each paddock. Tap any pill for the label’s own words, the clear date and a link to the label on the APVMA register. Settings → Label markers turns the pills off. Every clear reads “clear · check products” on purpose: it is read from the products and dates as recorded, so a wrong entry makes it wrong — it is a prompt to check the label, not a certification. A product with no APVMA link, or a label wording that could not be read for that crop, shows “WHP: check label” — the app never invents a number. Pricing → Chemicals lists at the top any product not linked to an APVMA registration, and any linked provisionally (~): open one and Confirm keeps the match; “No APVMA registration” marks a name that is not on the register — an unregistered adjuvant, say — so it stops asking you to check a label that does not exist. Link products there (most link on their own: by name, by product family, or for generics like “Glyphosate 450” to a registered product carrying that active at that strength — those show a ~ on the pill until you confirm them; “label ↗” opens the product’s page and labels on the APVMA register). Under each chemical, Alternatives lists the other brands of the same thing you use — Hyperspray under Hasten, Genfarm Imazapic and Implode under Imazapic — each with its own APVMA link; an import that meets one of those names writes YOUR product on the record and remembers the brand, so the season’s totals stay in one line and the label read is the brand’s own. “Same actives, on this farm” suggests candidates, and the import wizard fills the list itself: map “Implode” to Imazapic once and Implode is added under it, with its own registration looked up. Want brands kept separate? Add them as products and list nothing. Fertilisers and ameliorants have the same list (Genfarm urea under Urea) with “same analysis” suggestions instead — they are not APVMA-registered, so no label link. Source: APVMA PubCRIS (data.gov.au), CC BY 3.0 AU; the registered label is the legal document.
Plantback on a fallow (or pasture) paddock is judged against NEXT season's planned crop at next season's sowing date — the crop the residue can hurt. The pill names it ('plantback clear for 2027 Wheat'). With no crop planned yet it reads 'plan 2027 crop' instead of hiding.
Plantback in a season being planned is judged as of its seeding date (the paddock's planned seeding record, else your usual seeding date) with rain after today at the long-run normal — the pill reads “clear by 15 May est.” or how much is still short by then; re-check as the season comes in. Plantback: each paddock card and the paddock sheet on Planning → Overview check every herbicide applied in the last 24 months against the plantback table for the crop the paddock is planned or sown to — “plantback Imazapic: 3 mo or 25 mm” until the label allows it, or “plantback clear”. Months and rain are what is STILL needed: the label’s requirement minus the time and the gauge rain since the pass. The check is on the conventional rule; where the label exempts a tolerant type (Clearfield, TT …) the line says “a CL variety may be exempt — check variety and crop type” rather than deciding for you. Where the table writes the rule only for a named type (TT canola, say) that rule judges, and the line says “(TT rule)”.
A record’s rig & cost picker always shows what is actually costing it. A harvest costed by the older Harvest Fleet setup shows as “Harvest Fleet (auto) · $/ha (as recorded)” rather than “Pick a rig or fleet”. That $/ha was frozen when the record was made and isn’t changed unless you pick something else. Once that setup has been copied into your “Harvest crew” fleet, new harvest passes are costed from a fleet by name — your default Harvest fleet in Machinery → Rigs & fleets, else the copy.
Each paddock card shows N, P and K on its front: kg/ha applied so far over kg/ha planned, e.g. N 53/63. Green means that nutrient's plan is met, amber means it's short, grey means none is planned and only the applied figure shows. Both numbers come from the same sum over your actual and planned records, scaled for part-paddock passes — hover for the detail. A figure that looks about double what you put on is worth checking for a pass recorded twice.
Zone map on a planned pass: under Rig & Cost in the pass editor, 🗺 Zone map lists this paddock's zone maps — Attach a zone map opens the same picker as the row's 🗺 chip (which map, each zone's %, which product varies) and the link is saved with the pass; Remove goes back to a flat rate. A paddock with no zone map yet says so with ＋ Build a zone map, which opens Planning → Imagery & VRT → Zone studio on that paddock (it asks first if the pass has unsaved changes) — build the map there, then come back and attach it. Add the product first, so the map knows what it varies. Maps are named with their paddock — “Home 20 · Lime map”. Once a map is attached, tap its name (or the row's 🗺 chip) for the map sheet: a picture of the zones, each zone's hectares, % and rate, and what the pass puts out on the map — each product's total in tonnes or litres, its average rate, its cost and $/ha, and the difference from the flat rate (hover a line for the sum). Change a %, press Save zone rates, and the totals under 🗺 Zone map in the editor follow. They are worked out on the pass's treated area (or its paddock hectares) and shown only: the pass's budget and buy list still count its flat rate, and done passes keep their frozen costs.
Two views — ☰ List (the classic per-paddock timeline) and 🗺 Map: click a paddock on the map for its season's operations in date order; entries with a John Deere layer show the key metric (t/ha, kg or L applied) and paint it on the map when clicked.
Under each pass's cost a summary line says how its $/ha is made up: “inputs $31.00 · machinery $8.40 · seed $30.00 = $69.40/ha · $6,940 over 100 ha” — inputs at this season's Pricing prices, the machinery $/ha frozen when the pass was saved, the contractor's rate and seed where there is any (a $0 for inputs or machinery is shown on purpose: nothing is priced, or nothing costs it). The same breakdown sits at the foot of the pass editor, and a pass that costs nothing shows no line. Open the pass for each product's own $/ha.
A “from card <name>” chip shows only on a PLANNED pass a Cropping Card wrote: re-applying the card (Planning → Programs) updates that pass; deleting it here removes it, and re-applying the card would add it again. Once a pass is marked done the chip goes — the card no longer owns it, and it is never rewritten or removed by a re-apply (the card still knows that block is done).
Expand a paddock to see its season timeline. Each row: date, type, products + rates, status (planned/actual) and $/ha. On the phone each row is the products on their own line with the date, status and area under it and the cost at the right; tapping a row opens the editor in a bottom sheet (swipe down or Cancel to close), and + Add record opens the same sheet. + Add plan / activity under each paddock is the one way to add a pass by hand: pick the operation (the same list as a cropping card — seeding, spray, DTT, topdress, pre-seed spread, ameliorant, tillage, harvest), then the full editor opens; A spray block on a card and a spray record both carry a water rate (L/ha); a mix picked into either brings its own timing and water. “Add tank mix” in any record's products puts a saved mix's lines on the pass (scoped to the paddock's crop, same sheet as the cards); a plan starts on the farm's USUAL date for that job — the median of your own past passes of that type (a spray's products pick its slot: glyphosate + Garlon finds your summer sprays, MCPA your June broadleaf pass; a December summer spray filed under the next season counts as the December before it) — shown as “suggest 14 Jan” beside the date, one tap to take it; its Status select makes it a plan or a done pass — and back again; every status change is stamped on the record (when, plan → done, who), shown beside the Status select. An imported pass with the same products at the same rates as another pass on the paddock within a day carries “Possible duplicate of the 10 Jun pass on file”, naming that pass, its cost source and where it came from; a banner at the top counts them and opens those paddocks. “Remove this copy” deletes only the imported copy, after you confirm — the pass on file stays, and John Deere won't bring the copy back on the next sync. A pass you typed is never called the copy. A spray record's More details holds the diary fields, all optional: start/finish, wind speed and direction, temperature, humidity (Delta T is worked out from those, with the 2–8 ideal band), nozzle, pressure, spray quality, and a batch number per product (a planning season starts planned, this season starts done), and a plan becomes actual the same way later.
🌾 The harvest record: every box keeps its label once filled (Protein %, Oil %, Screenings %, Moisture %, Grade, Receival site, Seed kept). Grade offers the grades you have priced in Pricing for that crop; any grade can still be typed. Weighed / delivered tonnes is the paddock's true figure — scales, weighbridge or dockets — and is the same correction tonnes the Harvest tab's sheet import writes (two headers on one paddock share it by area). Beside it: what the yield box says (t/ha × hectares harvested) and, when the paddock has a yield map, “Map says 2.10 t/ha · 58.0 t over 27.6 mapped ha”. If the map and the weighed tonnes differ, Scale the map to this sets the map's average to the weighed tonnes ÷ hectares — a two-header map is evened first — and zones, stability, the margin map and Rx then read the scaled map; the logged readings are kept and Undo is in Yield map tools (Matched to weighed tonnes). Type a yield yourself and the record offers “Use 2.02 t/ha × 27.61 ha = 55.8 t as weighed”; type weighed tonnes and it offers to set the yield to weighed ÷ hectares — neither happens unless you tap it, and the header's own yield is never offered as weighed (that would check the monitor against itself). Under it: the paddock's Margin $/ha and $ (income − its season's costs: seed, fert, chem, machinery, contractor, levy & freight; before overheads; the same figure as Financials), income and costs with where each came from — “AGP1 at $340/t from Pricing”, “no grade — Wheat's top price”, or “ASW1 has no price in Pricing” with a button to set it. A grade or yield you've changed shows its money straight away, marked “with your changes — Save to keep them”. No grain price at all says so — never $0 income. Each harvest card in the list shows the same margin and income per hectare on one line.
📅 Dates: a done pass dated after today says “Date is in the future — check it” (nothing is changed). A pass John Deere logged is dated by John Deere's operation — its start, and for a job over several days the end shown beside it (“→ 28 Oct”) — never by the plan it was matched to. Records already on file are not redated: when the record's date differs from John Deere's, the record and its card say “John Deere logged this on 26 Oct” with Use it. John Deere's day comes from the record (the next John Deere sync stores it on harvest records already on file), else from the yield map built from that operation; with neither, the record says only that it is linked to the operation.
+ Add record → pick a type, date, products (from your library, with an add-new option), rig/fleet for the cost, operator and notes.
Paddock total (under an open paddock's passes): three figures, each $/ha with its $ total — Costs (seed · fert · chem · machinery · contractor · levy & freight underneath), Income (its tonnes and price: “56 t (2.02 t/ha × 27.61 ha harvested) × $400/t”, or weighed tonnes) and Margin, before overheads. They are the paddock's Financials figures — the same margin the harvest record shows — all per paddock hectare. Not harvested yet: income and margin say “projected (target yield × price)”. No grain price: it says so, with the link to Pricing, and no margin is shown. Fallow shows its costs as the margin. Hover any figure for how it was worked out; the costs tip also says what the passes above add up to (Financials adds contractor jobs and levy & freight, and counts a plan only while the season is open). On a phone the three stack.
🌿 Hay and straw live on the harvest record. Pick Grain + hay, Hay only, Straw bales or Grain + straw on the record and type the paddock's tonnes — or the bales and the kg per bale (tonnes win when both are there). The Harvest tab's Hay t and Straw t boxes write onto the same record (a paddock with no harvest record gets one). They are priced from Pricing → Grain Prices, crop Hay: straw from a grade with "straw" in it (Wheat Straw on a wheat paddock first), hay from the others (Oaten Hay on oats first); no price says so with the link — never $0. Income = grain + hay + straw, the same in Financials, the record's money box, the Records Paddock total and the Harvest table, whether or not the season was imported. Under the margin: the margin by product — grain margin (the crop's season costs), hay margin and straw margin (costs that exist only because of them: a Hay only / Straw bales record's machinery and contractor, a contractor job under Hay & Silage or named baling / hay cartage, or any pass set to “Cost is for: hay / straw” on its record). A paddock cut for hay has no grain, so the hay carries the crop's costs. The parts add up to the paddock margin. “Straw removes nutrients — not counted in this margin”: baled straw and hay carry nutrients off — potassium most — and that cost isn't priced yet. Hay typed on the Harvest tab before 28 Oct was copied onto each paddock's harvest record once; a paddock with no record keeps its old figure counted until you type it again. Where the record already held a different hay figure, Settings → Data Health lists both with “use the record's” / “use the Harvest tab's” — the old figure is never deleted. Hay OR straw: hay is the crop cut green instead of harvested for grain and straw is baled after the grain comes off, so one crop's season has one or the other (Grain + hay — part cut for hay, the rest harvested — is fine). Typing straw where the paddock has hay (or the other way) asks “replace it?” on the Harvest table, its phone sheet and the record; a sheet import never replaces. A paddock that already had both keeps both counted, marked “Hay and straw both recorded — check which” on the record, the Harvest row and Data Health.
The total cost beside the record count adds every done pass and each plan still to do — a plan you marked done counts once, as the done pass; a plan a never-planned done pass of its type has matched, and an overdue plan, are left out (each row still shows its own $). “plan 1/2” counts plans marked done against every plan the paddock had. The OVERDUE badge means the plan is out of every total: Financials, Budget and this one.
A new pass is costed when you save it — whether you add it here, plan it in Nutrition, have Ask PaddIQ create it, or enter yields or protein on the Harvest page. The machinery $/ha comes from the rig or fleet shown on it; with none picked, from the job's default fleet, else the one rig set up for that job (a fleet with no $/ha yet also falls back to that one rig). The picker always shows the rig or fleet the save will charge, and before you save the cost line reads “costed on save at $X/ha” (hover it to see whose rate). To go back to the job's default after picking something else, choose “— Job default (costed on save) —”. That $/ha is then frozen on the pass: changing the rig's or fleet's costs later doesn't move it. If a new pass names a fleet you've since removed from Machinery, the editor says so and costs it from the job's default instead; a saved pass on a removed rig or fleet shows it as “as recorded — removed from Machinery” and keeps its $/ha. If nothing in Machinery can cost the pass, the editor says so and the pass saves with $0 machinery — for a contractor's job pick their rate from Pricing → Contractor, never a pretend “Contractor” rig (that would put their $ in the machinery bucket). Fert down the tube (DTT) stays at $0 on purpose — it goes on with the seeding pass, which already carries the seeder's cost. A pass charged to a contractor rate saves without needing a rig or fleet. Passes added between 25 September and this update that show a fleet or rig but $0 machinery keep their $0 until you change them: Machinery → Rigs → Needs attention lists them under “$0 machinery”, and “Cost these” costs them in one go after showing each pass's $ before and after (untick any to leave; Undo straight after).
Each pass keeps a history of who paid for it. When its cost source or machinery $/ha changes — you pick another rig, fleet or contractor rate in the editor, a Needs-attention fix moves or costs it, or a John Deere match puts it on a rig — the old value is kept on the pass. The editor's Rig & cost box shows the last change (“Cost source changed 7 Oct (costed at today's rate): Spray Rig A $0.00/ha → Spray Rig A $2.40/ha”); “Use the earlier one” puts the old source and $/ha back when you Save. A pass has one cost source only: picking a rig or fleet drops a contractor rate it carried, and picking a contractor rate drops the rig or fleet (machinery $0, the contractor bills it). A contractor pass's job row in Pricing → Contractor now follows the pass wherever it is made, changed or deleted — by you, a Cropping Card, Nutrition or Ask PaddIQ.
The variety picker filters to the paddock's crop; typing a new name offers “+ Add to library”.
Search box filters across products, paddocks, notes, operators and machines. Type, farm and machine filters up top: the machine filter lists every machine that did a pass this season (counted the same way as the Machinery page — the machine John Deere recorded on a fleet pass, else the rig, else the fleet's split) plus the cost sources worth a look ($0 machinery, Default fleet — a guess, Contractor, On the seeding pass), each with how many passes.
Each row carries a chip saying what pays for the pass: the rig, the fleet (and on a done fleet pass, who did it — “Spraying Fleet → 2M 8270R”, or “· shared” when John Deere named none of its machines), “Contractor: rate”, or “On the seeding pass” for fert down the tube. Amber “$0 machinery” means nothing in Machinery costs it; an amber chip ending “· guess” is a John Deere import that went on the job's default fleet because no single rig holds the machine it recorded — open the pass and pick the rig (your pick clears it, and the next import remembers it); a dashed grey chip means its rig or fleet has since been removed and the pass keeps the $/ha it was saved with. Hover any chip for whose rate it is. Nothing is changed by these — they are worked out each time from the record and today's Machinery.
Open a pass and the Rig & cost box shows what John Deere recorded for it — “Recorded by John Deere · 2M 8270R, Tractor · 41 L · 1.2 h” — and which machine it is counted to; an amber line says when Deere named a machine that is not on the rig the pass is costed to. The picker and the cost line read “$7.80/ha as recorded · $9.10 today” when the rig's or fleet's rate has moved since the pass was saved: the pass keeps its frozen figure.

Tips & tricks

Records need a cost source (rig, fleet, or a CONTRACTOR from Pricing → Contractor rates) — picking a contractor writes the job and its cost into the Contractor bucket automatically. Works for aerial spraying, cartage, anything with a rate.
Harvest records show the paddock's receival levy + freight line (rate × tonnes). Grain staying on farm? Hit '✕ No freight for this paddock' and it isn't charged.
“+1 more” on a seeding row means fert was bundled in the same pass — expand the record to see it.
Costs are snapshots (price and area at the time of the record). Changing prices or boundaries later never rewrites existing records.
A paddock's header crop comes from its actual seeding record first — what's in the ground beats what was planned.

💰Pricing

One library for every price: chemicals, fertilisers, fuel & oil (diesel, any other fuels you add, bulk engine/hyd/gear oils), ameliorants, seed, grain, overheads, leases and contractor rates. Season-scoped — each year keeps its own prices.

How to use it

Work through the tabs. Products imported from JD are already here at $0 — just fill in the numbers.
Seed Prices fills itself with every variety you've seeded or planned this season, plus every variety in your library from earlier seasons (they persist until you delete them). A row with no seeding record or plan this season wears a 'not sown' chip — open it and delete it if it is not one of yours to keep. Nothing in this list ever comes from another account: your library holds only what your own records, imports and typing put there. Operations Center writes '---' on a pass with no variety set; that is never registered as a variety, and any already there are removed by the next automatic tidy.
Grain Prices drive income: each crop needs at least one price with a real number, or income shows $0.
Fill prices from history copies a previous season's prices in — then adjust what moved.
Filing cabinet (also in Inventory → Coming in — same cabinet): every invoice that enters the app, grouped by supplier then by what it mostly was (herbicides, fertilisers…), dated, with the original file. Type 'glyph' in the search to see every invoice with glyphosate on it. An invoice priced here is filed 'prices only'; receiving it in Inventory upgrades the same card. An account statement with tonnes and amounts (CSBP) prices each row too and files one card per document number — upload the real invoice later and it replaces that card by number, no portal needed.
Parts ledger (the cabinet's second view): every line on every filed invoice, newest first, by year — part numbers, the photo from your part scan where there is one, supplier, the original invoice, quantity and price — and which machine it is on. The top figure is what you bought that year that is on no machine yet: until it is, it sits in no machine's repairs and that machine's cost per hectare reads low. Open a line to put some or all of it on a machine (a repair at the invoice's unit price, dated the invoice day; the rest stays listed for the next machine), to link it to a repair you already logged with the same part number (which fills that repair's cost if it had none), or to mark it not a machine part. 'Fill costs' does the one-match cases in one tap. Farm inputs such as chemicals and fertiliser are set aside under Not machine parts, never hidden. Editing needs Machinery edit rights. It also opens from Machinery → Maintenance (the Parts ledger button).
Splitting a line: an invoice line of 10 can go 3 to one machine, 2 to another, 4 on the shelf and 1 to general. Type how many in the box, then tap where they go; repeat until the line is sorted. Fitting a part later takes it off the shelf. Undo clears the whole line.
Parts ledger layout: the four totals (on no machine, on machines, on the shelf, general), then Invoices (tick each off) or Lines (every line, filtered).
A repair with no cost: open it and PaddIQ looks for the part in your past repairs and filed invoices — 'Use this price' fills it in. If nothing is found, add the invoice to the Parts ledger and open the record again.
Searching a machine's log: once a machine or implement has more than three records, a search box sits above the list — type a part, part number (dashes optional), job, note or date.
Logging a repair: the form opens from 'Log repair', 'Scan part' or a record's pencil. Type 2 or more letters of a part number or name and parts you have logged before or bought on a filed invoice are offered, with the last price and where it came from — tap one to fill the part and its number. The machine's photo, VIN, service interval and hours are under 'Details'.
Adding a parts invoice on the phone: '＋ Add invoice' is on both views of the filing cabinet (Invoices and Parts ledger — Pricing, Inventory, or Machinery → Maintenance → Parts ledger); filed from Invoices, it opens that invoice's checklist. In the checklist only Suggested machines show at first — tap Machines, Implements or Not on a machine to open them; they stay open for the next lines. Pick the PDF from your email (save it to Files first) or photograph each page — several photos make one invoice. It is read by AI with the part numbers, checked against the printed subtotal (a mismatch is flagged), filed in the cabinet once (the same invoice number is never filed twice), and opens as a checklist. Each line: tap the machine it went on (machines the invoice's customer order names, e.g. '740D/S760/S790', are green and first), enter how many if it went on more than one, link it to a repair you already logged with the same part number, or mark it not a machine part. The ✓ count shows when every line is sorted; the Invoices list on the ledger shows each invoice's progress. A close part-number match (e.g. 62032RS against 6203-2RSH) is offered for you to confirm, never filled automatically. Account statements split into their separate invoices, one line per item. Chemicals and fertiliser on the same paper: the review offers 'File it, then price the farm-input lines in Pricing' — Pricing's own import opens with the same file and updates your prices like any invoice. Read an invoice again to correct it: if none of its lines is on a machine yet, the new read replaces its lines; a line that looks like several items joined (two pack sizes in one) is flagged in orange. A PDF is read one page at a time, so a 4-page invoice cannot lose its later pages, and a PDF holding two invoices files as two. In the checklist, ◀ Back goes to the line before; tap a ticked line for ↩ Undo (a repair the line made and you have not added to is removed; a repair you logged keeps everything you entered and only loses the tie and that line's cost). 🔍 Picture searches images for the part number — John Deere's own catalogue pictures cannot be shown in PaddIQ. Where a line goes, grouped: Suggested (a machine already logging that part, machines the invoice's order names, the last one used), Machines, Implements, and Not on a machine — General (a farm overhead: added to your itemised overheads in Financials for that season, spread over your hectares; with a flat overhead figure it is shown but not added, since the flat figure already covers it), Stock (on the workshop shelf: counts as sorted and can still be put on a machine from the ledger's 'On the shelf' view when fitted), or Not a machine part. An invoice cannot be dated in the future: a date read more than a month ahead (a photo turning 2026 into 2028) is set to the same day this year — or last year if that is still ahead — with a note on the check screen, where the date is a box you can change. Invoices already filed that way are corrected when the ledger opens, and it says how many. The add-invoice check screen shows the supplier it read in a box you can type over (orange when none was read), suggesting suppliers already in the cabinet so one supplier keeps one spelling; Edit details does the same later. Name an invoice your own way (e.g. 'S790 pre-harvest parts') when you add it or under Edit details — the name is its title in the checklist, the ledger and the cabinet, and the cabinet search finds it. Edit details (top of the checklist) also corrects a filed invoice's supplier, number or date — lines already on machines stay on them. Remove invoice takes a wrong read out of the cabinet while none of its lines is on a machine (tap twice).
Fuel & Oil: log every delivery (or 🧾 upload the fuel invoice — each diesel/petrol/oil line is matched to its log for review) and 'use weighted average' sets the price from real purchases.
Grain Prices: one table of crop × grade × channel. Per crop the highest Farm Gate price wins, else the highest Market price — that drives Financials income, harvest load values, card gross margins and the N economics. 📷 Snap price sheet reads a LoadNet / DailyGrain / broker screenshot into a review list; nothing saves until you Apply.
Import price list / invoice takes a supplier CSV/XLSX, or an invoice PDF/photo (same AI reader as Inventory), and matches products by name — matched products get the invoice's per-unit price, unknown ones are added. For an invoice you can Save prices only, or Save + add to Inventory, which opens the same invoice in Inventory's receive sheet to book the stock in.

Tips & tricks

Enter prices as $/kg, $/L, $/tonne or per-pack — the table converts and shows the per-unit rate.
A product's Type controls which tab it lives on. “— set type —” in amber means PaddIQ couldn't guess — pick one.
Log purchases on a product to track actual invoices against the season price.
Levies & Freight tab: set each crop's receival levy $/t plus one freight/GFR $/t (site-based). Every harvested tonne is charged (levy + freight) against its paddock — the Receival Levy bucket in Financials.
Products, varieties, grain price rows and their Types are permanent once used: they appear every season at $0 until priced (grain rows keep their receival levy); deleting removes from this season and stops carrying forward (past seasons keep their data).
Contractor tab holds rates only — jobs are created from Field Records or Cropping Cards by picking the contractor as the pass's cost source: choose “👷 Contractor…” in the machinery dropdown, then which rate. The cost bills through the Contractor bucket, never machinery. A contract pass saves even when you have no rig or fleet for that job; it won't save until you've picked which rate.
Prices apply from now on. Existing records keep their snapshot — that's deliberate (your March urea pass shouldn't change cost because June urea is dearer).

📅Planning — Overview, Crops, Fertiliser, Programs, Costs & orders, Calendar

Season planning end-to-end, in four steps: Crops (what goes where — the old Rotation tab), Fertiliser (what it needs — the old Nutrition tab, with the Nutrient Balance under it), Programs (reusable crop programs — Cropping Cards and tank mixes) and Costs & orders (what it costs, returns and what to order — the old Inputs & Margins).

How to use it

The plan strip, at the top of Overview and every step: PLAN 2027 · Crops 39/39 › Targets 31/39 › Fertiliser 12/39 › Programs 12/39, then the one thing to do next with a button to that step. Crops counts paddocks with a crop for the season (sown, else planned). The other three count the paddocks with a harvested crop: Targets — a target that is yours or built from your harvests (a paddock on PaddIQ's crop default isn't counted); Fertiliser — fertiliser planned, or a fert pass already done; Programs — a seeding pass planned or done (what a Cropping Card writes, and what puts seed and machinery into Costs & orders). Tap a step with paddocks missing to list just those on Overview; Show all clears it. The strip only reads — it saves nothing.
Calendar (/planning?s=calendar): every date of the season on one calendar — Agenda (day by day from today; a phone opens here) or Month (a grid, Monday first; tap a day for its list, ‹ › to move months). On it: each planned pass in Field Records on its own date, the paddocks doing that job that day grouped together with their hectares and $ (as Field Records costs them) — a date the planner only suggested from your usual date says “Suggested date”; what a Cropping Card would add on the paddocks of its crop it isn't applied to yet, dashed and marked “From card, not applied” (the same passes and dates Apply would write — only when the crop has one card; with two or more a note says to apply one); done passes, faded; withholding periods ending (harvest and grazing — the pass's date + the label's days, for passes done or planned) and plantback dates (the date each herbicide's label months run out for the crop the paddock is planned to, red when that is after the planned sowing; a rain requirement is said, not dated) — both from the APVMA label tables, always “check products/label”, and any product the tables can't read is named in a note; machines whose service is due soon or overdue, and machines with Daily checks overdue, on today; paddocks with no soil test or one 3+ years old, under Not dated; and, while the season has no harvest pass, your usual harvest date (the middle day of your own past harvest passes — your habit, not a forecast; PaddIQ does not predict harvest). Filter by type, farm and crop (machinery reminders show while no farm or crop is picked). Tap an event for its sheet: where its date comes from, each paddock with hectares and $, Open pass (Field Records opens on that paddock with the pass's editor open) and Paddock sheet. 📅 Add to my phone calendar downloads the planned passes shown (filters apply) as an .ics file — open it on the phone to add them; reminders stay in PaddIQ, and downloading again after the plan changes updates the same events in calendars that support it. Nothing on the calendar is saved — it is read from your passes, cards, machines and soil tests each time.
Each step has its own link — /planning?s=crops, ?s=fertiliser, ?s=programs, ?s=costs (and ?s=calendar, ?s=soil, ?s=vrt) — so a refresh stays on the step you were on and the phone's Back goes back a step instead of leaving Planning. Old links naming Rotation, Nutrition or Inputs & Margins still land on the right step. In a paddock's sheet on Overview, Plan fertiliser opens the Fert Plan with that paddock's card scrolled to and its program open in a sheet and Change crop opens Crops scrolled to its row, outlined.
A link to a step followed while Planning is already open (the Getting-started step in the sidebar, the Planning menu item) moves to that step too — it used to leave you where you were. Plan fertiliser on a paddock with no crop for the season — or a fallow or pasture — opens the Fert Plan with a note saying it has no plan and a Pick its crop in Crops button, instead of a list with nothing selected. With no paddocks in the season, the plan strip offers Add paddocks on the Farm Map.
Overview is the landing view: a card per paddock — crop, name, farm and hectares, $/ha (plan + actual), the target box and the season so far in words (✓ Sown · ✓ Sprayed 2 · – Spread · – Harvest; done passes from Field Records, lime and gypsum count as Spread). Filter with the chips above: a farm, one or more crops (each with its hectares; pick one crop to see its varieties), and More filters for where the season has got or the soil test's age. On a computer the map sits beside the list; on a phone the list comes first and Map is one tap away. Filtered-out paddocks stay on the map, faint, and can still be tapped. Farm colours are the ones in Settings → Farm Setup (a farm with none gets its own fixed colour, never green, amber or red) — the same on Planning, the Dashboard and Pricing.
Tap a card or a paddock on the map for its sheet: the gross margin with its sum (target × price − costs) and break-even, the season so far, the soil N bank in kg/ha and Colwell P, Colwell K and sulfur in mg/kg (with the test's age), every pass dated with its $/ha, the cost split (seed · fert · chem · mach · contr · levy & freight), plantback and the last five crops. Each planned pass with a product has a 🗺 button: attach one of the paddock's zone maps, set each zone's % and which product varies — the same picker as Field Records' 🗺 chip, and it saves only that pass's zone map. The sheet's buttons open Plan fertiliser, Change crop, Apply card (Programs), Records (Field Records) and Zones & Rx (Imagery & VRT).
One money everywhere: a paddock's $/ha is the same on Overview, the paddock sheet, Inputs & Margins, Financials, the Dashboard and the Season Plan PDF — seed, fertiliser, chemical, machinery, contractor, and levy & freight on the projected tonnes. Until October 2026 Planning left out levy & freight, a Cropping Card's contractor passes and (on Overview) the seed of a paddock with no seeding pass, so the same paddock could read $212 on Overview, $248 on Inputs & Margins and $298 in Financials; Planning's figures now rise to Financials'. Nothing stored changes.
Seed before a seeding pass exists: the planned sowing rate (a rate typed in Planning, else the paddock's last sowing of that crop, else the farm's, else the crop default — the rate Nutrition puts on the planned seeding pass) × your Pricing → Seeds $/kg, marked plan. Once a seeding pass exists, its own rate and variety are used.
Grain prices: projected income uses this season's bids in Pricing; until you enter any, it uses the latest season that has them and every money view says so — “Prices: 2026 bids — enter 2027 in Pricing” (Overview's paddock sheet, Inputs & Margins, Financials and the PDF). Levy and freight follow the same season. Harvested paddocks are always priced by the grade they went, at their own season's prices.
Soil test age, one rule everywhere: current up to 2 years old, aging at 3–4 (amber — plan the next one), stale over 4 (red ⚠ re-test). The Overview filter, the ⚠ beside a paddock, the paddock sheet and the Balance all use it.
Which paddocks Planning shows, and their hectares, come from Settings → Farm Setup: the paddocks active in the season you are planning (each paddock's and each farm's active years), at the area Farm Setup holds — the figure a Farm Map cut (with “use the new area”) or a Farm Setup edit sets. Overview, Rotation, Nutrition quantities, Inputs & Margins and Cropping Card totals all use it, straight away, without a visit to Settings. Field Records keep the hectares frozen on each pass. Until 7 October 2026 Planning kept the largest area any season's planning list had ever held, so a cut never reached it; Settings → Data Health lists the paddocks whose Planning area changed (“Show all” lists every one; “Got it” stops listing them all; no area changes). If no paddock is active in a season, Planning says how many you have and points at Farm Setup's years. Paddocks an older import listed that Farm Setup has no entry for are named in one line with “Add to Farm Setup” — Planning used to add them by itself every time it opened.
Crops (the old Rotation): paddock × season, three seasons back to next season. On a computer it is a grid of crop chips — each cell shows the crop, the variety, the yield harvested (past seasons) or this season's target with where it came from, any rotation warning, and — in this season and next — a red “⚠ plantback …: 4 mo” when a herbicide on the paddock is still short for that crop (amber when one could not be checked); tap a cell to change it in a sheet: the crop (the one crop picker, with “＋ Add a crop type…”), the variety, this season's target, and the plantback for that crop (the herbicides recorded on the paddock, judged at the planned seeding date — a herbicide still PLANNED before then counts too, marked “planned pass”; with nothing short it lists each product checked and its actives — check products/label). The sheet has the seasons along the top, so you can move between years without closing it. On a phone each paddock is a card — this season's crop, the sequence (“Wheat → Canola → Wheat → Barley → Wheat (2027)”, ? for a season with nothing recorded or planned) and its warnings — and a tap opens the same sheet. “Classic table” (computer) puts back the old table with a picker in every cell, for the 2027 autumn plan; it will be retired after that. Rotation checks, above the list, cover this season and next: crown rot (three or more cereals in a row — a season with nothing recorded ends the run, it is never skipped over), canola-on-canola, the same crop two seasons running, and no legume in the five seasons ending there (shown once at least three of the five are known). Tap a check for the paddocks and their sequences, and a paddock to open it. Legume % of area is set against the 40% that a WA paddock survey found holds the N balance in every WA zone — the same 40% line as Fertiliser → Balance; it used to say “20% ok”. A variety added in a past season's cell joins your library only; one added for this season or next adds its row to that season's Pricing → Seeds (it used to land in the season you were viewing, at $0). The crop you plan — here, by applying a Cropping Card, through Ask PaddIQ or on the Farm Map — is saved in one place, so every page shows the same planned crop, and opening Planning never changes it. A crop picked in the next-season column is saved as that season's crop, and a past year you type in is saved as that year's — so the next season's view, the plantback pill and the Balance's legume history all see it. Picks like these made before October 2026 were saved only in the season you were viewing; PaddIQ copied them to their own season once, wherever nothing was planned (it never replaces a crop already set, and a year a seeding record names keeps the sown crop). Any that differ from the crop planned now are listed under Settings → Data Health. Choosing “— Crop —” clears the plan everywhere and it stays cleared (an older entry, or a new boundary for the paddock, can't bring it back); a paddock already sown still shows the crop in the ground. Every page shows ONE crop per paddock, read the same way: the crop actually sown once a seeding record exists (from John Deere, a PDF or typed in), otherwise your plan, otherwise a planned seeding pass when nothing is planned. When they disagree a chip says so beside the crop — “Barley · planned Wheat” once sown to something else, or “card is Wheat · re-apply?” when a Cropping Card's planned seeding pass no longer matches your plan (your plan wins; re-apply a card to bring its passes into line). Settings → Data Health lists every paddock showing a chip. “Set crop on several” (a sheet with the map, on a phone too — tap paddocks, or Select the ones listed) skips paddocks already sown and says how many (“3 skipped (already sown)”) — their records decide the crop.
Varieties and timings are picked from your library everywhere (Rotation, Cropping Cards, Field Records) — choose “＋ Add …” at the bottom of the dropdown to type a new one; it back-adds to the library and Pricing → Seeds.
Target yields: one box on Overview and in a Crops cell's sheet (and every cell of the Classic table). Until you type one, PaddIQ suggests a figure — the average of that paddock's last 3 harvests of the crop (within 6 seasons), else the farm's average for the crop over the last 3 seasons, else a conservative crop default — shown muted with a chip saying which (tap the chip for the harvests behind it). Tabbing past a suggestion saves nothing; type your own figure, or tap Use 2.6 to keep the suggestion as yours. Blank your figure to go back to the suggestion. A target is kept with the crop you typed it for: switch the paddock to another crop and the box shows that crop's suggestion with "your 3.0 t was for Wheat", and the paddock's planned fertiliser is flagged stale — the fert passes, and the seeding or spray pass that carries Nutrition lines (DTT down the tube, liquid N with a spray). Fallow, pasture and no-crop paddocks have no target. The same figure drives Nutrition, Inputs & Margins, Financials and the Dashboard.
Cropping Cards: build a full-season program (seeding pass, sprays, topdress) once, then apply it to any set of paddocks. The list shows each card as a card — its crop, “7 passes · on 14 paddocks · 1,480 ha” and its $/ha (what its passes on those paddocks cost, priced as Inputs & Margins prices them; “/ha typed” when it is on no paddock yet, at the rates typed on the card), with an amber “changed since applied” when a re-apply would change something; crop chips above filter it. Open a card: its cost for the season up top, then the card's name, crop and sow date, then its passes — each a card (operation, timing, what goes on, $/ha); tap one to edit it in a sheet (operation, timing, water, the Nutrition-plan switch, seed, products with rate, unit and $/ha, machinery, note; a seeding pass shows its seed the way it shows its fertiliser — “Seed Scepter 60–75 kg/ha ($42/ha)” on the pass and, in the sheet, where each paddock's rate came from: the rate typed on the card, the planned seeding pass the card takes over, or — where the card's rate is left blank — the paddock's seed plan (a rate typed in Planning, else its last sowing of the crop, else the farm's, else the crop default), priced from Pricing → Seeds; the card cost and the buy list count the same seed; Duplicate, Remove pass, and ↑/↓ to reorder — or drag on a computer). Delete card asks first and says what stays: the card's planned passes stay in Field Records as they are, marked “from a deleted card”. Apply to paddocks… opens a sheet — farm chips, a search, “All <crop> paddocks”, Tick all shown, or 🗺 Pick on map — then “See what changes…”; Apply writes planned Field Records (each wears a “from card <name>” chip in Field Records) and sets each paddock's planned crop to the card's crop (and its seeding pass's variety), so Rotation, Inputs & Margins and Nutrition all show the card's crop. Each pass is dated by its timing from the paddock's real sowing date once it is sown; until then from the card's planned sow date (its day and month, in the season you apply to), else another planned seeding pass on the paddock, else your usual sowing date — so sow 1 May puts the seeding pass on 1 May and a 2–3 leaf spray on 29 May, and re-applying an unchanged card leaves every date where it is.
Card passes collapse to one line each (op · timing · products · $/ha) — click a line to edit it, ▴ Done to close, ⧉ Duplicate to copy a pass. Each product line shows its own $/ha at the typed rate from your Pricing-tab prices (“plan” where the rate comes from the Nutrition plan). The Card cost is what Apply writes on the crop's paddocks (or the ones you ticked), priced the way Inputs & Margins prices them: each paddock's own rates, the Nutrition lines merged into the card's passes (DTT on the seeding pass), and each pass's machinery as the saved pass will be costed — its rig or fleet, else the job's default fleet, else the one rig (a fleet with no $/ha yet falls back to that rig; harvest uses your Harvest Fleet). It lists Products, Seed, Machinery (Contractor), Total, Income (target yield × grain price — last season's prices, labelled, until this season's are entered), Levies & freight and Gross margin, each saying where it came from. With no paddocks of the crop yet it prices the typed rates and says so. Products to buy orders the same passes: each paddock's rate × its hectares, one line per product even under two names. A pass set to a contractor with no rate picked stops Apply until you pick one. A card's seed is priced exactly as Inputs & Margins prices it: the variety's $/kg in Pricing → Seeds (name matched ignoring capitals and extra spaces), else a priced seed of the same crop; no priced seed shows no seed cost. A hybrid at $35/kg costs $35/kg on the card and its Products to buy list too.
Apply shows what it will do first, in a sheet: how many card passes the paddocks will have (new, updated in place, already right), the planned seeding passes it takes over, the Nutrition lines it merges, which paddocks it re-crops (“Home 01 Canola → Wheat”) and any passes another card already has there. Nothing is written until you press Apply, and ↺ Undo beside the result puts back everything that Apply changed — passes, lines and planned crops (a pass someone changed since is left alone). Re-applying a card updates its own passes in place, so an unchanged card changes nothing and lines you added to a card pass in Field Records stay; a pass whose block you took off the card is removed. Passes from OTHER cards stay unless you tick “Remove other cards' passes on these paddocks too” in the sheet (one with a zone map always stays). Each paddock gets ONE planned seeding pass: a planned seeding pass Nutrition (or you) already made is taken over by the card's seeding pass — its date, seed and machinery from the card, its DTT lines kept — and an extra one left by an older Apply is merged in. A seeding pass already done (converted to actual) is never planned again, and neither is one on a paddock already sown by any actual seeding record — a John Deere or PDF import, or one typed in: Apply plans no seeding pass there (“Already sown — no seeding pass planned”), and re-applying removes the card's own earlier planned seeding pass on it, listed in the sheet first (“Planned seeding passes removed — the paddock is already sown”), so seed and the seeder are not costed on top of the real sowing. A paddock sown on only part of its area still gets the card's seeding pass. Seed is saved in kg/ha with the card's crop; a seed rate in plants/m² or seeds/m² stops Apply (“enter it in kg/ha”) until PaddIQ can convert it, and isn't costed or ordered meanwhile. Changing a card's crop clears a seeding variety and rate that belonged to the old crop. A card already on paddocks shows “On 14 paddocks · up to date”, or “Changed since applied · re-apply?” when the plan there has moved away from the card (a crop picked in Rotation, a card edit, a Nutrition line planned since, the real sowing date) — nothing changes by itself; tap it to see the re-apply.
Cards never double up with the nutrition plan: a card product matching a planned fert row (same product + timing, by alias — “Agflow” on the card takes the plan's “Agflow Xtra” line once you've linked the names) merges that line into the card's pass; two card passes of one product pair with the plan's passes in date order (topdress 1 ↔ plan pass 1, topdress 2 ↔ plan pass 2). With the pass's “Rates from the Nutrition plan” on, the plan's per-paddock rate wins — and stays on a re-apply; off, the card's rate wins — merged either way. DTT-timed plan ferts ALWAYS fold into the seeding pass, even products the card doesn't list (all DTT goes down with the drill) — except a seeding pass with a zone map: an older prescription varies every product on its pass by the zones, so there the DTT stays its own pass and the Apply message says so (“Home 01: Flexi N stays its own DTT pass — the seeding pass has a zone map”). A planned pass with a zone map (Zone studio, or a 🗺 VRT link) is never merged, folded or replaced: re-applying the card that made it updates that same pass (its zones keep their %, and a sent prescription keeps its sent stamp; a product the card now lists that the pass didn't have goes on at a flat rate — the zones still vary only the lines they had, and the Apply message says so), and any other card leaves that product on the zone plan — the Apply message names each one (“Home 01: Urea kept on its zone plan”).
Planned rows in Field Records have quick actions right on the row: “✓ actual” converts the plan to a done pass, “✕” deletes it — no need to open the editor for plans that never got a pass.
Inputs & Margins: three views (Order list · Margin what-if · Plan vs history), each labelled with the season's grain prices it uses, with farm chips above the Order list and Plan vs history. Order list opens with the season's inputs as one big number ("Inputs $1.24M · $339/ha", the exact dollars under it) with a chip per bucket — Seed, Fert, Chem, Mach, Contractor, Levy — and the income and margin before overheads (the Fertiliser and Chemical cards add up to the Fert and Chem chips to the dollar: a few dollars of rounding are shared across that paddock's lines); then cards: Fertiliser to buy, Chemical to buy, Seed (by crop and variety), Machinery, contractor, levy & freight, and Paddocks (each paddock's inputs $/ha, the same figure Financials shows). Tap any card for a sheet: a product shows what to order, its area and $, and each paddock's share; a paddock shows its gross margin and how it is made up — each bucket with where it comes from, income, break-even and the products on it — with Plan fertiliser and Change crop. One Export button lists every file the step makes: the Order list and the Paddocks as Excel (the farm picked, or all), the Margin what-if as Excel (the figures you typed, with the TOTAL row's inputs $/ha filled in), and the Season plan PDF — the same PDF Home, Financials and Import make, now here where the plan is built. Negative money reads −$120. Quantities are what to order: rate × the hectares each pass covers (a half-paddock spray counts half, a paddock split between two seeding passes counts each for its share), added up in kg or litres — mL and g are converted, and litres show their weight when the product has a density; a product entered in a unit PaddIQ can't read is listed on its own row, flagged mixed units. Each product has one row per timing — urea at seeding and urea top-dress are separate — with planned or applied beside it. The Seed cards (crop · variety) add up to the Seed chip on the Inputs number. A finished season counts only what was done (as Financials does) and says how many planned passes were never done. Products the Nutrition recommender suggests that you have not yet accepted appear greyed and tagged recommended, with their own subtotal. They are worked out when the page opens, on whichever device you use, at today's prices — the phone and the desktop list the same rows, and you no longer need to open Nutrition first. A product the paddock already has at the same point in the season (at seeding or in-season, under any of its names) is not listed again; urea planned at seeding no longer hides a recommended urea top-dress. A finished season (an earlier year) lists no recommended rows — it counts only what was done. Margin what-if — every crop with paddocks (fallow and hay too, their sprays cost money), yields and inputs starting from those paddocks' figures in the Order list, levy & freight following the yield you type, overhead from Pricing → Overheads (or your flat figure) with lease & finance below the margin, as in Financials. Plan vs History compares against one year's actuals (the rows Financials shows for that year), or Same-crop average: each paddock against its own history of the crop it is planned to (blank where it never grew it) — a card per paddock with yield, inputs/ha and margin/ha for the plan and the other year. The what-if has its crops as cards with Yield, Grain $/t and Inputs boxes, an overhead box under them and Reset to the plan's figures; nothing typed there is saved. Tapping a product, seed, machinery or paddock card opens its own sheet. If one sheet or view can't be worked out it says so in place (“… couldn't be shown”, with Try again) — the rest of the page keeps working and nothing is changed.

Tips & tricks

A season you are planning gets one planned Seeding record per paddock with a crop (variety and seed rate from Rotation) the first time its fert plan is saved — open it in Field Records to change the rate, and every planned line carries the product's catalogue unit (Flexi N in L/ha, Agflow Xtra in kg/ha). Run all repairs renames aliases like plain 'Agflow' to the catalogue name and fixes planned units. Once harvest records exist, Inputs & Margins income switches from target-yield estimates to actual yields automatically.
A paddock you seeded but never planned still shows up everywhere with its real crop — actual records always win.
Build next year's card from a past season: it collapses that year's actual passes into a representative program.

🧪Planning — Nutrition

Per-paddock nutrient accounting (applied vs planned, kg elemental/ha) plus an economics-aware fertiliser recommender built on your soil tests, field records and prices.

How to use it

Grain protein is turned into nitrogen removed on the basis the receival lab reports it: wheat at 11% moisture, barley on a dry basis, as the receival standards report them, brought back to the tonnes delivered using your recorded moisture (11% if none). Barley used to be treated like wheat, which put its protein-based N removal about 23% high. Barley’s N-status label and residual-N credit still use wheat’s protein thresholds — barley-specific ones are on the list.
Organic-matter nitrogen follows the season’s rain: it rises with growing-season rain on each paddock’s own gauge and with the organic carbon on the test, in both the recommender and the Nutrient Balance. Until September 2026 the recommender used a flat rate per soil type, which gave the same credit every year — in a dry year like 2023 it counted about 70% more nitrogen than was released, so it recommended too little. Expect dry-year N recommendations to rise by a few kg/ha and wet-year ones to fall. The OC mineralisation rate in Assumptions is now only the fallback for paddocks with no rainfall history.
Fert Plan: one card per paddock — name, farm, hectares and its fertiliser $/ha (planned and done passes × your prices, the same figure as Inputs & Margins), then a chip per nutrient in kg elemental/ha. Before anything is applied the chips read planned / recommended ("N 62/58 ✓", "K 0/30 !"); once any pass is on they all switch to applied / planned, and the line under them says which. ! = under 85% of the recommendation; ✓ = covered (or, once applying, fully on). Macros / Micros switches the chips to Zn, Mn and Cu. The paddocks sit in groups — by Farm (the default) or by Crop — each under a small header with its count, hectares and hectare-weighted fert $/ha, with a gap between groups; Sort orders each group by Paddock (2 before 10), $/ha (dearest first) or Shortfall (most kg/ha under the recommendation first, over the nutrients shown). Cards / Table switches to one compact row per paddock — paddock · crop · ha · $/ha · the same chips — and the choice is remembered on this device (a phone starts on cards, a desktop on the table). Tap a card or a row for its program in a sheet: on a computer it fills the window, in two rows — the N optimum chart beside the N explanation and the nutrient breakdown, then the products planned and applied beside the season summary and the N bank — and on a phone it is one column. Explanatory notes (the yield line, Already seeded, split passes, residual N, the two N views) sit as one line each — tap to open; a warning that needs you (a nutrient no preferred product covers) stays on show. Each plan line and each pass done is its own card. The yield line reads off the same N response curve and the same ceiling as the N optimum chart: "Water sets the ceiling at 3.09 t/ha — about 2.9 t/ha expected at your N". Until 14 October 2026 it showed the ceiling × 0.9 and a flat 40 kg N per tonne budget, so it could say "water caps near 2.8, your N supports 1.7" beside a chart drawing 3.09 and an optimum near 3 t. A paddock with no N curve (no grain or N price) still gets the rough budget, and says so. "Use recommended program for M1" replaces that paddock's own plan lines only; Undo (on the button beside it, and in the message that pops up) puts the lines back as they were — passes it added are removed and rates go back; a pass it removed comes back as a new planned pass without its date, rig or notes. Undo lasts while the sheet is open (the message's Undo, 8 seconds).
Add products to a paddock's plan with timing (seeding vs topdress); the nutrient breakdown updates live. Every Nutrition screen uses the same five timings — Seeding (DTT), Pre-seed spread, Topdress, Spray pass and Ameliorant — in + Add product, the wizard and Preferred Products. When a topdress would go over the product's max rate the recommender splits it, and the extra pass is planned as its own Topdress pass 2 a month after pass 1 (two months after seeding). Until 7 October 2026 a pass 2, or a product added as “Post-emergent”, was saved onto the paddock's pre-seed spread two weeks before sowing; nothing was moved, and Settings → Data Health lists any spread that still carries a product also planned in-season on the same paddock — Use recommended program (or the wizard) on that paddock re-plans it, or leave it if the spread is right. In a paddock's program, applied passes are shared out among its plan lines in date order: with Urea 100 (pass 1) and Urea 50 (pass 2) planned and 100 kg on, pass 1 reads done and pass 2 still shows 50 to go. A Spray-pass line counts as in-season N, not seeding N. Each planned kilogram is counted once: a line that rides on the seeding or spray pass is counted as the plan line it is, not again as part of the pass, and the same product analysis the Nutrient Balance uses credits the planned and applied units here (so a John Deere pass named "Gran Urea" counts its N on both screens). In + Add product the unit is the product's own (kg/ha or L/ha); pick g/ha or mL/ha to type a small rate and the conversion shows before you add (500 g/ha = 0.5 kg/ha). Adding a product already planned at the same timing changes that line's rate; at another timing it becomes a second line; a product on a Cropping Card's pass is changed on the card. Taking a Seeding (DTT) or Spray-pass line off with × takes it off the pass it rode on. Settings → Data Health lists any paddock where a product is planned twice for one job (a card's line and Nutrition's), with a Merge per paddock and Undo, and any trace-element line whose rate reads like grams saved as kilograms.
A planned rate saves when you press Enter or Tab, or tap out of the box — not while you type. An empty box, 0 (or anything that rounds to 0) or Esc puts the saved rate back, so backspacing to retype a number never removes the pass. Esc in the rate box only puts the rate back — it doesn't close the paddock's panel around it; press Esc again to close the panel. Each plan line stays tied to its planned pass in Field Records: a new rate, Switch in-season N → cheapest or accepting the wizard again updates that same pass, keeping the date, rig, operator and notes set on it. The switch (shown on a paddock only when it would change a line) moves every topdress N line — any pass — to the cheapest N at the season's prices, at the same kg N/ha; a Spray-pass line moves only when the cheapest N is a liquid, since it goes in the spray tank. It changes dedicated N products only, never a compound such as Agflow. To take a line off, use ×. If that would delete a planned pass, you're asked first.
In-season fertiliser is planned one pass per product (liquid N through the boom and urea spread are different jobs), a month after seeding; a line timed “Spray pass” in the wizard goes out WITH the paddock's planned in-crop spray — it joins that tank mix rather than making a fert pass. Planned DTT fertiliser lives ON the paddock's planned seeding pass (one pass, not two): the plan writer folds it in, matches products by alias (Agflow ≡ Agflow Xtra) so a card's line and the recommender's line are one line, and re-rates it when the recommendation changes. A seeding pass or spray with a zone map never takes on a new product this way — an older zone plan's prescription would vary that product by the zones too — so the line is saved as its own pass; a line already on a zone-mapped pass shows as part of that zone plan (rate editable; to take just that product off, edit the pass in Field Records — removing the Prescription removes the zone plan for the whole pass); a planning season's seed rate comes from that paddock's last sowing of the crop, else the farm's, else the crop default — never a stray number off an old import. The Recommendation wizard (Fert Plan, above the cards) opens as a sheet — "Paddock 7 of 42", with Back, Skip and “Use for M1 only →” at the bottom — every green button says which paddock it is for (the wizard plans one paddock at a time, never all at once); ×, Esc or tapping outside closes it. Each paddock opens on the program in your plan (corrections included) — ↻ Recompute swaps in the recommender's own program, and nothing changes until you accept. Every open starts fresh: edits you made in an earlier open but never accepted are not brought back over a plan changed since. "How the rates were set" shows N and P/K/S separately: N as the supply at sowing built from its parts (soil test and its year + organic matter + legume credit, less stubble tie-up) against what the target needs; P, K and S as the soil test walked forward to this season (every removal since already taken off — never subtract it again), each against its critical level (build/maintain/mine) with what the crop takes and the rate. “Use for … only” writes that paddock's plan as planned Field Records (the message that pops up has Undo, and the summary has “↶ Undo N paddocks”, which puts every paddock this open changed back as it was before the wizard — for this open only); the summary at the end reads what is in the plan now — every paddock's, not just this open's — and is the buy list — solids in kg, or tonnes from 1,000 kg up; liquids in litres, with their weight beside them when the product has a density set (Flexi N: 42,500 L ≈ 56.1 t). A preflight checklist under the button shows what it still needs before it can run.
The N·P·K·S chips at the top of each wizard step re-total as you edit: this program plus anything already applied, against the recommendation (the Fert Plan's own chip rule — ! under 85%). Every program line is a card with its timing, rate (saved to the program when you leave the box), $/ha, what it supplies and why, and a red Remove; "Add a product" under them adds ANY product from your library — pick gypsum for S and it shows what it would supply before you add it.
In the wizard the target beside the crop is the same target box as Overview and Crops: type a new target and the paddock's recommendation is worked out again at it (the source chip beside it says whether it is yours, a paddock or farm average, or the crop default). A program you have already edited or accepted keeps its rates — the chips compare it with the new recommendation, and ↻ Recompute swaps the recommender's program in. The summary lists every planned paddock's fert $/ha and $ at today's prices under the buy list. Each accept logs, for later learning, what the recommender asked for and what you accepted per nutrient (kg N, P, K, S per ha) as one entry per paddock — accepting the paddock again replaces its entry; entries logged before October 2026 are kept as they were.
Legumes (lupins, peas, chickpeas…) get N rec 0 by design — they fix their own nitrogen. The wizard says so on the N row rather than leaving a bare zero.
Nutrient Balance: soil-bank view — what tests say, what crops removed, what you've added. It lists your current paddocks only: a soil test saved under an archived or renamed paddock is left out, with one line saying how many — the test is still in Planning → Soil → Soil Tests under its old name.
Nutrition setup has moved to Settings → Nutrition Setup: preferred products, removal rates, product nutrients, your equipment (what the seeder can carry) and the assumptions the recommender runs on. It’s the same screen as before — anything you set there applies here straight away. Preferred Products is a card per product (timing · rated for · max rate a pass, then its crops and soils); tap one to change it in a sheet, where Remove takes it off the list. Opening it (or Soil → Soil Tests / Tissue) never changes your plan or your planned passes: only Planning → Nutrition works out and saves the fert plan.
Passes a Cropping Card made show in a paddock's fert program as “from card <name> · edit on card”: they count in the planned units, but Nutrition never changes, re-dates or removes them — change the card and apply it again (a pass whose card has since been deleted reads “from a deleted card · edit in Field Records”). A planned pass with a zone map shows “zone map <name> · remove in Prescription”: a rate typed here becomes that pass's new flat rate and its zones keep their %; it is never deleted or flattened from here. “Use recommended program” and the wizard's accept leave both kinds in place and say so.

Tips & tricks

The N rate is the one rate with the best EXPECTED margin across every recorded finish (since 14 October 2026): the paddock's yield-response curve is run against each year of rainfall on record at its gauge (or the farm's station), and the rate that earns the most on average across all of them — under the top of the response, inside the band around the budget — is what the program fills. No forecast is used: every recorded finish counts the same. Rates whose expected margin is within $5/ha of that best are a flat-profit zone (“66–96 kg N all earn within $5/ha of the best”): a plan anywhere in it is not marked short — no ! on the chip, no “your N is short” on the yield line. The explanation also says what a wrong guess at the finish costs at that rate (“at 60 kg N: a decile-2 finish wastes $12/ha of N; a decile-8 finish leaves $18/ha”). A finished season (its finish is known), or a device that has not read the rainfall record yet, uses the average-finish curve's ECONOMIC OPTIMUM instead and says so; the record is fetched once per farm when the Fert Plan opens. When the rate is held at the top of the response rather than set by the economics, it is called “capped at the top of the response”, never “economic optimum”. The economic optimum on that curve is the point where the next kg of N stops paying for itself at the grain and N prices in Pricing (wheat's curve comes from the PaddIQ Response Bank — built on WA trial results and growers' own records; other crops run on industry curves until the Bank holds theirs), under a yield ceiling that is the lower of what the season's rain allows and your target. The rain figure is never below what the paddock has shown it can do with its water: its best harvested season of that crop gives a water use — the yield divided by that season's water above the evaporation allowance — and that water use is applied to this season's water (and, on the chart, to each finish's). A paddock that grew 3.4 t on 162 mm when the rain line said 2.2 t lifts this season's ceiling in proportion to this season's rain; a big crop grown in a wet year with an ordinary water use lifts nothing, so a wet-year record no longer lifts a dry season's ceiling to wet-year tonnes (until 14 October 2026 the floor was the best tonnes). The text says so — “ceiling raised to 3.6 t — this paddock's 2025 crop — 3.4 t on 162 mm GSR — used its water better than the rain line assumes”. When your target or the crop's genetic cap sets the ceiling it says “set by your 3.5 t target (water would allow …)”, never “ceiling raised to”. Only harvested seasons up to the one planned count, with every April–October month of rain recorded; yields above the crop's genetic cap, or a water use no crop achieves (more than 40 kg/ha per mm), are ignored as slips; your target still caps the ceiling. The rain line itself is your farm's own once there is enough of it: with 3 harvested seasons and 8 harvested paddock-seasons of that crop with rainfall recorded, your best yields against growing-season rain are blended into the Response Bank's line (more weight as more seasons come in), otherwise the Response Bank's alone. Every ceiling says which — “water line: your farm (5 seasons) blended with the Response Bank” or “Response Bank — your farm needs 2 more harvested seasons with rainfall recorded”. On a farm that shares with the Response Bank, once enough farms in its rainfall zone share and their results predict better than the trials alone, the line (and the response curve and the lift after a fallow) is tuned with those farms — it can raise the water line, never lower it — and the text says “tuned with farms in your rainfall zone (7 farms)”; no zone figure or other farm's number is ever shown. Stored summer rain: when the November–March before the season is fully recorded, a share of it is added to the growing-season rain as water stored at sowing. Your own water line has two halves — one on April–October rain alone, used when the summer is not known yet, and one with the stored summer added, which needs its own 3 seasons with November–March recorded; until it has them the summer is not counted on your line and the ceiling says so. The budget — demand at target minus soil supply (test N + organic-matter N + legume/protein credits) plus stubble tie-up — is shown beside it for comparison only. The wizard's "How the rates were set" fold, and the paddock's sheet in Fert Plan, say which rate the program fills and what bound it (the top of the response, the band around the budget, the water ceiling); with no grain price or no priced N product the rate falls back to the budget and says so. The Balance tab's Assumptions & Methodology panel describes the same rules the maths runs on; the legume credit in Settings → Nutrition setup is kg N per tonne of legume grain, × last year's yield, with a ceiling. No legume credit is added when the paddock's soil test was taken in the season being planned: a test taken after the legume year already measures the nitrogen it left, so adding the credit as well would count it twice (“How the rates were set” then shows no legume line). After a fallow year (since 21 October 2026) the crop gets two things: the N your N bank says the fallow left in its N supply — what the fallow year added from organic matter, with nothing harvested, times the share that survived the summer, the same figure the Nutrient Balance shows (a WA trial figure is used only when there is no soil test from before the fallow) — unless this season's soil test already measured it (Settings → Assumptions & Calibration → Fallow N credit to change it); and a higher yield ceiling for the break — disease, weeds and stored water together — a WA trial figure for wheat and barley, blended toward your own farm's figure once you have 2 seasons with paddocks of the same crop after a fallow and after a cereal side by side (Settings → Assumptions & Calibration → Yield lift after a fallow shows which). The ceiling text says it (“a lift after last year's fallow”, with the figure once your own seasons set it); it still never raises your target. Stored moisture is part of that lift, not added again. PaddIQ's fitted parameters and coefficients are not shown on grower screens — the explanations give this paddock's inputs and result.
The optimum chart (open a paddock) runs the paddock's own yield-vs-N model against every recorded finish at the paddock's rain gauge (or the farm's station) and draws three of them: the mean of the years whose August–September finish fell in decile 2 (deciles as the Bureau of Meteorology numbers them — 1 is the driest tenth; dry, long dashes), decile 5 (the middle, solid — it replaces the old average-finish line) and decile 8 (wet, short dashes), each under its own ceiling, with a dot at that finish's best rate and the $/ha over nil N it earns there (on a phone those three sit in a small table under the chart). The blue line is the recommended rate — the best expected margin across ALL the finishes, not just those three — and the faint blue shading is every rate within $5/ha of it. Above the chart the rates read as numbers first — recommended, the within-$5 range, yield max and your plan, each in kg N/ha — and the line under them says what a decile-2 or decile-8 finish would cost at the recommended rate. The faint ink band is the trial spread around the curve, shown only. The row under the axis is the share of finishes in which each rate out-earns nil N (a dash past the top of the response; a small table on a phone). A season already finished (its finish is known) draws one curve. And "How this is worked out" under it holds the full basis. The chart is drawn at the width it has, so its labels stay readable on a phone. It splices each historical year's remaining months onto this season's rain to date and prices haying-off from that year's Aug–Sep, so a dry finish counts against the top rates. It is not a soil-water simulation (Yield Prophet); it is the app's own fitted model run once per year of record. Rainfall: SILO, Queensland Government (Long Paddock), CC BY 4.0.
On the optimum chart every rate is fertiliser N. Wheat's curve starts from fertiliser N alone: across the trials behind it, the soil nitrogen measured at sowing did not predict how much fertiliser lifted yield, so the paddock's soil, legume and organic-matter nitrogen act through the budget band the rate is held to and through the shaded top of the response (where all the nitrogen in the crop — soil plus fertiliser, less stubble tie-up — outruns what the water can carry); a paddock with plenty of soil N still gets little or none. Crops on an industry curve start from the paddock's supply, as before. The economic optimum always sits at or left of the yield-max marker and the shaded top of the response. Behind the curve an ink band shows the trial spread: how far real trials sat from this curve — its top edge a paddock that responds like the weakest tenth of trials (more yield without N, less to gain), its bottom edge the strongest tenth. It is there to show the uncertainty; the rate is not worked out from it. The ceiling line says what set it: your target, the season's rain, the paddock's own best harvest of that crop (“grown 2025” — when it beats what the rain alone allows), or the crop's genetic cap. Wheat's response curve comes from the PaddIQ Response Bank; barley and canola say they run on an industry curve until the Bank holds theirs.
Nutrient Balance, before harvest: a paddock with this season's crop in and no harvest recorded is graded on its PROJECTED end — the N bank less the expected removal at the projected yield (your target, else your own average) × kg N per tonne — marked "proj."; once the harvest is entered it grades on the recorded bank. Open a paddock: the waterfall starts from the bank the season opened with and names where it came from (the soil test, the OC estimate when the test has no mineral N, or last year's carry-over), and shows the expected removal hatched. Looking at an older season uses the newest soil test taken by then, never a later one. Model accuracy compares each later soil test with the bank at the close of the season before it was taken.
The data-confidence badge (High/Med/Low) tells you how much guessing went in: old soil test, missing yield, borrowed analysis all lower it.
Import Soil Tests takes the lab’s CSV or Excel export, a PDF report, or a photo of it, from any lab. CSV and Excel are read on your device; a PDF or photo is read by PaddIQ’s AI. Either way you get a review sheet first: every column in the file, its unit, its first value, and what PaddIQ will read it as — fix any column from the dropdown and tick Remember so that lab is right next time. Units are converted on the way in (ppm, cmol/kg, mS/cm all become PaddIQ’s units). A file that cannot be read is explained on screen, and you are asked “Send this to PaddIQ to help fix it?” — the box shows exactly what would go (the file name, the lab it looked like, and the first line's column names only — never a result, paddock name or sample id; a first line that reads as data offers nothing). Nothing is sent unless you press Send to PaddIQ.
Products with no nutrient analysis count zero units and get flagged — fill their analysis in the product library.
Legume history earns an N credit automatically when last year's paddock grew lupins/peas — scaled by that crop's actual yield.
The recommender and the Nutrient Balance use the same critical levels. Critical Colwell K is set by each paddock's soil type (40 on deep sand up to 55 on loam and clay), and canola never reads below 60; critical sulphur is 4 mg/kg. A figure you type in Settings → Nutrition setup → Soil Test Critical Levels overrides every paddock — leave Potassium blank to go back to soil type. Before October 2026 the recommender used a flat 45 for K, so K recommendations rise on loam, clay and canola paddocks. A Potassium figure of exactly 45, or a lupin credit of exactly 75, saved before then was the old default saved automatically, so it now reads as per-soil-type and 30; type it again if you really want it.
K and S are set from the soil reserve — the same bank the Nutrient Balance shows: the soil test, plus every K and S applied since it, less what each harvest took off, read at sowing. If the bank is still at or above critical after this crop takes its share, no K or S is recommended that season, and the paddock sheet says so — “soil bank covers it — next K due ~2029” when the ledger can see that far ahead at this season’s yield, else “covered by soil reserve”. Below critical it builds back up — but only as much K in one season, the crop’s removal included, as WA trials found worth putting on: the rest of the lift comes over the next seasons, and the sheet says so. A crop that removes more than 60 still gets its full removal. And a build-up is only ever worked from a current test: when the soil test is more than 4 seasons old (the same age rule as the ⚠ re-test mark) the paddock gets the crop’s removal only, and the sheet reads “from a 2018 test (8 yr old) — retest before building up”. An old test walked forward is an estimate, not a measurement, and too rough to spend a build-up on. So one big MOP or gypsum hit carries the paddock for as many seasons as the bank lasts. Until October 2026 a paddock above critical was still asked for the crop’s full removal every year.
A soil value no soil can carry in its box’s unit is flagged ⚠ on Soil Tests and the Balance and left out of the recommendation: Colwell K under 5 mg/kg (it looks like exchangeable K in cmol/kg typed in the Colwell box), Exch K over 10 meq/100g (a Colwell figure in the Exch box), or anything negative. Your test is never changed — check the lab report and Edit the row. A test with no K or S at all now reads “no K on the soil test” and the crop’s removal is recommended, where it used to read as a bank of 0 and ask for a large build-up.
Each planned product in a paddock’s sheet says where it is in Field Records. A Seeding (DTT) line rides INSIDE the paddock’s planned seeding pass — one pass, one trip — so Field Records lists it as a product on the Seeding pass, not as a separate DTT row; once an actual seeding is recorded that planned pass shows PLANNED ✓ (done).
A paddock's soil type lives in one place, Farm Setup (Soil Tests → Classify paddocks by soil type writes there too). The recommender, the Balance and the critical K all read it, so a change in Farm Setup moves all three.
N is priced on the N product you will actually use: the cheapest priced product in that paddock's Preferred Products that is rated on N. Only when none is priced does the economic optimum fall back to the cheapest N in your library, and the paddock's "How the N rate was set" says so. The wizard's projected income uses the yield the season's rain allows when that is below your target — the same yield the N rate was sized to — and says which.
App Setup (Settings → Nutrition setup) limits the recommendation once you set it: how many granular and liquid products go down the tube, whether you pre-seed spread or top-dress, by boom or spreader, and the most top-dress passes. Products it leaves out are listed under the paddock's program, and what they would have covered shows as a shortfall that names App Setup. Until you pick something there, nothing is limited.

🛰️Planning — Soil, and Imagery & VRT (Soil Map, Imagery, Zones)

The precision-ag studio: soil sampling on the map, free Sentinel-2 NDVI back to 2017, and a zone builder that turns layers into variable-rate prescriptions.

How to use it

🗺 Getting into Zone Studio: Planning → Imagery & VRT opens on Zones. The first time, a card explains the four steps (1 Pick layers · 2 Make zones · 3 Set rates · 4 Export Rx) and names the paddock to start with — the one with the most seasons of yield maps — with its button; × hides the card on this device and “What is Zone Studio?” brings it back. Below it every paddock shows its zone status (Zone map ✓ / Draft — not saved / No zones), what it has to make zones from (yield maps by season, protein, satellite peaks, soil-test sites, soil colour, radiometrics, elevation) and one button: Open Zone Studio (opens the newest saved zone map), Continue zones (the zones you started on this device and haven't saved) or Make zones (a new map on step 1). In a paddock's sheet the same button is the big green one at the top (＋ New zone map beside it when one is saved). Other ways in, each one tap and straight into the studio on that paddock: the Farm Map's paddock panel (the yield map on screen comes ticked), Make zones from this map on a yield map, Vary by zone → in the Fert Plan's paddock sheet, the 🗺 button in Planning's paddock sheet, and Field Records' ＋ Build a zone map. The link in the address bar follows the studio (…?s=vrt&zs=<paddock>), so a refresh keeps it open.
Grain samples by zone (Zone Studio → zone card → + sample): at harvest, pull a bag of grain at one of a zone’s numbered sampling dots and record its protein, moisture and screenings. It’s the only way to get protein zone by zone without a protein sensor on the header — receival protein is one number for the whole paddock. Each sample is saved against the dot’s location, so if the zones are ever redrawn it lands in whichever zone now covers that ground. The card shows each zone’s average protein and how many samples it’s from; tap the (n) beside it to see each sample (date, dot, protein, moisture, screenings) and Delete a mistyped one — it leaves the average on every device, and Undo brings it straight back.
Soil Map: every sample site plotted and colour-coded by analyte (Colwell P, pH, K…). Click a paddock to filter to its sites; pick the year or Latest. A chip reading “—” is not tested — a blank on the lab file, or a 0 it printed for a test it didn't run (PCT files put 0 in every column not run on the 15–30 cm rows): PBI, OC, pH, Colwell P or K and the like can never really be 0, so a 0 is never shown or used as a result. New imports say how many such 0s they read as not tested.
Soil Tests / Tissue Tests: the full lab tables. Import lab CSVs — sites, depths and years are preserved; each year archives separately.
Imagery: pick paddocks → load a single date, build the whole season's biomass curve, or compare 5 years of peaks. Save any layer to the paddock's library: ⭐ Save names where it goes (“⭐ Save Home:07 to Zones”) — the paddocks the picture was built for, with the index and colours it was built with, even if you have clicked other paddocks since. When the selection has moved on, the caption says so and Rebuild for N selected builds it again for the paddocks picked now.
Four indices, picked with the chips beside the colour ramp and carried on the saved layer: NDVI (green biomass — flattens once the canopy closes), NDRE (red edge — chlorophyll and canopy nitrogen, keeps working after canopy closure; the mid–late season index for N), MSAVI2 (soil-adjusted — early cover on pale sand where NDVI mostly reads the soil) and NDMI (shortwave infrared — canopy water content, moisture stress and drying-off). NDRE and NDMI use 20 m bands, so they are a little coarser than NDVI. The season curve stays NDVI; clicking one of its dates loads that date in the index you have picked.
Zones: each paddock's saved-layer library. Search paddocks, or filter with the pills (All, Has zone map, Yield, Satellite, Soil & terrain, As-applied); each paddock is one row (a table on a computer, a card on a phone) with its zone status, what it has to make zones from and its Zone Studio button. Tap the paddock itself for its zone maps and saved layers; every layer wears a kind chip (Yield, NDVI or its index, Soil, Elevation, Radiometrics — as-applied maps stay plain) and zone maps wear RX (green once a pass uses the map, “RX · no plan yet” until then; a version 2 map whose plans are still on version 1 reads “RX · plans on v1”, and its tooltip counts them — those plans keep version 1's zones). 🔗 Link to a plan on a zone map's card lists the paddock's planned passes for the season; pick one and the same zone-% picker as Field Records opens with that map chosen — the pass keeps its own rate and the map sets each zone's % of it. A pass with several products asks which one the zones vary (a pass already linked keeps the lines it had). Tap a layer for its picture with the legend it was painted with: its own colour ramp and index, or for a stepped map (a two-rate seeding run) a swatch per rate with its share. Delete sits in red at the foot of the sheet and asks once more. Paddocks follow your paddock list: a boundary uploaded under its own name shows as that paddock (its name in brackets), and layers saved under either name are found. Zone studio generates 2–5 zones from any weighted blend of layers, or draw them by hand with full vertex editing.
Season biomass chart (Imagery → Season): the whole farm in dark ink and up to four selected paddocks, each with its own colour and dash; hover, or tap on a phone, for the date, each line's mean and the cloud on that pass; a click loads that date. Pick paddocks with the chips above it — past four, the legend says how many more are selected. On a phone the chart scrolls sideways inside its own frame instead of shrinking its labels.
Imagery says what it hides: the cloud figure on a date chip or a season-curve point is the whole 110 km satellite tile's — a clear farm can sit under a cloudy tile and the reverse — so once a date is loaded the caption gives the share of YOUR paddocks the per-pixel cloud and shadow mask removed (“7 % of your paddocks hidden by cloud (shown as gaps)”, or “clear over your paddocks”); hover a curve point for both figures, and the whole-farm curve now skips a pass with half or more of the farm under cloud, as the paddock lines always did. A peak biomass caption lists each paddock's pass with how clear it was and the share left as gaps (“Home 08 · 4 Sep · 64 % clear — 36 % gaps”); gaps are skipped by the zone engine. A pass whose scene had no readable cloud mask reads “cloud not checked” rather than a clear figure. Rebuilding a peak after saving one, or during a running season, builds afresh instead of handing back the earlier picture. A multi-year layer names a year it had to leave out and why (“2021 skipped: no clear pass”), says how many pixels are missing a year, and its library name lists the years it USED with the skipped ones after. In the Zone studio each loaded source says what it hides under its name: a yield or as-applied map “measured 86 % · filled 14 %” (the share of the drawn ground the fill invented between machine passes — it takes its neighbours' values and can never show as poor on its own), a satellite layer “7 % of this paddock hidden (gaps)” or “clear over this paddock”, a multi-year one its skipped years.
Saved satellite layers load from the device: ⭐ Save on Imagery now keeps the layer's value grid with its picture, so the Zone studio reads a saved date, peak or multi-year layer off this device in a moment instead of searching and reading the satellite again every session (and it works where there is no signal). A layer saved before this is read from the satellite once, on its first studio use on a paddock it is filed under alone, and kept from then on; “· from this device” under the source says it loaded locally, and the ↻ beside it reads the imagery again and replaces the kept copy. The save message now tells the two outcomes apart: “Saved to Home:07 ✓ · copied to your cloud”, or “Saved to Home:07 on this device — too large for the cloud copy (5.2 MB, cap 4 MB)” when the cloud copy was skipped (it used to say Saved ✓ either way, and the phone then found no snapshot). Saved files no longer carry the three display-only arrays that bloated them.
Layers across devices: layer definitions sync with your account; the pixel files are copied to your cloud when fetched, and once a day (on a computer, never on its own on a phone) PaddIQ sends any still waiting — a failed or offline upload, a layer saved while signed out — except as-applied maps, which are usually just a spray pass and stay on the device that fetched them. Another device, or a worker's phone, pulls each layer from the cloud the first time it opens it instead of fetching it from John Deere or the satellite again. 'Send waiting layers now' on the Zones tab runs the catch-up on demand (small batches on a phone) and says what it found. Layer files live in the farm owner's cloud folder, so the catch-up and the button are the owner's: a team member's device shows “Layers are sent from the farm owner's device” instead, and its daily run sends nothing. A file over 4 MB compressed is skipped and needs fetching on each device. Deleting a layer removes it from every device: the deletion syncs with the layer list, so another device's copy can't bring it back, and it now takes every file the layer owned — the main grid and each measure file (elevation, moisture, soil redness, radiometric bands) on this device and in your cloud folder (older deletes left those behind; they are not listed anywhere and are harmless). If a layer was deleted on one device but its file is still on another, that device's Zones tab shows it under 'deleted on another device' with a Restore everywhere button. Soil colour and radiometrics are one per paddock; duplicates left by older versions are merged into one copy the next time the Zones tab opens, keeping its files.
🌏 Get open layers (per paddock, Zones tab): two free national layers fetched straight from Geoscience Australia for zoning — Soil colour (Barest Earth: every Sentinel-2 pixel at its barest 2017–2020, 10 m, so colour = soil; brightness separates pale sand from darker loam, redness picks iron/red soils) and Radiometrics (airborne gamma K / Th / U, ~100 m — coarse but real). Both CC BY 4.0, attributed on the layer. There is one of each per paddock (per source for soil colour); re-fetching replaces it, and duplicates left by earlier versions tidy themselves the next time the Zones tab opens. John Deere exports also carry the receiver's Elevation — new syncs save it as a measure, the library shows one ⛰ Elevation row per paddock (from the newest layer that has it, harvest preferred), and the studio offers it plus a Relative elevation surface (low spots − / rises +). Every layer preview draws the paddock boundary over the snapshot. An as-applied layer's headline is the applied rate; when Deere logged none it falls back to the target rate, never fuel. All of these appear as tick-able sources in the Zone studio alongside yield, biomass and as-applied maps.
Computed sources in the Zone studio (no fetch needed): 📈 Yield productivity — each season's yield map divided by that season's paddock mean, then averaged, so 1.3 means 30% above the paddock every year (a season saved as one map per crop is divided crop by crop, each by its own mean; a map with two crops in it, or a wet-mass or volume column, is left out and marked ⚠ in the source list); 📉 Yield stability — how much that ratio swings between seasons (low = steady ground, high = the season decides; needs 3 seasons to trust); 💰 Gross margin for the current season and the multi-year average — the same grids as the Farm Map overlay. Zoning on productivity + stability is the published way to find ground that reliably earns inputs versus ground that reliably doesn't.
Zone studio v2: sources are grouped (yield & economics, biomass, soil & terrain, radiometrics, as-applied), each group folded until you open it (a group with a ticked layer opens itself); as-applied folds year → pass kind (seeding, fertiliser, spray). Layers carry the same names as the Zones library. The left column scrolls on its own. A Layer slider top-right of the map sets how strongly the ticked layer shows over the satellite image; each kind of source paints in its own colour family (yield red → green, biomass straw → green, moisture blues, soil browns, radiometrics purples, elevation green → brown → pale), with the family's swatch beside the slider. Hover a zone on the map (or its row in the list) and it lights up with its name and hectares while the others fade. The Biomass group is always listed; with nothing saved for the paddock it tells you to save a layer on Imagery first. After Generate, a Breakpoints bar sits along the bottom of the map: the cut points between zones on the ticked layer's own scale (t/ha for a yield map, NDVI, or 0–1 for a blend) with each zone's share of the paddock. Drag a handle and the zones re-cut on release; Auto hands the cuts back to the method. A Rates block under the zone list takes one product and a rate per zone (kg/ha, t/ha for lime and gypsum, or L/ha — tonnes is a display choice, the record still carries kg/ha) and shows hectares, product needed per zone, the paddock total, its cost at your Pricing price, and the flat rate it equals. Totals follow the rate's unit: a line in kg/ha, t/ha or g/ha totals kg (shown as t from 1,000 kg), one in L/ha or mL/ha totals litres — hover the total for the sum written out. Attach to picks where the rates go: a new planned record of the purpose's type, named as Field Records names it (Nitrogen → Fert — In-season, Bar fert → Fert — DTT, Lime / gypsum → Ameliorant, General → Fert — Pre-seed), or one of the paddock's existing planned records — a seeding record varies its seed rate. Either way the layer saves and the record carries the flat rate with each zone's %, which is what the Rx export and the plan read (seed rates export as a SEED column). Only the line you rate varies: attached to a seeding pass carrying Seed · Mace and MAP, the seed changes zone by zone and MAP runs its flat rate in every zone — the Rates block says so before you link. Every zone needs a rate before Create or Link: a blank box shows the flat rate greyed (“flat 89”) but nothing is applied from it — the button stays off and names the zone (“Medium has no rate”), and Fill blanks puts the flat rate in every blank zone (the attached line's own rate, or the average of the zones you typed for a new record). Type 0 to apply nothing in a zone; it shows amber. The sketch also saves with the layer, so linking that layer from a record's 🗺 VRT chip in Field Records prefills the zone % when the product or seed matches. Harvest and as-applied grids are gap-filled across the passes before zoning, so a 1 Hz yield map gives whole zones, not ribbons. Older 1 Hz harvest maps that showed stripes between passes are re-drawn gap-filled the first time they open. ✨ Suggest lets the data pick the number of zones (k-means 2–5 scored by silhouette; fewer wins unless more is clearly better). 🧭 Stability classes → zones (3+ yield seasons) makes the four Blackmore classes directly: high/low productivity × stable/unstable. Set your machine width: generating removes every zone finger or sliver narrower than that width (the ground joins the neighbouring zone) so nothing on the map is thinner than the bar or boom that applies it, and the studio still flags a zone whose average width is under one pass and any layer with more than four rates. Smooth zone edges rounds the raster staircase twice over. 📋 Zone card shows, per zone, the mean of every ticked source, yield productivity and stability, the soil-test sites that fall in it (topsoil only — several sites are averaged when they agree, outliers named; subsoil on its own lines) and three numbered sampling points sitting deepest inside the zone — sample there, topsoil and subsoil. Tag the layer's purpose (Nitrogen, Bar fert, Lime/gypsum, Seed) on save. ↶ Undo (or Ctrl+Z) steps back through every zone change — generate, re-cut, draw, vertex edit, simplify, add, remove. To draw into a particular zone, press Draw polygon then click that zone's row in the list before drawing. A class puts every pixel of the same value in one zone wherever it sits, so two different soils that happen to read alike land together — 🎯 Move parts fixes that: click the row of the zone they should join (Add zone first if they need their own rate), then click each separate piece on the map and it moves across whole. Blending in Soil redness or Radiometric K with the first layer usually separates pale sand from red loam before you get to that. On the Farm Map, a margin overlay's paddock panel has 🗺 Make zones from this, which opens the studio with that map pre-ticked. Nothing you draw is lost by a mis-click: ← Zones with unsaved zones or rates asks “Discard unsaved zones?” (Keep editing, or Discard); switching to Imagery or Prescription, or a refresh, keeps the unsaved work as a draft on this device only (never synced, never in a backup) and the studio restores it the next time it opens on that paddock and map — “Unsaved zones restored — kept 10:32 today”, with Discard draft to go back to the map as saved. ⭐ Save, Create planned record and Link clear the draft. Create planned record and Link rates to that record now land on Prescription with that plan's card lit — “✓ Planned Urea for Home 07 created” — ready to Export Rx or Send to Operations Center.
Zone studio on the phone: the map fills the width (about half the screen tall) with the Breakpoints bar along its foot — the grips are thumb-sized — and under it the four steps, Layers · Zones (n) · Rates · Export, as one row of numbered buttons. Layers (Evidence) has the Protein + yield card and the layers zones are generated from; Zones has a card per zone with its hectares and rate (tap one to rename it, type its rate or remove it), Add zone, Zone card, machine width and each zone's yield and protein; Rates (the same Rates block as the computer, with N rates from protein + yield above it); Export has the map's name and purpose, the Rx checklist and Create planned record. ← Zones, ↶ Undo and ⭐ Save sit in the header. Drawing a zone, dragging its corners and Move parts need a mouse — the phone says “Edit shapes on a computer”; everything else, the zone card and grain samples included, works there. Nothing stored changes between the two layouts.
Protein + yield in the Zone studio (Planning → Imagery & VRT → Zone studio, step 1 Layers): beside the map (under it on a phone) a card reads the paddock's yield map — the newest with protein first; pick another in the list. Layers: Yield × protein (each spot's yield against the paddock average and its protein against the threshold — four classes: High yield · low protein = likely ran out of N; Low yield · low protein = likely short of N; Low yield · high protein = water or another limit, more N won't help; High yield · high protein = N was enough), Yield, Protein, N removed (each spot's yield × its protein, turned into kg N/ha the way the receival standards report protein — wheat at 11% moisture, barley on a dry basis; any other crop has no verified factor and shows no N figure) and Productivity when you have two or more yield seasons. Each layer has its stepped legend, the mean, the middle 80%, the variation (CV) and its area, and a histogram in the map's colours with the threshold drawn on it (barley also shows the 9–12% malt window — a quality band, not an N test). Under it, what it says in words — “31 ha high yield, low protein — likely ran out of N” — and how your hand grain samples compare with the map (“Your 3 hand samples differ from the map by 0.4% protein on average”). Every number on the card reads the same cells and counts hectares one way (since 28 October 2026): the statistics are on the yield READINGS inside the boundary — a logged 0 t/ha is no reading, as on the yield map, so the Mean matches Yield map tools' Statistics — and a line under the layer chips says what they are out of: “76.5 ha mapped · statistics on 12,760 readings (31.9 ha under the GPS points)” on Yield, “69.6 ha with yield and protein (36.6 logged, 33.0 estimated) of 76.5 ha mapped · 6.9 ha with no protein” on the protein layers. A 1-a-second John Deere file logs the cell under the GPS receiver, not the whole front, so the readings sit on roughly 40% of the ground; each reading stands for its share of the mapped ground, and the legend, the histogram, the Area tile and the hectares in What it says are all counted that way — so they add up, and the classes add to the ground that HAS protein (ground with yield but no protein is its own line, “not classed”), never spread over the whole paddock. The Yield view also says when the map's name reads differently (the file's average as John Deere sent it, before your header correction and cleaning). The protein layers say how much protein the sensor logged, how much is estimated, and why the rest has none (further than 2 pass widths from a reading). The threshold: wheat 11.5% (from Australian protein-map work), barley 10.2%, or type your own. Include estimated protein (filled gaps) is off unless you turned Fill the gaps on for that map in Yield map tools; on, the estimates are hatched and every number built on them says so. Zones from these classes makes the zones from the four classes (cleaned to your minimum zone size and machine width) — offered only when protein covers 80% of the harvested ground, so a map with protein on every other pass needs the estimates first. Protein is read after harvest: it flags a crop that ran short of N, it doesn't measure the yield lost. Since 28 October 2026 the Yield view's numbers ARE the yield map's own Statistics (Yield map tools) — the same readings, after the corrections you chose (header correction, passes, cleaning, weighed tonnes — the line under the numbers names them), and the same robust spread around the median, so a handful of absurd monitor readings can't make it read hundreds of per cent; Protein and N removed use the same spread. Under the numbers a line says what Clean monitor errors does on this map: off — how many readings it would take out, how many of the low ones, and the mean it would move to; on — that the low readings left passed its test (a run of low readings together: a headland, a turn or poor ground). 🛠 Correct this yield map (beside the map picker, and on each yield map in Generate from layers) opens the map's own tools over the studio — Paddock tonnes, Headers, Corrections, Missing readings, Statistics, the map big beside them (the whole screen on a phone). Changes save as you make them. Save & back to Zone Studio goes back with them; Back without changes puts back the corrections and weighed tonnes the map had when you opened it (a fetch from John Deere and header names stay). Your zones, step, ticks and rates are exactly as you left them. Back in the studio the analysis reads the corrected map again; zones already made from that map are NOT remade — an amber note says “This yield map was corrected after these zones were made — Generate again to use it”, with the button (Undo brings the old zones back).
🧪 Protein map against what you delivered (Zone studio → Layers → Protein, Yield × protein or N removed; and Yield map tools → Protein): PaddIQ averages the map's measured protein, weighted by each spot's yield (as you corrected it — estimates never count), and sets it beside the protein on your harvest record (the CBH figure you imported or typed on the Harvest page): “Map reads 0.9 points below your delivered 11.4%”. An uncalibrated header sensor can read about a point out — a whole band of the 11.5% rule. Shift the map to match delivered adds that gap to every protein reading and estimate on that map — the protein layer, the classes, zones made afterwards, N removed and the N rates all read the shifted map; the readings themselves are kept, and Undo takes the shift off. Within 0.2 points it says the map agrees; more than 3 points apart it says that is not the sensor (check the record is the same paddock, crop and basis). Zones you already made stay as they are — make them again to use the shifted map. Where two headers both logged protein, it compares them where they ran side by side, the way two yield monitors are compared, and flags more than 0.3 points apart: calibrate both sensors on one sample set.
⚠ When the season makes protein misleading: the protein rule (under 11.5% = ran short of N) holds for seasons without a dry finish. On the protein views in Zone studio, the N rates step and Yield map tools → Protein, PaddIQ warns — “Dry finish in 2025 — high protein here may mean water ran out, not spare N” — when that season's August + September rain was in the driest three tenths of your farm's own rainfall record, or its April–October rain in the driest third, and when you left that paddock-season out of the learning record as Frost (PaddIQ never guesses frost). A crop given plenty of N early can also hay off in a dry finish. Hover the warning for the rain figures. The rates you use carry the warning to the plan. Where “dry” is drawn is PaddIQ's choice, not a published figure.
📅 Zones from protein, season by season (Zone studio → Zones and Rates, when the zones were made from the yield × protein classes or a protein layer): a card under the zone table reads every yield map of the paddock with protein — one per season — and shows each zone's main class in each (ran out of N, short of N, water or other limit, N was enough; “no N meaning” for canola or a crop PaddIQ has no protein target for; “dry” on a dry season). A zone is labelled a Stable N zone only when at least two seasons give it the same class and one of them was not a dry season; otherwise it says One season — treat as a guide, or Treat as a guide when the seasons disagree. Nothing is held back — it is a label. No published rule says how many seasons a protein zone needs; two is PaddIQ's line.
🧪 Protein as a zoning layer (Zone studio → Generate from layers → Yield & economics): each yield map with protein adds two layers — Protein shortfall below target (how far each spot fell below the crop's target, wheat 11.5%; 0 at or above it) and N removed (each spot's yield × protein, as kg N/ha). Both rank high values into the higher-N zones, and neither can be flipped: raw protein is never a blend layer, because high protein can mean surplus N or a water limit and a blend can't tell them apart. Canola, and a crop PaddIQ has no protein target for, is listed but can't be ticked — its protein has no N meaning, so it is never filled with zeros. They use the map's corrections, its checked protein estimates and any shift to match delivered, and need protein on 80% of the harvested ground. ↕ High = more / High = less: every other ticked layer (yield, biomass, soil, elevation) has a direction beside its weight. High = more (the default — what every zone map before this used) ranks high values into the higher zones; High = less flips it, for a layer where high values mean poorer ground. The choice is saved with the zones and shown in the library (“high = less”). The protein histogram draws the 12.5% line beside the 11.5% one: above 12.5% the crop had more N than it used. Protein-based N lines carry a sandy-soil note — the work behind them was on loams over clay; on sand, test with a strip first.
N rates from protein + yield (Zone studio, step 3 Rates): pick a strategy — PaddIQ N rec, adjusted by zone (the paddock's own N recommendation from Planning → Fertiliser for the studio's season, 20% more in zones where low protein says N ran short, 20% less where high protein on low yield says water or another limit held yield, unchanged where N was enough), Replace what was removed (each zone gets back the N its grain took off — only where protein was at or above the threshold; a zone below it uses the adjusted rate and says why), or Type my own. Every rate is held inside the recommender's own band (0.4–2.5 × the budget gap). Each zone shows its kg N/ha, the product rate (Urea or the N product you pick, priced from Pricing) and one line saying why; the paddock total reads against the same rate flat (“2,580 kg N vs flat 2,700 — 120 kg less · $4,128 vs $4,320”). Use these rates puts them in the Rates table below — nothing is saved; type over any zone and the plan says “then edited by hand”. Variable-rate N pays modestly (an SA N-Sensor trial gained 0.8%), and the card says so. Step 4 Export shows the Rx checklist the Prescription card will run, then Create planned record (or Link) saves the zone map and the pass and opens it on Prescriptions to Export Rx or Send to Operations Center. Rates built on estimated protein carry it: the pass's notes, and a ⚠ on its Rx checklist — “Rates use estimated protein on 48% of the paddock”.
Satellite layers in Zone studio (NDVI, NDRE, NDMI — a date, a peak or a multi-year peak) look exactly as they do on the Imagery tab: the same colours (the ramp the layer was saved with, else Imagery's high-contrast red → blue) and the same value range, shown beside the Layer slider (e.g. 0.21 ▬ 0.78 NDVI). Every other layer keeps the one map scale (dark red low → dark green high). While a layer is showing, zones are drawn as outlines in their own colour so the layer underneath reads in its own colours; hover a zone to fill it, or slide Layer to 0% to see the filled zones.
🧪 Soil tests by zone (Zone studio): every soil-test sample with GPS inside the paddock shows on the map the way the Soil Map (Soil → Soil Map) shows it: a dark dot with value chips beside it — one chip per depth (0–15 cm on top, 15–30 cm below), the value of the analyte you pick under the map, coloured by what it means (red constraint / low, amber watch, green good, blue high; an analyte with no WA interpretation sits on the map colour scale). “—” means not tested — a blank on the lab file, or a 0 the file printed for a test it didn’t run (PBI, OC, pH, Colwell P or K and the like can never really be 0, so a 0 is never shown or used as a result). The year above the chips is outlined amber when the test is 3–4 years old and dashed red when it is over 4 (re-test); a pencil marks one typed in the studio. Under the map: the analyte, Depth (show one depth or both) and Years (Latest = each site’s newest test, or pick years to see them side by side) — these change the map only; the zone table and the rates use every site. Sites closer together than a chip’s width are drawn as one pin with a number on its dot — zoom in to split them. Hover a site (tap on a phone) for its card: year, site, depth, then Colwell P, Colwell K, PBI, pH and OC a row each, one column per depth; it opens on whichever side fits inside the map. Every year is shown, and a test filed under another paddock but sampled on this ground says so. Tests without GPS (typed by hand, or a lab file without coordinate columns) can’t be drawn — the line under the map counts them. On the Zones step, Soil tests by zone lists each zone: its own sites and year, or not sampled (the paddock’s own test stands in, greyed), with the five values (topsoil only, the newest year in that zone — older years are listed, not averaged in). A zone whose samples are all from 10 cm down (10–30, 15–30 cm) reads subsoil only: those rows show as subsoil, and the P and K rates use the paddock’s topsoil test instead (or the crop’s removal when there is none) — a subsoil Colwell P or K is never read as topsoil. The same holds for the whole paddock: when its newest test is subsoil only, the Balance and Fert Plan walk from the newest 0–10 cm test (the paddock sheet names the subsoil-only year), and with no 0–10 cm test at all the Balance reads “no topsoil test — subsoil only”. + Test opens the zone card at that zone: type the lab results for a sample taken at dot 1 (the point deepest inside the zone — furthest from the fence and from the next zone; dots 2 and 3 are the next-deepest, spread apart), or Attach a lab result that came without GPS to that zone. It is saved in your soil tests (Soil → Soil Tests) with the spot’s coordinates. A sample in a year that already has a lab test is added beside it (the paddock’s figures stay); a sample in a new year becomes that year’s paddock test (the mean of the year’s zone samples) — newest year wins in the Balance. ⭐ Save soil zones saves the zone map with each zone’s soil; it then appears under Generate from layers → Soil & terrain as Colwell P / K / pH… by soil zone, to zone on or blend with yield, and its zones carry the P & K rates.
P, K and S rates by zone (Zone studio, step 3 Rates): the N · P · K · S switcher follows the product in the Rates table (Agflow Xtra → P; pick another any time), and the zone table swaps its columns to that nutrient — removed kg/ha (the zone’s yield × the crop’s removal per tonne), the zone’s soil value, the rate and the product rate. Strategies: PaddIQ rec by zone (the Fert Plan’s own rule run on each zone’s soil test and yield: P builds toward critical Colwell P for its PBI — about 20 below PBI 100 — K and S toward critical for the soil type from the soil bank at sowing, K at most 60 kg/ha a season including removal, no build-up at all from a test over 4 seasons old), Replace what the crop removes (removal only), or Type my own. A zone with no test of its own uses the paddock’s test (it says so), or the crop’s removal when the paddock has none. Each zone’s yield is its mean on the yield map, or the plan’s target spread by each zone’s yield (better when the map was another crop). Below PBI 56 the P rate is a starting point — Colwell P is a weak predictor there. Each zone line says what else the product puts on (“also puts on 21 kg N/ha, 7 kg S/ha”) and, with the N card’s rates, the N in all. Three tiles compare the zones with the paddock’s flat rate in kg and $. Use these rates fills the Rates table; Create planned record / Rx export as for N.
Zone studio on a computer is one screen with one scroll: the map stays put on the left at the full height of the window, and everything else — the steps, Your zones, Generate, the protein + yield analysis, the zone tables and the zone card — is one column on the right that scrolls on its own; the page itself no longer scrolls (on a very short window it falls back to the page scroll). The map's + / − / ⤢ (fit the whole paddock) are one control at its top-left. On the phone nothing changes: one page scroll, map on top, sections below. The protein + yield analysis is THIS paddock's: a yield map John Deere logged over several paddocks (one operation over several fields) is cut to the paddock's boundary — the statistics, the legend's hectares, the histogram and the area all read the readings inside it, and the line says “of 373.9 ha in the map, 121.4 ha inside this paddock”. Yield map tools' own Statistics still read the whole map.
Your zones — keep every try (Zone studio, steps 1 Layers and 2 Zones): Generate no longer replaces the zones on the map. Each Generate, Suggest, Stability classes → zones or Zones from these classes adds a version to Your zones (above Generate on a computer, a section on the phone), named from what made it — “3 zones · quantile · NDVI 2 Sep 25 + Rel. elevation” (tap the name to rename it). The new one is ticked and the last one stays ticked, so both show: several ticked draw as outlines over the layer (the ★ one in its zone colours, the others in white, black or grey with their own dash — the little line beside each row), one ticked is filled. Untick the eye to hide one, tick it to see it again. ★ picks the working set — the zones the Zones, Rates and Export steps use (the newest, until you pick another). Your saved zone maps for the paddock are in the list too. Drawing into or reshaping a saved map makes a draft based on it; the saved map is unchanged until ⭐ Save zone layer, which writes over it (asking first when plans use it). Undo takes a new version away again. Drafts are kept on this device only — 10 a paddock; the oldest unticked one goes first and the list says so — and ⭐ Save puts the working set in the Zones library on every device. Delete (asks first) removes a draft; Archive hides a saved map here and in the Zones library without deleting it (plans that use it keep it; Archived ▸ Restore brings it back). Your one unsaved draft from before this change is the first draft in the list.
Season plan and zone totals (Zone studio, step 3 Rates): put several passes for the year on one zone map. Set a pass in the Rates table (a product and its zone rates — from the N or P · K · S cards or typed), pick its pass type and date under Season plan on these zones, and press + Add to the plan; the table clears for the next pass. A pass you picked under Attach to stays that planned pass — its zone rates go onto it, it is never doubled. Passes already on this map, flat planned passes and done passes are listed too (Edit loads one back into the Rates table). 📋 Save the season plan saves the zone map once and makes each new pass its own planned record linked to it. Zone totals (under the map) add every pass up per zone: N, P, K and S in kg/ha — planned, plus what was applied to date — against the zone's target (the N rate from the N card or the paddock's N rec; P, K, S from the Fert Plan's rule on the zone's soil test and yield, removal where there is no test), the gap (▼ short / ▲ over outside 10% or 2 kg), $/ha and $ per zone and for the paddock, and a bar per zone with one segment per pass. A product with no analysis or no price is named, not counted as 0. Unsaved passes stay on this device with the rest of the studio's draft.
One colour per zone, everywhere (Zone studio on a computer): a zone's colour is its place in the list, low to high — the same colour on the list dot, the map, the hover outline, the Breakpoints bar, the “Drawing into” note, the Rates and Zone card rows, the Zones library and a plan's zone table. Three zones read red, amber, green; two read amber and green; remove a zone and the rest re-colour as a set, so two zones never share a colour. The stored colour on an older map is not repainted and not rewritten. One “too narrow” rule as well: a zone that averages narrower than ONE pass of the machine width is flagged under the zones and shown amber in the zone card (the card used to go amber at two passes while the warning stayed quiet). The studio's panels are now cards in the app's own tokens — 13.5 px text, mono numbers with units, Generate as the one primary button, a skeleton over the map while a layer loads and “Tick a layer or draw a zone” on an empty map.
Zone card — true numbers, under the map: 📋 Zone card now opens below the map (it used to float over it, behind the Breakpoints bar) as one card per zone — ■ Low · 42.1 ha · ~38 m wide, then a line per figure with its unit: Yield 2023 1.84 t/ha · 81 % measured, Colwell P 22 mg/kg (0–10 cm, 2 sites), Stability Low · stable 70 %, Grain 2026 11.2 % protein (2) [+], Sampling dots 1 · 2 · 3 [Copy coordinates]. The figures are what was measured: a yield (or as-applied) mean reads only the cells the monitor logged — the map still fills the gaps between header passes to draw the zones, but that filled ground is left out of the number, and the share logged is shown. Soil figures are the topsoil only (the same rule the nutrient balance uses), with any subsoil on its own lines — a 10–30 cm row is no longer averaged in or called an outlier. Stability shows whichever layer is ticked (it used to vanish once any layer was ticked). Hover any number for where it came from. Sampling dots name themselves on hover instead of all at once; Copy coordinates puts a zone's dots (or Copy all dots, every zone's) on the clipboard as latitude, longitude. On the phone the same cards stack under the tabs. Nothing stored changes — the card's figures may read differently from before because they no longer count filled-in ground or subsoil.
Zone studio remembers, tiles, and is quick: a zone map now saves what it was made from — the layers and their weights, the zone count and method, Min zone, Smooth edges and the machine width — as they were when you pressed Generate (ticking a layer afterwards no longer changes the record), and opening the map ticks those layers and sets those sliders again. Drawing, dragging a corner, moving parts or removing a zone marks the map hand-edited: the Breakpoints bar greys out and says dragging re-cuts and replaces the edits. Stability classes → zones hides the bar (those zones have no breakpoints), and Undo also puts back the breakpoints. Under the zone list a line reads Zones cover 139.6 of 140.2 ha · 0 ha overlap — amber when more than 0.5 ha is in no zone, in two zones or over the fence; hover it for what each means. Generated zones are clipped to the paddock boundary and never overlap (an edge two zones share is simplified once, so both keep the same corners), and since 28 October 2026 they cover the WHOLE paddock: ground inside the boundary with no value on the layer (a strip by the road the header never harvested, a corner, a gap) takes the zone of the nearest ground that has one, small pieces join their largest neighbour, and a strip the smoothed edge leaves along the fence joins the zone beside it — the line under the zone list then says “4.2 ha had no reading and joined the nearest zone” (Generate, the yield × protein classes and Stability classes alike; zones you draw yourself keep their gaps, which run at the flat rate); a drawn shape or a dragged corner stops at the fence and takes its ground from the neighbouring zone; a corner dragged across the zone's own edge snaps back. Zones are worked out on the paddock's own 10 m grid, so the same layers make the same zones whichever was saved last, and dragging a breakpoint is instant — the zones re-cut when you let go. Saved maps keep their shapes; only a new Generate uses the 10 m grid. The Zones library says where each map came from — or source not recorded for a map an older save erased.
Hold the plan's total: in the Zone studio's Rates block, type a product this paddock already has planned (Urea on its in-season pass, say) and Attach to picks that pass for you — the zones vary its rate rather than adding a second Urea pass that the budget, buy list and nutrient balance would count twice. Pick New planned record instead and a warning says the paddock already has it planned, with Attach to that pass. Attached, Hold the plan's total — zones average 90 kg/ha starts ticked: the rates you type set how the zones differ, and every zone is scaled by the same factor so they average the pass's own rate — the Rx column shows what each zone will run at, and the total equals the budget. Untick it to run the rates exactly as typed; the block then says how far the average is from the plan (“Your rates average 100 kg/ha — the Rx puts out 11 % more Urea than the plan's 90 kg/ha”). A chip says where the plan's rate came from: “Rate from Recommendation Wizard plan, accepted 12 Sep” (only while the pass still carries the rate you accepted — a rate typed since reads “changed since the Recommendation Wizard plan”), “Rate from Cropping Card …” or “Rate set in the Zone studio”. The same check is on each Prescription card, on the TOTAL: what the Rx puts out against the plan's rate × the pass's area (its treated hectares, else the paddock's) — “✓ Zones average the plan's 90 kg/ha Urea — the Rx total 9.0 t is the budget's”, or “The Rx puts out 4.5 t Urea — 4.5 t (50 %) less than the plan's 90 kg/ha × 100 ha = 9.0 t the budget counts”, which also catches a zone with no rate, and Field Records' 🗺 VRT box has Rescale to 100 % — one factor on every zone's %, nothing saved until you press Link. Linking records which plan rate the zones were set against.
Link a zone layer to a planned fert record (the 🗺 VRT chip in Field Records) with per-zone % of the flat rate; beside each % the box shows the rate each product will run at in that zone — the same number the Rx file writes. On a pass with more than one line (seed and MAP, or two products), Which line do the zones vary? picks the line the % applies to: the others run their flat rate in every zone and their column says (flat); Every line moves them all by the same %. A new link waits until you pick. An older plan, linked before you could pick a line, opens on Every line — as it runs now; pick one line and Link to change it. A product added to a zone plan later (by hand, or a Cropping Card that now lists it) runs flat until you pick it here.
A zone map a plan uses is never changed underneath it. In the Zone studio, dragging a breakpoint, Generate or Stability classes → zones keeps each zone's identity when the number of zones stays the same (the lowest zone stays the lowest, and so on), so the rates you typed stay on their zones. Saving a map that Field Records use, after its zones changed (shape, a zone's name, or a zone added or removed), asks first: “This zone map is used by 2 plans”, listing each plan and when it was sent. Save as version 2 — plans keep version 1 is picked for you: the plans keep the zones they were made on, so a file already sent stays true, and version 2 becomes the map the Zones library and the Field Records picker show (with a v2 tag). Move plans to the new zones (by rank) carries each plan's zone % to the zone in the same place, low to high; it is only offered when the zone count is unchanged, a plan already sent then reads “changed since sent”, and an Undo right after saving puts the plans back on version 1. Completed passes always keep the zones they were applied on. A map nothing uses, or a save that only changes the map's name, purpose or rates, saves in place. Prescription shows which version each plan is on. Export and Send refuse a plan with a zone that has no % — “Zones changed since rates were set — open the plan” — and the plan's 🗺 VRT link in Field Records names the zones to fill.
🎯 Rx (Prescriptions): every VRT-linked plan, every season, as a list of cards like Inventory. Each card carries the pass type's icon, the paddock, what varies and the pass (“Urea · Fert — In-season · 1 Jun”), the rate range and how many zones, the line's total on the right (“3.7 t”), and a status chip — To do, Exported or In Operations Center — with the latest word on where it has gone. Tap a card and its sheet opens: the zone table (each zone's hectares, the rate the machine will run there in the line's own unit, and what that comes to), a row for the ground outside the zones at the flat rate, the totals with their ⓘ, the checklist, and the commits along the bottom — ⬇ USB file, 🚜 Send (or Send again) and Remove (red). ＋ New prescription starts one from a pass you have already planned: pick the paddock, one of its planned passes this season, then Pick the zone map and rates opens the same 🗺 VRT picker Field Records uses — the map, which line the zones vary and each zone's %. The sheet first says what varies — “Varies by zone: Seed · Mace 55–85 kg/ha (flat 70) · Flat in every zone: MAP 80 kg/ha” — which is exactly what the file writes (a flat line goes out at its flat rate in every zone, same columns as before). An older plan whose rates were set for one line in the Zone studio but that varies every line shows Vary <line> only: it asks first, changes only that plan, and Undo puts it back. A plan whose varied line is no longer on it says so and won't export until you pick a line on its 🗺 VRT link. Each card shows each zone's rate in the line's own unit (Low 63 kg/ha, not 70 %; the % and hectares are on hover) — the number the Rx file writes — and a Total per product in its own unit: a lime plan in t/ha totals tonnes, a trace element in mL/ha totals litres, priced at your Pricing price. The ⓘ beside a total writes the sum out (each zone's hectares × its rate, plus ground outside the zones at the flat rate, and the price used); a zone with no rate is not counted and the card says how many hectares that leaves out. Under the zones each card shows the file's name and a checklist that runs before anything leaves — ✓ what was checked and found right (the map is this paddock's, every line has a rate, every zone has a rate, the zones cover the paddock), ⚠ what you should know (a zone at 0 %, ground outside the zones that the display's 'rate outside prescription' must cover, no date on the pass, two passes of the same product planned on the paddock this season — the budget counts both, a bar-fert zone map on its own DTT pass when the paddock has a seeding pass planned — bar fert goes on the seeding pass), ✗ what stops it (a line at 0 — the file would write zeros, a zone with no rate, a map that is another farm's paddock's, a deleted map, nothing varying). A ✗ turns Export and Send off with the reason written on the card; Tick all and Send all skip those plans and say why. File names read Rx_Home-01_Urea_0601_a3f9.zip — farm, paddock, product, date, and a 4-character tag from the pass, so Home 01 and Dodds 01, or two products on one day, never share a name; a long paddock name is shortened, never the date. Files already exported or sent keep their old names. ⬇ Export Rx downloads the John Deere USB zip (unzip at the USB root, it holds the Rx folder). 🚜 Send to Operations Center uploads the same file straight into your Operations Center Files — Foundational tier, no Ultimate — then in Operations Center open Files and press Send to machine; the file is read back after upload and the card says what Operations Center answered: “✓ In Operations Center Files (your organisation) · sent 14 Sep” when it is there, “⏳ Uploaded — Operations Center was still processing it” when it hadn't finished when PaddIQ last looked (check Files there before Send to machine), “Uploaded — can't confirm it landed” when Operations Center didn't hand the file back, and “✗ Operations Center rejected the copy” (red) when it refused it. If Operations Center files it as something other than a prescription, the card shows the type it gave. PaddIQ does not go back and ask again later. The file goes to the first John Deere organisation with PaddIQ access switched on; the card names it after the send. ⬇ Export Rx is recorded too (“⬇ USB file exported 3 Jun”). Each send and export remembers a fingerprint of the file — the rate columns, every zone's rates and every zone's shape — so the card knows when the plan no longer matches what went out, and says what changed: “⚠ Zones redrawn since sent 14 Sep”, “⚠ Urea 90→100 kg/ha since sent”, “MAP added”. Notes, the date, the rig or the file name don't change what the machine applies, so they don't flag it. A plan sent before this (no fingerprint) can only tell it was edited after the send (“⚠ Edited since sent”), not what changed. The chips filter: To do (never sent or exported, or changed since), Exported (USB file, unchanged), In Operations Center (uploaded, unchanged); a season picker appears when more than one season has plans; inside a group, to-do plans sort first. With John Deere connected each card has a Tick pill: Tick all to do ticks only plans still to do, Send ticked sends them one after another, and sending a plan that is already in Operations Center asks first — Operations Center keeps every upload as its own file, so a second send adds a copy beside the first. Remove (in the sheet, red) deletes a prescription: one the Zone studio created goes with its planned record; one linked from Field Records keeps the record and just loses the zone link. Nothing already in Operations Center is touched. In Field Records a planned pass's 🗺 chip says where its prescription has gone — “Zone map” (linked, not sent), “Zone map · sent 14 Sep”, “Zone map · changed since sent 14 Sep”, “Zone map · exported 3 Jun”, “Zone map · rejected”, “Zone map · deleted” — the same answer the Prescription card gives; hover it for the map's name and the full line. The 🗺 VRT picker lists only this paddock's own zone maps (matched on farm and paddock, so Home 01 never sees Dodds 01's zones), each named with its farm and paddock (“Home 20 · Lime map”); a map saved long ago without a farm says so. This is the only place a prescription's plan is removed: Nutrition and Cropping Cards update its rate in place but never delete it or turn it back into a flat rate. Send again asks first, then uploads a fresh copy — delete the old one in Operations Center Files. Set 'rate outside prescription' on the display to the plan's flat rate.
Zone maps and grain samples across devices: they sync with your account and merge — a zone map (or a hand grain sample) saved on the phone and another saved on the PC both stay, even when the PC hadn't synced since. When the same map was saved on two devices, the later save wins. Deleting a zone map hides it everywhere (it is kept, hidden, in your data, so a device that still had it can't bring it back); a plan linked to it loses its zone map, as before, and deleting version 2 of a map puts version 1 back in the pickers. If the device is out of space, ⭐ Save says “Not saved — device out of space” and the studio stays open with your zones, nothing changed; a grain sample says the same under its Save.
🎯 Rx check (top of Prescriptions): a banner counts the zone plans that are already broken on your farm, in every season, and the zone maps holding rates no plan uses — “3 zone plans won't do what they say”. Review opens the list. It looks for a plan with no rate for some or all of its zones (the zones were re-cut or edited after its rates were set — Export and Send refuse it), a zone map that was deleted or belongs to another paddock, a plan whose varied line is no longer on the pass, a zone at 0 % (nothing is applied there — fine if you meant it), and a zone map edited after the plan was made. A plan that was already sent says the copy in Operations Center may be wrong too. The check only counts: it changes no record or map, and each row says what to do by hand on the pass in Field Records (🗺 VRT). Zone maps that hold rates no plan uses are listed apart; a what-if sketch, or a plan you deleted here, shows up there too, and a map next to a flat pass of the same product is marked as possibly flattened. When nothing is wrong the banner says how many plans and maps it checked.
💰 Margin by zone: open a zone map, open Margin by zone, pick One season or Multi-year and press Compute — one card per zone with its gross margin $/ha on the right, hectares, yield and total underneath, a chip for the gap to the paddock mean and one for any hectares below break-even. Recompute builds the margin map again from your records as they are now (it used to show the previous result). Multi-year averages each season the paddock grew the picked crop group (All / Cereal / Canola / Legume). Same engine and figures as the Farm Map margin overlay; 'Outside zones' is ground the layer doesn't cover. Use it to decide which zone deserves more or less input before you set the per-zone %.

Tips & tricks

“Stretch to crop” rescales colours to the 2–98% range inside your paddocks — differences stay visible even when NDVI saturates late season.
Peak biomass = each paddock on the ONE clear pass (at least 90% cloud-free over it) where its crop was greenest that season — a real picture of one day, not each pixel's best day stitched together. Different paddocks can peak on different dates (canola before wheat); the layer title names the pass. It finds the date from the season curve and reads only that pass in full detail, so it is quicker than before.
Imagery zooms like the Home map: selecting paddocks flies to fit them (clearing the selection goes back to the whole farm), and a newly loaded layer fills the view.
Multi-year peaks average each season's peak pass. A finished season (its window closes on 15 November) that already has a saved peak layer reuses that layer's date (marked ● on the year chips), so it costs one read, not a season sweep. The season still running is always read afresh — a peak saved in July never stands in for a greener August pass — and its peak layer's caption says “season still running — the peak can still move”. Opening a saved peak layer from the Zones tab (↗) rebuilds it exactly as it was saved, pass and all; for a newer peak, press Peak biomass layer. On a paddock the year chips show what grew and what it yielded, so a dry year or a break crop can be left out on purpose. Multi-year averaged peaks are the most stable base for zoning.
Layer definitions sync with your account; the preview images rebuild from fresh satellite data on any device — nothing is lost.
Grey bars under the season curve are cloud cover — points on those dates are less trustworthy.
Generated zones too dense to edit? ✨ Simplify edges in the zone studio reduces every zone to its corner points (run it again for a stronger pass), then Edit vertices gives you corners + midpoints to drag.

📈Financials

The season P&L: gross profit, input costs, yield and income for the farm, each block and each paddock — recomputed live from Field Records × Pricing.

How to use it

Sensitivity sliders start at your own season prices: diesel from Pricing, urea and Flexi N from your library, compound fertiliser as the average of the compounds you have priced, overhead from Pricing → Overheads when any line is priced (else the flat rate in the box top right). A slider marked "default" has no price behind it yet. Ranges stretch with your price, so a dear year still fits. Lease & finance is its own slider, seeded from Pricing → Lease & finance, and sits below operating margin: the sensitivity total and breakeven include it, the P&L shows it as an after-lease line.
Harvested grain is priced by the grade it went. Each harvest record’s tonnes are valued at that grade’s price in Pricing, so a paddock recorded as ASW1 is booked at the ASW1 price, not the crop’s best one. Grade names match however they’re typed (ASW 1 = ASW1). Where there’s no grade, or the grade has no price in Pricing, the crop’s top price is used and the income line says so — open a paddock’s income to see which. Projected crops have no grade yet and use the crop’s top price. The per-crop price shown is the realised one its income was built from, and the margin map and farm history use the same prices.
Top cards: whole-season totals. Farm comparison bars: $/ha profit per block.
Filter by farm, crop or variety. Sort and group the paddock table however you read it.
Expand a paddock for the category cards — seed, fert, chem, machinery & fuel, contractor, harvest income — each drilling down to the actual passes behind the number.
Which passes count, here and on Budget, Overview and the Field Records header: every done pass, and each planned pass still to do. A plan you mark done is its own match: marking the first of two planned top-dresses done leaves the second in the cost, the Order list and the machinery. A done pass that was never planned (typed in as done, or imported unplanned) matches a plan of the same type — counted one for one, earliest plan first, so 4 planned sprays and 1 unplanned spray done still carry 3 sprays of cost — and its products stand in for the planned products of the same kind on that paddock. Plans for a past season, and overdue plans (marked overdue, or more than a year past their date), count nowhere. Fert down the tube that went on with the seeder adds no machinery of its own — the seeding pass carries it. Contractor $ follows the same rule, and a contractor job whose pass has been deleted no longer adds to the total (the job row in Pricing → Contractor is left as it is).
A paddock with Field Records but no crop is not dropped: its costs sit under “Crop not set”, with no income, and a note names them — set the crop in Planning → Crops and they move to that crop. Fallow is a crop: a paddock planned as Fallow sits under Fallow. One with no crop planned that had work done this season, none of it seeding, is counted as Fallow once sowing is over (a past season, or this one from 1 July) — a note says how many. The Season Plan PDF and Planning → Costs & orders count exactly the same paddocks, “Crop not set” included.
The 5yr Average on the Overview averages each season the same way the single season is worked out — machinery and fuel, contractor and levies included — so its profit is no longer higher than any season it is made from. The button shows when two or more seasons have a harvest or an actual pass on file (hover it for which seasons); each paddock is averaged over the seasons it had actuals in, newest first — a planned-only season never counts.
Picking a product anywhere (cards, tank mixes, records, nutrition) uses one picker: search by name or active, or drill Chemicals › Adjuvant › Hasten. Not in your library? Pick it from the built-in catalogue or ＋ add it — it lands in Pricing at $0 under the right Type. The picker also offers products your passes use that this season's Pricing does not list yet — a product typed on a pass this season, or in last season's Pricing or passes (planning 2027 while Exirel was added to 2026, say) — tagged “on 2026 passes” or “2026 Pricing”; picking one adds it to this season's Pricing with its type, unit and nutrients, and last season's price as a starting price.
Export Season Plan / Export Paddocks for spreadsheets that leave the app. The Season Plan PDF carries Financials' own numbers: income as booked (grain at its grade, hay sold), yield averaged by hectares, cost columns that add up to the Total (contractor, levy & freight, adjuvant & trace included), each paddock's Inputs, Income and Margin all per hectare, your overhead from Pricing stated once with lease & finance after it, and the grain-price season named. It is titled PLANNED only while nothing has been done that season.
A season with no imported season data (every farm built from Field Records) is costed the same way Planning costs it: the paddocks and hectares in Farm Setup, seed (or the seed plan), fertiliser, chemical, contractor, levy & freight and machinery. Until October 2026 this page built its own forecast from the newest planning list's hectares, priced harvested grain at the crop's top price and counted planned passes of a finished season that were never done; those figures move to match. Nothing stored changes.
Sensitivity: Price Assumptions sliders re-cost every crop's breakeven — Diesel $/L, Urea and Compound $/t, Chemicals in $/ha (the farm's area-weighted chemical spend is the base; every crop scales by the same ratio), Flexi N per 1000 L, Overhead $/ha. Each crop's card has its own Yield slider (50–150% of its average) that moves the highlighted row and the Margin box without touching the other crops. Reset all puts everything back. The Diesel slider moves fuel only — the fuel part of each pass's machinery $, kept on passes saved since this update and estimated for older ones — not ownership, repairs or labour, so Machinery and Fuel are separate lines in each crop's cost.

Tips & tricks

Income = tonnes × your grain price. A harvested paddock's tonnes are its weighed / delivered tonnes where the harvest record has them (scales, weighbridge or dockets — what was actually sold), else its t/ha × the hectares HARVESTED (the record's harvested area; with none recorded, the paddock's area when the record was made, else today's). Since 28 October 2026 — before that it was t/ha × the whole paddock, which overpaid a part-harvested paddock (32 ha with 27.6 ha cut was paid for 32). Income $/ha, costs $/ha and margin $/ha are all over the paddock's hectares, the area its costs are over, so they subtract. Open a paddock's income to see which: “56 t (2.02 t/ha × 27.61 ha harvested)” or “82 t (82.4 t weighed)”. A crop showing $0 income almost always means no grain price is set for it in Pricing.
Current-season paddocks without harvest project income from target yields (marked as projected) — the same figure Planning shows: your own target for that crop, else the paddock's or farm's average, else the crop default. Past seasons use actuals only.
If a number looks wrong, expand the drill-down — it shows the maths (rate × price × area) for every line.

🚜Machinery

Your fleet's real cost per hectare: machines, implements, rigs (tractor + implement combos) and fleets (harvest gangs, truck teams), with ownership, fuel, labour and R&M built in.

How to use it

Machines: add each tractor, header, sprayer with purchase price, life, salvage, insurance — money fields start at $0, fill in your real numbers.
Connected to John Deere? The blue JD Machines Discovered panel lists everything in your Operations Center equipment list plus any machine seen in imported operations. ＋ Add all from John Deere creates them in one go, typed by Deere's own classification (tractor, combine, sprayer, air cart, bar, head → machine or implement); anything of a Deere type PaddIQ does not map stays in the panel for you to add by hand with the right type. Purchase price and work rates start at the type defaults — fill them in after.
Implements: bars, carts, trailers — they attach to tractors as Rigs.
Crew lists: a machine's page in Maintenance shows what's still to get for it on the Lists (linked to the machine or to a rig it's in), and its card says how many — tick them off right there.
Maintenance log: each record shows as one line — date, job and cost. Tap it for the parts, hours, notes and photos, the Part photo button (when the record has a repair photo) to see it full size, and the pencil and bin to edit or delete; delete asks once more ('Delete?'). A new record starts on today's date, and a part number read off a label drops the label ('PART #S', 'P/N') and is never listed twice. More than one of a part: use the − / + on its chip, type '2x 6203-2RSH' or '6203-2RSH x2', or type the same number again for one more. The suggested cost then prices that many at the invoice's unit price.
On a phone: the add-a-rig and add-a-fleet rows carry the machine's own drawing, a fleet's members are a card each instead of a table that ran off the screen, and the maintenance form's boxes are thumb-sized with a number pad on the number fields.
Needs attention, at the top of the Rigs tab: one list of this season's passes whose machinery story does not add up, grouped by problem — no cost source; on the wrong rig; a fleet pass where John Deere named a rig; on a rig or fleet you have removed; $0 machinery (a rig or fleet is named but the pass saved at $0 — the ones saved from 25 September are marked); fert down the tube charged twice (its own $ and its seeding pass's); two cost sources; possible duplicate; and “Default fleet — a guess” (a John Deere import the default fleet took because no single rig holds the machine it recorded — “Put N on a rig” moves them to the rig you pick, $ shown first, with Undo, and the import remembers it). Each group says what it means and what to do, opens to the passes, and carries its fix: “Move N → rig” (on the wrong rig, and passes with no cost source whose John Deere machine fits one rig), “Put N on a rig” (the rest of the no-source passes, by job — you pick the rig), “Cost these N” ($0 machinery — each at its own rig's or fleet's $/ha today), “Mark N as on the seeding pass” (DTT charged twice — $0, linked to the seeding pass), “Put N on the seeding pass” (Flexi N on the seeder filed under a sprayer: fert John Deere recorded on the seeding tractor in the seeding window that an older import took for another machine's pass the same day — it adds a down-the-tube pass with John Deere's products, rate and hectares on the seeding pass at $0 machinery; the pass it was filed under stays as it is unless you tick it in the second list, where its matching lines come off — the whole pass when nothing else is on it; read from this device's last John Deere sync, so sync on a device that has not) and “Keep one source” (two cost sources — the contractor rate while it still exists, else the rig, at the $/ha the pass was saved with). Every fix first lists each pass with its $ before → after and a tick box; nothing changes until you confirm, a pass that can't change says why, each changed pass keeps its old figure in its history, and a green bar gives Undo (a pass changed again since is left alone). Fleet passes John Deere put on a rig stay on the fleet with the $ they were saved at — no fix is offered for them. The same list is behind setup step 5, Settings → Data Health and the amber notice on Financials, so they always agree. A contractor pass with no rate picked (or whose rate was deleted) counts as no cost source. A pass a contractor pays for — its rate, its contractor job, or a contractor name on it — is never listed under “$0 machinery”, “On the wrong rig” or “Default fleet — a guess”, and no fix puts machinery on it. If a John Deere import took a contractor rate off a planned pass (it used to, when it matched the plan and put the job's fleet on it; it no longer does), the pass is listed under “Contractor rate taken off”, and “Put N back on the contractor” restores the rate with $0 machinery ($ shown first, with Undo). “On the wrong rig” is based only on John Deere's data — the machine it recorded, or a work type naming another rig's implement — and never lists a pass you put on its rig yourself (in Field Records, with a Move here, the import wizard's pick or Ask PaddIQ). “Cost these” and “Keep one source” only re-price or tidy a pass — they don't count as you picking its rig or taking a contractor off it, so a contractor pass you costed before this update is listed under “Contractor rate taken off”, not left charged to machinery. Each pass there has “Leave it on this rig”: it stays off the list while it is on that rig (remembered across your devices), and “Show them again” brings it back. Groups that found nothing are named in a “✓ Checked … — none found” line, so you can see they were looked at. Four groups are only worth knowing — a fleet pass John Deere put on a rig, a default-fleet guess, a removed rig or fleet whose passes kept their $, and a possible duplicate: they don't hold setup step 5 open or raise the Financials notice, and Data Health shows them as info. Removing a rig or a fleet asks first (it tells you how many passes are costed to it) and then archives it rather than deleting: its passes keep their $/ha and still show its name, it leaves the pickers, its fleets and the default, and sits under Removed rigs / Removed fleets with a Restore button.
Rigs: tractor + implement = the cost source Field Records snapshot for seeding/spraying/spreading. Each rig card shows its passes and hectares this season (open it for the list, grouped by how each pass got there): a pass costed to the rig is the rig's; a pass costed to a fleet is the rig's when John Deere recorded its machine on it; a fleet pass with no machine recorded is shared by the fleet's split and counted as 'shared', and passes a support rig rode along on as 'riding along' — so the whole-pass counts of all your rigs add up to the passes done. With two rigs on one tractor (a ripper and offsets), the John Deere import picks the rig whose implement Deere's work type names ('Tillage: Ripper' → the ripper rig) before the rig it remembered for that tractor, and it learns YOUR pick — a wizard select, a Move here, or a rig picked in Field Records — per machine, job and work type. A pick the import made by itself is never learned, and only rigs are: a pass put on a fleet or contractor never replaces the rig a machine has learned. Needs attention → “On the wrong rig” lists passes the John Deere data says belong on another rig: the machine Deere recorded for the pass (matched exactly to each machine's linked JD name and VIN aliases — two machines answering to one name are never guessed between), or a work type naming another rig's implement. A spray pass's product name is not treated as a work type. “Move N → rig” shows each pass's $ before and after, then re-costs the ones you confirm at the new rig's $/ha, as editing its cost source would, with Undo. Passes with no rig, fleet or contractor are under “No cost source”: the ones John Deere places on one rig get a Move button, the rest a rig picker per job. Fert down the tube that went on with a seeding pass is in neither list: the seeding pass already pays for it and counts its hectares, so putting it on a rig would charge the seeder twice.
Which $/ha a new pass is charged: its rig's rate for the pass's OWN season — that season's diesel price, depreciation and repairs year and farm area, with each machine's hectares from Field Records (next paragraph) and its work rate and fuel from John Deere's average over every season. It no longer matters which season Machinery was last open on, or whether it has been opened since you changed a machine, a rig or the diesel price: a 2026 pass is costed at 2026 rates, a 2025 pass entered late at 2025 rates. The Operation cost cards on the Rigs tab show those rates for the season you are viewing. A pass keeps the $/ha it was saved with — nothing already saved is re-costed. (Until Machinery is opened once after this update, new passes use the rates it last showed.)
The hectares a rig's $/ha is spread over come from Field Records: the hectares each machine did this season, by the same who-did-it rule as its job cards (its rigs' done passes, fleet passes John Deere recorded on it, its share of a fleet split). It used to be John Deere's yearly average, which on a tractor John Deere rarely logs on seeding counted a few hundred hectares against thousands in Field Records — so its passes charged two or three times its yearly cost — and on a job John Deere never named counted 0 ha, so the tractor's ownership and labour sat in no pass at all. An implement in a rig (a seeding bar, a ripper) is spread over the hectares its rigs did in Field Records too. While the season is still open, the hectares are the LARGEST of this season's records so far, last season's records, and John Deere's average (for a machine John Deere doesn't know, the whole farm): a pass freezes its $/ha when it is saved, so the first passes of a season must not carry the whole year's ownership on a few hundred hectares. Once this season's records pass the others they take over, and the rate settles as the season's work is marked done. A finished season uses its own records. A hectares figure you type on a machine's job card still wins. The Operation cost cards on the Rigs tab show under each rig the hectares its rate is on and where they came from. Only new passes take the new rate — every saved pass keeps its $/ha, so this season's cost recovery still shows what was charged before.
How a machine's yearly ownership is worked out: depreciation — Straight Line is (price − salvage) ÷ life every year; Diminishing Value is price × 2/life × (1 − 2/life) for each year after the first, and the purchase year and the year after both count as year one (the purchase year used to come out larger than year one). A machine saved without a method has always been charged Diminishing Value, and its card now shows that ("Not saved — charged as Diminishing Value") instead of Straight Line. Pricing → Overheads' "already in pass costs" depreciation uses the same figures, for the machines owned that season. Repairs & maintenance for a season is the LARGER of the estimate (R&M % of purchase price) and what is logged in the Maintenance log so far that season — a single early service no longer replaces the whole year's estimate (the R&M box on the machine's card shows both). John Deere's work rate (ha/hr, the “⚡ JD” figure behind hours, labour $/ha and how a tractor's ownership is shared between its jobs) is the hectares of every pass that carries engine hours divided by those hours — it used to be, in effect, the rate of the last paddock imported. An implement in a rig (a ripper, a disc, a bar) is charged in the rig's $/ha on the hectares its rigs do a year — every rig it sits in, each tractor job counted once — unless you typed its hectares or John Deere records it by name. It used to be spread over the whole farm when John Deere never named it, which made a dumb ripper's share a fraction of its real cost; tillage and seeding rigs with such an implement go up. A truck with its yearly cost split across uses, in a harvest fleet: its harvest share ($ a year) is spread over ONE year of the headers' John Deere hectares (each header's total ÷ the seasons it has data for; a header with none counts the average) — it used to be divided by up to six seasons of hectares, or by the number of headers when none had John Deere data. With no header hectares at all the truck's own rate card is used and its line says so; hover its $/ha on its fleet card (Rigs & fleets) for the sum. In a harvest fleet, a rig whose tractor or implement is a chaser bin, truck or trailer is support by itself (its role chip reads “flat add · auto (Chaser)”): its $/ha is added flat on top of the headers' blend and it rides along on every harvest pass instead of taking a header's share of the hectares. It used to look only at the tractor, so a tractor + chaser bin was averaged in as a header. Tap the chip to set the role yourself — a role you set always wins. A rig with a machine not owned in the season (its Active from / Retired after years) is retired for that season: its card on the Rigs tab carries a “not owned in 2026” chip that names the machine and the year behind it (“Deep Ripper active from 2027”), its sheet says the same with an “Open Deep Ripper” button to fix the year under Ownership Costs, and the fleet member picker lists it greyed with that reason (tap Take out to drop it from a fleet). It is left off the Operation cost cards, the Field Records picker, Needs attention's move suggestions and its fleets, and an implement it shares no longer counts its hectares. Passes already costed to it keep their $/ha and its name. Passes already saved keep the $/ha they were saved with.
Cost recovery (on each rig's sheet, each fleet's card and each machine's sheet): what this season's done passes have charged to paddocks against what the gear costs a year — '$X charged to paddocks of $Y yearly cost; N ha in Field Records vs M ha in John Deere'. Charged = each done pass's frozen $/ha × its hectares (planned passes charge nothing yet). Yearly cost = ownership + fuel + labour (+ support duties, + any contractor flat rate) for the season, on the same basis the $/ha is worked out, and a rig shows the hectares a year its $/ha assumes. If the season ends well short of those hectares, the passes won't cover the year. When the rate counts no hectares for a job, the panel reads “not counted” instead of “0 ha a yr” and says why: John Deere has the machine on other jobs but never this one (so the rate counts 0 ha rather than guess the whole farm), or a job split by implement whose implement John Deere's ops never named. The rate's hectares come from Field Records (this season's, or last season's or John Deere's average while this season's are short of them), so “not counted” now means Field Records has no passes of that job on the machine either, this season or last — put its passes on a rig with it in Field Records, or type its hectares a year on the job card. Until then that job carries none of the machine's ownership or labour in a new pass's $/ha. A machine's figure is its part of each pass it worked, from today's rig make-up — an estimate of where the money went. Hover any line for how it was worked out. Nothing here changes a pass.
Fuel on a pass: a pass saved from now on keeps the fuel part of its machinery $/ha beside it (the rig or fleet's fuel $/ha and litres at that season's diesel price). Financials shows it as Fuel, separate from Machinery; a pass saved earlier has its fuel estimated from its rig or fleet's fuel share today, and Financials says how much is estimated. Moving a pass to another rig drops its saved fuel part — it is estimated from then on.
John Deere has, PaddIQ doesn't (on a machine card linked to a John Deere machine, under the Usage Log): every operation Deere recorded on that machine this season that the last sync on this device did NOT write as its own pass, and why — read from the same fetch the sync already made, no extra John Deere call, and kept on this device only (never synced). Amber groups are hectares missing from Field Records: written under another machine's name (two machines did the same work in a paddock on one day — the pass carries the first machine), a pass of the same shape already on file (a repeat pass taken for a re-run), already on file but on another machine, a second header in the paddock (its yield is kept for the header comparison, its hectares are not), waiting in the import wizard, a field not in your paddock list, or a write the sync could not finish. Grey groups are explained: fert down the tube folded into the seeding pass, under half a hectare (machine noise), a kind of operation PaddIQ doesn't import, deleted by you in the wizard, or already in Field Records by its id. Each group opens to the operations (date, paddock, work, hectares). Nothing here changes a record — it is the explanation for a card reading short of Deere's hectares. Since each John Deere operation became its own pass, a sync no longer writes a pass under another machine's name or folds a second header away; operations an older import skipped wait in the import wizard ("waiting in the import wizard", with a note naming the pass on file) until you say whether each is a second pass. Sync again to refresh it.
Where a machine's hectares come from: Ha/yr counts this season's Field Records that are marked done and costed to a rig with the machine in it (or to the machine itself) — Spread and Ameliorant passes count as Spreading; liquid N through the boom (every product in L/ha) counts as Spraying, on a fleet or on a rig. A pass costed to a FLEET goes in full to the machine John Deere recorded on it — through the rig holding the most of what Deere named, in the fleet or any other rig set up for that job (a tractor named with its boom picks that boom's rig; on a tie the fleet's own rig wins), else the machine itself — matched exactly to each machine's linked John Deere name and VIN aliases. Only a fleet pass with no machine recorded, or one naming two of the fleet's machines, is shared by the fleet's own split: each worker gets its exact share (the fleet's weighting, or the shares you dragged — the % on the fleet card is rounded, the split is not, so no hectares go missing). A support unit such as a chaser counts all of a fleet's passes either way, and a member rig passes its hectares to its tractor and implements. Nothing on the pass changes: it keeps the fleet's $/ha it was costed at. The caption says how many passes were shared by the split; the breakdown labels each fleet pass 'the machine John Deere recorded', its % by the fleet split, or 'rides along'. L/ha and ha/hr from records divide only by the passes that carry a John Deere fuel figure or engine hours — hover the caption for how many. Editing a fleet, a rig, or a machine's linked John Deere name updates these hectares straight away. Harvest the older Harvest Fleet costed shares by the “Harvest crew” fleet it was copied into (by your default Harvest fleet before the copy, or if you removed it). On a machine's sheet each job is its own card under Jobs (🌱 Seeding, 🚜 Tillage…) — tap it to open. Its headline is the $/ha the job costs and the hectares a year it is counted on, or “not counted” when nothing is; inside, every box shows the figure in use as its placeholder (hectares, work rate, hours, fuel) and says underneath where it came from — your figure, this season's Field Records (how many passes), John Deere, PaddIQ's typical rate, or “not counted”. A blank box with “not counted” means the cost uses 0 ha for that job: type the hectares if the machine did it. Every job card also shows John Deere's work rate (⚡): this season's ha/hr with how many ops it came from, and the figure over every season (the one a new pass's $/ha reads unless you type a work rate) — or says there is none (not linked to a John Deere machine, or no ops with engine hours for that job). Tap “Where do the hectares come from?” on the card to list the passes counted, grouped by rig, and every other pass of that job on the farm with the reason it did not count — the most common reason first, with how many passes it covers, then the groups largest first: no rig on the record, a fleet pass John Deere recorded on another machine, another tractor's rig, a rig whose tractor has been removed, typed as a different job on this machine's rig, or still marked planned though its date has passed. Fert down the tube that went on with a seeding pass counts toward no machine — the seeding pass already counted those hectares — and the Seeding breakdown lists it apart, under “Fert down the tube — on the seeding pass”, not as a missing pass. To move a pass onto the machine, edit it in Field Records and pick the rig as its cost source, or use Needs attention on the Rigs tab. A split card (one per implement) shows the hectares it is using in its box; “John Deere, all tillage: N ha” in the caption is John Deere's figure for the whole job on this machine, not that implement.
On a tractor's job card, “Split … or add a duty” splits the job into one card per implement (each bar with its own hectares, work rate and fuel — the rig for that implement reads its card) or adds an hours-only support duty like filling the seeder, whose cost a year is spread onto that job's $/ha. “Flat rate — a contractor does this job” on a card charges the job at a flat $/ha or $/yr instead of the machine's fuel, labour and hours (its ownership $/ha still applies).
🔧 Maintenance: the workshop view — every machine's services, repairs, parts and hours, sorted tractors → headers → trucks → sprayers, newest first; tap a machine for its full log. ⬇ Export log asks which machines to include (all ticked to start, with All / None) and saves their records as an Excel file — one machine names the file after it (every export file now starts with what it is, then the farm and the date). Each record's detail has large Edit and Delete buttons, Part photo when there's a photo, and 🔎 Search part online when it has a part number — a web search for that number opens in a new tab. Edit scrolls up to the form with the record filled in. Trucks/road vehicles can switch their service meter from hours to km (⇄ toggle next to the interval). The service countdown counts from the last record filed as a Service — a repair logged at higher hours no longer restarts it (until October 2026 the machine's card counted repairs too and could disagree with its log). Amber means within 50 h (or 15% of the interval, if more) of the next service, red means past it — the same on the card, in the log and on Planning → Calendar.
✅ Daily checks (on each machine's maintenance log, beside Log repair · Upload invoice · Scan part): the operator's pre-start checklist for that machine — engine oil, coolant, hydraulic oil, fuel and AdBlue, screens blown out, tyres, lights, grease points and so on, with extra jobs for headers (blow-down, chopper, feeder chain, knife and guards), sprayers (nozzles and filters, breakaways, rinse tank, PPE), trucks (wheel nuts, brakes and air, load restraints, logbook) and implements. Each job shows how often it is done (Daily, Weekly, or Every 50 h — every so many km on a km-metered truck) and when it was last done. Jobs that are due sit at the top; overdue ones (a whole week, or twice the hours, missed) are marked red; the rest fold under 'Not due yet'. Tap ✓ OK or ⚠ Issue (an issue takes a note), type the hours off the dash and who checked, then Save check. A higher hours reading than the machine has updates the machine's hours. After saving, each issue offers 'Log a repair for this', which opens the repair form filled in. History lists every check with who, the hours and any issues; Remove hides a check. Customise list renames, adds, removes (history kept, 'Put back' to restore), reorders and changes how often each job is done, per machine; Reset to defaults asks twice and never touches saved checks. The defaults are a starting point — check your operator's manual for the machine's own intervals. Once a machine has a check saved, its Maintenance card shows 'Check due' when today's daily jobs aren't all done, or how many are overdue. Checks and lists sync to your account and merge between devices, so an operator's phone and the office computer both keep theirs. View-only members can see the list and history but not save or change them.
📷 Scan a part / fix: photograph the part box (or the finished job) inside a machine's log — AI reads the part name and numbers off the label and pre-fills the record with today's date, the machine's engine hours and the photo attached. Add the cost, hit Save.
Fleets (Machinery → Rigs & fleets, under your rigs — Needs attention stays at the top): multi-machine teams for one job (harvest: headers + chaser + trucks). Workers are averaged, support units (a chaser bin, truck or trailer) are added flat on top. For the machines' hectares, a fleet pass goes to the machine John Deere recorded on it; the split only shares the passes with no machine recorded. Each fleet card says what it did this season — “This season: N passes · X ha · $Y”, how many of those John Deere named the machine on, and what is still planned (hover it for how it is counted: each done pass's frozen $/ha × its hectares, the same as Financials). The Rate box is the one control for how the $/ha is worked out: Area-weighted (each worker weighted by the hectares John Deere recorded for it over six seasons — the “JD ha, 6 seasons” column, not this season's), My shares (drag each worker — the % shown is the same on a phone and a computer, scaled so the workers add to 100 %; it also splits passes with no machine named) or Typed $/ha. “Default for …” means every pass of that job with no rig or fleet picked is costed at that fleet's $/ha. Trucking fleets are no longer offered: no pass is a trucking pass, so they never cost anything — one you built earlier stays listed, marked “not used for costing”. “Split yearly cost across uses” on a machine now shows only on a machine with a Harvest job (or one already split): only its Harvest share is used, added flat when it is support in a Harvest fleet; the other jobs read “not used for costing yet”.
The older Harvest Fleet (a hidden crew of combines, chasers and trucks at hourly rates that no screen could change) is copied, once, into an ordinary Harvest fleet called “Harvest crew” the first time you sign in after this update. The old setup itself is kept exactly as it was; the copy is yours to edit. Its members are the rigs or machines that crew named (a combine works; a chaser tractor, truck or support unit is added flat — a rig with a chaser bin is support by itself), and its rate is that crew's $/ha typed in, so harvest costs what it did the day before; switch the Rate to Area-weighted to cost it from the machines' own rates (shown beside it). It is ticked the default for Harvest only if no other Harvest fleet was. From then on a new harvest pass with no rig or fleet is costed by your default Harvest fleet, else this copy, and names it; harvest passes the old crew costed keep their $/ha and name, and their hectares are shared by the copy's machines. The fleet card says what was copied and any crew machine not yet set up for Harvest (not counted until it has a Harvest job or sits in a Harvest rig). The old one-off fix that moved John Deere harvest passes off a header rig onto the hidden crew no longer runs — a harvest pass you put on a rig stays there.
Maintenance log per machine: each record has a job description ("replaced rear spreader bearings"), the part, its part numbers, invoice and photos — cost feeds R&M. List bulk-oil litres on a service (your own oil types from Pricing → Fuel & Oil) and they're costed automatically; each record freezes the price list it was saved with.
Cost auto-fill: type or scan a part number and the cost box fills itself from the last time that part was logged on any machine, else from a filed service invoice that lists it (Inventory → Coming in), else from the same part name — the green line under the box says which. Type over it if the price has moved. John Deere's parts catalogue isn't reachable through the Operations Center API, so there is no live dealer price.

Tips & tricks

JD imports carry actual fuel per operation — those beat the estimates whenever they exist.
Contractor-mode ops (flat $/ha or $/yr) cost at the contract rate with no labour on top.
One physical pass never charges twice: fert applied through the seeder in the seeding pass carries no separate machinery cost. A separate DTT pass from John Deere is saved at $0 and linked to its seeding pass — also when the seeding was costed to a fleet — and never appears as a pass with no rig. Older DTT passes the import zeroed read the same way; nothing is rewritten on them. Any DTT pass already carrying machinery $ keeps it until you change it — Machinery → Rigs → Needs attention lists the ones charged twice, and “Mark as on the seeding pass” sets them to $0 linked to that seeding pass after showing the $ before and after (with Undo).

📋Lists — one shared list for the crew

Shared lists for the whole farm — what to pick up in town, parts to order from Perth, harvest spares. Anyone with edit rights adds to them and ticks things off; everyone sees the same list on their own phone. In the menu under Machinery (on a phone: More → Lists).

How to use it

Make a list: the first time, tap Town, Perth or Harvest spares (or a list with another name). ＋ New list makes more. Rename / archive sits above a list once its chip is open; archiving hides the list and its items from everyone — nothing is deleted, and Restore at the foot of the page brings it all back.
Add something: type it in the box at the top, how many beside it (as you'd say it — 2, 20 L, a box), and press Add to Town (the button names the list it goes on — the list chip that's open, else the last one you added to).
The chips: All (everything still to get), one chip per list with its count, Tagged to you (only when someone has tagged you), and Done (ticked).
Tick the box when you've got it — it moves to Done. Untick it there and it goes back (to Ordered if it had been ordered).
Tap an item for its sheet: where it's at (To get → Ordered → Got it), the name, how many, which list, what it's for (a machine or rig, a paddock), a product from Inventory, who's tagged, notes and its History (who added it and every change, with when). Save keeps the changes; Cancel throws them away.
Remove (red, in the sheet) hides the item; Undo appears at the top of the page for a few seconds and puts it back. Nothing is ever deleted outright.
Each item shows who added it — “Added by Jo · today” — from the account that was signed in, never typed.
Tag people: the item counts on their Lists badge (the number beside Lists in the menu, and on More on a phone) until it's got. Tags are in PaddIQ only — nobody is emailed.
Linked to a machine or a rig, an item shows on that machine's page (Machinery → Maintenance → the machine → On the lists), and its card carries “📋 2 on lists”.
From Inventory: link the product it is (say an oil filter in the Workshop). Ticking Got it does NOT change your Inventory. Once it's got, the sheet offers Add to stock — pick the place and how many came in, and it is recorded as stock in at that place, like any other.

Tips & tricks

Two people ticking different things at the same time both land — each item syncs on its own. If two people change the same item, the later change wins and the other still shows in its History.
Team members: Settings → Team has a Lists permission. A member who had no Lists setting yet can edit the lists if they can edit anything else, and read them if they can only view.
Which list a phone opens on is remembered on that phone only.

📦Inventory

What is in the shed, what is on its way, and where each drum or tonne physically sits. Three tabs: Stock (every product and how much you hold), Coming in (orders not yet delivered, then every invoice filed), and Places (your sheds, tanks and silos and what is in each). Stock goes out when you record it: open the place and use Stock out (or ask PaddIQ to). Saving a done pass in Field Records does not move stock by itself.

How to use it

Places come in five kinds: chem shed, fert shed, liquid fert tank, silo and fuel tank. Stock in opens the picker on what that kind of place takes — Fuel for a fuel tank (Diesel, Petrol, AdBlue are offered before you type them), Chemicals for a chem shed, Fertilisers and Ameliorants for a fert shed, liquid fertilisers for a tank — and a product that does not belong is never offered. Fuel is a product type of its own: it prices on Pricing → Fuel & Oil. A fuel tank or liquid fert tank remembers its product from the first Stock in — after that the product is already picked and 'change' is there if a different load goes in; the place's edit sheet can forget it. On a one-product place with a capacity (fuel tank, liquid tank, silo) the bar under On hand is a gauge: drag it to where the level sits, the number and the emblem follow, and Save records it as a stock count. A silo takes grain (pick the crop, and the variety or grade if you know it — stored as 'Barley · Maximus') or a solid fertiliser, and what it holds changes by season, so it offers what is in it now rather than locking it. Its checklist is dip, drain water, change the filter, inspect the bund and hoses.
Inventory is place-first (from 30 Sept 2026): a shed, tank or silo is the page. Places lists every place with its photo or icon, the farms it serves, what it holds and its fill; + Add place takes a name, kind, a number or description (a silo number, a VIN — no tags needed), a photo and an optional capacity. Tap a place: On hand (products, and for a chem shed how many have a safety data sheet), then Stock in (a delivery, or just list a product that is here — quantity optional) · Stock out (or move to another place that can take it) · Count stock (tap a container size once per drum) · Safety sheets · Where is it (a pin from your phone's location or a tap on the map, with the photo) · Maintenance (a checklist per kind of place — cleaned, fumigated with the fumigant and a ventilation date, inspected, seal tested, ready for harvest… — each tick logged with who and when, the latest of each shown on the place, anything with a next-due date flagged when it falls due) (a link or a PDF per product, farm-wide), the Stored-here list with quantities and SDS chips, and the activity log — every change is one movement with who and when. The previous inventory was carried over on first open (places and opening levels) and its records are kept untouched; field records no longer post usages automatically — they come back as movements you confirm. Invoices stay filed under Pricing → Invoices. Stock report (on the Places page) exports stock on hand — pick the product types to include, by type or by place — as Excel (a summary sheet plus one per type) or a print window for Save as PDF. Places with a pin, and rain gauges, show on the Farm Map: hover for the name and photo, click to open. Silos get their grain page (loads, dockets, parcels, checks) next.
Stock: every product with its on-hand figure. Tap one to see where it is coming from (Unassigned first, then each place), the drums it is in, average cost, stock lots, and a plain-English movements log — 'Used 40 L · Home:01 · 6 May', 'Received 2 × 1000 L', 'Corrected −40 L · stocktake', 'Moved 1000 L to Tank 2'.
Stock comes in three ways: Add stock (typed in), Upload invoice (each line becomes a stock lot, the invoice is filed, and its price feeds the Pricing purchase log once), or ticking an order in on Coming in. Every one goes through the same door, so cost is carried whenever it is known.
Correct the count is the only manual out: a stocktake difference, a spill, or stock lent to a neighbour. It needs a reason. For what went on a paddock, use Stock out instead — saving a pass in Field Records does not take stock off by itself.
Needs attention (a chip on Stock, with the count on the tab) shows negative stock, what the season plan still needs (need / on hand / on order / to buy), and products that have run dry. Negative usually means old spray records posted before inventory started — Zero it to write that off; the spray records stay. Better still, set Count stock from (More) to the day you started counting: usage before that date is never posted, so a Rebuild from records can't dig holes for past seasons. Rebuild also clears earlier write-offs (they answered the usage being re-posted), so after a rebuild only genuine shortfalls remain negative.
Coming in: add a supplier, log what you have ordered (quantity, unit, expected date, and the agreed price if you know it). When the truck arrives tick Received → into a place; if the order had no price the stock lands at no cost and the toast says so — set it in Pricing. Uploading the delivery's invoice instead receives the stock AND closes the matching order.
Each section heading on Places (Fuel tanks, Liquid fert tanks, Seed silos…) shows the total across its places — held over capacity and the percent — so one tank reads 2,350 / 4,500 L today and a second tank adds to it.
Place cards carry a light fill per kind (red chem shed, straw fert shed, blue liquid tank, yellow silo, teal fuel tank) and a 'checked 1 Oct' chip — the last stock count or checklist entry on that place; amber after 90 days, 'never checked' until the first one.
Places: one card per shed, tank or silo. The emblem fills from the bottom as the place fills — yellow for seed silos, blue for liquid tanks, red for chem sheds, brown for fert sheds — with a fill bar when a capacity is set. A silo also carries the variety it holds and the season it was entered for (set both in its sheet); the variety shows on the card (stock in another unit is converted with the product's density; anything with no density is listed as 'not counted'). Every card has two doors: What's in it (type what the silo, tank or shed holds right now — 20 t, 15,000 L — and the ledger is corrected to match with one dated row) and Add stock here (a delivery with cost and invoice, received straight into that place). Tap a place to set which farms it serves, move stock (one container at a time when sizes are known, or 'Move all' which opens the move sheet with the whole amount filled in), send it back to Unassigned, or write it off. If a Stock chip like Seed comes up empty, In the shed is hiding products with no stock yet — Show all lists them, or count them into a place.
Unassigned is stock with no shed yet. Its one rule: it is used first, before any shed's stock — sort it into a place when you know where it went. 'Draws from' on a product is Automatic (Unassigned first, then its own place) unless you pin a place.
Stock opens on In the shed — only products with stock on hand or any movement; All products shows the whole library (a search or Needs attention looks at everything). The three everyday actions sit on top (Add stock, Upload invoice, Correct the count); ⋯ More holds Add product, Tidy list, Fill details from John Deere and Rebuild from records.
Tidy list: the Stock list starts with every product in your library. Press Tidy list, tick the products you actually keep, then Keep only ticked — the rest are hidden from Inventory (they stay in Pricing and keep any stock). Show hidden brings them back; tick and Unhide to restore one.

Tips & tricks

Red buttons delete or take stock out — 'Write off (takes it out of stock)', 'Zero this', 'Delete order', 'Remove this location'. Removing a place never loses stock: everything that pointed at it moves to Unassigned first.
Rebuild from records (red) deletes every automatic usage movement across all seasons and re-posts them from your Field Records. It does not change purchases — only which paddock and shed each use is attributed to. Do it after fixing rigs or sheds, and read the count in the confirm box first.
A ≈ on a place figure means that use was not tied to a shed, so it is spread across the places holding the product. Received amounts and moves are always exact, and the places always add up to the farm total.
The stocktake reminder (EOFY and new year) is one line — Done records it, Dismiss hides it for the season. Stock carries across seasons, so the half-yearly walk through the sheds is the truth check.
The duplicate-invoice warning fires on invoice number, or supplier + date + total — not on file name, so two phone photos called IMG_0001 do not false-alarm.

🌧️Season Tracker

Rainfall, weather and water-limited yield for your nearest SILO station — no paid weather subscription.

How to use it

Pick your town, Fetch Data. Monthly rain lands against long-term averages, with GSR months marked.
Weather view, This week: one card per day — sky, max / min, rain and its chance, wind and gust, the daylight Delta T range, and how many hours are good for spraying with the best run. Tap a day for its hours: on a phone it opens in place (tap again to close); on a computer the hours show in a panel under the week. Each hour has temperature, rain and chance, wind, gust and where it comes from, humidity, Delta T, inversion and the spray verdict with its reason. The hourly forecast reaches eight days; days 8 to 16 sit under Further out with the daily figures only. Times are the farm's own local time.
Spray window outlook: This hour's GOOD / MARGINAL / AVOID verdict with wind, Delta T and inversion; the green pills are the best runs coming up; the chart is the hour-by-hour detail — tap or hover an hour to read it. The rule: wind 3–20 km/h, no inversion (air at 80 m warmer than at 2 m in light wind), Delta T 2–8, no rain; it is a forecast model, so confirm on the ground and follow the label. Compare forecast models: the same days from five models — where the lines split, the forecast is unsure.
Radar (the Radar tab beside Forecast, once it is switched on): the rain radar over your farm with your paddock boundaries drawn on it — the past hour of radar and the next hour of nowcast, 10 minutes apart. Press play to loop it or drag the slider; drag the map to put the cross over a paddock and it reads the rain rate there (mm/h) and how heavy that is. The scale along the bottom is the one Windy uses. Future frames are a forecast, and a radar rate is an estimate — your gauge is the measurement. Map / Satellite swaps the background; ⌖ brings you back to the farm. The Farm Map has the latest frame as an overlay (Overlays → Rain radar). Radar from Rainbow.ai.
Gauge Override: type your own rain-gauge reading for any month — it feeds GSR and the yield estimate while the station data stays untouched.
Rain gauges (Rainfall): add a gauge per location, drop its pin on the map and tick the farms it serves — Home on the Kalannie gauge, Dodds and Painters on the Painters gauge. Type each month's reading; blank months fill from SILO at the pin. Every farm on a gauge then reads its own rain for growing-season total, the water-limited yield ceiling and N mineralisation, and the Overview shows GSR farm by farm. Farms on no gauge keep using the station table.
A month that has not happened yet is never counted as rain: next season, and the rest of this one, read as “no reading yet” and take the long-run average — never 0 mm — whatever was saved for them. A past month that recorded 0 stays a dry month. The long-run average is your own records over the last 15 years; a year your gauge or station table is missing is filled from SILO at the gauge's pin once that history has been fetched (opening a paddock's N optimum chart fetches it). The ceiling text says where it came from — “normal from your gauge + SILO, 2012–2026” — and flags a month with fewer than 10 years behind it as low confidence. The water-limited yield ceiling also counts part of the summer rain before the season (November to March) as water stored in the soil at sowing — the text says how many mm it stored, e.g. “+ 9 mm stored from 94 mm Nov–Mar rain”. Until all five of those months are recorded (next season, or a month nobody typed) none is counted, and the text says “Nov–Mar rain not recorded yet”.
Yield Estimate: water-limited yield per crop from growing-season rain, with the water-use efficiency and soil evaporation you can adjust yourself.
Satellite Yield: a SECOND, independent estimate that works from satellite imagery instead of rainfall — it measures how much sunlight each paddock canopy actually caught, converts that to biomass, then to grain. It knows nothing about the rainfall ceiling, so where the two agree that is real corroboration rather than one number shown twice.
The page opens on this season; the backtest scoreboard, the rows worth a look, the farm / crop / paddock learning, the season tables and the red-edge trial sit under it as folded cards. Nothing is fitted to the crop, the farm or the paddock until THREE seasons have been scored; from then the harvest index, each farm's offset and each paddock's factor refit themselves from the backtest, farms held apart, and a crop whose record is one farm's is left alone.
The page opens on this season; the backtest scoreboard, the rows worth a look, the farm / crop / paddock learning, the season tables and the red-edge trial sit under it as folded cards. Nothing is fitted to the crop, the farm or the paddock until THREE seasons have been scored; from then the harvest index, each farm's offset and each paddock's factor refit themselves from the backtest, farms held apart, and a crop whose record is one farm's is left alone.
Start with the backtest button. It runs the model over harvests you have already cut and prints how far out it was, separating BIAS (a consistent offset, which is a fixable parameter) from TYPICAL MISS (scatter, which is noise). Read that before you read this year estimate, then use Refit harvest index to pull the model onto your own numbers.
Beside this season's canopy estimate the table shows RAIN — the rainfall-limited ceiling for that paddock, what the growing-season rain allows after soil evaporation, using rain to date at the paddock's gauge and the long-run average for the months still to come. It is the same ceiling the Nutrition recommender uses (one derivation), so it is never below what the paddock's best harvested season of that crop shows it can do with this season's water — hover the figure to see when that raised it. It is a boundary about one season in ten reaches, not an expectation — a paddock well under it is normal. YOURS is your own estimate: type a t/ha and it is kept with the season (and synced), never fitted from, so at harvest you can see which of the three was closest.
The last estimate of the live season stays on the page with its date after a reload. It is not reused in place of a run — press Estimate again to read the passes since.
This season gives a RANGE, never a single number: the canopy is measured but the finish has not happened, so every paddock is run once per historical finish percentile and once off the 16-day forecast. Tap any paddock row to see how each finish plays out.
Red-edge trial (the switch above the backtest buttons): NDVI stops telling a good crop from a great one once the canopy closes — its response to intercepted light is measured to fall away past about 0.7, which is exactly when a good crop is setting its yield. The red edge keeps responding. Switching the trial on reads a second band on every pass, so every sweep roughly doubles, which is why it is off by default.
It is not a straight swap. The red edge is weaker over bare and part-covered ground, and it tracks chlorophyll — so a full canopy that is nitrogen-short reads low on it while still catching all the light. PaddIQ keeps NDVI below 0.70 and hands over to the red edge above it, ramped so the two never meet as a step, with the bridge between them fitted on your own paired passes rather than borrowed from overseas maize trials.
The red edge is only ever allowed to push the estimate UP, never down. It was brought in for one job: above canopy closure NDVI stops responding and under-reads the light being caught, so in that range the truth is at or above what NDVI says. A red-edge reading that comes back lower is the known confound — red-edge indices track chlorophyll, which is why they are used to map crop nitrogen, so a closed canopy that is nitrogen-short reads low while still intercepting every photon. That is a real signal in the wrong term: nitrogen belongs to conversion efficiency, not to light interception.
The trial card also says, season by season, whether the bridge actually engaged. It needs 40 paired NDVI/red-edge passes inside the fitting window at a correlation of 0.6 or better; a season with fewer clear passes than that runs on NDVI and says so — and if no season engaged, the red-edge run is NDVI in all but name and the comparison cannot show a difference.
The trial keeps both runs on file and compares them season by season. The test is not whether the average improved — it is whether the gain lands on the seasons whose canopies actually closed. A change that improves every season equally is a rescale, and moving a constant is the cheaper way to do that. PaddIQ says which of those it is.
Harvest index moves with the finish — the same biomass yields far less into a hay-off than into a soft spring. Paddocks too small to measure at the imagery resolution are listed as skipped rather than given a confident number.
The satellite passes are stored separately from the scoring, because they have different lifetimes: what Sentinel-2 recorded over a paddock in August 2024 is fixed forever, while the score changes every time you correct a harvest, refit a harvest index or reclassify a paddock as hay. So those changes now re-score in seconds and read no imagery at all. Stored passes are only thrown away by the three things that genuinely change them — a redrawn boundary, a change of resolution, or the season still being under way, where new passes keep arriving every few days.
Switching the red-edge trial on does not re-read NDVI either. The NDVI in a stored season is exactly the NDVI the trial would fetch, so only the missing band is read — the trial costs one extra band, not two.
A finished season stays on file once it has been read, so the backtest opens instantly instead of sweeping the imagery again. Correct a harvest record, redraw a boundary or refit a parameter and it says the stored run is out of date — use Read the imagery again to rebuild it.
Rows worth a look: after the backtest PaddIQ flags any paddock-season that does not sit with the rest of its crop — either it carries most of that crop's whole error on its own, or it is a long way from the others. It flags and stops there. Salty country, a frost hollow and a genuinely exceptional paddock all look the same from here, and two of those are exactly what the model should be learning from.
Tap a row to open it and rule on it. Set a row aside only when the RECORDED figure is not what the paddock grew — only part of it was cut, it went for hay, the yield was booked against the wrong paddock, the area is wrong, or a one-off event like frost. A genuinely poor paddock should stay in: that is the model being told something true.
Nothing is ever deleted. A row you set aside keeps its place in the table, greyed, with its reason on it, and it comes straight back out if you change your mind. It drops out of the score, out of the learning and out of the harvest-index refit at once — no re-reading of imagery, because the pixels never changed.
This matters more than it sounds. One wrong harvest record does not stay in one place: a single part-harvested lupin paddock was inflating the lupin constant, that farm's lupin term and the paddock's own factor at the same time — three corrections all chasing the same phantom.
Whose error is it: after the backtest, every miss is split four ways at once — the season, the crop, that farm's version of that crop, and the paddock — all fitted together rather than one after the other. They compete for the same error, which is what makes it work: when a crop constant tries to swallow one farm's offset, the paddocks growing that crop elsewhere pull it back, so the offset lands on the farm where it belongs. Fit them in sequence instead and whichever goes first takes the lot.
Why the split is worth it: the crop level is a constant that ships to every farm, while the farm and paddock levels stay yours. If one farm grows nearly all of your barley, letting its difficult country be recorded as 'barley converts worse' would misprice barley everywhere else you grow it — in the wrong direction. Where a crop is grown almost entirely on one farm the two genuinely cannot be told apart, and PaddIQ says so instead of picking.
The farm level is always farm-AND-crop, never a bare farm offset: a place can grow poor barley on salty country and perfectly ordinary wheat on the rest of it.
The held-out test also reports WHICH level earned the gain — farm-and-crop alone, paddock alone, or both. That is a different question from whether there was a gain, and it decides what to do next: a farm-and-crop term stands on a dozen or more paddock-seasons while a paddock term can stand on one. If the farm level is doing all the work, the paddock level is decoration until more seasons are scored.
That learning is tested before it is used: each season is hidden in turn, the levels are learned from the other two, and they only get applied if they improved the year the model had never seen. If they did not, PaddIQ leaves them off and tells you. You can switch it either way yourself, and your choice sticks.
Refit harvest index, farms held apart: this moves the crop constant using the crop level above, not raw average error. It refuses any crop whose record comes almost entirely from one farm. The farm and paddock levels are never folded in, so the refit and the learning switch can never double-count each other.
It says HOW MUCH a paddock is behind and how consistently, never WHY. Salt, sodicity, compaction, a frost hollow and a paddock that is always sown last look identical from orbit — a paddock sitting well under year after year is worth walking over with a soil test.
Flowering and maturity are worked out from THERMAL TIME — accumulated degree-days from your own seeding date against real daily temperature — not from a fixed calendar. A warm season flowers earlier and a late-sown crop gets a shorter grain fill, and both change which rain counts as finishing rain. Without a seeding record it falls back to typical WA dates and says so.
BUT temperature is only part of flowering — vernalisation and photoperiod matter as much, so the estimate reads LATE for early sowings. Measured on Scepter at Kalannie it catches about half the real sowing-date effect. So use Flowering dates (on Satellite Yield, or Library in admin) to record when a variety actually flowered: a date you saw replaces the estimate outright.
Record TWO sowing dates for a variety, not two records of the same one. The gap between them is what tells PaddIQ how much sowing date moves flowering on your place — one record fixes a level but cannot show a slope. Outside the range you have recorded, the figure is held at the nearest one rather than projected, and says so.
Admin entries go in the master list every account reads; a grower recording their own variety overrides it. Adding the maturity date (when it went off green) is the only way grain fill ever gets measured — nothing has measured it yet.
In admin these live under Model parameters, not the product library — flowering and grain fill decide which rain counts as post-anthesis and therefore the harvest index, so they are numbers the yield model runs on rather than a catalogue somebody maintains.
Farm History: yields vs rainfall across every season you've imported.

Tips & tricks

The yield estimate's N factor reads your actual applied N from Field Records — fert decisions show up in the forecast.
10yr History pulls a decade of station data for context in one click.

⚙️Settings & Data Health

Settings is six groups of cards — Account, Farm, Connections, Display, Data and Recommendations. Every card starts closed with a one-line summary; tap one to open it (each remembers, on this device, whether you left it open). Nothing in them changed when they were regrouped on 28 October 2026 — only where they sit.

How to use it

Account: who you are signed in as, Change password (emails a reset link), Log out (it sends this device's changes to your account first; if any can't get there — no signal, or your account refused one — you stay signed in and it says how many: Try again, Download a backup, or Log out anyway, which asks first and names how many will be lost; a view-only team member's changes can never be sent, and it says that instead), Help & guide, and PaddIQ on your phone (opens the help section with the home-screen steps). Logging out clears PaddIQ's farm data from this browser — records, maps and map pictures, satellite caches, and anything mid-import — so the next person to use it starts clean; your own unsaved zone drafts stay on this device, filed under your farm, where no other account can see them. The Delete this account card removes the sign-in, the cloud data, team memberships, saved layers, invoice and safety data sheet originals, feedback and its files, your saved Ask PaddIQ conversations, the question log and its meter, the unused sign-ins your invitations created (and your name and farm from any that were used), and everything PaddIQ keeps in the browser you delete from; it revokes John Deere's access. PaddIQ keeps only a note that an account was deleted and when (no email, no content) for 7 years. Type DELETE to confirm, and if you signed in more than 5 minutes ago it asks for your password again (Confirm it’s you) so a stolen session can’t delete your farm — forgotten the password? Change password emails a link that signs you in, then delete within 5 minutes; Download everything first if you want a copy. If deleting stops part-way, press it again — it finishes what is left.
Account → Billing (29 Oct 2026): PaddIQ is free during early access, and this card says so. Once paid plans start, the farm owner sees the plan and its price (in Australian dollars, including GST where it applies), the status — Trial with the days left, Active with the renewal date, Cancels on a date, Payment failed (update the card), or Cancelled — and two buttons: Start subscription opens Stripe's secure checkout, and Manage billing opens Stripe's billing page to update your card, download invoices or cancel (you keep full use to the end of the period you paid for). PaddIQ never sees your card. Team members see “Billing is managed by the farm owner” and the farm's status — their access follows the owner's subscription. If a subscription ever lapses after early access, the farm turns read-only, never locked: every page still opens and Settings → Data → Export all data still works, but records can't be added or changed until the subscription restarts. You get at least 30 days' notice of the price before any charge.
Farm: Team & Permissions (owner only), Farm & Paddocks (the master registry — sizes, active years, soil types, splits and merges; boundary shapes live on the Farm Map), Crop types and Crop Colours.
Team & Permissions: invite a team member at the top (name, email, role → Add & invite sends the sign-in link), then click each tab to cycle Hidden → View → Edit. Adding someone is an invitation: they see “You’ve been invited to join <your farm>” at their next sign-in and choose Join, Not now or Decline — nothing about their account changes until they say yes, and a person with a farm of their own keeps it. Their email must be confirmed. It is live — they sign in with their own account, see your farm's data, and a change you make reaches them within a minute, or the moment they next open the app. Removing someone signs them out. Invite on a row re-sends the email. A member with Edit on a tab saves onto your farm — records are merged by id, so two people can work the same season; you see their work at your next sign-in or Sync. What is enforced, and what is not: a member’s changes reach your farm only in the areas you set to Edit (Field Records, Planning, Pricing, Inventory, Machinery, Lists …; paddocks, boundaries and the product library follow Edit on any tab), and the team list and farm settings are yours alone. What a member receives (29 Oct 2026): their device gets only the farm data behind the tabs set to View or Edit, plus what every screen needs — paddocks, boundaries, crops and the rotation, the product library, rain, places, saved layers, farm settings, and team NAMES (never your team list, its emails or anyone’s permissions). Tabs that save passes (Field Records, Planning, Import) also get the machine list, rigs, fleets, maintenance, diesel and contractor rates, because saving a pass fixes its cost; Financials also gets what it adds up. With Pricing and Financials both Hidden, their screens show “Not shared with you” where a dollar figure would be — but the product library itself carries your product prices, so don’t treat Hidden as hiding product prices. Set a tab to Hidden and its data leaves the member’s phone at their next sync (your copy in the account is untouched); set it back and it comes back. Ask PaddIQ follows the same rule. A member already on a team before 28 Oct 2026 is asked once at sign-in, “Open <farm> on this device?”: Yes opens it (and is remembered on their account), “That’s not me” takes them off the team, Sign out changes nothing. Roles: Manager, Operator, Accountant, Viewer; anyone but the Owner can be removed. If an invite says the email limit for the hour is used up, the person is still on the team — press Invite again later. Invites open a day after your account is created and once your own email is confirmed; an account can send 10 invite emails a day, and any one address gets at most 3 a day. The message is the same whether or not the person already has a PaddIQ account.
Crop Colours also lists any crop name in your records that PaddIQ doesn’t recognise — say John Deere’s “Wheat white”, or a new crop you’ve imported. An unrecognised name has no colour, no grain price and no removal rate until you say what it is: pick “the same as Wheat” (your records keep the name they came in with, and the choice applies everywhere a crop is read, every season) or “its own crop”, which adds it to the colour list. Choices are listed underneath and can be undone. White wheat is recognised as Wheat already — noodle and soft classes are grades, priced by grade.
Connections → John Deere opens the John Deere Operations Center connection on the Import page — connect, disconnect and sync there.
Connections → John Deere → Remove my John Deere data (farm owner only): disconnects John Deere (and says whether John Deere confirmed the revoke) and deletes what PaddIQ downloaded from it — the maps from John Deere (here and in your account) and the links between its fields and machines and yours. Tick the box to also delete the Field Records imported from John Deere and tank mixes copied from it; untick keeps them as your own records (your spray diary is among them). Paddock boundaries and product details are not touched. PaddIQ records the removal and reports it to John Deere, as its licence with John Deere requires.
Display: Maps (how yield, protein, moisture and rate maps are coloured on this device — seven solid classes or the smooth scale, and the yield-map picture logged or smoothed) and Label markers (withholding and plantback pills on or off).
Data → Data Health scans for problems that make paddocks read “Unknown”, show $0 costs or lose spend — duplicate or blank registry entries, orphan records, unpriced products — and fixes what is safe with one click. It also lists how many passes need attention in Machinery (no cost source, $0 machinery, charged twice, on a removed rig…) — the same list as Machinery → Rigs → Needs attention; it is never changed from here.
Data Health → Run all repairs: one button runs every safe, idempotent fix — duplicate imports, orphaned paddock keys, mis-labelled mL units, double-counted seeder costs, and stock lots received in tonnes (or litres for a kg product) that posted at face value — re-expressed in the product's base unit.
Data Health → “older Rotation picks differ from the crop planned now”: crops picked for another year before October 2026 that weren't copied to their own season, because a different crop is planned there or two old picks disagree. Nothing was changed. To use the older pick, set it in Planning → Crops and it drops off the list; Keep planned crops leaves every crop as it is and stops listing them. Settings → Data → Clean-up says how many were copied.
Data → Backup & sync: Export all data (or Import → Backup & Restore → Download backup) saves the whole farm as one JSON file — every season of Field Records, paddocks and boundaries, soil tests, machines and maintenance, prices, zone maps and saved layer settings. The message says what is in it (for example “7 seasons of records (412), 9 zone maps”). Layer image files are not in the file; they come back from your account or John Deere. Import backup puts each item in the file back and keeps anything the file doesn’t have; Restore from backup (Import tab) clears this device first. A restore has to reach your account, so it only starts when it can: a team member with view-only access, or a device that’s offline or signed out, gets a message and nothing changes. Both buttons ask before changing anything, send the restored farm to your account and reload the page. A restore replaces the whole farm, so a team member needs edit access to Settings or Import to run one; it goes to the farm owner’s account and changes the farm for everyone on the team. If sending doesn’t finish, the page still reloads and says so — don’t enter anything new, and choose the same file again as soon as you can. Backups from older versions still restore. Download everything (Import → Backup & Restore, or here) makes one .zip: the backup file, the invoice and safety data sheet originals you filed, files you attached to feedback, the questions you asked Ask PaddIQ as PaddIQ logs them, your saved conversations, your terms acceptances and team rows, and README.md, which says what every part holds; tick “include map pictures” for the yield, NDVI and as-applied pictures too (they can be hundreds of MB). Check cloud sync compares this device with your account; Check this device's storage shows how full this browser's small store is (about 5 MB), whether the large store (IndexedDB) is working, and the biggest items.
Data → Change history (farm owner only, 29 Oct 2026): every time a data set in your account is replaced or deleted — a season's Field Records, the machines, the paddocks, the product library, a setting — by you, a team member or another device, PaddIQ keeps the version it replaced for 30 days (one every 10 minutes while you work, and always a delete or a big drop; after 3 days, one a day). Pick a data set to see its earlier versions — when each was saved, and when and by whom (you or a team member, and on what kind of device) it was replaced. Tap one to compare it with now (“Than now: 3 records more · 1 fewer · 2 changed”), then Restore this version. Restore makes the data set exactly that version on every device: Field Records deleted since come back as they were, records added since are removed (the button is red when it removes anything), and what was there before the restore is kept at the top of the list, so a restore can be undone. Season deletes and Reset account can be undone the same way, data set by data set. Hard refresh your other devices first. Until PaddIQ's database update is run it says it isn't switched on yet.
Data → Clean-up: Clear a season's imported data; the automatic repairs, which run after every John Deere import and sync (records filed in the wrong season are moved to the season their date belongs to, part-paddock passes get their covered area, records get their machine, fuel and hours, harvests get each header’s yield, seeding passes get each variety’s rate, and the data-health repairs run for every season — none changes a frozen cost; the card shows when they last ran); and the duplicate scanner, which lists suspected doubles for review before anything is deleted — two imports of one pass count as a double even when they differ by a rounding of the rate, a unit (30 g vs 0.03 kg) or a carrier line such as Boomspray or water. A genuine second pass on the same day at the same rate looks the same, which is why you decide. Clearing a season here, or Import → Delete all records / Delete everything (and clearing a value such as a season's fuel price), now removes it from EVERY device: a phone or computer that still held the season drops its copy the next time it syncs — keeping only anything typed there after the delete — instead of sending the whole season back. Re-importing the season afterwards works as before. To undo a delete, use Data → Change history.
Data → Share with the Response Bank (asked once, on its own screen, only to the farm owner and only after the terms are accepted — straight after your first sign-in, or the next time PaddIQ opens if you haven't answered: “Help tune recommendations for your rainfall zone”, with Yes, tune my zone or Not now and nothing picked for you. A Yes includes results that came from John Deere Operations Center (yield-map yields, as-applied rates) — the screen says so; there is no separate tick. Until you answer nothing is sent or removed, and the screen stays until you answer. Not now, or closing it, counts as No and you aren't asked again (if you are being asked again about an earlier Yes, Not now keeps that Yes as you gave it) — never at sign-up, never in a terms notice, never on a recommendation screen): a switch, off unless the farm owner says yes (members see the choice, never the switch). When on, each harvested paddock-season in your learning record is shared with the PaddIQ Response Bank under a random code — crop, season, yield, protein, rain totals, N/P/K/S applied, soil type and the soil test values the recommendations use (pH, organic carbon, Colwell P and K, PBI, exchangeable K, sulphur, mineral N, CEC, sodium %, EC, rounded), paddock size in 50 ha bands and your district as a 1° square (about 110 km across) — never names, paddock keys, boundaries, exact locations, products, dates or your email — sent when you switch it on and brought up to date each time PaddIQ opens on that browser. “Shared: N” is read from the Response Bank there and then; if the read or an upload fails the card says so, with Try again. A Yes given before 29 October 2026 did not include John Deere results, so you are asked once more. A row whose yield is above the crop’s genetic cap (usually a typing or unit slip) is not shared, and the card names it so you can check that harvest. Switching it off deletes every row you shared. The key that tells your paddock-seasons apart is made from a secret kept on the device that uploads them — with two owner devices (or two addresses of PaddIQ in one browser), the one that has been uploading keeps doing it while its rows are there, and the other takes over after two weeks without it, at once if those rows are gone, or if you flip the switch there. An automatic upload never removes rows another device sent. What sharing is for: once enough farms in your rainfall zone share, PaddIQ uses their results to tune its recommendations for that zone, for the farms that share; until then your recommendations and nutrient rates are exactly the same whether you share or not. Spray, withholding and plantback checks never change either way. Zone figures are never shown to growers, and no grower ever sees another farm's rows.
Data → Reset account (owner only) empties every season in the cloud and this browser but keeps your sign-in.
Recommendations → Assumptions & Calibration: what your own records say about water-use and nitrogen-use efficiency, beside the PaddIQ Response Bank that sits underneath. The two are blended, not switched: the Response Bank runs until your farm has 3 harvested seasons and 8 harvested paddock-seasons of a crop with rainfall recorded, then your own line counts for more as seasons are added (the card says how many are still needed). Nitrogen-use efficiency is shown for comparison only. The figures you can set yourself (stubble N tie-up, fallow N credit, N carryover by soil type) are blank — PaddIQ's figure — until you type your own.
Your farm’s learning record (inside Assumptions & Calibration) is what those fits are made from: one row for each paddock you harvested in a season — crop, yield (your weighed tonnes ÷ the hectares harvested where you recorded weighed tonnes, else the harvest record's t/ha; two headers on one paddock are one row), April–October and November–March rain, N applied, the soil test in force that season, protein and soil type — saved to your account and updated whenever the farm owner saves a harvest or signs in, with older rows kept rather than overwritten. The table is closed until you tap Show the <n> paddock-seasons, then shows 25 at a time (‹ Newer / Older ›); hover a growing-season rain figure to see where that season’s rain came from (your gauge, SILO at the gauge’s pin, or your station record). Refresh from your records re-reads them on the spot. Under it the same rows are plotted for each crop: yield against the season’s water with PaddIQ's ceiling and your farm’s own line, and yield as a share of each season’s ceiling against the N you applied, with a sentence on how far your N rates spread (a curve cannot be learned from your history without lower and higher rates — strip trials make them). Worth a look lists the paddock-seasons that stand out (above the crop’s genetic cap, far above or below that season’s ceiling, or rain not fully recorded). Tap a card or dot to see it and, if it was frosted, hailed, cut for hay or grazed, or is a data error, choose Exclude from my learning record with a reason: nothing is deleted, but your farm’s line and N efficiency stop using it and it is not shared; Undo puts it back.
Recommendations → Nutrition Setup (preferred products, removal rates, product nutrients, application setup) and Default Values (the overhead $/ha that Financials and the exported plan use).
Saving offline or just before closing: what you save lands on this device straight away and is sent to your account a few seconds later. If the page closes or loses its connection first, nothing is lost — the next time PaddIQ opens it keeps your change and sends it, and if another device or team member changed the same list meanwhile (Field Records, inventory, zone maps, daily checks, machines, rigs, the maintenance log, places, tank mixes, hazards, rain gauges, contractor jobs, operators, saved layers and their yield corrections) the two are merged item by item: different items both stay, the same item changed on both → the later change wins, and something deleted on one device stays deleted. The paddock list, the season product and price library, soil tests, harvest entries and rain readings are still saved whole: when two devices changed one of those, or the same single setting, the account's copy wins. The ☁ Sync button sends this device's changes and then fetches the farm's latest.
Terms, advice and AI (28 Oct 2026): the Terms of Service and Privacy Policy were updated, so everyone is asked to accept them once more at the next sign-in. Since 29 Oct 2026 a new account agrees on the sign-up form itself — tick “I agree to the Terms of Service and Privacy Policy” (both open in a new tab) and Create Account becomes available (just above the tick, one sentence points to the two terms that matter most, each linked to its section of the Terms: recommendations are decision support, not agronomic advice, and the label comes first — section 6 — and our liability is limited as set out in section 10; the update notice shows the same sentence above Accept and continue); an invited team member ticks the same box when setting their password. Neither is asked again for those terms. When the terms next change, you'll see a short “We've updated our Terms of Service and Privacy Policy” notice: the date they take effect, what changed, links to both documents, a folded summary of how we handle your data, and Accept and continue. Wherever PaddIQ recommends a rate — the fert wizard's accept step, a paddock's Use recommended program, the N chart's How this is worked out, Zone Studio's rates and every prescription — one line says “A recommendation, not agronomic advice — check rates, the label and your agronomist.” Making a prescription's USB file or sending it to John Deere Operations Center asks first, and says you are responsible for the rates loaded into the controller. Ask PaddIQ says at the top of every conversation that it is an AI assistant (Claude by Anthropic) and can be wrong. A withholding or plantback pill that is clear reads “clear · check products/label” — the label is the legal document. Data credits (SILO rain, Sentinel imagery, Esri and OpenStreetMap maps, Open-Meteo forecasts) sit with the data, and in full at paddiqag.com/sources.
Privacy in short: the Privacy Policy (paddiqag.com/privacy) opens with a short version — our commitments, what we collect and why, and how your data is protected — before the full policy. How your data is protected is also under Settings → Data. A terms update notice folds the commitments and what we collect under “Summary of how we handle your data”. Data sources & licences (paddiqag.com/sources) lists the public data PaddIQ uses — rainfall, satellite imagery, soil and radiometric layers, map tiles, the chemical register — with the credit each licence asks for. The home page (paddiqag.com) carries the same under “Your farm. Your data.”: six plain lines on what PaddIQ does with your records, then the privacy summary, the full Privacy Policy, Terms in plain English, the Terms and the data sources folded underneath — closed until you open one, and the words are the same ones /privacy, /terms and /sources show. Terms in plain English is the short read: your data and who can see it, what we never do, AI and advice, your rights under Australian law, your account, payments and cancelling, changes to the terms and contact, a few lines each; /terms and the terms update notice link to it. paddiqag.com/#privacy, #terms-plain, #terms, #privacy-summary and #data-sources open that fold. The home page’s tour runs on a made-up sample farm, never anyone’s real data.

Tips & tricks

When something goes wrong: if a screen crashes, PaddIQ shows "Something went wrong" with a Reload button and sends the PaddIQ team an automatic error report — the error message, the part of the app and the page (without anything after a ?), the app version, the kind of device and browser ("iPhone · Safari") and your account, so we can follow up. It never includes your farm data, records, emails or anything you typed; reports are kept 30 days and deleted with your account. You don't need to describe it, but Send feedback (menu) or an email to admin@paddiqag.com still helps if you want to tell us what you were doing.
If a fertiliser recommendation ever comes out impossible — an N rate over 250 kg N/ha or below zero, P over 100 kg/ha, a yield past what the crop can grow, or a number that isn't a number — the paddock shows a red "Check this number" note and a low data-confidence badge instead of quietly showing it, and PaddIQ is sent a short report (which figure, rounded, the crop and the paddock's size band — never the paddock, farm or your inputs). It is usually a typing or unit slip in a target yield, a soil test or a product's analysis.
When you ask PaddIQ for help, support may open your account's details — when you signed in and synced, your terms and two-step status, team size, whether John Deere is connected and how your last syncs went, AI use, billing status and error reports. That page shows no farm records, paddocks, prices or messages, and every opening is written to your farm's access log with the reason.
When you tap John Deere Sync or import a file on the Import page, PaddIQ notes whether it worked — the counts (operations imported, rows read) and, if it failed, the kind of problem (connection, sign-in, a file it couldn't read). No file, paddock or value goes with it; it is kept 90 days so we can spot a broken import before you have to tell us.
If PaddIQ switches a part off for a while (Ask PaddIQ, John Deere sync, imports, or the whole app to read-only for maintenance), a note at the top of every page says so in plain words. Nothing of yours is lost: you can still open and export everything, and the note goes when it is switched back on.
Run all repairs after big imports — it's safe to run any time; repairs only touch records that are provably wrong.
Hard refresh (Ctrl+Shift+R) after an update if a page looks stale — your browser may be running old code.

Stuck on something this page doesn't cover? Email admin@paddiqag.com — guide updated as the product changes. Data sources & licences