What this is
Yield Centre brings every harvest together: production by crop and season, what the grain was worth, each paddock's record against the farm, yield maps on the paddock's real ground, harvest loads and deliveries, the yield forecast and the original yield records.
Where to find it
More → Data Centres → Yield Centre.
From a paddock: Map → tap paddock → Yield.
Views and buttons
Yield Centre has five views across the top: Overview, Paddocks, Maps, Deliveries and Data (on a phone all five fit across the screen). Under them is the heading with what you're looking at, for example "All properties · All crops · All recorded history" (Reset clears it), then:
Filters, with how many are on (on Overview, Paddocks and Data)
Import (an upload icon on a phone; not on Maps)
Log load (not on Maps)
Actions, on every view: John Deere yield maps, CBH LoadNet deliveries (opens the CBH LoadNet connection), Combine crops & varieties, Grain prices, Export (opens Data, where the CSV and PDF buttons are) and Quick walkthrough
Import, John Deere yield maps and Combine crops & varieties need permission to edit the farm's data. Grain prices is listed only for people who can see the farm's finances.
There is no Loads tab any more: harvest loads are under Deliveries → Harvest loads, and an old link to Loads opens them there.
Overview
Overview looks at one season at a time. Choose it with Season at the top, and everything on the page follows it.
Four numbers: Production (with the change on the season before), Harvested hectares, Season rating (how the season went across every crop, as a percentage of each crop's own average, weighted by area) and Yield maps (how many of the season's harvests have one).
Grain value, for people who can see the farm's finances: what the season's grain was worth, with its average under it ("$338/t average"), or how much is not priced yet ("1,240 t not priced yet"). Grain prices beside Season opens the prices for that season (see Grain prices below).
Crop trends puts every crop on one chart. Yield shows t/ha for each crop; % of average shows each crop against its own average, so a good canola year and a good barley year sit at the same height; Tonnes and Area stack each crop's share of a season; Value (for people who can see finances) stacks what each crop's grain was worth, season by season. A season a crop wasn't grown is a gap with a dotted line across it, never a zero. Point at (or tap) a season to read every crop in it; select it and the whole page moves to that season.
Crops in 2026 (the season you chose) gives each crop a card: that season against the crop's average, for example "10% above", a line of every season it was grown that you can run a finger along, the average, the best and lowest seasons, and a button to that crop's paddocks.
Paddocks in 2026 lists the season's strongest and weakest paddocks, each against the same crop on the farm's other paddocks that season. Select one to open the harvest.
Forecast & rainfall is always open at the bottom (see Forecast below).
Grain prices
A sale contract in Inventory → Grain & Hay → Contracts isn't the only way to say what grain sold for. Grain prices puts a $/t on any harvest, old seasons included, even one with no contract and no crop plan. Open it with Grain prices beside Season on Overview, or Actions → Grain prices.
Choose a crop. Its seasons are listed newest first, each with its tonnes, how it is priced now, its value and its average $/t (or Not priced). Open a season to see its paddocks.
Tick one season, several, Every season, Only the unpriced, or single paddocks.
Type a price in $/t and press Set price (Enter works too).
That covers both "the same average price for everything" and "these paddocks got more". Suggestions beside the price fill it in for you: that season's contract price, the crop plan's price, or the price you gave the crop in your latest other season. Clear takes your price off the ticked harvests, and Undo puts back what was there while the sheet is open. A price below $50/t or above $3,000/t is flagged ("Check it is dollars a tonne") but still saves.
Each harvest is priced in this order: its contracts first (delivered, then still to deliver, spread over all of that crop's tonnes that season), then your price for the rest, then the crop plan's $/t if you haven't set one. Tonnes nothing prices count as not priced, never as $0. Financial Performance prices grain the same way (see What the grain is priced at in Financial Performance). Nothing changes to your yield records.
Prices are financial information. Only people who can see the farm's finances (Can view financials) see Grain prices, the Grain value card, the Value view or the prices, and only those who can also edit the farm can set or clear them; anyone else reads "You can see prices. Someone who can edit the farm sets them."
Paddocks
Paddocks opens on Every season: a row per paddock and a column per season, each cell showing the crop and its yield. A cell is shaded blue when it beat the same crop on the farm's other paddocks that season and orange when it fell short, with ▲ or ▼ as well; a crop grown on only one paddock is left unshaded. A paddock's overall figure sits under its name. Sort puts the strongest or weakest paddocks first. Select a cell to open the harvest.
One season lists every paddock for the season you choose, with Yield map where it has one.
Data and Edit yields
Data keeps the production records: search, sort, Quality columns, and tick rows to export them as CSV or PDF. Add record adds one harvest by hand. Manage yield data underneath shows coverage by year and the John Deere records, where you can remove one.
Data → Edit yields edits one harvest year at a time:
It opens on the latest year that has yields. The arrows step to any year up to this one, including a year with no yields, where every paddock is listed blank to fill in.
Type a yield in t/ha or total tonnes; the other is worked out from the paddock area.
Press Save on that row (it sits right after Tonnes), or press Enter. A row you have typed in is shaded and its Save turns solid.
While anything is unsaved, a line under the editing note says how many changes are waiting, with Discard and Save all. Done editing asks Save and finish or Keep editing if anything is unsaved. A row with no crop or no yield can't be saved; it stays open and the message names the paddock.
One yield figure per paddock
A paddock's yield for a season is one figure, kept on its yield record. Averages, the paddock list, gross margins and the yield map's legend all read it.
A yield you change in Data is yours. Its Source reads, for example, John Deere · yield set by hand, and the next John Deere or spreadsheet import sets that row to Skip so your figure stays. Yields corrected before this came in, in October 2026, are not marked this way: change the yield again, or choose Skip on the import.
The yield map follows the figure. Change a paddock from 5.93 to 5.50 t/ha and its map moves with it, every reading by the same amount, so the map still averages what the paddock yielded and the pattern across the paddock stays the same. This happens when a yield is edited in Data, replaced by an import, or recorded from harvest loads. A map that never matched the paddock's figure, such as your own calibrated map kept beside a different recorded yield, is left as it is.
Importing figures keeps the map. Replace on an import saves the new figures and keeps the paddock's map. A map cleared by an earlier re-import is not brought back: fetch it again from Maps → John Deere maps.
Delivered tonnes stay separate. Loads from CBH LoadNet never change a paddock's yield.
Combine crops & varieties
John Deere sends its own crop codes, so a harvest can arrive as WHEAT_WHITE beside your own Wheat, and one variety can come in several spellings, such as Scepter, SCepter and SCEPTER. Two names count as two in charts, averages and filters. Capitals alone never split a crop: BARLEY and Barley are already one.
Actions → Combine crops & varieties has two views:
Crops lists every crop name on your yield records, with how many records and which seasons.
Varieties picks a crop and lists its varieties, with every spelling of one variety shown together and placeholders such as "---" shown as No variety.
Tick the names that mean the same crop or variety, keep the suggested name or type another, and press Combine into …. Tick one name to rename it. Suggested lists the safe ones first, each with its own button, plus Tidy all: crop codes Phase recognises (WHEAT_WHITE → Wheat), other spellings of one variety, and placeholders cleared to no variety. Two different names, such as Havoc KW and Havoc, are never suggested; combine them yourself if they are the same variety. Undo puts the old names back while the sheet is still open. Only yield records change; crop plans, harvest loads and contracts keep their names.
When a code splits a crop, Overview and Data show a note with Combine crops and Not now. Not now hides it on that farm until a new code turns up.
Since 7 October 2026 a harvest from John Deere is saved under the crop's own name (WHEAT_WHITE as Wheat), and a placeholder variety is saved as no variety. Records saved before then keep their names until you combine them. A re-import finds the renamed record instead of adding a second one.
Import yield
Import opens Import yield, grouped by where the yield comes from:
From John Deere: Harvest yields (each paddock's harvested yield, moisture and varieties, across as many seasons as you choose) and Yield maps (see below). Both are Phase Ultra; on Phase Pro they show an Ultra mark and open the upgrade prompt.
From a file: Spreadsheet (CSV or Excel) and Shapefile (a yield-map package: zip the .shp, .shx, .dbf and .prj together). Every plan.
By hand: Manual entry.
A yield map file uploaded in Spatial (Import layers → Upload) is also saved to the paddock's yield record for the season you choose, so it appears here too.
John Deere yield maps
John Deere yield maps fetches the yield map of every harvest in a season. Open it from Import → Yield maps, Maps → John Deere maps, or Actions → John Deere yield maps. It needs Phase Ultra and a connected John Deere account.
Choose the season to file the maps under, the farm, and the harvest window (Harvest from and Harvest to). A harvest that ran into the new year still belongs to the season it was sown in, so move the window rather than the season.
Find harvests lists what Operations Center holds, paddock by paddock: Ready to fetch, Already have a map, No harvest in this window and Not found in Operations Center.
Fetch N yield maps asks John Deere to build them.
John Deere takes 30 to 60 minutes to build each map, and it appears in Maps on its own, so you can close the sheet. Maps still being built are listed under On the way from John Deere. A paddock that already has a map is left alone; delete that map in Data to fetch it again. A paddock not found needs the same name in Operations Center, or a boundary imported from John Deere.
Every paddock with a harvest that season is checked, even one the season's paddock list leaves out, so running John Deere maps for a past season may find paddocks it skipped before. A map is only filed on a paddock it actually sits on: if John Deere's paddock of the same name is somewhere else, the map is refused and the paddock shows Did not finish with the reason. A paddock linked to an Operations Center field is never given another field's map because the name reads the same. When a map arrives for a paddock with no yield recorded, John Deere's own figure for that harvest is saved with it.
How an import matches rows to paddocks
Import → Spreadsheet or Harvest yields matches each row to a paddock by name on the review step. Phase looks for the name exactly as written first, ignoring capitals, spaces and dashes, so "NORTH-1" is North 1. It finds paddocks named with a number or letter, such as "North 1" or "East A", even when a word in the name is also in the farm's name, like North 1 on North Farm. It never matches a row to a paddock with a different number or letter: "North 1" is not North 10, North 2 or North B.
When two paddocks fit a row equally well, such as two farms that both have a North 1, or a row that just says "North" on a farm with North 1 and North 2, the row is left for you to pick and marked Multiple similar paddocks. A row that only names a farm stays unmatched, marked Farm name, not a paddock. A row whose name has the paddock's name inside it, like "North Farm North 1", is marked Paddock name found in a longer name. Yields already imported are not changed; if an earlier import put a yield on the wrong numbered paddock, find it under Data and move it.
Yield maps
Maps opens on the newest season that has more than one mapped paddock, so a single early import for the coming season does not hide last harvest; a lone map is treated as a stray. Above the map, a crop dropdown (All crops or one crop) and a season dropdown choose what you are looking at. The crop list only shows crops harvested in the chosen season, and changing season goes back to All crops. Beside them are Open in Spatial, which carries the selected paddock and harvest across, John Deere maps and Settings (all three show as icons only on a phone). With no maps yet, the map offers From John Deere and Upload a shapefile.
Settings opens a small panel over the map: Smoothing (Off, Light, Medium or Strong), Range (type a Min and Max to fix the colour scale, or Auto to let it follow the maps), Colour scale, Map unit (only when the season has maps in more than one unit) and Opacity. At the bottom, Paddocks shows how many are on the map and opens the list to pick the active paddock, a farm, or which paddocks to show. Tap outside the panel to close it. The old Scope and Style buttons are gone.
On Auto, the colours cover the main body of the readings, not the stray ones: a header running empty over a headland, or a blockage clearing. Readings beyond the scale are still drawn, in the lowest or highest colour, and the legend says Auto scale, ignoring spikes, with < on the low end and + on the high end. Nothing is deleted, and low patches stay on the map. John Deere maps imported from mid-October 2026 also bring in fewer impossible readings; a map imported earlier keeps its readings until it is fetched again. To set your own scale, type a Min and Max under Range.
Phase opens with every yield figure and a note of which paddocks have a map, and fetches a map when you look at it, so a farm with many seasons of maps opens faster and uses far less memory. The first time a map is opened there is a short wait while it loads; going back to it is instant for a while. A map needs a connection to open; with no signal, the yields, averages and which paddocks have a map are all still there.
The Map / Explore / 3D switch in the map's top-left corner changes how you read it. Explore redraws each paddock as thousands of small dots in the same colours and scale. Drag a finger (or move the mouse) across a paddock and the dots part around it, while the yield under it, for example "3.42 t/ha · North 2", follows just above your finger. On a phone the map is locked while Explore is on, so zoom in on the paddock in Map first, then switch. Tapping a paddock to make it the active one only works in Map.
3D shows one paddock's real ground in 3D, rises and low spots and all, with its yield map laid over it in the map's colours, so a wet hollow or a poor ridge can be read straight against what it yielded. The first time anyone on the farm opens 3D, Phase fetches the ground under all the farm's paddocks at once (30 m elevation data, the same worldwide) and keeps each paddock's piece as an Elevation layer on that paddock in Spatial. From then on every paddock opens straight away, for everyone on the farm; only a paddock added later is fetched again, the first time it is opened. If a paddock already has its own elevation layer in Spatial (from a survey or RTK data), 3D uses that instead.
Drag to turn and tilt it, scroll or pinch to zoom, and click or tap the ground to fly to it; Reset view comes back. The card in the corner picks the paddock, switches Perspective / Top view (computer and tablet), True scale or Height ×N (the rise and fall stretched so a few metres across a kilometre can be seen; the number is how many times), and the colours: Yield (the map's scale) or Height (dark low to light high, with its own legend). It gives the ground's lowest and highest point, the fall between them and the paddock's average yield. On a phone the card is folded behind 3D settings at the top right, so the ground has the whole screen; tap it to open the card and again to close it. The elevation credit sits under the card (on a phone, behind Credits).
Yield by height splits the paddock into five bands of equal area, from Highest fifth to Lowest fifth, each with its average yield against the paddock, and one sentence says whether low ground yielded less, high ground yielded less, or there is no clear link. Tap a band to pick that ground out on the paddock; tap it again to show it all. Point at or tap the ground for its yield, how it compares with the average, its height and how far it sits above the paddock's lowest point.
Fetching the ground needs permission to edit the farm. Anyone else, on a farm whose ground hasn't been fetched yet, sees "<paddock> has no elevation yet" and is asked to have it fetched once. Phase has a daily allowance for these fetches across all farms; past it, a paddock not fetched yet says No more elevation today and loads the next day, while paddocks already fetched still open. Smoothing, range and colour scale in Settings apply to 3D too. Nothing in 3D changes your yield records; the only thing saved is each paddock's elevation layer.
Yield maps from John Deere Operations Center read in tonnes per hectare. John Deere's map file gives yield as a grain volume, and Phase converts it: if the paddock already has a yield for that season, the map is scaled so its average matches that yield; otherwise Phase uses John Deere's own harvest summary for the job, or the crop's standard grain weight. Maps imported before 2 October 2026 were corrected then, and seasons Phase had created from a John Deere map now show a lower yield, converted with the crop's grain weight. If you know the real tonnes for one of those seasons, edit the yield record; importing the map again then scales it to your figure.
What you can do
Import yield from John Deere: harvest yields, and whole-season yield maps (Phase Ultra)
Import from a spreadsheet or a yield-map shapefile
Add or correct yields by hand (Data → Edit yields)
Combine crops and varieties that arrived under two names
Log harvest loads into storage or delivered off the paddock
See everything delivered, from CBH LoadNet and loads logged in Phase, and each paddock's quality from its CBH loads
Put a $/t on any harvest, old seasons included, and see what each crop was worth
Compare every crop across seasons, and every paddock against the farm
View the whole farm's yield maps, and read them with Explore or in 3D on the paddock's real ground
Forecast this season's yield from its rain
Review water use efficiency (WUE) in kg/ha/mm
Forecast
Overview → Forecast & rainfall is always open at the bottom of Overview. Yield forecast starts with this season's rain, April to October: a bar of what has fallen so far since 1 April, what is still to come, and a mark for a typical season on that farm, with the season total the forecast uses.
The rest of the season sets what is still to come: Typical (the middle of your recorded years from today to 31 October), Dry or Wet (the driest or wettest fifth of those years), or My own to type an April to October total. Once October is over, the forecast uses the finished season and the choice goes away.
Under it, Every crop forecasts each crop on its own from its own harvests, all on one t/ha scale: the expected yield, the low to high range and, where the crop is planned this season, the tonnes that makes on the planned hectares (for example "≈ 2,987 t" on 973 ha). Each row also shows every past harvest as a tick and your average as a dashed line, and says how many harvests it learnt from. A crop without three harvests that each had a full April to October of rain uses its crop plan's yields and says so, or says how many more harvests it needs. Select a crop to see how rain has turned into its yield: each harvest against its season's rain, with a line in plain words such as "Wheat has made 10.4 kg/ha for every mm…".
Farm and Learn from (Every season, Last 10 seasons or Last 5 seasons) sit beside the heading. Farms on different rainfall grids are forecast one at a time, starting on the farm with the most history.
The forecast is one rainfall-use-efficiency model: each crop's kg/ha for every mm of April to October rain on your own harvests (the median for the expected yield, the 25th and 75th percentiles for low and high) times the season's rain. A year that is not a finished growing season is never used as history.
Harvest loads
Select Log load at the top of Yield Centre, or open a paddock's harvest activity under Map → paddock → Plan → Log a load. Choose Into storage for a silo or other structure, or Delivered off the paddock for grain sent straight to a receival site or buyer. Add the tonnes, docket details, grade or quality, truck and carrier where known.
The Harvest loads panel groups the season's stored and delivered loads by paddock and shows the resulting tonnes per hectare. Use Record as yield to create or update that paddock's yield record from its loads. A delivered load does not touch silo stock; it remains visible in the activity record, Harvest loads and the Totals view of Inventory → Grain & Hay.
A delivered load can be saved on an estimate and weighed off later (see Grain And Hay Storage). Open the load's date under Deliveries → Harvest loads for its detail: an estimated load shows its estimate and Record delivered weight, and a weighed one shows Delivery details for dockets and receipts. The yield uses the delivered weight once it is in. Export loads includes Estimated tonnes and Weighed off columns.
Log load opens the same sheets as Grain & Hay, so each starts with Read it off the docket: photograph the weighbridge or delivery docket, or choose a photo or PDF, and Phase AI fills in what the paper says for you to check before saving. Edit load details opens the form the load was recorded with, and every part of it can change, tonnes and whether it came in or went out included; the silos follow by the difference. A load's details name the contract it counts towards and its docket number, and a load the receival site refused shows Turned away. See Grain And Hay Storage for each of these.
Deliveries
Deliveries has a switch at the top, Delivered and Harvest loads, and remembers the side you used last on that device.
Harvest loads is every load off the header, into storage or delivered, with logging, editing, weigh-off, export and Compare with production. It is what the old Loads tab held.
Delivered is everything that left the farm in a season: every load CBH weighed, from CBH LoadNet, and the deliveries you logged in Phase, off the paddock or out of a silo. Chips across the top narrow it: All receivers, CBH LoadNet and Logged in Phase, then To sort and Deleted by CBH when there are any (dockets CBH deleted count for nothing).
The totals show what was delivered, how many loads and the latest one.
Each crop shows its tonnes, protein and screenings, with its grade mix and varieties.
Each load shows when it was weighed, the receiver, crop and grade, net tonnes, protein, screenings, and which paddock its quality goes to.
Export downloads the list.
A load you logged in Phase whose docket carries the CBH load number is the same load as CBH's record, so it is listed once. Once the farm is connected, a load you logged to CBH without a number is left out, because CBH's records already hold it. Grain into your own silos hasn't left the farm, so it is on Harvest loads, not Delivered. Delivered tonnes are a crop's total, never a paddock's yield: a truck often carries grain from more than one paddock.
Not connected yet? The farm's owner or an admin sees Connect CBH LoadNet on Delivered (anyone else is told who can), and Actions → CBH LoadNet deliveries opens the connection from anywhere in Yield Centre. Connecting, disconnecting and what Phase keeps are in Data Feeds.
The Deliveries tile on Overview shows the season's delivered tonnes, loads and crops, and how many loads are waiting to be sorted, and opens this tab. Connecting CBH LoadNet switches it on, after the weather, on the device you connected from; anyone else adds it with Customise → Widgets.
Which paddock a CBH load came off
Phase places each CBH load on a paddock in this order:
The paddock you chose. On Delivered, open a load by its date and pick a paddock, or No single paddock for grain out of storage or a mix of paddocks. Let Phase match it undoes your choice.
A paddock code written at the bin, once you have confirmed what it means. Under Paddock codes from the bin on Deliveries, Phase suggests a paddock for each code (PIGE looks like Pigeon Well) with a button to use it, or you can choose another paddock or Don't use this code. Phase never uses a code you haven't confirmed; once you have, every load with that code follows.
Harvest time, from John Deere's harvest jobs (the header's real start and finish on each paddock, reconciled or not) and Phase's own harvest records: the paddock harvested in the few hours before the load was weighed, else earlier that day, else the day before. If two paddocks were harvested then and neither was clearly the main one, Phase asks rather than guesses.
Loads Phase can't place are To sort: the To sort chip on Deliveries, the Deliveries tile and the CBH LoadNet page all count them. They still count in delivered totals; they just don't give any paddock its quality until they're sorted. Choosing a load's paddock and confirming bin codes need permission to edit the farm's records; anyone else can look but not change them.
Quality from CBH loads
When CBH loads are matched to a paddock, its harvest (Paddocks, open a harvest) shows Quality from CBH loads: protein, moisture, screenings, test weight, grades and varieties, weighted by tonnes and labelled Source: CBH LoadNet, estimate, because a load can carry grain from more than one paddock. Loads of a different crop matched to the paddock are named, not averaged in. A paddock's yield always comes from what came off it; delivered tonnes are never split back onto paddocks.
Use yield maps in Spatial
Phase Ultra Spatial can use a saved yield map when the selected paddock has at least three usable cells. Open More → Data Centres → Spatial and add the yield layer. Spatial can also retrieve a John Deere yield map from its import window.
Crop-specific yield
Yield is always crop-specific: a t/ha figure is one crop's, and crops are never added together. Season rating and % of average compare each crop with its own average, which is why different crops can sit side by side there. If one crop shows twice, its records are under two names: see Combine crops & varieties.
Latest actual yield
Latest actual yield refers to the most recent harvest date, not simply the most recently imported record.
Rainfall and WUE
Water use efficiency (WUE kg/ha/mm) is a harvest's yield for every mm of April to October rain on that farm. You see it, with GSR and Rain source, in the Data → Edit yields table.
The rain comes from each farm's SILO grid, unless you choose one of your stations under Overview → Forecast & rainfall → Rainfall for production; choose a station only when it has a complete April to October history. The same rain drives WUE and the forecast. Changing it does not change any yield record or the station's own rainfall history. Only an owner or manager can change a farm's rainfall source. If rainfall WUE looks wrong for a paddock, check its GSR and Rain source in the Edit yields table first, then the station's or gauge's own history.
If yield looks wrong
Check:
Harvest date
Crop, and whether it arrived under two names (Actions → Combine crops & varieties)
Variety
Field match
Unit
Area
The farm's rain source under Rainfall for production (for WUE)
Whether the record is imported, manual or from John Deere, and whether its Source says yield set by hand
On Maps, the season and crop chosen above the map, and Settings → Paddocks
