Land Management

Map land boundaries precisely with interactive polygon tools. FarmManager takes the field size from the polygon as you draw and recalculates it whenever the outline changes – with the same spherical area formula (WGS84 equatorial radius) as the map, so the map display and the stored size match. If a field is assigned to an official field block, the recorded size stays put; if the drawn area deviates from it by more than 10%, the form points this out. Drawing is helped by an address search, switching between street and satellite maps and undoing the last point; you can also enter each vertex as a coordinate with latitude and longitude, change or remove it, and return to the original outline. With the switch at the top right you show the map full screen, while drawing together with the address search and the drawing buttons; Esc or a second click ends full screen.

With the layer switch you add official maps, in the area overview, when you draw a field, on the forest map and on the map of the grazing plan. As base map you can choose the official aerial image (DOP) of the state survey offices or the topographic map TopPlusOpen of the Federal Agency for Cartography and Geodesy (BKG). On top you lay the field blocks, the cadastral parcels from the land register or the protected areas of the Federal Agency for Nature Conservation (BfN). If you trace a boundary along a hedge or ditch, you see the aerial image and the parcel boundary underneath. The services offered are those of the federal states in which the farm and its fields lie. For land on both sides of a state border, that means both. Aerial images and cadastral parcels exist for all 16 federal states, field blocks for ten. Cadastral parcels only appear once you zoom in close. Your browser loads the tiles directly from the respective agency, and only once you switch a layer on. The authorities’ data remain binding. In every plan, starting with the Field (Lite) plan.

For every field you keep the land type, status, soil texture, ownership, the country it lies in, environmental regulations and notes. If you create a leased field, you assign the lease contract in the same step from the Business (Pro) plan or create it there.

Separate a partial area from a field – you set two points on the map, FarmManager lays a straight cutting line through both and shows both parts with their hectares in advance. The larger piece remains the existing field with name, history, records and crop plans, the smaller one becomes a new, empty field; what has already been recorded is not moved over, because it describes what happened on the field at the time. Paddocks, water bodies and landscape elements that lie entirely within the separated piece move with it, the soil details from conditionality are carried over, and the FLIK assignment of both halves is dropped. FarmManager rejects a cut that does not produce exactly two parts, produces a piece under 0.01 ha or cuts through a protected landscape element. A drawn outline is a prerequisite.

From the Farm (Basic) plan, you subdivide a field into individual paddocks directly on the map. Drawing is constrained to the parent parcel's area and automatically prevents neighbouring paddocks from overlapping. All paddocks appear together on an overview map, and you can start a grazing plan straight from a paddock.

Start directions directly from a field or, from the Farm (Basic) plan, from a paddock – via a map service on desktop or your device's navigation app on mobile. For a field, you set the field access point on the map; it snaps to the field boundary, and navigation then leads there instead of to the middle of the field. If the map point is missing, you get an explanatory note.

In the “Map markers” tab of a field, you note what to watch out for there, for example the entrance, the stone at the headland, the wet hollow, a drainage shaft or the power pole. In the dialog, you open the map of the field, place the point and choose the type: gate or entrance, obstacle, stone, wet spot, drainage, wildlife, pole or other. When you are standing at the spot, “Use my position” takes your phone's location together with the accuracy the device reports; the map shows it as a circle around the point. A name is added and, if you like, a note and photos. Each type has its own symbol and colour, and so the markers appear on the map of the field, on the live fleet map and in the 3D terrain, where each type stands as its own figure, for example as a gate or a power pole. There the label shows the name when you tap it or point at it with the mouse, and when you zoom out, the view merges labels that lie close together into one with a counter. The roles that may edit the field can set and change them; everyone who sees the field can see them. Your own markers are available in every plan, starting with the Field (Lite) plan. From the Business (Pro) plan, with a John Deere connection the markers from the Operations Center arrive in the same list, with the provider as the source; they continue to be maintained there.

Track irrigation, fertilization, harvests and other events per field. View all details, automatically track costs in FarmManager and plan future activities. Over 25 operations are available, from ploughing, planting and fertilizing through pest control and liming to mowing, baling and chopping. Planned and completed field work appears with its date in the team calendar, and a click on a calendar day creates a new one there. Optionally record the machine used, operator, area worked in hectares and hours per activity. On site, “Field from location” opens a new event with the field you are standing on – FarmManager reads your device's location for this, and the field needs a drawn outline; for harvesting, mowing, baling and chopping the current crop is also pre-filled if you keep planting plans. For these events you record the quantity (dt, t, kg, pieces, bales or m³) even without a crop plan, for grassland cuts for example, and “Store” books it into storage – from the Business (Pro) plan.

You upload the field operations of your previous program as a CSV or Excel file in the list of field activities. Each row is one product; rows with the same operation ID become one operation with several products. The import takes over field (name, agricultural-portal field ID or FLIK), date, operation type, area worked, working hours, machine, operator, costs and notes. Operation types and products that FarmManager does not know you assign once in the dialog; the assignment stays saved for the next import. Quantities per hectare are converted with the area. The products appear as material use on the operation without changing the stock, in the Field (Lite) plan as text in the notes. The costs stay on the operation and are booked as an expense only if you wish. Plant protection products from your product catalog are also created as a plant protection application – only if complete, with crop, applicator and application rate per hectare, and never twice. What could not be taken over is listed in a notes file, and a second import of the same file creates nothing twice.

Maintain lab soil samples per field with sample reference, lab (e.g. LUFA), soil texture, pH, humus percentage, plus phosphorus (P₂O₅), potassium (K₂O) and magnesium in mg/100 g following the VDLUFA method. Three Nmin layers (0–30 / 30–60 / 60–90 cm) sum automatically into the total Nmin value. The 6-year DüV validity is tracked with a status badge and an “expired samples only” filter, and FarmManager reminds you of follow-up samples that are due. A further filter shows samples expiring soon. Above the list you see the number of samples, the average pH and the samples expiring soon; charts show the nutrient distribution per field, pH and humus of all samples as a scatter plot, the nutrient trend and the samples expiring in the coming 24 months. In the fertilizer demand calculation, “Pre-fill from farm records” takes over the phosphorus content, in plans for Hesse with the content class, as well as humus level and soil texture from the latest valid sample of the field, and the Nmin value only from a sample of the plan year. You take over your laboratory's result list as a CSV or Excel file; the import converts phosphorus, potassium and magnesium from element or oxide form and from mg/kg. A row with a sample number updates the sample with that number, one without a number the sample of the same field and day, and a sample created by hand without a number is supplemented instead of duplicated. From pH, humus content and soil-type group, FarmManager determines the pH class, the lime requirement in dt CaO/ha and the magnesium class according to VDLUFA; without these details there is no estimate. The DBE plan shows per field the lime requirement of the latest sample, and “Plan liming” creates the liming as a field operation.

Labs in Lower Saxony deliver their results for ENNI as a CSV file following the record description of the Chamber of Agriculture. You read that file in through “Import ENNI soil samples” in the list of soil samples. In the second step, each sample appears with the field FarmManager has assigned to it, matched by the analysis number of a sample that already exists, by the field number in the “CAP application” tab or by the field name. If the match is wrong, you pick the field yourself or create it on the spot. Only values by the CAL method are taken over. The import rejects results by DL or EUF and says why; nothing is converted. Reading the same file in a second time creates no duplicate samples, the existing ones are updated. You go the other way from the export menu with “ENNI soil samples (CSV)”. You choose the year of sampling and get the samples in this format, with the field number from the aid application. Before the download, a check shows which samples do not make it into the file and what they lack, for example the humus class, the soil texture or the field number. In every plan, starting with the Field (Lite) plan.

Under every arable field you find its humus balance, year by year up to the harvest you are planning right now. It is calculated in humus equivalents per hectare, using the lower VDLUFA values that also applied to Cross Compliance in the past. Cereals, maize, beet and potatoes draw humus down, peas, field beans and clover grass give some back, and a catch crop that stays over winter counts for more than one that freezes off in autumn. Straw that stays on the field is worked out from the recorded yield. If it is baled and taken away, you switch on “Straw taken off” on the harvest operation. Slurry, manure, digestate and compost come from the applications recorded as spread in the N plan, by quantity and dry matter. At the end you get the balance with its group from A to E and the average of the last three years. In crop planning the value stands next to every field, and below the board you see the area-weighted average of the farm. Where a crop has no factor, or the yield for the straw is missing, the table says so instead of estimating. In every plan, starting with the Field (Lite) plan.

A fertilizer application with a date in the N plan and a plant protection application appear without a second entry as a field operation in the field record – with field, date and area from the record, while costs, hours and weather stay on the operation; the list shows where it comes from. Conversely, “Document fertilisation” on a “Fertilization” operation enters the application in the field's N plan. If there is already a manually recorded operation for the same field and day, FarmManager links the two instead of creating a second one, and the export of the field record names each measure once. This also applies when importing the operations from your previous field record – the imported operation takes over the application or dose already recorded. An operation on which you yourself entered costs, hours, notes or material is deleted neither by the import nor by the deletion periods of the record; it stays, and the import's notice file names it for review.

When switching from another program, the “Data takeover” guides you step by step through taking over its export files – CSV or Excel, one file per data type. Fields, cropping history, field operations, soil samples, fertilizer applications and plant protection applications can be taken over, and from the Farm (Basic) plan animals too. FarmManager detects character set, separator, decimal comma, date format and the header row and suggests which column belongs where; you can change every setting. FarmManager remembers the column profile for your farm, so the next file with the same header runs through without a new assignment. Crops, operations or fertilizers in the spelling of the old program you assign once, a preview shows before saving which rows are conspicuous, and after the takeover you download failed rows with their reason as an error file. There are no ready-made formats for individual programs; every table is read by its columns. In the legacy archive you file field records, consumption data, plant protection and fertilizer records and posting lists of the old program unchanged, with SHA-256 checksum, by program, category and harvest year and, if you wish, per field; an archived document cannot be deleted before the retention period has expired. In every plan, even from the Field (Lite) plan.

Map the surface water bodies adjoining each field – watercourses, standing water, ditches or coastal water – with their geometry, water type and the distance from the field boundary to the bank; if you draw the shoreline, FarmManager calculates the distance itself. Whenever a field lies closer to water than the statutory minimum buffer width (3 m by default), a GAEC 4 conditionality finding arises. A mapped water body always takes precedence over a manually flagged buffer, so you get one accurate result per field instead of duplicate warnings. From distance and slope, FarmManager also determines the minimum distance under § 5 DüV (4 m on level ground, up to 10 m on steep slopes) and flags water bodies whose distance falls below it; the list can be filtered to “Non-compliant only”, and a chart shows compliance. You do not have to measure the slope yourself. “Slope from terrain model” lays a profile from the drawn shoreline into the field every 25 m, one 20 m long and one 30 m long, and the steepest profile counts. If the terrain model of the field is already loaded, this happens by itself when you save the shoreline. The value is shown below the input with source and date, and a value you enter yourself always takes precedence. The heights come from the European terrain model EU-DEM with a 25 m grid. The model does not see a sharp embankment edge, so a look on site is still worthwhile.

Record hedges, tree rows, single trees, field copses, ponds, wetlands, field margins, ditches, dry-stone walls, stone ridges and terraces directly on the map – as a point, line or area depending on the type; FarmManager calculates length and area from the drawing. Every element carries a flag for protection against removal. In the element's history you record new planting, maintenance, removal and restoration with date and reason, and for a removal after official approval also the file reference and a replacement measure. On fields with a conditionality profile, findings on GAEC 8 arise from this – the ban on removing protected elements, a note on the cutting ban from 1 March to 30 September and a warning if a removed element is documented without the approval's file reference. Active, protected elements count towards the share of non-productive area on arable land, which appears in the holding overview as the GAEC 8 traffic light; the minimum share is currently treated as voluntary and is only monitored. The area is counted without a weighting factor – lines without a recorded width with a default width per type, single trees with 20 m² per tree.

Upload the official InVeKoS field-block cadastre of your German state as a zipped shapefile or as GeoJSON. The state code is optional – without it, FarmManager derives it from the FLIK where possible. You enter the EPSG code of the coordinate system yourself if the data is not in WGS84 – 25832 or 25833 for ETRS89/UTM 32N or 33N, 3857 for Web Mercator; for WGS84 the field stays empty. Every field block is stored with its FLIK, the state and the official area in hectares, and every import run is logged with file, source, status and the field blocks read, created and skipped. With “Assign fields” you then assign to each field with a drawn outline the field block it lies in and take over its FLIK; a FLIK already set is kept when there is no match. In the reconciliation you see FLIK and official area next to your drawn area, with the variance in hectares and percent, and on the field's map the field block appears as an outline behind your drawing. “Adopt official area” replaces the drawn boundary with the largest contiguous part of the field block – only after a confirmation that names both areas, because a deliberately smaller drawn working area is lost in the process. A column and a filter “Geometry origin” distinguish drawn, imported and officially adopted fields. Once the cadastre has been read in, you can also create individual fields directly via their FLIK in the “Import geodata” dialog – without a file.

In most federal states FarmManager fetches the field blocks from the state itself. Once a week it asks the field-block service which blocks lie around your fields and compares them with the stored version. If the authority has redrawn a block, the new boundary is in the program afterwards. In the import list you see for every run how many blocks are new, changed or gone. Connected are Lower Saxony with Bremen and Hamburg, Brandenburg with Berlin, Bavaria with its Feldstücke, North Rhine-Westphalia, Saarland, Saxony, Schleswig-Holstein and Thuringia. Fields without a FLIK get their field block assigned afterwards, and a FLIK that still exists in the cadastre stays. If you have just drawn new areas, you do not have to wait for next week and press “Sync now”. Only a rounded frame around your areas goes to the state, no name and no farm data. Baden-Württemberg, Hesse, Mecklenburg-Western Pomerania, Rhineland-Palatinate and Saxony-Anhalt offer no open service. There you upload the file from the state portal yourself, as before. In every plan, starting with the Field (Lite) plan.

Every field has its own federal state. If your farm works land on both sides of a state border, for example with the farm in Lower Saxony and some fields in North Rhine-Westphalia, each field is in the right state. FarmManager reads the state from the FLIK or from the imported field-block cadastre. Without either, it takes the state in which the field lies from the official administrative boundaries. If no state can be determined from those either, for example because the field lies on a state border, FarmManager assumes the federal state from the farm settings or the farm address and writes under the field that this is an assumption. A state you choose yourself stays until you clear the field again. If nothing can be determined, the field stays empty. The fertilizer demand calculation and the closed-period check in the N plan follow the federal state of the field when the FLIK, the field block, the position of the field or your own choice backs it up. A state that is only assumed does not count there, and then the state of the plan applies. The calendar shows the closed periods and the “Compliance deadlines” list their end for all states in which your fields lie, and a new DBE plan suggests the state with the most hectares if it can already be selected there. In the field list you can show the “Federal state” column.

In the “Area designations” tab, every field shows the municipality, the district and the federal state in which it lies, plus the administrative region where there is one. The official key is shown under the name, so for the municipality the municipality key. The boundaries come from the VG250 dataset of the Federal Agency for Cartography and Geodesy (BKG). FarmManager imports it itself and checks every month whether the BKG has published a newer edition. If one is out, FarmManager reassigns the fields. It determines the position from the field boundary and, if a field has none, from the field access point. If a field lies on a boundary, you decide yourself which municipality applies, and your choice stays through every recalculation. In every plan, starting with the Field (Lite) plan.

For Berlin, Hamburg, Hesse, Mecklenburg-Western Pomerania, Lower Saxony, North Rhine-Westphalia, Saarland, Saxony-Anhalt and Schleswig-Holstein FarmManager takes the designated drinking-water and medicinal-spring protection areas from the open data of the states and updates them every month. Planned areas and drafts are left out. In the “Area designations” tab you then see whether the field lies in zone I, II or III, with the name and number of the area. Below it you find the source note of the state with the licence and a link to the dataset, as the licences of the states require. If you enter a fertilizer application on such a field, the check before fertilizing points you to the protection-area ordinance (§ 52 WHG). FarmManager does not judge what the ordinance allows, because every water protection area has its own. For the other federal states the areas are not stored yet. In every plan, starting with the Field (Lite) plan.

For Brandenburg, Schleswig-Holstein and Thuringia, FarmManager downloads the wetland and peatland area designation under GAEC 2. The erosion area designation under GAEC 5 comes for Brandenburg and North Rhine-Westphalia with water and wind erosion, for Thuringia with water erosion. FarmManager also updates this data every month. If a field lies within such an area designation, the “Area designations” tab shows it with the share of the field in percent and hectares and suggests taking the peatland or erosion class over into the GAEC profile of the field. Nothing is written to the profile until you accept the suggestion. In the other states you keep entering both yourself in the GAEC profile. In every plan, starting with the Field (Lite) plan.

You get your fields from the application portal of your federal state. Export the geodata of your aid application there and upload the file in the field list under “Import geodata”, as a ZIP with shapefile, as GeoJSON, KML/KMZ or GML, up to 50 MB. FarmManager detects the format and the coordinate system itself. Besides ETRS89/UTM 32N and 33N, WGS84 and Web Mercator it also reads the national systems of neighbouring countries: MGI Austria Lambert from Austria, LV95 and LV03 from Switzerland, Lambert-93 from France, RD New from the Netherlands and the official systems of Belgium, Poland, Romania and Bulgaria. Older German files in the Gauss-Krüger system, zones 3 and 4, it converts as well. If the file names no coordinate system, FarmManager infers it from the coordinates and your farm's country, flags the assumption as a note, and you can change it in the dialog. For older national systems such as MGI or Stereo70, FarmManager converts without the grid files of the survey offices; how accurate the conversion then is is shown in the review step. Before anything is written, a review step shows every field individually with hectares, FLIK and land use, plus the total across new and existing fields – deselectable row by row. A second import creates no duplicates: recognised fields are refreshed in outline, size and FLIK, while name, land type, soil and notes stay as you entered them. A field split by a road is broken up into several fields in the process. Once the agrirouter connection is released, from the Business (Pro) plan the field boundaries (shape) that arrived through agrirouter are also available in the same dialog under “Received via agrirouter”. There is no direct connection to the state portals. The dialog preselects the state from your farm's address and names the portal, with a link to the sign-in and the menu path to the export. On file are FIONA (Baden-Württemberg), iBALIS (Bavaria), profil inet (Brandenburg and Mecklenburg-Vorpommern), Agrarportal Hessen, ANDI (Lower Saxony), ELAN-NRW, FLOrlp (Rhineland-Palatinate), DIANAweb (Saxony), ELAISA (Saxony-Anhalt) and the Sammelantrag Schleswig-Holstein, and eAMA for Austria. For the other states the dialog has a general guide.

When importing from the aid application, FarmManager also takes over, for each field, the usage code with its wording and the field number, as far as the file contains them. In the review step the field number already appears next to each area. It is saved per application year in the “CAP application” tab of the field. If a field carried winter wheat in 2025 and oilseed rape in 2026, the 2025 application year still shows the wheat. The import takes the application year from the file and, if the file has none, from the “Application year” field in the import dialog. A second import for the same year refreshes the details from the file and leaves the other years as they are. In the tab you correct single values or create a year by hand, also for woodland. FarmManager does not link the code to the crops in the crop plan, because the code lists differ by state and year. In every plan, starting with the Field (Lite) plan.

Farms in Austria take their fields from eAMA. In the INVEKOS-GIS you request the applied-for fields as a shapefile under Extras › GIS Datenexport and upload the file in the import from the aid application. For a farm with an Austrian address, the region “Austria (eAMA)” is already selected in the dialog. FarmManager sets the land type from the Schlagnutzungsart (the land-use code in the file), so a mown meadow (Mähwiese) becomes grassland, while a Wechselwiese, a meadow in the crop rotation, stays arable land. In every plan, starting with the Field (Lite) plan.

FarmManager has no connection to iBALIS. The exchange with the Bavarian application portal runs through files that you download and upload yourself. You export your areas from iBALIS as a ZIP file with a shapefile and read the file in under “Import geodata” in the field list, with the same review step as for the other states. The import converts older files in the Gauss-Krüger system. For the way back, you choose “iBALIS: parcels and usage codes” in the export menu of the field list, and an application year. The ZIP file holds the fields as a shapefile in ETRS89/UTM 32 with the field number and usage code of that year, plus a CSV list with field name, field number, usage code, use, FLIK and area. You copy the codes from the list into the Flächen- und Nutzungsnachweis (the statement of areas and land use). The values come from the “CAP application” tab of the fields. Fields without a code for the chosen year appear in the file without one, and a notice tells you how many there are. The export appears only if your farm is located in Bavaria. In every plan, starting with the Field (Lite) plan.

From the field list, in every plan you export your drawn fields as a ZIP with GeoJSON (WGS84) and shapefile (ETRS89/UTM, zone 32N or 33N chosen automatically; farms with an address in Austria, Switzerland, France, the Netherlands, Belgium, Poland or Romania get it in the national system, that is MGI Austria Lambert, LV95, Lambert-93, RD New, Belgian Lambert 72, PL-1992 or Stereo70), per field with name, FLIK, hectares, land type and use category – as a basis for your aid application; fields without a drawn outline are skipped and listed. The field record (Schlagkartei) you output in every plan as CSV or JSON, per field with name, FLIK, area and GAEC status, plus, in chronological order, crop plans, field activities, plant protection applications and fertilizer applications.

If your farm has a Swiss address or manages parcels in Switzerland, you find the “ÖLN field calendar” in the export menu of the field list. You choose the harvest year and get, for each parcel, what happened that year: crop and sowing with variety, soil tillage, fertilization, plant protection with product, W number and amount, and finally the harvest with its yield. The PDF is meant to be shown at the ÖLN inspection, the CSV is for your own spreadsheet. Work is counted by harvest year. Plowing and fertilizing in October that you assigned to the winter wheat therefore appear under the wheat of the following year, and work without a crop counts in the calendar year. You can go back up to six years, the minimum period for keeping the records under Art. 25 DZV (the Swiss direct payments ordinance). In every plan, starting with the Field (Lite) plan.

The statutory deadlines are at the top of “To do” on the home page. Under “Manage all deadlines”, the “Compliance deadlines” list shows the upcoming statutory deadlines, sorted by the consequences of being late, each with status and sanction including the legal basis. For the collective application on 15 May this is a reduction per day of delay – until 31 May the deadline reads “In grace period” –, for agri-environment measures and eco-schemes it is rejection. FarmManager reminds you in the app 30, 14, 7, 3 and 1 day before, on the day of the deadline and daily during the grace period; a deadline marked as done or hidden no longer reports. The deadlines also appear in the calendar, next to the closed periods of the fertilizer ordinance. For farms with land in Austria, 31 January of every year from 2028 also appears there, the date for the previous year's plant protection records in electronic form. In every plan, starting with the Field (Lite) plan.

If the area monitoring cannot confirm something on the satellite image, such as the crop or the minimum activity on a meadow, the paying agency asks for georeferenced photos of the field (§ 41 (2) no. 5 GAPInVeKoSV). You record the request in the “Area monitoring” tab of the field, with the date, the request number from the photo app, the reason and the deadline. FarmManager suggests a deadline, which you can change to the date in the request. You take the photos with the field capture right at the field, even where there is no network, or you upload photos from your phone later in the office. FarmManager then reads location and viewing direction from the image data, provided the camera wrote them. For every photo it shows whether it was taken on the field or how many metres away. In the field list, the “Area monitoring” column uses a traffic light to show where a request is open, where the deadline is getting close and where everything is done. Before the deadline runs out, FarmManager reminds you in the app and by email. For your records you download a ZIP per request, with the photos, a table of the photo data and a map on which every place a photo was taken is drawn with its viewing direction. You still have to hand in the photos in the app or portal of your region; FarmManager sends nothing to the paying agency. In every plan, starting with the Field (Lite) plan.

If you are converting to organic, you record in the “Organic status” tab of the field where it stands: conventional, in the first or second year of conversion, or organic, each with start, end and the code of the control body as printed on the certificate. A running period stays without an end date. The periods of one field must not overlap, so exactly one status applies on every day. From the first day of conversion, FarmManager looks at the active substances of every plant protection application on the field. If the product is a herbicide, or an active substance is not listed in Annex I of Implementing Regulation (EU) 2021/1165, a warning appears. Copper, sulfur or Bacillus thuringiensis pass. For fertilization, the app speaks up for sewage sludge, also as compost, and for mineral nitrogen such as calcium ammonium nitrate. If you know better for a product or fertilizer, for example a preparation used only in traps, you change the classification there yourself. Whether the warning is only shown, has to be acknowledged or blocks depends on the check mode for plant protection and fertilization. For GAEC 7, the farm counts as an organic farm as soon as at least one field is in conversion or organic and none is recorded as conventional. In every plan, starting with the Field (Lite) plan.

When an inspection is announced, the “Inspection dossier” page assembles what you have recorded in FarmManager anyway. You select the inspection and the period. For the specialist-law inspection on plant protection, the dossier contains the application records, also in the machine-readable format under Implementing Regulation (EU) 2023/564, plus the certificates of competence and the sprayers. For the specialist-law inspection on fertilization, it contains the fertilizer demand assessments and fertilizing measures, Annex 5 with the 170 kg limit, the storage capacity under § 12 DüV and the manure handed over and taken in. The conditionality inspection takes both and adds the GAEC status of the fields, the field record and the landscape elements. The inspections for animal identification and veterinary medicines, QS and QM-Milch, occupational safety and food hygiene can also be selected; they are described under Quality, Safety & Traceability. For organic farms there is the organic inspection, with the organic status of all fields including the control body, the plant protection products and fertilizers on organic and conversion land, the plant protection and fertilization records and the livestock medicine register (Bestandsbuch). It names as a gap a product that is not permitted, a period without a control body or a field without a status. The page is available in every plan, even from the Field (Lite) plan; the dossier contains only what your plan includes and what you may see.

Before you create the dossier, the page shows what an inspector would miss in the selected period, such as a plant protection application with missing mandatory details, an expired certificate of competence, a device without a valid inspection plaque, fertilizing without a fertilizer demand assessment or a field without GAEC details. A click opens the record you need to complete. The dossier is built in the background as a ZIP file, and FarmManager notifies you as soon as it is ready. The table of contents as a PDF lists the checkpoints of these three inspections in the order of the Hessian conditionality brochure and names the folder with the evidence for each point, the gaps found and a SHA-256 checksum per file. What the inspector looks at only on the farm, such as the storage of plant protection products, is listed there as “show on site”. The dossier can be downloaded for a limited time, after which FarmManager deletes it.

You upload the TASKDATA folder from the USB stick of an ISOBUS terminal or the ISOXML export of another field record system as a ZIP; a single TASKDATA.XML works too; ISOXML versions 3 and 4 are read. Before saving, a preview shows every sub-area with area, crop and farm, and whether it is newly created or updates an existing field – recognised by the name, after a renaming by the congruent boundary. FarmManager subtracts cut-outs such as a hedgerow from the area, the field access from the file is taken over, and a boundary from the agricultural portal or from the official field block stays as it is. The origin “ISOXML import” is visible and filterable in the field list. Devices and drivers from the terminal you assign once to your machines and persons, products – with the stock from the Business (Pro) plan – to your stock items; the assignment applies to all further imports. Customers from the file you create as customers right away from the Business (Pro) plan. Once the agrirouter connection is released, master data can also arrive through agrirouter from the Business (Pro) plan; you then find it in the same dialog under “Received via agrirouter”. Orders that the terminal has run you read in under “Machine data”. In every plan, starting with the Field (Lite) plan.

Under Agriculture › Machine data, you upload the TASKDATA folder from the USB stick as a ZIP or just the TASKDATA.XML file; ISOXML versions 3 and 4 are read. Once the agrirouter connection is released, from the Business (Pro) plan the orders also arrive on their own when your terminal sends them via agrirouter, and you get a notification. Every order that the terminal actually worked on then appears per product as a row in the inbox, with date and time, machine and driver. Area, quantity and working time come from the implement that did the work, such as the sprayer, the spreader or the seed drill. If an order involves several implements without ISOBUS and none of them counted anything, the tractor stays the machine, the implements are listed next to it by name, and a notice says that the hours come from the tractor. The counted quantity comes along even if the file assigns no product to it, for example the kilograms of a seed drill; FarmManager then suggests the type of work from the implement type. If the file assigns no product but the planning of the order (the treatment zones) names exactly one, FarmManager takes over that product with a check notice saying it comes from the planning. If a counter restarts in the middle of an order or drops to 0 at the end, the total keeps what it had counted before, and the order gets a check notice. Planned orders that were never started and empty orders that were only opened and closed again stay out. Next to every quantity it says what it is: counted for the product alone, total at the implement, or calculated from the mixing recipe of the file. FarmManager finds the field by name, FLIK or outline. It recognises products, fertilizers, machines and drivers by the assignments from the ISOXML master data import or by an unambiguous name, and what does not fit you choose when accepting. In doing so you check type, field, date, area and quantity. If FarmManager had to fall back on another value, such as the area of the tractor, or if the area is clearly larger than the field, a check notice appears at the top of the dialog. A spraying run becomes a plant protection application together with the work operation, and the notes from the approval register then appear on the order. The litres a sprayer counts are the spray liquid made of water and all products in the tank load. FarmManager enters them as spray volume per hectare and never as the application rate of the product. You enter the application rate and its unit yourself; it is pre-filled only if the terminal counted the product on its own, for example with direct injection. A fertilizing becomes the work operation and the dose in the N plan if there is a fertilizer demand assessment for the field and year; otherwise only the work operation is saved, and the order says so. Sowing, harvest with yield and other work become work operations in the field record. You always accept plant protection individually, because someone has to confirm the application rate. Orders with a check notice about area, quantity or product, and fertilizing whose litres come from a sprayer, also stay open for the dialog. You can also accept the other orders in bulk. The same file is recognised and not read in again, and a later stick brings only the new orders. FarmManager rejects an archive that contains further TaskData archives; you upload those archives individually. From the Business (Pro) plan, as-applied maps, for a combine harvester yield maps, are also made from the time logs of the terminal, and the work operations from the John Deere Operations Center also arrive here through the telematics connection, one order per variety, product or fertilizer. In every plan, starting with the Field (Lite) plan.

You download spray orders, planting plans and the fertilizer demand assessment with “Download TaskData (ISOXML)” as a file to ISO 11783-10, for a single entry, for the filtered list or for the selected rows. You copy the TASKDATA folder from the ZIP file onto the USB stick. The file holds one planned order for every field, with field boundary, field access, FLIK and crop. From a spray order only the fields that are not yet done go along, and a cancelled order stays out entirely. The tank mix carries the name of the order, with the water volume per hectare as the target value and each product with its application rate, and the applicator is listed as the driver. From the N plan come only the doses that have no date yet or are planned for today or later, with the quantity in cubic metres or decitonnes per hectare. The planting plan brings field and crop; seed and seed rate you set at the terminal. Every download appears in the activity log of the entry. In every plan, starting with the Field (Lite) plan.

So that your fields are already set up on the terminal before the first order arrives, choose “Field boundaries as ISOXML” in the export menu of the field list, for the filtered list or for the selected fields. The file holds boundary, FLIK, area and field access of every field, but no order. You copy the TASKDATA folder from the ZIP file onto the USB stick. From the Business (Pro) plan.

A field you only know from the lease contract you bring in by Gemarkung, Flur and parcel number (Zähler): FarmManager queries the German state's official Flurstück service with it and creates outline and official area as a field – no file and no field-block catalogue needed. Several matches for one parcel number are normal and are offered for you to pick from. What comes back is geometry and area only, never ownership or land-register data. Connected are Baden-Württemberg, Brandenburg, Hamburg, Hesse, Mecklenburg-Western Pomerania, Lower Saxony, North Rhine-Westphalia, Rhineland-Palatinate, Saarland, Saxony, Saxony-Anhalt, Schleswig-Holstein and Thuringia. You may leave the Flur empty, for example in Saxony or Hamburg, where there is none. Bavaria, Berlin and Bremen are not connected; for them the route stays the export from the aid application.

If a field has a drawn boundary, “Cadastral parcels in the field” shows which Flurstücke lie underneath. For each one you see Gemarkung, Flur and number, the official area and how much of it lies in the field, plus the total and the source credit of the state. Only the box around the boundary goes to the cadastre; FarmManager works out the share itself. Nothing is stored. Flurstücke that reach under the boundary with only a small corner are left off the list. In every plan, starting with the Field (Lite) plan.

For the EU Deforestation Regulation (EUDR), you export your fields from the field list as GeoJSON in the format of the EU information system – WGS 84, accurate to six decimal places, closed polygons, with field name, hectares and country of production (selectable per field, otherwise from your farm address) – for upload to TRACES. In addition there is a template for the due diligence statement in the data model of the EU information system; you add HS code, quantity and signature yourself. For cattle, FarmManager provides – from the field list as well as from the animal list – a template of the EUDR declaration with geolocation of barns and pastures, simplified or as a due diligence statement depending on company size; the animals are included from the Farm (Basic) plan, the barns from the Business (Pro) plan. FarmManager transmits nothing to the EU information system – you upload the files yourself and check them beforehand.

There are three land types for woody areas because the law treats them differently. A field of the type Woodland shows no crop plan, no GAEC classification and no entries under the Fertilizer Ordinance (DüV), because that applies to utilised agricultural area. Woodland does not count as utilised agricultural area either, which FarmManager uses for the 170 kg N limit and the livestock density per hectare. Under the Federal Forest Act (Bundeswaldgesetz), short-rotation coppice and agroforestry systems are not forest. They therefore have their own land types and remain agricultural land. When you import the aid application, fields whose use says “Kurzumtrieb” (short rotation) or “Agroforst” (agroforestry) get the matching type straight away. For areas imported earlier, you switch the type by hand. The farm profile has the activity area “Forestry / woodland” for this, and anyone who signs up with the Field (Lite) plan is asked during setup whether they manage woodland. A pure forestry farm then removes “Cropping / Land” in the farm profile and afterwards sees its fields, the forest stands, the timber lots, plant protection and the EUDR declarations in the menu, but not the fertilizer demand assessment. In every plan, starting with the Field (Lite) plan.

Under “Forest stands” you divide a woodland parcel into its stands, for example the old spruce on the north slope, the Douglas fir plantation on the former bark-beetle area and the alder carr by the stream. Each stand gets its forest location with compartment, sub-compartment and sub-area and a boundary that you draw on the map inside the woodland parcel. If you enter no area, FarmManager works out the hectares from the drawing. You record the tree species separately by overstorey, intermediate layer, understorey and regeneration, each species with share and age. The catalogue holds 51 tree species with German and botanical names. You enter stocking degree, standing volume and increment yourself, from the forest management plan or by your own estimate. The list then shows the leading species and the standing volume per hectare and for the whole stand. In every plan, starting with the Field (Lite) plan.

For each stand you record which protected areas it lies in, for example a Habitats Directive site or a water protection zone, and on which day it was first afforested or converted to another use. If one of these dates falls after 31.12.2020, the cut-off date of the EU Deforestation Regulation, the list points it out. That is not a legal assessment. An administrator enters the forest area from the contribution notice of the agricultural social insurer SVLFG under “SVLFG check”. A tile above the list puts it next to the sum of your stands and, if they differ, names the difference in hectares. In every plan, starting with the Field (Lite) plan.

If you manage your woodland according to a forest management plan, the key figures from it are with the forest stands. Under “Allowable cut (Nutzungssatz)” farm management enters the allowable cut the tax office sets for ten years, in harvest cubic metres without bark per year, and the day the period starts. In the “Forest management planning” tab, tiles show whether the period is still running or has expired and by when the plan has to reach the tax office, which is one year after the start. This is an aid for keeping track and not tax advice. A chart splits your woodland by age class and tree species. It works with the layers you maintain on each stand, and an age class without area stays in the picture so that the gap stands out. On each stand you also record the target stocking, for example 50 % beech, 30 % sessile oak and 20 % sycamore maple for the old spruce area on the north slope. Forest management planning belongs to the Business (Pro) plan; the forest stands themselves are available from the Field (Lite) plan.

On a woodland parcel the tab is called “Forest objects and markers”. There you draw forest roads and skid trails as a line, damage areas and protection or set-aside areas as an area. As a point you set landings, habitat trees, fire water points, rescue points and boundary stones, if you like with “Use my position” and the accuracy the phone reports for it. For a boundary stone this helps you find it again and is no survey. For a forest road you enter the road class and the width and whether a timber truck gets through, for a habitat tree the day it was marked and for a rescue point the number on the sign. From the skid trails you have drawn, FarmManager works out their total length and the average spacing as an approximate value. FarmManager does not compare it with any requirement from PEFC, FSC or a funding programme. To record forest objects the phone needs a connection; recording in the forest without a network does not exist yet. In every plan, starting with the Field (Lite) plan.

The “Forest map” button above the field list opens all woodland parcels of the farm with their forest objects on one map. You switch each type on and off individually if you only want to see skid trails and rescue points, for example. A click on an area shows the link to the field. The button appears as soon as the farm has a field of the type Woodland. In every plan, starting with the Field (Lite) plan.

Many forest owners submit the declaration under the EU Deforestation Regulation themselves in the EU information system, or their forestry association (Forstbetriebsgemeinschaft) or an authorised representative does it for them. Under “EUDR declarations” you file such declarations in FarmManager, with reference and verification number, the date, the declared quantity with unit, your identifier such as the SVLFG company number, and the areas the goods come from. Short-rotation coppice and agroforestry areas can be assigned in the same way. For the buyer who takes the timber first, FarmManager prints an evidence sheet from it as a PDF. It passes the numbers on and does not replace the declaration. Here you also file declarations for cattle or for the goods from your areas that you submitted outside FarmManager. A declaration can be deleted only once its retention period has expired; the date is shown on the declaration. On a timber lot you choose the declaration the wood belongs to. In every plan, starting with the Field (Lite) plan.

Under “Timber lots” you keep every log pile with the number that is also on the tag and the stand the wood comes from. You set the position on the map, or you take your own position at the pile. The accuracy the phone reports is stored with it, because under a canopy it is often several metres off. Grading follows the German framework agreement for the roundwood trade (RVR). You choose the tree species, and FarmManager fills in the RVR species group, hornbeam for example under beech. Sawlogs get a quality class and a diameter class. You enter the quantity in the unit it was measured in, so in solid cubic metres, stacked cubic metres, loose cubic metres, oven-dry tonnes or pieces. For industrial wood by the forest road, a small calculator works out the stacked volume measured by sections from pile length, mean height and piece length. Next to it is a solid-metre value from the RVR conversion tables, with its source. It shows you roughly how much wood has been felled. The RVR rules it out as a sales measure, and the form says so too. For each lot you record how the wood is placed on the market under the EU Deforestation Regulation: with your own declaration, through the forest owners' association (Forstbetriebsgemeinschaft) with its name and number, sold standing, or for own use. If the lots of a declaration add up to more solid cubic metres than declared, the form warns you. Photos of the end face and the tag are attached to the lot. For the buyer or the haulier you print the timber tally sheet with number, assortment, quantity and position, without prices, for one lot or several. In every plan, starting with the Field (Lite) plan.

If you market your wood yourself, you have to declare it under the EU deforestation regulation. In the timber lot list, “EUDR · Wood declaration template” builds that declaration from the lots you declare yourself: as a simplified declaration if you are a micro or small enterprise, otherwise as a due diligence statement. Depending on the assortment, the wood is listed under a six-digit HS subheading of 4403 or 4401, with tree species and solid cubic metres. FarmManager picks the subheading by tree species and, for roundwood, by the diameter of the lot, pine of 15 cm and more, for example, under 4403 21. If the sawmill's mill measurement is already in for a lot, FarmManager counts that, otherwise the conversion value under the RVR. Only the stands the wood comes from are geolocated. If a stand has no outline of its own, the file carries the boundary of its woodland. Lots that the forest owners' association declares for you, that were sold standing or that go into your own stove stay out, and FarmManager lists them for you. “EUDR · GeoJSON of the stands” also delivers the outlines as a file for upload to the EU information system. If a stand records a conversion after 31 December 2020, FarmManager points this out when you download. This does not replace legal advice. In every plan, from the Field (Lite) plan.

When a storm has blown down spruces or bark beetle has been in the stand, you tick “Salvage wood” on the timber lot, choose the cause and enter the day of the damage. As long as the date of the report to the tax office is missing, a task stays in your task list, due on the day of the damage. As soon as you enter the report date on the lot, it is done. Farm managers and agronomists also write on the lot who took the wood, whether mill, forest owners' association, timber merchant or private customer, plus settlement date, mill measurement, revenue and deductions. Nothing is booked in the process, and other roles do not see these entries. If the lot is part of a timber sale, they come from the sale. The lots feed the “Timber evidence” under § 34b EStG. For each fiscal year of your farm it shows how much wood was sold and how much you took for yourself, split into ordinary use and calamity. Farm management enters the start of the fiscal year and the allowable cut from the forest management plan under “Allowable cut and financial year (Wirtschaftsjahr)”. With up to 50 ha of woodland the evidence also shows the flat-rate business expenses under § 51 EStDV, 55 percent of the income for felled timber and 20 percent for sales standing. You save each year as a PDF for the tax advisor. The evidence is a calculation aid and does not replace tax advice. In every plan, starting with the Field (Lite) plan.

Under “Timber sales” you settle the wood you have sold. A sale combines the lots that one buyer settles on one day, for example the three spruce piles the sawmill collected in March. For each lot you enter the mill measurement, the mill’s quality class, the price per solid cubic metre and the deductions for marketing or skidding, and below each row you see the shrinkage compared with the measurement in the forest. The sale books the revenue once as income, with the income type “Timber sales”. The tax rate that goes with your taxation is suggested, 5.5 % under § 24 UStG for wood from your own forest and 19 % under standard taxation. Firewood and wood chips for burning you switch to 7 % under standard taxation. If the sawmill sends a self-billed invoice as an e-invoice and you book it against the sale, only the difference is booked. After that the sale can no longer be deleted, and its lots do not go into a second sale. Firewood for a private customer or wood for a timber merchant, on the other hand, you invoice yourself. “Create invoice” in the row menu creates an invoice draft for it, with one line per lot in solid cubic metres times price and at the tax rate of the sale. When the buyer pays, the payment takes over the income of the sale, so the revenue is booked only once. A sale can have an invoice or a self-billed invoice, not both. The “Evaluation” shows mill measurement, shrinkage and revenue per solid cubic metre for each stand and year. Timber sales appear in the menu when “Forestry / woodland” is ticked as an activity in the farm profile. From the Business (Pro) plan.

Where your forest borders a public road, a car park or a building, you document in the “Roadside tree safety” tab of the woodland parcel when someone last looked at the trees. You draw the section along the road as a line and set a single tree as a point, if you like right at the trunk with “Use my position”. Both also appear on the forest map. For each inspection you enter the date, whether the trees were in leaf or leafless, who inspected, the result (no defect, defect or acute danger) and the finding with photos. For a defect, the dialog asks for a measure with a deadline. That becomes a task in the task list, with high priority for acute danger, and once you enter “Measure done” and the date, it is ticked off. How often to inspect is up to you, for example together with your tree inspector. FarmManager keeps the next inspection per section or tree as a recurring task that moves on to the next date with every newly recorded inspection. The “Inspection report (PDF)” summarises all inspections of the field for a period of your choice and counts the open and overdue measures. If a section or tree was not inspected in that period, the report says so too. The report reproduces what you recorded and is not legal advice. In every plan, starting with the Field (Lite) plan.

Every field has a “Game damage” tab, on arable land and grassland as well as in the forest. There you enter when you noticed the damage, which game species it was and which type of damage, such as browsing, bark stripping or rooting. You add the affected crop, your estimate in euros and photos that are stored unchanged. You type the damaged area in hectares or draw it on the field map, and FarmManager works out the size. You keep your claim to compensation only if you notify the damage to the competent authority in time, usually the municipality (§ 34 BJagdG). On arable land and grassland that is one week after you noticed the damage, in the forest notifying by 1 May or 1 October is enough. FarmManager works out the deadline as soon as you enter the date, and the list shows whether the notice is still pending, the deadline has passed or the damage has been notified. As long as no notice date is recorded, FarmManager reminds you in the app and by e-mail of damage whose deadline ends within the next 14 days or has just passed. “Notice (PDF)” creates the letter to the authority with field, damage, liable party, hunting district and deadline. You have to sign and hand it in yourself. On woodland parcels the dialog also asks whether the main tree species does not otherwise occur in the hunting district and whether the culture had a fence or individual tree guard. If the protection is missing for such a culture, FarmManager points to § 32 (2) BJagdG: the damage is then not compensated, unless the federal state provides otherwise. The calculation follows the Federal Hunting Act; a state hunting law may differ. In every plan, starting with the Field (Lite) plan.

On a woodland parcel you write the order for a felling in the “Work orders” tab: the felling area with location and boundary, the task with the order of work and the access for ambulances and timber trucks. You choose the person in charge on site and the people on the team from the people of the farm. You enter the chainsaw course once with the person, with its date, and the order immediately shows for the team who lacks it. People from the forest contractor or helpers without access to FarmManager you add with their course as text. You also link the risk assessment the work is based on and the safety instruction the team received. If someone works alone with a chainsaw or a winch, you tick working alone and note whether an emergency call system is at hand, for example a mobile phone with an emergency call function. If it is missing, the dialog shows a red notice pointing to the accident prevention regulation for forestry (VSG 4.3), and the order gets a red symbol in the list. FarmManager does not place an emergency call. The team gets the order as a PDF together with the forest roads, landings and skid trails of the parcel, the habitat trees and protection areas that are to be left standing, the rescue points from the Forest objects tab, the emergency call number 112, the protective equipment under VSG 4.3 and the team list with the chainsaw courses. In every plan, starting with the Field (Lite) plan.

You enter work in the forest like any other operation in the field record, with the stand where the work was done. The choices are planting, tending of young plantations, cleaning, thinning, final felling, bark-beetle inspection, forest road construction, fencing and browsing protection, high pruning and advance regeneration. When a forestry contractor does the job, you add the contractor's name and certificate with number and expiry date, and the form points it out if the certificate had already expired on the day of the measure. For a planting, each delivery from the nursery gets a row of its own with tree species, number of plants, category, region of provenance, assortment, master certificate, delivery note and supplier, and you photograph the label along with it. Below that you note whether a fence or individual guards were put up and on which day. For the bark beetle, “Plan bark-beetle inspections” creates a recurring task on the stand with a checklist for the round. You enter the finding of each round as a bark-beetle inspection, with the deadline for clearing the wood in case of suspicion or infestation. From an infestation, “Create calamity lot” makes a timber lot in which stand, cause, day of damage and deadline are already filled in. Thinning and final felling gather the timber lots that come from them as a felling. That way farm managers and agronomists see per felling and per stand what the measure cost and what the wood brought in, as a calculation aid and without booking anything. In every plan, starting with the Field (Lite) plan.

Fields are rendered to scale as terrain; the elevation data comes from the stored cache and does not slow the view with queries. Crop type, landscape elements, water bodies and soil samples sit as toggleable layers over the terrain - depending on the data available. The fields can be coloured by land type, crop, slope, fertilizer demand or soil status, water bands show in colour whether the minimum distance is kept, and you add paddocks and grazing herds as further layers. A field's info box names the crop, mean and maximum slope, the erosion risk from the conditionality profile, fertilizer demand and soil values. If telematics is connected, a further layer shows the machines with their driven track of the last four hours; when a machine is working on your fields, it switches on by itself. Which layers you see depends on the plan – the crop layer is available in every plan, fertilizer demand and telematics from the Business (Pro) plan.

Every hour of the DWD MOSMIX forecast is rated as suitable, marginal or unsuitable based on precipitation, wind, gusts and temperature - with a reason. The next suitable window is visible at a glance: FarmManager searches for it across the whole forecast period of the DWD model; the hourly table shows the next 24 hours. The rating gives guidance values without legal force; the label instructions of the products used remain binding.

The DWD forecast for the next 48 hours is summarized for frost, heat for crops, heat stress for animals (THI) and infection-favourable conditions. Reported are, among others, minimum temperature, frost and heat hours, the highest THI value and the longest infection-favourable phase. In addition there are disease forecasts over 120 hours for the crop that the crop plan puts on the field, as well as the currently measured weather of the nearest DWD station. Everything is an advisory aid and is available for fields with a drawn outline.

In a field’s weather dialog, FarmManager runs seven published forecast models and shows the ones that fit the crop in the crop plan. For potatoes these are the Smith periods for late blight. For wheat, Fusarium head blight, brown rust and yellow rust join Septoria, and triticale gets the same models without Septoria. For rye, brown rust runs with its own, cooler temperatures. On winter oilseed rape in flower, the SkleroPro infection criterion for Sclerotinia stem rot runs, and if you have beet standing, you see the Cercospora daily values by the method of the University of Nebraska. For Fusarium head blight FarmManager also looks at the preceding crop: if maize stood on the field before, a displayed infection risk goes up by one level. If the crop plan shows nothing on the field at the moment, all models appear. The calculation uses the DWD forecast for the next five days. If a model sees a high risk for the crop on one of your fields, a notice arrives in the bell in the morning and by email, as you have set your reminders. It is no call to spray, and the forecast does not replace walking through the crop. In every plan, starting with the Field (Lite) plan.

Every field has a “Vegetation” tab – with the NDVI trend from images of the Sentinel-2 satellites, per recording day with the mean and the range from the 10th to the 90th percentile, an NDVI map of the chosen day over the field with 10 × 10 m per pixel and a table of all evaluated days. FarmManager removes clouds, cloud shadows, cirrus and snow pixel by pixel, and days on which too little of the field is visible do not count. If the mean NDVI drops markedly, a notice appears – that can be harvest or cutting, but also drought stress, frost or disease. For woodland, FarmManager instead compares the last weeks with the same weeks of earlier years, so that leaf fall and leaf flush trigger no notice. If the forest is markedly below, the notice “Woodland weaker than in earlier years” appears with both values and the years. The index does not say what the cause is, and FarmManager does not detect bark beetle infestation with it. The comparison needs clear images of the same weeks from an earlier year and therefore usually appears about half a year after the first fetch. FarmManager searches for new images regularly by itself, for grassland, woodland and for fields with a current crop from crop planning; “Fetch now” starts the search immediately. A drawn field boundary is required. The images come from the Copernicus Data Space Ecosystem of the EU, which runs on behalf of ESA in data centres in the EU. FarmManager divides its monthly quota evenly among all farms. If your farm’s share is used up, FarmManager keeps searching in the open Sentinel-2 copy, and no recording day is evaluated twice. The “Source” column shows where a day comes from. You do not need an account with a satellite service of your own, and only a rectangle around the field, rounded to about 100 m, goes to the data services, never its boundary. In every plan, starting with the Field (Lite) plan.

Almost every field has spots that lag behind year after year, often a wet hollow or a hilltop with shallow soil. FarmManager looks for them in the Sentinel-2 images already stored for the field. Only days count on which nearly the whole field is clearly visible and a crop is standing. Each image is related to the field average, so a dry summer weighs as much as a wet one. In the “Vegetation” tab you pick the years and two to five zones, either of roughly equal size or split where the values differ most. The zones then lie on the map in colour, clipped at the field boundary. The table below gives each zone's hectares, its share and how strong the crop stood there compared with the field average. The first fetch reaches back about half a year, so multi-year zones build up over the years. If you have yield maps from the combine harvester, pick the yield maps as the basis in the same dialog instead of the images. Each map is then related to its own field average, and the table gives the yield per zone compared with the field average. From the Business (Pro) plan.

From the yield zones of a field you make maps for fertilizer, seed or plant protection in the “Application maps” tab. You pick the fertilizer from the fertilizer catalog, the seed or the product, and enter a rate per zone, so a different one on the hilltop than in the hollow. Seed rates go in grains per square meter. Along a drawn ditch a strip stays free and gets the rate 0 in the map. For fertilizer FarmManager suggests the distance under the Fertilizer Ordinance (DüV), for plant protection 10 m under § 4a PflSchAnwV (the Plant Protection Application Ordinance). You can change the width, for instance when the product has a stricter distance requirement. Before the export you see the total quantity and the treated area. For fertilizer FarmManager compares the field average with the N requirement from your fertilizer demand calculation, for plant protection every zone with the approved maximum application rate for the crop. These are notices, nothing is blocked. You download a shape file with the rate in the column RATE, in WGS84 or ETRS89/UTM, or an ISOXML file with a grid of mostly 2.5 meter cells in which every cell along the water buffer is set to 0. Whether a terminal reads grids is in its manual. A plant protection map becomes a spray order with one click, and a fertilizer map goes into the N plan as a planned application. If your farm is connected under Telematics to an organisation in the John Deere Operations Center, the map needs no USB stick. “Send to John Deere” in the row menu puts it as a shape file into the files of the Operations Center, and from there you send it to the display in the tractor. The “Status” column then shows when it arrived at John Deere. If John Deere does not accept the file, that also shows on the map, with the cause and what to do. Whoever may edit the map and change the John Deere connection may send it. From the Business (Pro) plan.

When you upload the TASKDATA from the USB stick under Machine data, FarmManager also reads the time logs of the jobs from the Business (Pro) plan. For each job this produces an as-applied map with the rate that the spreader, sprayer or drill actually put down on the field. The setpoint gets a map of its own too, as far as the terminal records it. You find the maps on the field in the “As-applied maps” tab and in Machine data via “View as-applied map” on the job. To compare, you choose an application map of the same field. The table then gives, per zone, the planned rate, the terminal's setpoint, the mean rate applied and the deviation, and larger deviations are marked. The area where something was applied inside the water buffer of the map is shown below the table. An implement that records no working width appears only as a track, and the map says so. The position in the log is usually the antenna on the tractor, so the map can lie a few meters off.

When you upload the TASKDATA of the combine harvester under Machine data, its time logs produce from the Business (Pro) plan a yield map of the field with 5 meter cells. Each cell carries its yield in kg/ha, as the yield sensor weighs it as harvested, and the measured grain moisture. The map is cleaned before FarmManager averages it. The start and end of every pass are dropped, because the elevator is only filling or emptying there. If the combine drives over ground that has already been threshed, for instance on the last narrow strip, only the pass that harvested there first counts. Single outliers of the yield sensor stay out as well. The map sits on the field in the “As-applied maps” tab, with the mean grain moisture. In the crop plan, “Yield from yield map” takes the mean over as yield and water content. For cereals, rapeseed and grain maize, FarmManager first converts every cell to the standard moisture of the crop, which comes from your deduction scale or, without a scale of your own, from the template. The harvested quantity is the yield per hectare times the area of the field, and the dialog shows what is taken over before you save. If you work with John Deere and upload no map, you get the suggestion from the harvest mass and grain moisture of the harvest operation in the Operations Center.

View each soil sample as a 3D core – the Nmin values of the three DüV depth bands (0–30, 30–60, 60–90 cm) form coloured segments by content (green, amber, red), while pH, humus and P, K, Mg annotate the core in an info panel.

Above the field list stand the number, total area and average size of your fields as well as the conditionality summary. The “Statistics” tab distributes the areas by land type, ownership, soil texture and status; the “Forecast” tab shows the development of your total area with trend and the shares of the land types over time. In the farm overview, the Fields area summarizes fields, field work, planting plans about to end, soil samples including those expiring soon, and water bodies below the minimum distance.