Skip to content
Assessment
LibraryProduction

How to register each field: code, area and history

When a field changes name or area, last year's yield, cost and soil results stop matching this year's, and nobody can tell which ground each record belongs to. A register with a fixed code, a dated area and a line per season lets you follow the same field from year to year.

Published Updated 16 min read
In this article

Last year the crew called one field “soy 3”. This year it is “the creek field”, and the 190 hectares (about 470 acres) written beside it came from nobody knows where. Its yield, cost and soil results no longer match last year’s, and its cost per hectare rests on an area nobody can vouch for.

Keep a register with one line per field: a code that never changes and an area you measured and dated, plus one history line per season (crop, sowing and harvest dates, operations). The boundary drawing may change; the code and the lines already written do not. With the register, every yield, cost and soil result stays tied to the same field from one year to the next. In this article a field is a piece of ground where the whole area gets the same crops on the same dates, so it has a single history.

What counts as one field in the register?

Two written definitions of what counts as a field (the unit of the register) give two answers, and the register has to pick one. The first comes from the FAO, the United Nations food and agriculture agency. Its manual for national farm censuses defines a field as a piece of land bounded by recognizable limits, such as paths or hedges. A field of that kind can hold more than one crop.

The second comes from Brazil’s agriculture ministry. It appears in a 2025 rule for its climate risk zoning (the official maps of the sowing dates with the lowest climate risk for each crop) that sorts areas by management level. There, a field is a delimited cultivation area inside a farm, defined by uniform conditions of management and cropping history, including sowing and harvest dates and operations. Operations here are the passes on the ground, such as tillage, spraying and fertilizing. It is the one written source here that ties the unit to its history, and history is what a register keeps.

The two disagree where it matters. Take a piece of land bounded by a road, with soybean on 80 hectares and corn on 50. By the FAO definition it is one field. By the ministry’s it is two, because the history is not uniform. From here on, “field” means the ministry’s unit: ground where the whole area gets the same crops on the same dates, so each field has one history. The register exists to hold history, and a unit that holds two histories answers the question “what happened on this ground?” for neither.

The price of this choice is that a paddock fenced as one, with two crops, becomes two fields in the register even if the crew still calls it one.

The sources give no rule for what comes next, so this one is the library’s own. Split a field the day two parts of it get different crops or dates. Retire the old code and never reuse it, create two new codes, and write the parent code and the date on each new line.

Figure: One field split in two when part of it changes crop. Illustrative values
A field with two crops becomes two fields with two codesField F-07 of 130 hectares carries soybean on the whole field in 2024/25. In 2025/26 soybean stays on 80 hectares and corn goes on 50. F-07 is retired and two fields are created: F-07A of 80 hectares and F-07B of 50 hectares, both naming F-07 as parent.One field, before and after the splitF-07, 130 ha2024/25: soybean on the whole field2025/26: part goes to cornSoybean on 80 ha, corn on 50 haF-07A, 80 haparent F-07F-07B, 50 haparent F-07

Can I trust the area I already have?

Only as far as you know how it was taken. The one study among the sources that measured this comes from West Africa, on small farms. The working paper is by two researchers of the International Food Policy Research Institute, a food policy research center. In it, farmers in Burkina Faso, Mali, Niger and Nigeria stated field areas that differed from the GPS measurement. The gap ran above the measure in Burkina Faso, Niger and Nigeria and below it in Mali, by the amounts in the figure. In Nigeria, 171 percent above means a stated area about 2.7 times the measured one.

The averages hide a split: small fields were overstated and large ones understated, and in all four countries larger farms tended to make larger errors.

Figure: Average gap between farmers' stated field area and the GPS measure, four West African countries. Mali is shown as a range because the authors give 40 percent in the conclusion and 49 in the table. Source: Goundan and Magne Domgho, 2016
Stated field areas strayed from the GPS measure in all four countriesAverage gap between stated and GPS-measured field area: 14 percent above in Burkina Faso, 18 percent above in Niger, 171 percent above in Nigeria, 40 to 49 percent below in Mali.Stated area against GPS area, average gapBurkina Faso14% aboveNiger18% aboveNigeria171% aboveMali40 to 49% below

Read this with care. These are household surveys of small farms, comparing what a farmer told an interviewer with a GPS measurement. A grain farm keeps its areas in a title, a map or the file of a GPS-guided tractor, and none of the sources tests how far such areas are off. One habit carries over to your farm: write the method and the date beside every area (walked, drawn on a map, taken from the title or remembered). Without them you cannot tell a measured area from a remembered one.

There is also a check that needs no equipment. The FAO manual states that the areas of a farm’s separate pieces of land, owned or leased, must add up to the area of the farm. On your farm, add up the fields and the land outside them that you have written down (reserve left uncultivated, roads and yards, buildings), and compare the total with the farm’s area on the title. A gap does not prove an error, and it does not say which field is wrong. So start with the field whose area you trust least, walk its boundary, and then go to the next one you trust least.

The example is a grain farm with six fields and a title of 1,200 hectares (a hectare is about 2.47 acres). F-03 is the creek field. The values are illustrative, and the farm is not real.

Why must the code outlive the crop and the boundary?

Because the records you keep by field all depend on the code, and they stop matching when it changes. The yield series of a field, described in how to read each field’s yield year by year, needs the same field in every season. A soil test report has one page for each field, as in reading the soil test report.

A lot of grain you sold, one delivery for example, is traced back to the ground where it grew by the field its record names, as in tracing a lot back to the field. If those records are filed under the crew’s name, “soy 3” this year and “the creek field” next, the old records and the new ones stop matching on the day the name changes. A code that never changes keeps them together.

Three rules keep the code stable. They are this library’s own, not findings of the sources. The code holds no crop, no year and no owner, so it is F-07 and never Soy-2026. The name the crew uses goes in its own column of the register line, and every record is filed under the code. A retired code stays in the register, marked retired, with its date and the codes that replaced it, and no code is ever given to another piece of ground.

Figure: One code, three records tied to it
One field code ties together yield, soil test and lot recordsField code F-07 on top. Below it, three records tied to the code: yield for each season, the soil test page with its date, and the sold grain lot traced back to the field.The code that does not changeF-07Yield, season by seasonSame field in every lineSoil test page, with its dateOne page per fieldSold grain lot, traced to its fieldThe trace ends at a code

How strong is the evidence for keeping a register?

Thin, and mostly indirect. The definitions above are written standards, and the area gap was measured, but in another setting. On whether keeping records pays, the nearest source is a 2023 review, in the scientific journal Heliyon, of 24 empirical studies on farmers’ decision-making and farm performance. It found studies that link record keeping to better efficiency (more output from the same inputs). But it rates the link between planning and monitoring with record-keeping tools and farm performance as not a conclusive finding.

Farms with different record habits also differ in other ways, so a comparison between them cannot show that the records caused the result, and this article claims no cause. None of the sources tests a field register on a large grain farm of the kind found in Brazil’s Cerrado, a savanna region that grows soybean and corn at scale. Keep the register for a plainer reason than a measured gain. A yield, cost or soil record can only be matched from one year to the next when the field has a fixed code and a dated area.

Figure: What each part of this article rests on
Definitions are written, area gaps are measured, record benefits are only comparedWhat a field is: written definitions from the FAO manual and Brazil's ministry. How far areas stray: measured in four West African countries on small farms. Whether keeping records pays: farms compared, the review calls it not conclusive, and no test was found on large grain farms.Strength of each claimWhat a field isWritten: FAO manual, Brazil's ministryHow far areas strayMeasured: 4 countries, small farmsWhether keeping records paysFarms compared; review: not conclusiveNo test found on large grain farms

What goes in the register, and where do I start?

Start with the field whose area you trust least, before the next sowing. The register has two parts: one register line per field, and one history line per field and season. The ministry’s rule for sorting areas by management level asks for three things on record for each area it sorts. They are the identification of the property and of its owner or tenant, the geolocation of the area’s perimeter, and the history of use and management. That sorting is valid only for the crop and season assessed, which is why the history needs a line for each season.

The register line, one per field, and what goes wrong without each column
Column What it holds What goes wrong without it
Code A short code that never changes and never repeats The history is lost when a field is renamed
Crew name What the crew calls the field The crew and the register talk about different fields
Area, in hectares The measured area, not the remembered one Every per-hectare number moves with the guess
Method and date Walked, GPS track of the tractor, drawn on a satellite image, from the title, or estimated, and when A change of method looks like a change in the field
Owned or leased Whether the land is owned or leased, and from whom A lease ends and its fields leave the register with no trace
Boundary A dated drawing or GPS file of the boundary The field cannot be found again after the boundary moves
Parent code The code it came from, if it was split or merged, with the date The history stops on the day of the split
Retired Yes or no, with the date and the codes that replaced it A retired code looks like a field still in use
The history line, one per field and season
Column What it holds What goes wrong without it
Season The crop year the line belongs to The lines cannot be ordered
Crop What grew on the field A drop in yield cannot be tied to a crop
Sowing and harvest The two dates The seasons cannot be compared on timing
Operations Each operation on the field, such as tillage, spraying or fertilizing, with its date What was done is kept only in memory
Source Who wrote the line, and whether it came from a record or from memory A line from memory cannot be told from a line copied from a record
Figure: The register of one field, with illustrative values
One register line and the history lines of field F-05Register line of field F-05, the back field: 174 hectares, measured by a GPS walk on 2026-03-10, owned, boundary drawing filed, no parent. History lines: 2024/25 soybean sown 2024-10-12 and harvested 2025-02-20; 2025/26 soybean sown 2025-10-08 and harvested 2026-02-14; operations listed with their dates.Field F-05, one registerRegister line: F-05, back fieldArea 174 ha, GPS walk, 2026-03-10Owned. Boundary drawing filed.Parent code: noneRetired: noHistory: season, sown / harvested2024/25 soybean 2024-10-12 / 2025-02-202025/26 soybean 2025-10-08 / 2026-02-14Operations: one line each, with its dateSource: written beside each line

Once the history lines exist, you can check a field against its planned crop rotation: see whether the field followed the rotation plan. The same history line can also hold the group of each product sprayed on the field: which spray group went on each field, and when.

A register like this is the base of the records kept under farm management. More on field records is in the production library. Related: Cost per bushel by field: your invoices over your harvest and Pest scouting sheet: write the action level first.

Provenance

Derives from
  1. FAO, A system of integrated agricultural censuses and surveys, Volume 1, World Programme for the Census of Agriculture 2010, FAO Statistical Development Series 11, chapter 11, paragraphs 11.53, 11.54 and 11.56
  2. Ministério da Agricultura e Pecuária, Instrução Normativa SPA/MAPA nº 2, de 8 de julho de 2025, Diário Oficial da União, 9 July 2025, annex, items 1.1, 3.3 and 4.1 (copy of the published text)
  3. Goundan and Magne Domgho, Land Area Measurement bias: Evidence from West African countries, MPRA Paper No. 75476, International Food Policy Research Institute, 2016
  4. Taramuel-Taramuel, Montoya-Restrepo and Barrios, Drivers linking farmers' decision-making with farm performance: A systematic review and future research agenda, Heliyon 9(10), e20820, 2023
What this article covers
Opening a register with one line per field (fixed code, crew name, measured area with method and date, whether the land is owned or leased, boundary drawing, parent code, retired or not) and a history of one line per season (crop, sowing and harvest dates, operations), the rule for splitting a field, and a check of the fields' total against the farm's area.
What it does not cover
How to survey or map land, which boundary is the legal one, and what the land registry of your country requires, which is for a surveyor or a lawyer. It also leaves out what to do with the history once it exists, such as yield by field or cost by field.
Published
Updated
Error found
Point out an error and the article is corrected with a note on what changed.

How to cite this article

Rurivia. (2026, October 27). How to register each field: code, area and history. https://rurivia.com/en/library/production/register-each-field-with-code-area-and-history/


Keep reading

Production

What goes on each cow's card, and how many have none?

When no card says when a cow last calved or what her calf weighed, a cull decision rests on what the ranch hand remembers. Five entries per cow, and a dated count of the cows without a card, give the herd a history.

Oct 28, 2026
Production

How do you know how much weight a cattle lot really gained?

What an animal has in its gut changes its weight on the scale, so the gain worked out between two weighings can come out smaller or larger than the real one. On a sheet per lot, you write the conditions of each weighing beside the weight.

Oct 27, 2026
Production

How many days did the bulls stay, against the plan?

A breeding season that runs past 90 days spreads the calving and lightens the late calves. Writing the planned and the actual dates for each lot shows the gap, what it cost, and how fast it can be closed.

Oct 28, 2026
Production

Do you have enough forage to last until spring grass?

A full silage bag and a stack of bales say little about how long the forage lasts. Weigh each depot in dry matter, subtract the loss still ahead of it, divide by what the lots eat each day, and decide to buy at the early end of the date range.

Oct 27, 2026

Farm Management

If this article were a plant, farm management would be the whole field.

Planning, organizing, leading and controlling: the four functions, what each one decides, and a farm example for each, all on one page.