What it is
The farm database is the list of every farm in your account. You reach it from the left-hand menu: select Farm Data, then Farms. It is where farms are created, found, filtered and opened.
There is one farm database for the whole account, not one per business unit. What you see in it depends on your permissions.
A farm record is the farm itself, not a year of its data. It holds the farm's code, name, region and location, plus the country and climate zone derived from its coordinates. Everything that belongs to a particular reporting year — the data you enter and the result it produces — sits in an assessment attached to the farm.
What the list shows
The Farms list has a column for each of CODE, NAME, COUNTRY, REGION, CLIMATE ZONE, LAST UPDATED, LAST CHANGED BY and TAGS.
Every column can be filtered, and your filters persist. If you filter the list to France, open a farm and come back, the list is still filtered to France. This is convenient during a reporting cycle and confusing the week after — if a farm you know exists is not in the list, clear the filters.
What sits on a farm's page
Select a farm's name to open its page. This is where everything attached to that farm is collected in one place:
- the farm's own details
- its assessments, year by year
- its past carbon results over time
- files uploaded against the farm
- visits logged by advisors
- notes
- the scenario groups the farm belongs to
- the insetting programmes it takes part in
Farms and regions
A farm belongs to one region at a time, and assigning one is optional.
Regions sit in a hierarchy that an administrator defines when building the region list — country above region above city, for example. A farm is assigned to one region in that structure, and its results roll up through every level above it during reporting. Assign a farm to a city and it also counts towards that city's region and that region's country, without you doing anything further.
Tags are the other way of grouping farms — informal markers an administrator makes available for your team to apply, useful for filtering the list. Regions are what reporting groups by; tags are not. For both, see Regions and supply groups.
Why it matters for your results
A farm is not an assessment, and this is the distinction worth getting straight before a reporting cycle. Adding a farm gives you a record, not a result. The farm is permanent and carries no year; the assessment is one year's data for that farm, and the result belongs to the assessment. A farm can sit in the database for years with no results at all if no assessment has been submitted for it.
Two parts of the farm record reach the calculation. The country and climate zone come from the coordinates you set, and both feed into a farm's results — for how, see the methodology documentation in the platform. The region does not change a farm's numbers, but it decides which group those numbers are reported under — and, through the hierarchy, every group above it.
Editing a farm does not restate results that have already been calculated. A change of region is reflected in reporting straight away; a change of coordinates applies from the next submission onwards. Edit farm data covers what to do if you find a location error after an assessment has been submitted.
Key terms
- Farm record — one farm's permanent details: code, name, region and location. Holds no reporting year.
- Farm code — your own unique identifier for the farm. The platform does not generate it.
- Region — the structured grouping a farm belongs to, and what reporting groups by. One per farm.
- Tag — an informal marker applied to a farm for filtering the list. Not used for reporting.
- Assessment — one farm's data for one reporting year, for one assessment type. Where results live.
