Ceres · field notebook

Ceres is the digital field notebook and the traceability system of a vegetable-growing cooperative. It brings together in one place what happens on each plot and what happens to the vegetables afterwards: the farms of the cooperative and its members with their plots (SIGPAC enclosures) and their crops; the farm field notebook —plant protection treatments, fertilisation, irrigation, field work, the technician's visits and lab analyses—; the harvest and the packhouse, by lot; sales to customers, purchases of produce from third parties and settlements with the members; and, above all, the traceability of every lot and the compliance of every farm.

Everything is connected. A treatment only lets you choose products that the official Plant Protection Products Register of the Spanish Ministry of Agriculture (MAPA) authorises for that crop and that pest, and it checks the rate, the sprayer's licence, the equipment inspection and the pre-harvest interval before it is saved. The pre-harvest interval stops a harvest being recorded too early. The harvest creates a lot; the lot is packed, labelled with a QR code and goes out on a delivery note. And for every box a customer buys you know which plot it came from, which treatments it received and with what interval, and which other customers got the same consignment.

1234567

1. 1
   The sidebar takes you to each section, grouped by area: Overview, Farm, Field notebook, Harvest & packhouse, Commercial, Traceability & control and Resources.
2. 2
   The search box finds a plot, a lot, a treatment, a member or a product from any screen (also with ⌘K or Ctrl+K).
3. 3
   Create adds a treatment, a field task, a visit, a harvest, an order… without leaving where you are.
4. 4
   The bell with your notifications: the order assigned to you, the settlement issued, the licence about to expire… (see Notifications).
5. 5
   Your user: your profile, the language and the theme, your notification settings, the connection to Claude and signing out. If you are an administrator, also Users, Settings and Audit log.
6. 6
   Your day: what is on your plate today according to your profile, before anything else (see Dashboard).
7. 7
   The Help menu opens this manual —at the chapter for the screen you are on— and the interactive guides.

#The journey of a box of vegetables

This is how a tomato travels through Ceres, from the plot to the customer. Each step is a section of the application and a chapter of this manual (click any of them to go to it):

#What is new in this version

#Where to start, depending on your job

Everyone sees in Ceres what their access profile allows, and only for the farms assigned to them (see Profiles, permissions and farms). These are the chapters you will use most, depending on your work:

If this is your first time, read Signing in to Ceres and The screen and what is common first: they explain what works the same way in every section (searching, filtering, opening a record, filling in a form).

#How to read this manual

• Annotated screenshots. Every screenshot is of the real application. The numbers 1 point to the parts explained below, in the legend. Hover over a marker or its line in the legend and the area is highlighted in the screenshot; click the screenshot to see it full screen.
• On-screen labels. What you see written on a button, a tab or a field appears like this: Create, Save. Keys, like this: ⌘K.
• Steps. Tasks are explained step by step in numbered boxes, with what happens at the end.
• Coloured boxes. Tips are in green, important points in amber, regulations (the digital field notebook, pre-harvest intervals, sprayer licence, sustainable nutrition…) with a green stripe on the left, how a figure is calculated in light green, and what changes depending on your access profile with a padlock.
• Abbreviations. The trade ones (PHI, BBCH, IPM, ROPO, ITEAF, SIGPAC, UF, ET₀, MRL, FEFO…) are explained the first time they appear and are all in the Glossary.
• Search. The search box on the left (or the / key) finds any word anywhere in the manual.
• Print. Print or save as PDF, at the bottom left, prints the manual on paper or as a PDF, each chapter starting on its own page.

#How this manual is organised

After these first steps, each chapter matches a section of the application's sidebar, in the same order and with the same icon. At the end come the appendices: profiles and permissions, glossary and frequently asked questions.

Everyone at the cooperative signs in to Ceres with their own user: an email and a password. What they see afterwards depends on two things an administrator decides:

• their access profile (general manager, field agronomist, farm foreman, sprayer operator, member, packhouse, sales, finance or auditor): the sections in the sidebar, the figures they can look at and what they can create or change;
• their farms: the agronomist sees those of the members she advises; the foreman, the cooperative's own farm; each member, only their own.

Accounts are created by an administrator in Users; there is no self-registration.

#The sign-in screen

12345678

1. 1
   Email: the address the administrator registered you with.
2. 2
   Password. The eye on the right shows or hides it while you type.
3. 3
   Sign in (or the Enter key in the password field) opens your field notebook.
4. 4
   Demo accounts: in the demo, one click on a person signs you straight in with their account.
5. 5
   The presentation video: about five minutes on what Ceres does. Press ▶ to watch it (best with sound; it is in Spanish).
6. 6
   Explore the proposal: the specification, the presentation and the PDF summary of Ceres.
7. 7
   The application's language (Spanish, English or Galician), right from the sign-in screen.
8. 8
   Switches between light and dark mode.

On narrow screens (a phone or a small window) the presentation on the left disappears and only the form remains, with the logo at the top and, below the demo accounts, the video and the proposal documents. In both, clicking the Ceres logo opens its presentation website.

1

1. 1
   Invalid email or password: check both fields (capital letters matter in the password). If the message is «Could not reach the server», the problem is the connection, not your details.

#The demo accounts

In the demo version, ten fictitious people from the sample cooperative («Sotovega, S. Coop.») appear below the form. Each one has a different access profile and some assigned farms, so you see the same application as each job would see it. They all use the password demo1234.

The chapter The screen and what is common explains how you can tell on screen what a profile cannot see (a padlock instead of the figure), and Profiles, permissions and farms what exactly each profile allows.

#The proposal video and documents

In the presentation on the left there is a video of about five minutes that tells what Ceres does. Press ▶ to watch it, best with sound (it is in Spanish); the full-screen button enlarges it.

Below it, the Explore the proposal block brings together three documents about Ceres, intended for whoever is evaluating it (in Spanish):

• Specification — every feature, section by section. It opens in another tab.
• Presentation — the key processes, animated. It opens in another tab.
• Proposal · PDF — a four-page summary that is downloaded to your computer.

If the browser blocks the new tab, Ceres warns you with «Could not open the document»: allow pop-up windows for the page and click again.

#If you forget your password

Ceres does not send emails to recover your password: accounts are managed by an administrator. Ask them to go to Users (in their user menu), open your record and give you a new password with Reset (at least 8 characters; Ceres can generate one): they have to pass it on to you securely. The old one stops working straight away.

#Your user menu and «My profile»

At the top right is your user button: your initials, your name and your access (the name of your profile or «Administrator»). Clicking it opens your menu. To its left, the bell with your notifications (see Notifications).

12345

1. 1
   My profile: your details, the language and the theme.
2. 2
   Notification settings: which notifications reach your bell and which also arrive by email (see Notifications).
3. 3
   Connect to Claude: work with Ceres from a chat with Claude (see Connect to Claude).
4. 4
   Only administrators see Users and Settings here; the Audit log, whoever has its permission.
5. 5
   Sign out takes you back to the sign-in screen.

1

1. 1
   Everyone else has My profile, Notification settings, Connect to Claude and Sign out; the Audit log, only whoever has its permission (in the demo, the general manager).

12345

1. 1
   Job title: your job at the cooperative, as the administrator entered it.
2. 2
   Access: «Administrator» or your access profiles. If you have several, they are joined with «+».
3. 3
   Language: ES (Spanish) or EN (English). It switches the whole application instantly.
4. 4
   Theme: light, «System» (whatever your computer or phone uses) or dark.
5. 5
   Close the dialog: the changes are already applied.

#My day in full screen

The Sprayer operator profile (in the demo, Ander Iriarte) only has My day, so Ceres opens it in full screen, without the sidebar, designed for a phone or a tablet in the field: the weather right now and whether spraying is possible, and, on large cards, today's and tomorrow's treatments, field tasks and irrigations, with a button to record each one.

If your profile has My day and other sections (the foreman, the agronomist), you open it from the sidebar like any other section; on a phone it also opens in full screen, with a button to go back to the rest of the application.

#Signing out

#If your user has no access profile

A user who is not an administrator needs at least one access profile to see anything. If an administrator creates your account without a profile (or removes all of them), when you sign in you will see the No access profile screen: «Your user has no access profile assigned yet, so nothing can be shown. Ask an administrator to assign one.», with the Sign out button. Once the administrator has assigned you a profile, sign in again.

#Signing in from a phone or tablet

12

1. 1
   The same form: email, password and Sign in.
2. 2
   The demo accounts. Scroll down to see the others, the video and the proposal documents.

Ceres works the same way in the browser on a phone or a tablet. If you are going to use it often —the sprayer operator on the tractor, the foreman on the farm—, add it to the home screen from the browser menu («Add to Home Screen»): it will open like any other app. It needs an internet connection: the version that works without coverage will come later.

Every section of Ceres shares the same structure and the same building blocks: the sidebar to move around, the top bar with search and the button to create things, lists that are searched and filtered the same way, records that open on the right with their documents and their changes, and forms with the same buttons. What you learn here works on any screen.

The only exception is the sprayer operator's My day: it opens in full screen, without the sidebar, to be used on a phone or a tablet in the field (see My day).

#The parts of the screen

1234

1. 1
   Sidebar: the sections, grouped by area. The section you are in is highlighted.
2. 2
   Help menu, fixed at the foot: this manual and the interactive guides.
3. 3
   Top bar: the title of the section and the tools that work on any screen (details below).
4. 4
   The content of the section; it changes when you choose another one in the sidebar.

12

1. 1
   The title of the section you are in.
2. 2
   The global search: click it or press ⌘K (Mac) / Ctrl+K (Windows).

123456

1. 1
   Help for the screen you are on, with its guides (also with the F1 key).
2. 2
   Create: adds a treatment, a field task, a harvest, an order… from any screen.
3. 3
   Language: Spanish, English or Galician.
4. 4
   Theme: the moon switches to dark mode; in dark mode, the sun goes back to light.
5. 5
   The bell with your notifications; if any are unread, a red number on top (see Notifications).
6. 6
   Your user menu, with your name and your access profile below it (see Signing in to Ceres).

#The sidebar

The sections are grouped by area, in the order the cooperative works: from the field to the customer. You only see the ones your access profile allows: a member does not get Customers or Inputs, for example, and the sprayer operator only has My day.

If the list does not fit, the sidebar scrolls; the Help menu always stays at the foot. When you change section, the screen you leave goes back to its initial state: if you had searched or filtered something, you will find it unfiltered when you come back.

123

1. 1
   Each icon is a section (hover over it to see its name); the areas are separated by a line.
2. 2
   The Help menu stays at the foot.
3. 3
   The search box narrows to make room for the title (and still opens with ⌘K / Ctrl+K).

123

1. 1
   Opens this manual at the chapter for the screen you are on (here, Field work), in another tab.
2. 2
   Opens the full manual, from the cover page.
3. 3
   Opens the help for the screen with its interactive guides (the same as the Help button at the top or F1).

#Help: interactive guides and this manual

There are two kinds of help inside Ceres:

• This manual, which opens from the Help menu at the foot of the sidebar, straight at the chapter for the screen you are on, in your language.
• The help for the screen: the Help button in the top bar (or the F1 key) opens a panel on the right with what the section is, the link to its chapter in the manual and the interactive guides for the tasks you can do there. Each guide plays on real screenshots of the app: a pointer goes to the spot, highlights it and performs the action while each step is explained. In My day in full screen, the button is in its header.

123

1. 1
   Where you are: what this section is and what it is for.
2. 2
   Link to this section's chapter in the manual.
3. 3
   The section's interactive guides («What you can do here») and, below, those that work on any screen. Click one to follow it step by step. The F1 shortcut opens this panel.

#Finding anything

The global search in the top bar finds, from any screen, farms, plots, crops, treatments, harvests, lots, products from the Register, inputs, people, machines, customers, orders and delivery notes, purchases, suppliers, settlements and documents (by their name or their note). It searches by name and also by number or code: a SIGPAC enclosure, «S-003/01», «TR-2026-0558», a lot «LV-261003-002» or a product's registration number. It only shows what your profile can see and from your farms.

123

1. 1
   Type at least two letters or digits; the results appear by themselves as you type.
2. 2
   Each result with the details that identify it (farm, crop, product, status…). Click it to go to its section with the record open.
3. 3
   The results are grouped by section, each with its icon: here a product from the Register with no. ES-00558.

#Creating something new

The Create button in the top bar adds, without leaving where you are, any record your profile can create: it opens the same form as the «New…» button in its section. When you save it, Ceres takes you to that section.

1234

1. 1
   The field notebook: treatment, fertilisation, irrigation, field task, visit and lab analysis.
2. 2
   Harvest and packhouse: record a harvest and a packing run.
3. 3
   Commercial: a customer order and a purchase of produce from third parties; and an input receipt into the store.
4. 4
   The farm: a crop, a plot and a farm; and a customer.

1

1. 1
   Only the entries the profile allows appear: the member records his fertiliser applications, his irrigations and his field work.

If you cancel the form, nothing is created and you stay where you were. If your profile cannot create anything (the auditor, for example), the button does not appear.

#Language and theme

The globe in the top bar switches the whole application between Spanish (ES) and English (EN), instantly; the moon switches to dark mode, easier on the eyes at night or in low light, and the sun goes back to light. Both are remembered in your browser; on a phone you change them from My profile (see Signing in to Ceres). The data (names of plots, products, members) is not translated: only the application.

1

1. 1
   In dark mode, the sun goes back to light.

#Notifications (the bell)

The bell in the top bar, to the left of your name, gathers the notifications meant for you. It is not everything that happens in the cooperative (that is in the Dashboard alerts), but what concerns you according to your profile and your farms:

A red number on the bell tells you how many are unread. Nobody sees anyone else's notifications, not even the administrator.

123456

1. 1
   The bell, with the number of unread notifications.
2. 2
   Mark all as read marks them all as seen in one go.
3. 3
   The settings: which notifications you want and whether also by email (further down).
4. 4
   A new notification (the green dot): tomato leafminer above the threshold in S-003/01, on visit VI-2026-0244. Click it to open the visit.
5. 5
   Those already read stay in the list, newest first, each with its icon, what happened and when.
6. 6
   At the bottom, whether email is active on this installation (in the demo, it is not).

Click a notification to open its record —the visit, the order, the settlement, the lot— and it is marked as read. If your profile cannot open that record, the notification says so («Your profile cannot open this record»). Notifications are created when the thing they report happens (when the order is assigned, the settlement issued, the visit saved or the lot put on hold); expiry notifications once a day, when the bell is opened, with the days of notice set in Settings.

1

1. 1
   Settlement LQ-2026-0071 for September, just issued, with the kilos it covers; the amounts are in its record.

12

1. 1
   A lot on hold awaiting its residue analysis, with the reason and the kilos.
2. 2
   This year's mock recall, with its origin lot.

123456

1. 1
   Which address your emails go to and whether sending is active on this installation. In the demo it is not: your choice is saved and will apply once it is turned on.
2. 2
   Each type of notification that makes sense for your profile, with its ⓘ: what it is, who receives it and what is left out.
3. 3
   In the app: the notification appears in the bell.
4. 4
   By email: you also get an email.
5. 5
   Daily summary: the same as «Your day» on the Dashboard, every morning by email if you ask for it.
6. 6
   If you turn both off, that notification is not created; what it reports is still in its section and in the Dashboard alerts.

#Lists

Almost every section starts with a list: treatments, field work, harvests, lots, orders, customers… They all work the same way. This is the Field work list.

12345678

1. 1
   Some sections have several views in tabs: here the list of field tasks and the weekly planner.
2. 2
   The section's indicators. Those with an ⓘ are explained when you click it; some filter the list when you click them.
3. 3
   List search: filters by any word in the columns.
4. 4
   Export CSV: downloads what you see so you can open it in a spreadsheet (if your profile allows it).
5. 5
   The button to add a record to the section.
6. 6
   Quick filters with their count. Click one to see only those rows.
7. 7
   Headers: click one to sort by that column; click again to reverse the order.
8. 8
   Footer with the number of rows and the totals of what is shown.

123

1. 1
   What you type in the search box…
2. 2
   …is combined with the chosen filter…
3. 3
   …and with the sort order: the arrow shows the column and the direction.

#Records

Clicking a row opens its record in a panel that slides in from the right, without losing the list behind it. They all follow the same layout: a header with the name and the actions, and tabs with the information grouped.

123456

1. 1
   The header: the code and the name, and below them the details that identify it (holder, municipality, SIGPAC reference).
2. 2
   The record's actions: edit, and the ones specific to each record (here, editing the outline on the map). They only appear if your profile can do them.
3. 3
   Close the record (also with Esc or by clicking outside it).
4. 4
   Tabs: each one groups part of the information; the number tells you how many records are inside.
5. 5
   The ⓘ buttons explain the block or the figure they accompany.
6. 6
   Links open the related record (here, the farm) on top of this one.

If you change something in a record, the list behind it updates by itself when you close it. Records you open from another one (the farm from its plot, a treatment from its crop) open on top and, when you close them, you go back to the previous one. On a phone, records take up the whole screen.

#The documents of each record

Almost every record has the Documents tab: photos of a pest, lab reports, certificates (GLOBALG.A.P., organic, a plant's plant passport), delivery notes, maps or plot outlines in KML, stored alongside what they document. The number on the tab tells you how many there are.

12

1. 1
   The record's Documents tab.
2. 2
   Upload documents opens the window to choose the files; you can also drag them onto the window.

#The Changes tab

With the See the change audit permission, records also have the Changes tab: who created or changed that record, when and which fields, most recent first, from the app or from Claude. Click a line to see each field before and after the change. If nobody has touched it since the data was loaded, you will see «No changes recorded».

All the changes to every record, together with sign-ins and sign-outs, are in one place in Audit log.

#Forms

To create or change a record you use a form in a window. They are all filled in and saved the same way.

123456

1. 1
   Fields with an asterisk are required. Those that choose another record (here, the crop) open a selector with a search box.
2. 2
   Dates are chosen on a calendar; they come with today's date.
3. 3
   Lists drop down. Ceres suggests the most usual value.
4. 4
   Switches, with their explanation underneath.
5. 5
   Below some fields, a hint on how to fill them in or what Ceres calculates with them.
6. 6
   Save (or Cancel, which closes without saving anything).

12

1. 1
   Type part of the name or the code: the list is filtered instantly.
2. 2
   Each option with what identifies it (here, plot, variety, crop number, farm, area and irrigation). Click the one you want.

#The ⓘ help on figures and acronyms

Next to many indicators, blocks, abbreviations (PHI, BBCH, IPM, ITEAF…) and permissions there is a small ⓘ. Clicking it opens a three-part explanation: what it shows, how it is calculated and how to read it. It is the quickest way to find out where a figure comes from.

123

1. 1
   What it shows.
2. 2
   How it is calculated, with the data it uses.
3. 3
   How to read it: what to do with it. Click outside to close it.

#What your profile does not let you see

Each access profile decides which sections you see, which data you can look at and what you can create or change, and each user has their farms. What is not for you shows up like this:

• Sections: those your profile does not allow do not appear in the sidebar, nor do their results in the search.
• Farms: you only see the data of yours. A member sees their own farm; the agronomist, those of the members she advises. Counts, totals and reports are calculated with those farms only.
• Figures: a cost, a price or a settlement amount you cannot see does not appear (the column or the indicator disappears, like the cost in Field work for the agronomist) or shows as a grey padlock (hover over it: «Hidden by your access profile»).
• Contact details: phone numbers, emails, addresses, tax IDs and IBANs, the same.
• Buttons and tabs: the ones to create, edit, validate or cancel do not appear if you do not have that permission, nor do the tabs for what you cannot see.
• Export: the button to export to CSV only appears if your profile allows it.

123

1. 1
   Marta sees the member's deliveries (the kilos), but she does not have the Settlements or Changes tabs: her profile does not have «See settlements» or «See the change audit».
2. 2
   What belongs to her work, in full: the member's integrated pest management, with her as adviser.
3. 3
   The padlock: the member's IBAN is not for her profile. The database does not even send it.

#Ceres on a phone or tablet

On a phone (or a narrow window) Ceres rearranges the screen: the sidebar is tucked into a drawer, the indicators and filters scroll sideways, lists become cards (one per record, without columns) and records and forms take up the whole screen. On a tablet, the sidebar shows icons only (see above).

1234

1. 1
   The menu opens the drawer with the sections.
2. 2
   Search, help, Create, the notifications bell and your menu, as icons.
3. 3
   The indicators and filters scroll sideways.
4. 4
   Each record is a card; tap it to open its record in full screen.

1

1. 1
   The same sections as on a computer, with the current one highlighted. Tap outside the drawer to close it.

#Keyboard shortcuts

#Direct links

The Ceres address accepts a few parameters that open a screen directly, handy for saving a bookmark or sending a link to a colleague (who will have to sign in with their own user and will only see what their profile allows):

• ?seccion=tratamientos opens that section (the key of each section is the last part of the address of its chapter in this manual: #tratamientos, #cosechas, #trazabilidad…).
• &lang=es, &lang=en or &lang=gl chooses the language, and &tema=dark or &tema=light the theme.
• ?lote=<code> opens, without signing in, the public page of a lot: it is where the QR code on the labels leads (see Packhouse).

The Dashboard is the first screen when you open Ceres. It brings together on one page what needs attention in the cooperative today: the treatments, field work and irrigation due today or left behind, the crops that cannot be harvested yet because of a pre-harvest interval, the alerts (an expired spraying licence, equipment with an overdue inspection, a withdrawn product still in the store…), what has been harvested and what is coming, the packhouse, sales, the weather for spraying, how each farm's field log is doing and what has been settled to members. At the very top, Your day picks out of all that what is on your plate today, according to your profile.

It is not a report to read from top to bottom, but a board of warnings: every figure is a shortcut that opens the section (with the filter already set when there is one) and every row opens its record. That way you go from «10 crops within a pre-harvest interval» to the specific crop in two clicks.

The dashboard refreshes itself every 5 minutes (and when you press Refresh). What you see depends on your profile: each block has its permission, the database only calculates the blocks you can see and only with the farms assigned to you (a member sees their own; the adviser, the ones she advises). If your profile does not see prices, you get kilos instead of amounts.

#Your day

The first thing under the greeting is Your day: what is on your plate today, set apart from everything else. It is not the same for everyone: it tells the adviser what to visit and what to validate; the foreman, the orders and whether spraying is possible today; sales, the orders to be served. Each part has its count and its rows, and each row opens its record. This is how Marta, the field adviser, sees it:

12345678

1. 1
   Thresholds exceeded, not treated: pests that a visit has found above their threshold and that have no treatment yet. Here, tomato leafminer in S-003/01 (visit VI-2026-0244, yesterday).
2. 2
   Treatments to validate: those applied that are waiting for the adviser's review and signature, oldest first; See all (25) opens Treatments with that filter.
3. 3
   Low vigour from satellite: plots where part of the crop has fallen below its own average, with the Sentinel-2 image (see Plots & map).
4. 4
   Crops to visit: those with no visit for more than 14 days, or never visited.
5. 5
   Pre-harvest intervals ending: what can be harvested again today or in the next few days.
6. 6
   Same mode of action again: orders that repeat the FRAC, IRAC or HRAC group of the previous treatment on the same crop (here, TR-2026-0556 today and TR-2026-0555 tomorrow; see Treatments).
7. 7
   Your unread notifications (they open the bell, see The screen) and, on the right, the button to collapse the block.
8. 8
   Ceres builds it with rules, from your data (no AI). Claude tells you the same through the connector if you ask for the «daily summary» (Connect to Claude).

Each profile has its own Your day:

12

1. 1
   Orders for today and tomorrow, with the operator: order TR-2026-0556 for the asparagus of SV/01 is for today.
2. 2
   Spraying window: the hours today, from 6 am to 9 pm, in which spraying will be possible according to the forecast (today, none: wind and rain).

12

1. 1
   Orders due today and tomorrow (and overdue ones): here, one from yesterday not yet served.
2. 2
   The last 7 days: what has been harvested, shipped and sold, the open orders and the serious alerts.

Once you have read it, press the arrow on the right to collapse it: a strip remains with the titles and their counts, and pressing one expands it again. Ceres remembers how you left it. «Your day» does not replace the blocks below: it is the part that concerns you, drawn from them and from your notifications.

#The key figures

Below «Your day» are the key figures in large cards. Those of your profile's blocks appear, up to six; with all the blocks (administration and management) they are these:

123456789

1. 1
   The dashboard reloads itself every 5 minutes; on the left, when it was last updated. This button reloads it at once.
2. 2
   Your day, collapsed: the title of each part with its count. Press one (or the arrow) to expand it.
3. 3
   Tasks for today: treatments, field work and irrigation planned for today; below, the overdue ones and those for the coming days.
4. 4
   Serious alerts: something expired or forbidden (licences, ITEAF, withdrawn products in stock, certificates); below, the warnings.
5. 5
   Within PHI: crops that cannot be harvested yet; below, how many end within 3 days.
6. 6
   Harvested · 7 days and, in the pill, the difference from the previous 7 days.
7. 7
   Sold · 30 days (excluding VAT) and the open orders. Without the prices permission you get Shipped · 7 days, in kilos.
8. 8
   Cropped area: hectares with a crop established or being harvested; below, plots and organic hectares.
9. 9
   Each card and each block has its ⓘ: what it shows, how it is calculated and how to read it.

The whole card is a shortcut:

The last two appear for those who have those blocks and fewer than six cards, like the member (further down, in What each profile sees).

123

1. 1
   What it shows.
2. 2
   How it is calculated.
3. 3
   How to read it and what to do. It closes with Esc or by clicking outside.

#Today's tasks and alerts

Below, the blocks in three columns (two on a tablet, one on a phone). The first two answer the morning question: what has to be done in the field today, and what has expired or been left unresolved?

123456

1. 1
   Open My day: the same in large cards, designed for the field (My day).
2. 2
   Treatments, Field work and Irrigation planned up to 3 days ahead. Each figure opens its section with what is scheduled.
3. 3
   Not validated: applied treatments that the adviser has not yet reviewed and signed.
4. 4
   Harvests not graded: intakes waiting to be graded in the packhouse.
5. 5
   Each task: crop and farm, number, product and operator (or «unassigned») and when it is due. Press it to open its record.
6. 6
   The first six are shown; Show all 12 expands the rest.

1234567

1. 1
   Serious (red: something expired or forbidden), Warnings (amber: about to expire or needs action) and To review (blue: office tasks).
2. 2
   A plant protection product withdrawn from the MAPA Register that is still in stock: it cannot be applied.
3. 3
   Daniel Aranda's licence has expired: the database will not let him record treatments.
4. 4
   The AT-07 sprayer, with its ITEAF overdue. On the right, since when.
5. 5
   A residue analysis that does not meet a customer's requirements: AN-2026-0023, for pepper (see Analyses).
6. 6
   Alerts go from the most serious to the oldest; Show all 24 expands the rest.
7. 7
   View all opens Compliance.

Today's tasks shows the treatments (recommended or scheduled), field work and irrigation scheduled up to 3 days ahead, and anything overdue. A recommended treatment has a purple icon: the adviser has proposed it but it has no date or operator yet. For example, order TR-2026-0558 (cauliflower of S-003 with SANAGRICOLA WP, operator Ander Iriarte) appears here today and in Ander's My day.

Alerts gathers what Ceres watches on its own: spraying licences and equipment inspections (ITEAF), withdrawn products in stock, member and supplier certificates, expired or nearly expired inputs, pest thresholds exceeded in a visit, lots on hold, orders past their delivery date and treatments not validated. Each row opens the record where it is resolved (the person, the machine, the input, the lot…). When a type has more than three cases, they are grouped into one row with their count.

This version brings three new alerts, which appear when you expand the list:

123

1. 1
   Low vigour (satellite): plots with part of the crop below its own average; as there are four, they share one row with their count (see Plots & map).
2. 2
   Analysis not meeting a customer's requirements: in AN-2026-0026, for pepper, bupirimate is at 45 % of its maximum residue limit (MRL), more than Frutas Bidasoa and the school canteen accept (see Analyses).
3. 3
   Treatment repeating a mode of action: today's order on the asparagus of SV/01 repeats FRAC group 3 from the previous treatment (see Treatments).

#Pre-harvest intervals and weather

123

1. 1
   The one that ends first at the top: the artichoke of SV/02, within its interval until 8 October (3 days left, today included).
2. 2
   Each crop with its plot, its number, the farm and the treatment that started the interval (here, the tomato of SV/04 because of TR-2026-0548); on the right, until when and the days left. Press it to open the crop.
3. 3
   View all: Crops with the Within PHI filter.

1234

1. 1
   Whether spraying is OK now and until what time; on the right, this hour's wind and delta T.
2. 2
   Next 48 hours: each small bar is an hour, green if it is suitable for spraying and grey if not.
3. 3
   Yesterday's weather: maximum, minimum, rain, ET₀ and wind, from real data; the season's rainfall and degree-days.
4. 4
   View all opens Weather, with the hour-by-hour detail and the week's forecast.

The pre-harvest interval is the number of days that must pass between the last treatment with a product and the harvest. It is set by the product's authorised use on that crop (the MAPA Plant Protection Products Register) and Ceres calculates it when each application is recorded. While it lasts, the database will not record a harvest from that crop: the block tells you which are on hold and when they are released. For example, broccoli CU-2026-0051 of S-007 is within its interval until 16 October because of treatment TR-2026-0544: it can be harvested from the 17th.

Weather and spraying uses real weather data for the cooperative's location: the hourly forecast and, for past days, the daily data from Open-Meteo (the ERA5 reanalysis and the ECMWF model), with its source in Weather. An hour is suitable for spraying if it is not raining (and the chance of rain is under 40 %), the mean wind does not exceed the maximum set in Settings and the delta T is between 2 and 8 °C. Delta T is the difference between the air temperature and the wet-bulb temperature: below 2 °C droplets do not dry and run off; above 8 °C they evaporate and drift.

#Season, harvest and forecast

1234

1. 1
   Farms, Plots and ha of plots you see; each figure opens its section.
2. 2
   ha organic: opens Plots & map with the Organic filter.
3. 3
   Treatments applied since the start of the season (1 September).
4. 4
   The cropped area split by species, each with its colour (the same on the map, the planner and the reports).

1234

1. 1
   What was harvested in the last 7 days (with the difference from the previous week) and this season.
2. 2
   Kilos harvested per day over the last two weeks.
3. 3
   Forecast for the next 4 weeks (light green) against the open orders for those weeks (earth brown).
4. 4
   By species: what is left to harvest from the crops under way and the stock already in the packhouse.

Season is the snapshot of the season (in Ceres, from 1 September to 31 August, unless Settings says otherwise). Harvest & forecast is for planning sales: the sales team sees what is coming in over the next few weeks and how much has already been ordered. If a crop's forecast drifts, correct its expected yield in the crop record.

#Packhouse and sales

12345

1. 1
   In stock: kilos of pending or available lots.
2. 2
   To grade: field lots waiting to be graded into extra, I, II and waste.
3. 3
   On hold: lots held pending an analysis or a decision.
4. 4
   Expire within 2 days: they should go out first (FEFO).
5. 5
   Kilos by product, from most to least.

12345

1. 1
   Customers' open orders.
2. 2
   Due today or late: orders that have to be served now.
3. 3
   Shipped · 7 days: kilos that have gone out on delivery notes.
4. 4
   Sold in 30 days and receivables, only with the «See prices» permission.
5. 5
   Kilos shipped per week over the last 12; the highlighted bar is the current week, still incomplete.

Packhouse opens Packhouse with the filter of each figure; Sales, Orders & sales. FEFO is the outgoing order «first expired, first out», which Ceres follows when assigning lots to a delivery note.

#Compliance and settlements

123

1. 1
   The average score of the field log of the farms you see, from 0 to 100: green from 90, amber from 75.
2. 2
   Gaps (something the rules require that is missing) and Warnings (something worth reviewing).
3. 3
   Those needing most attention: the farms with the lowest score, with their gaps. Press one to see what is missing.

1234

1. 1
   Settled this season (net, issued or paid). At the start of the season it is zero.
2. 2
   Issued, unpaid: settlements delivered to the member and waiting to be paid.
3. 3
   Delivered, not settled: graded kilos not yet in any settlement.
4. 4
   Net settled per month over the last 12 months.

The Logbook compliance score comes from each farm's checklist (treatments recorded on time and validated, integrated pest management justification, adviser, licences, ITEAF, fertiliser plan, analyses, certificates, pre-harvest intervals…), which is in Compliance. Ceres helps you comply and keeps a record: it does not certify anything.

Member settlements summarises what the cooperative pays its members for their deliveries. Amounts are only shown with the «See settlements» permission; the detail is in Member settlements.

#Every figure, back to its source

#What each profile sees

Each block has its own permission and everything is calculated only with the farms assigned to you. With the demo profiles, the dashboard looks like this:

The sprayer operator (Ander) has no dashboard: he only sees My day. The external auditor (Begoña) does not either: she goes straight into the field-log sections she can look at. Alerts are also filtered by section: each profile sees the ones it can resolve (sales, for example, does not see spraying licences).

1234567

1. 1
   His Your day: what he delivered in 7 days, his plots under a pre-harvest interval and his settlements issued.
2. 2
   With fewer blocks, Logbook compliance and Settled this season also appear among the key figures.
3. 3
   His alerts: the low vigour of the cardoon on S-003/03 and three treatments on his farm not yet validated by the adviser.
4. 4
   His cardoon on S-003/03 is within its pre-harvest interval until 16 October: he cannot harvest it yet.
5. 5
   His settlements: what has been settled this season, what has been issued but not paid and the kilos delivered that have not been settled yet.
6. 6
   His compliance score: no gaps and one warning.
7. 7
   The sidebar has no more than that: his farm, his plots and crops, his field log, his harvests and settlements, compliance and weather.

1234

1. 1
   He sees prices: sales appear in euros.
2. 2
   His alerts are those of his job: supplier certificates, expired or held lots and orders past their delivery date.
3. 3
   The harvest forecast against his orders: with it he plans sales for the coming weeks.
4. 4
   The packhouse and sales: what he can serve today and the receivables.

#Tips

My day is the screen for people working in the field. It is designed for the phone or the tablet: large text, finger-sized buttons and only what is needed. It answers three questions: what do I have to do today?, can I spray now? and how do I record it when I finish?

• The sprayer operator (in the demo, Ander Iriarte) only has this section: Ceres opens straight into My day for him, full screen and without a sidebar (field mode). He sees what is assigned to his name.
• The farm foreman (Mikel Garbayo) and the field adviser have it in the sidebar, among the other sections, and can see their own tasks or those of the whole team. On a phone it also opens full screen.

What is recorded here goes into the field log with the same checks as in the office: the operator's licence, the equipment inspection (ITEAF), the product's authorised use, the dose, the number of applications, the interval and the pre-harvest interval. And if your hands are busy, you can dictate it: you say what you have done and Ceres fills in the form for you to confirm. It works in the phone's or tablet's browser, with a connection.

#Your day on the phone

This is how Ander sees his day of 6 October on his phone. At the top, the day, his Your day and the weather; below, the cards with what he has to do. Today he has two orders: TR-2026-0556, the farm's asparagus (SV/01), and TR-2026-0558, the cauliflower of Jesús Pérez Ciriza on S-003/02.

12345678

1. 1
   The day, your name and your spraying licence with its expiry date (in red if it has expired: then you cannot record treatments).
2. 2
   Your day: how many orders you have today (and the overdue ones) and whether there will be suitable spraying hours today. Its ⓘ explains where it comes from.
3. 3
   Today and Tomorrow, with the number of tasks for each day. Today also includes anything overdue.
4. 4
   Weather now: whether you can spray and until what time, the temperature, the wind (and gusts), the delta T and the humidity; below, the coming hours in a strip (green: suitable).
5. 5
   The tasks, by group: treatments, field work, irrigation and expected harvests, each group with its number.
6. 6
   Dictate: you say what you have done and Ceres fills in the form (further down).
7. 7
   The bell with your notifications: the orders assigned to you, with a red number if any are unread.
8. 8
   Your user menu (language, dark mode, notification settings, sign out). To the left of the bell, Help.

123456

1. 1
   The order: number and farm; crop and plot; member, location, area and the pest or disease to control.
2. 2
   Each product: name, dose and total to prepare for the whole area; below, what it is against and its registration number (and the store batch if there is one).
3. 3
   The equipment used to apply it and the spray volume: litres per hectare and litres in total.
4. 4
   The pre-harvest interval it will start and from when the crop can be harvested (in blue: the cauliflower is not being harvested yet).
5. 5
   A warning from the check: some customers would not accept the harvest so soon. Check it with the adviser or with sales.
6. 6
   Record application when you finish.

The card gives you everything you need to prepare the spray mix without doing any sums: the cauliflower order is SANAGRICOLA WP at 0.202 % with 600 litres of spray per hectare on 1.39 ha, so you need to prepare 834 litres of spray with 1.685 kg of product. If the order has several products, they appear one below the other, each with its quantity.

Below, warnings from the check the database runs with the order's data may appear:

• The pre-harvest interval: in blue if the crop is not being harvested («14-day pre-harvest interval: it can be harvested from 20 Oct»); in amber if it is, because it interrupts the harvest already under way.
• In amber, the warnings: that the harvest would no longer be fit for some customer with residue requirements, or that the product repeats the mode of action of the previous treatment (in the asparagus order, FRAC group 3). They do not prevent spraying, but it is worth discussing them with the adviser.
• In red, the errors that would prevent recording it: an expired operator's licence, an expired equipment ITEAF, a dose above the authorised one, a withdrawn product… If you see one, do not apply: tell the foreman or the adviser.
• «Not suitable for spraying right now: …» if it is raining this hour, it is too windy or the delta T is out of range.

The bell at the top tells you about every new order assigned to you, with its plot and when it is due: press it to see the list and press a notification to go to its card. From your menu, Notification settings decides whether they also reach you by email (see Notifications).

12

1. 1
   Today's two orders, new (unread): TR-2026-0558 and TR-2026-0556, each with its plot.
2. 2
   Those from previous days, already read.

1

1. 1
   The operator receives his assigned orders, his licence expiry and the daily summary: each one in the app and, if he wants, by email.

#The weather: can I spray now?

The Weather now card uses the hour-by-hour weather forecast for the cooperative's location (real data; see Weather). At the top it tells you, in big letters:

• OK to spray (green), with «Suitable window until …»: until what time the good conditions last.
• Not a good time to spray (amber), with the reason: «raining», «wind above 3 m/s», «low delta T: droplets do not dry and run off» or «high delta T: the spray evaporates and drifts»; and «Next window: …» or «No suitable window for the rest of the day».

Below, the temperature, the mean wind and gusts, the delta T and the humidity (and the rain, if it is raining), and a strip with the hours left in the day: each box is an hour, green if suitable for spraying. With Tomorrow, the card switches to Tomorrow and says which suitable windows there are the next day («Suitable windows tomorrow: 07:00–13:00», or «No suitable spraying hours tomorrow»): useful for planning when to go out.

#Recording the application

When you finish the treatment, press Record application on its card. On a phone it opens full screen with almost everything already filled in from the order: you just check and correct anything that changed.

1234567

1. 1
   Date and hours: today, from an hour ago until now. Change them if you applied earlier (never in the future).
2. 2
   The operator, with their licence and its expiry.
3. 3
   The equipment, with its ROMA number; the method and the spray volume per hectare.
4. 4
   Conditions: the weather in those hours and whether it was suitable for spraying. Use copies them into the fields below.
5. 5
   Temperature, humidity and wind; below, the maximum wind allowed.
6. 6
   Each product with its dose and the total quantity, calculated from the dose and the area. If you used a different amount, type it.
7. 7
   Record application saves it (if there are no errors).

12345

1. 1
   Store batch: choose the batch used so that it is deducted from stock (the cooperative has two SANAGRICOLA WP batches).
2. 2
   Each plot: the treated area (if you did not treat it all) and the crop's BBCH stage.
3. 3
   Harvest from: the pre-harvest interval and the first day that plot can be harvested.
4. 4
   The live check: authorised use, dose, applications, interval, licence and ITEAF. If there are errors, they appear here in red and it will not record.
5. 5
   Record application: with errors, the footer says how many are blocking it.

#Dictating what you did

With gloves on or the phone in a tractor pocket, typing is hard. That is why My day has the Dictate button (bottom right): you press it, say what you have just done and Ceres fills in the usual form —the application record, the irrigation or the field task— for you to check and confirm. For example:

• «I treated S-003/02 with Sanagrícola at 0.2 percent»
• «Irrigated SV/03 for three hours»
• «Weeding in SV/01, two and a half hours»

Ceres reads the sentence against your plots and crops (with or without the slash), the products in the Register by trade name and your orders for the day; it understands numbers in digits or in words and rate units. This is how Ander does it after finishing the cauliflower:

12345

1. 1
   The microphone: it listens while you speak; press it again to dictate once more. Its ⓘ explains what it understands.
2. 2
   What I heard: the sentence, as heard. If the recognition gets it wrong, correct it here by typing.
3. 3
   What I understood: what (a treatment), where (the cauliflower on S-003/02), the product, the rate and the order it belongs to (TR-2026-0558, today's). Anything it does not understand is listed separately.
4. 4
   Nothing is saved yet.
5. 5
   Record the application opens the form filled in with what you dictated.

1234

1. 1
   The notice: it has been filled in from what you dictated, and you have to check it before recording.
2. 2
   What you did not say comes from the order: the operator, the equipment, the method and the spray volume.
3. 3
   The order's product; further down, the dictated rate (0.2 %), in the order's unit, and the total quantity.
4. 4
   Record application: with the same checks as if you had typed it.

#Tomorrow, and on the tablet

On a tablet (or a computer) the cards go in two columns. With Tomorrow you see the next day: Ander has three scheduled irrigations on the farm waiting for him, and the weather card tells him that tomorrow there will be no suitable hour for spraying.

1234

1. 1
   Tomorrow: what is planned for the next day (without the overdue tasks).
2. 2
   Tomorrow's suitable windows and the 24-hour strip (green, suitable for spraying). Tomorrow there are none.
3. 3
   An irrigation: crop and plot, volume and hours, meter and system; the note says the water balance scheduled it (Irrigation).
4. 4
   Irrigated records it as done: date, hours, actual volume (or meter reading) and whether it included fertigation.

#The foreman's day

The foreman opens My day from the sidebar. As well as his own tasks, he can see the whole team: the field work assigned to each person, the irrigation and the scheduled treatments on his farms, and the expected harvests (crops being harvested). That way he shares out the morning's work and checks what is left.

123456789

1. 1
   For the foreman, My day is just another section in the sidebar.
2. 2
   Your day: the team's orders for today and tomorrow, and whether there will be suitable spraying hours today.
3. 3
   Mine (what is assigned to you) or Whole team (everyone's, with who it is assigned to). Ceres remembers your choice.
4. 4
   The asparagus order on SV/01, assigned to Ander, with its warnings: it repeats FRAC group 3 and is not fit for one customer.
5. 5
   Done records the field task as done, with each person's hours.
6. 6
   Open record opens the treatment (or the field task, or the crop) in its section.
7. 7
   Each expected harvest: what has been harvested against the forecast, the last harvest and until when it lasts. Record harvest records a harvest intake (Harvests).
8. 8
   The tomato on SV/04 is within its pre-harvest interval until 14 October: Record harvest stays disabled until the 15th.
9. 9
   Dictate is on the computer too.

• A field task (earthing up, weeding, staking…) has its number, crop and plot, the description, the machine and who it is assigned to. Done marks it as done.
• A scheduled irrigation has the volume, the hours, the meter and the system. Irrigated records it.
• An expected harvest is a crop being harvested. If the crop is within a pre-harvest interval, the card says so in red («Within the pre-harvest interval until …: it can be harvested from …») and Record harvest is disabled.

12345

1. 1
   Date: Today, Yesterday or Other date.
2. 2
   Workers and hours: who worked. Add adds more people.
3. 3
   Each person's hours: with − and +, or with the 2, 4, 6 and 8-hour shortcuts. They count towards the crop's cost.
4. 4
   Notes: incidents or observations.
5. 5
   Mark as done saves it in the field log.

#Tips

Claude is Anthropic's artificial intelligence assistant. Ceres comes with a connector for Claude: a secure connection that lets Claude work with your Ceres data from a chat, in claude.ai (in the browser), in the desktop and mobile apps and in Claude Code. Instead of going screen by screen, you ask in your own words:

• «What have I got on today?»
• «Which plots are within a pre-harvest interval, and until when?»
• «What can I use against aphids on organic lettuce without repeating a group, and with what pre-harvest interval?»
• «Is this lot fit for Frutas Bidasoa?»
• «Trace lot LV-261003-002: which plot does it come from, what treatments has it had and which customers has it gone to?»
• «Verify this field log» (with the exported file or the seal code on its PDF).
• «Record today's harvest: 1,250 kg of pepper from plot S-001/03.»

Claude enters Ceres as you: it sees the same as you see in the app —your sections, your farms, your figures— and can only change what you can change.

#What you can ask it

• Look things up: search for anything (like the app's ⌘K search); open the full record of a farm, a plot, a crop, a treatment, a visit, a harvest, a lot, an order, a customer or a product, with everything that hangs from it; get any list with filters, sorting and totals; the Dashboard; the current pre-harvest intervals; the authorised products for a crop and a pest (the solution finder on the official MAPA Register, with the crop and pest hierarchy); the traceability of a lot, backwards and forwards; the compliance and the farm field log of a farm (also in the CUE format); the harvest forecast; the irrigation balance and the fertilisation plan; the weather windows for spraying; and the reports (including the mass balance and third-party operations).
• What is new: the daily summary (the same as «Your day» on the Dashboard); your notifications; residues: a customer's requirements and its lots that are not fit, whether a lot is fit for a customer, an analysis against the EU MRL and the customers, or the MRL of a substance on a crop; the mode of action of authorised products and, for a crop, which ones alternate group; a plot's satellite vigour (NDVI) and its series; and verifying an exported field log (the file, the fingerprint of a PDF or its seal code) or the state of the whole fingerprint chain.
• Make changes, if your profile allows it: add, change or delete plots, crops, field tasks, irrigations, visits, traps, lab analyses, customers, suppliers, certifications, orders and purchases with their lines, people, machinery and thresholds; recommend or schedule a treatment (with the same check as in the app: authorised use, rate, applications, interval, product still authorised, organic, licence, ITEAF, wind and stock), record its application, note its efficacy or cancel it; record a harvest (also blocked if the crop is within its pre-harvest interval), grade it or cancel it; record a fertilisation; put a lot on hold, move it, adjust it or withdraw it; pack; receive or adjust inputs; prepare the delivery note for an order (with the lots by FEFO), ship it, invoice and collect payment; receive a purchase; prepare a settlement; run a mock recall; and save or remove a customer's residue requirements.

Claude fills in the same things as the app: the plot's area, the crop's harvest calendar and expected yield, the scheduled or applied status depending on the date, the visit's technician… An order or a purchase is created with all its lines at once, and if anything fails nothing is created. You can name things the way you know them («Jesús's tomatoes», «the El Recuenco plot») or by their code (S-003, S-003/01, CU-…, TR-…, LC-…, LV-…, a product's registration number).

Ceres also comes with six ready-made prompts that Claude offers alongside the connector (with their Spanish titles): Resumen del día (summary of the day), ¿Qué puedo aplicar? (what can I apply?), Estado de una explotación (status of a farm), Preparar un tratamiento (prepare a treatment), Verificar un cuaderno exportado (verify an exported field log) and Simulacro de retirada (mock recall).

#Why it is safe

• Claude enters as you, never with more permissions. The connector has no permissions of its own: every request from Claude carries your identity, and the Ceres database applies your access profiles and your farms to it exactly as in the app: the sections, the sensitive data (costs, prices, settlements, contact details) and the actions. What your profile does not see, Claude does not see either.
• Never My day, signatures or administration. My day is not used from Claude (it is each sprayer operator's field mode), a treatment is not validated with a signature (the signature belongs to the person), and users, profiles, keys or Settings are not administered: that is only done in the app.
• With a personal key you can revoke. Claude identifies itself with an access key of yours (it starts with ceres_). Ceres does not store the key, only a fingerprint to recognise it, so it is shown only once. It is revoked with a button and access is cut on the next request; it is also cut if it expires, if an administrator disables your user or if your profile loses the permission.
• Everything is logged. Every time Claude looks something up or changes something, it goes into the key's activity: what it did, on what, and whether it could be done. What changes is also recorded in the Audit log and in the Changes tab of each record, flagged «from Claude».
• Without the «Export CSV» permission, Claude receives at most 50 rows per query (500 with it).
• Your password is not stored in Claude. When you connect, you type your user and password on a Ceres page, not in Claude; Claude only receives a key you can revoke.

The connector follows MCP (Model Context Protocol), the open standard for connecting AI assistants to applications.

#What Claude asks you first

Claude always asks you to confirm before:

• deleting something (it cannot be undone; and anything in use cannot be deleted);
• recording the application of a treatment or cancelling a field notebook entry;
• shipping a delivery note, invoicing or settling with a member;
• putting a lot on hold;
• and creating or changing anything you have not explicitly asked for.

Afterwards it sums up what it did with the codes (TR-…, CO-…, LC-…, PE-…, AL-…), so you can find it in the app.

#Where it is in Ceres

Everything to do with the connector is in your user menu, at the top right: Connect to Claude. Everyone who works in the app has it; if your profile does not allow it, the panel tells you so.

12

1. 1
   Press your name to open the menu.
2. 2
   Connect to Claude opens the connector panel.

12

1. 1
   Your initials, at the top right.
2. 2
   Connect to Claude.

#The «Connect to Claude» panel

The panel opens on the right and has four parts: what Claude can do for you, how to connect it, your access keys and the recent activity.

123456

1. 1
   What your profile allows: looking things up, making changes and seeing contact details.
2. 2
   The farms Claude will work with: yours (for Marta, the cooperative's farm and the members she advises).
3. 3
   What Claude will do and when it will ask you first.
4. 4
   Examples of questions and tasks to get started; among them, the new ones: «What do I have on today?» (your daily summary), «Is this lot fit for Frutas Bidasoa?» and «Verify this field log».
5. 5
   Opens this chapter of the manual.
6. 6
   The connector address of your Ceres, with the button to copy it.

12

1. 1
   Look things up yes, Make changes crossed out: Claude only looks things up. Jesús records his field work and irrigation in the app.
2. 2
   Only his farm, S-003. And since he sees his settlements, Claude does too.

1

1. 1
   Without «Use from Claude», the panel explains that the profile does not allow it and whom to ask.

#Connecting Claude with your user

The simplest way: add Ceres as a connector in Claude and sign in with your Ceres user. Ceres then creates a «Claude» key valid for 90 days, which you will see in your list of keys. The steps are summed up in the panel itself, under How to connect it, with your Ceres connector address and the button to copy it.

1234

1. 1
   Connect Claude to Ceres: who is asking for access and what it will be able to do.
2. 2
   With my user (your Ceres email and password) or with a key you have already created.
3. 3
   With your user, Ceres creates a «Claude» key valid for 90 days.
4. 4
   Allow access and you go back to Claude, now connected.

#Your access keys

Further down the panel is the list of your keys: those created when you connected Claude and those you create by hand (for Claude Code, for example). For each one you can see where it comes from, when it expires, when it was last used and how many calls it has made.

1234

1. 1
   New key: creates a key by hand.
2. 2
   My access keys: each with its status (active, expired or revoked) and the Revoke button.
3. 3
   Recent activity: what Claude has looked up or changed with your keys, with its result (Done, Denied or Error).
4. 4
   A daily summary that Marta asked Claude for in the morning: the same as «Your day» on the Dashboard.

123

1. 1
   Name: where you are going to use it («Claude on my laptop», «Claude Code»…).
2. 2
   Expires: in 30 days, in 90 days, in a year or never.
3. 3
   Create key: the key is shown only once; copy it then.

Claude Code (the terminal) connects with a key:

claude mcp add --transport http ceres <connector address> --header "Authorization: Bearer ceres_…"

or without the header and, inside Claude Code, /mcp → Authenticate, which opens the same Ceres page.

The panel gives you the command ready-made with your Ceres address. Keep the key as you would a password: whoever has it gets in as you.

A farm is each unit that keeps its own field log: the cooperative's own farm (Sotovega · finca El Soto, code SV) and that of each member (S-001 to S-012). Everything else hangs from it: its plots, its crops, its treatments, its deliveries and its settlements.

Its record holds the details the farm field log requires: the holder and their tax ID, the REA code (regional register of agricultural holdings), how it complies with integrated pest management (IPM) and who its adviser is, registered in the ROPO (official register of producers and operators of plant protection means), and its certifications (GLOBALG.A.P., integrated production, organic, PGI…) with their expiry dates. And, at a glance, how its field log is doing this season.

#The list of farms

12345678

1. 1
   Active farms and how many belong to members; to the right, the area, the organic area, the season's kilos against the previous one and the certification warnings.
2. 2
   Search by holder, code, tax ID, REA, municipality or crop.
3. 3
   Filters: the own farm, the members, those with organic land, those with a certification about to expire, those with treatments not validated and the inactive ones, with their count.
4. 4
   The own farm (house icon, in earth brown) comes first; then the members by code, with their member number and municipality. Press a row to open the record.
5. 5
   How it complies with integrated pest management and its adviser.
6. 6
   The valid certifications (GGAP, PGI, IP, ORG…); with an amber warning if any expires soon or has expired.
7. 7
   Field log: whether there is a pre-harvest interval running and how many treatments are waiting for the adviser's validation. If everything is up to date, the date of the last visit.
8. 8
   New farm: add a new member or the own farm.

The Area column (with the plots or the organic part below), Crops (how many live ones and which) and Kg season (with the previous season below, «prev.») complete each member's picture. You can sort by any column by pressing its title and download the list with the export button (see The screen).

#A farm's record

Pressing a farm opens its record on the right. For example, that of S-003, Jesús Pérez Ciriza, member no. 3 from Cabanillas:

12345678

1. 1
   Code, type and member number, the holder, the municipality, the REA and the IPM system. The amber pill warns of a pre-harvest interval in progress.
2. 2
   The tabs: Summary, Certifications, Plots, Crops, Field log, Deliveries, Settlements, Documents and Changes.
3. 3
   Area, plots, live crops, kilos delivered in the season and the amount settled.
4. 4
   The warnings: crops that cannot be harvested yet, certificates about to expire, treatments not validated…
5. 5
   Holder: tax ID, REA code, type, member number, years of membership and VAT scheme (the special farming scheme, REAGP, changes the settlement).
6. 6
   Integrated pest management: the system, the adviser with their ROPO number, the last visit and the season's treatments (those not validated, in blue).
7. 7
   Logbook compliance: the season's score, the gaps and the warnings, with what is missing. View all opens Compliance.
8. 8
   Contact and payment: address, phone, email and the IBAN for settlements (hidden; the eye shows it).

At the top right, Edit (the pencil) opens the farm's details and More options (the three dots) gives shortcuts to create a New plot or a New crop on it, or to View on the map its plots.

Below the summary there is also the split of the cropped area by species (a ring with each one's colour).

#Certifications

The Certifications tab lists the farm's certifications with their certification body, their code (the GLOBALG.A.P. GGN, the operator number…), the scope and the expiry. Jesús has the PGI Alcachofa de Tudela (covering the artichoke on S-003/04) and GLOBALG.A.P. IFA v6 under option 2, the cooperative's producer group option.

12

1. 1
   New certification: type, name, body, code, scope, issue date and expiry date.
2. 2
   Each certification with its body, code and scope; on the right, whether it is valid, its expiry and the days left (amber if it expires soon, red if it has expired).

#Plots, crops, deliveries and settlements

• Plots: the farm's parcels with their SIGPAC reference, the current crop and its area; New plot and View on the map. Each row opens the plot's record (Plots & map).
• Crops: all those it has had, newest first, with their season, planting date, kilos harvested, the pre-harvest interval if any and their status; New crop (Crops).
• Deliveries: what was delivered this season (kilos and harvests, by species) and each harvest with its field lot, the waste and whether it has been graded (Harvests).
• Settlements: the member's settlements, newest first, with their period, kilos, status (draft, issued, paid) and net amount (Member settlements). Amounts only with the «See settlements» permission.
• Documents and Changes: the farm's files (the scanned certificate, the REA…) and who changed what and when (see The screen).

#The field log, as a timeline

The Field log tab brings together everything recorded on the farm, newest first and grouped by month: treatments, fertilising, irrigation, field work, harvests, technical visits and analyses. It is the quickest way to see what has been done on a member's farm before visiting them or before an audit.

1234

1. 1
   Filter by type of operation, with its count: treatments, fertilising, irrigation, field work, harvests, technical visits and analyses.
2. 2
   Grouped by month, latest at the top.
3. 3
   Each operation with its number, date, plot and status. Marta's visit VI-2026-0244 found Tuta in the tomato above the threshold. Press it to open its record.
4. 4
   Irrigations on the same day are grouped in one line with the total volume.

If something was recorded late, the line says so («recorded after 40 days»): the field log has a deadline for recording each operation (one month for treatments and fertilising) and Compliance counts it as a gap.

#Adding or changing a farm

1234567

1. 1
   Type: member or own farm.
2. 2
   Code: S-NNN for members; unique in the cooperative.
3. 3
   Holder: the name or company name as it appears in the REA.
4. 4
   REA code and tax ID (Ceres checks the control letter or digit).
5. 5
   VAT scheme: the general one or the special farming scheme (REAGP), which adds the compensation to the settlement.
6. 6
   IPM system and adviser. With assisted IPM or ATRIA, an adviser registered in the ROPO is required.
7. 7
   Save. Further down: contact details, settlement IBAN and whether it is active.

#What the member sees

A member signs in to Ceres and only sees their own farm: the list shows a single row, theirs, with their figures. They can open its record and look at their field log, deliveries and settlements, but cannot change its details.

1234

1. 1
   The figures are only his: 1 farm, 4.08 ha and his kilos for the season.
2. 2
   His only row: that of S-003. Pressing it shows his record, his field log, his deliveries and his settlements.
3. 3
   He can download his own data, but has no New farm and cannot edit.
4. 4
   His sidebar: his farm, his plots and crops, his field log, his harvests, his settlements, compliance and weather.

#Tips

A plot is a piece of a farm's land that is cropped as a unit. In Ceres each plot is a SIGPAC parcel (or part of one): the Geographic Information System for Agricultural Parcels, the same one the CAP and the digital field log use to identify land with seven numbers: province, municipality, aggregate, zone, polygon, parcel and enclosure. Plot S-003/01 · El Recuenco of Jesús Pérez Ciriza is SIGPAC parcel 31:108:0:0:13:4:1 (Navarre, Fustiñana, polygon 13, parcel 4, enclosure 1).

Each plot carries what determines what can be done on it: the cultivable area, the irrigation and whether it is open-field or protected, whether it is in a nitrate vulnerable zone or a specific zone, whether it is organic, whether it is registered in a PGI or PDO, and its soil data. With them Ceres checks treatments and fertilising and passes the quality labels on to the lots. And from space, the Sentinel-2 satellite measures its vigour every few days.

#The list of plots

12345678

1. 1
   Cultivable area of the active plots; on either side, how many there are, the irrigated land, the area in a vulnerable zone and the organic area (separately, the area in conversion).
2. 2
   Low vigour: plots where the satellite sees part of the crop below its average. Click it to see only those (further down, Satellite vigour).
3. 3
   Choose a farm to see only its plots, in the list or on the map (on the right, List or Map: Ceres remembers the last one you used).
4. 4
   Filters: no crop, within pre-harvest interval, vulnerable zone, organic, greenhouse or protected, specific zone, inactive and low vigour.
5. 5
   The SIGPAC reference and the land use (TA, arable land); under Area, the cultivable area and, below, that of the SIGPAC parcel.
6. 6
   Zones: PGI or PDO, vulnerable zone, specific zone, organic.
7. 7
   NDVI: the mean vigour in the latest satellite image; with the icon and the percentage, the part of the plot with low vigour (on S-002/02, 49 %).
8. 8
   PHI · activity: the pre-harvest interval in progress or, if there is none, when the last operation took place.

The Current crop column says what is on the plot now (with the dot in the species' colour), its status and its planting date; Irrigation · protection, the irrigation system and whether it is open-field, greenhouse, net or tunnel. Press a row to open the record.

#The map

With Map the plots are shown over the PNOA aerial photo (the aerial photographs of Spain's National Geographic Institute, IGN), each in its crop's colour, the same as on the dashboard, the planner and the reports. Zoomed out, each plot is a dot; as you zoom in, you see its outline.

12345678

1. 1
   The farm filter: the map zooms to its plots.
2. 2
   Switch between the aerial photo and the street map (OpenStreetMap), to find your way to the plot.
3. 3
   SIGPAC parcels: draws the official parcels on top (as you zoom in).
4. 4
   Vigour layer (NDVI): each plot's vigour as seen by the satellite (further down).
5. 5
   Plot codes: shows or hides the code of each one.
6. 6
   Fit the plots, go to the cooperative and go to my location (on a phone, with GPS); below, zoom in and out.
7. 7
   The legend: hectares per crop and how many plots are within a pre-harvest interval (amber border). It folds with its arrow.
8. 8
   Each plot, in its crop's colour. Press one to open its record.

Choose a farm in the filter to zoom to its plots. For example, the four of Jesús Pérez Ciriza between Fustiñana and Cabanillas, with the SIGPAC parcels layer turned on:

123456

1. 1
   Only the plots of S-003; the figures at the top are also his only.
2. 2
   S-003/03, with the amber border: the cardoon is within its pre-harvest interval and cannot be harvested yet.
3. 3
   S-003/01, in tomato red: its outline drawn, with its code.
4. 4
   The magenta lines are the official SIGPAC parcels: they let you check that the plot is drawn correctly.
5. 5
   The SIGPAC layer, turned on.
6. 6
   Where the maps come from: PNOA (© IGN) and SIGPAC (© FEGA).

#A plot's record

12345678

1. 1
   Farm, code and location name; the member, the municipality and the SIGPAC reference.
2. 2
   Edit outline (draw it on the map) and, to its right, Edit the plot's details.
3. 3
   Cultivable and SIGPAC area, the current crop, how many crops it has had and the last operation.
4. 4
   The outline drawn over the aerial photo, with its area and vertices.
5. 5
   SIGPAC viewer: opens that parcel in FEGA's official viewer.
6. 6
   SIGPAC: the reference and its seven codes, the land use, the parcel area, the cultivable area (and what share it is), the irrigation coefficient and the cadastral reference.
7. 7
   Zones and quality: vulnerable zone, specific zone, organic status and quality labels (PGI, PDO).
8. 8
   Irrigation and protection: irrigation system, open-field or protected, municipality, farm and coordinates.

12

1. 1
   Soil and water: texture, pH, organic matter, phosphorus and potassium from the last soil analysis, and the nitrates in the irrigation water, with the nitrogen they supply.
2. 2
   Current crop: species and variety (opens its record), status, planting, harvest dates, area and BBCH.

The Soil and water values come from the last soil analysis and the last irrigation water analysis recorded in Lab analyses: when a new one is recorded, they come through here and into the fertiliser plan. If a plot has no soil analysis from the last five years, Compliance warns about it. If the plot is within a pre-harvest interval, an amber warning above the record says until when.

#The plot's rotation

The Crops tab of the record tells the plot's history: at the top, the crop sequence with its botanical family; below, each crop by season with its dates, area and yield. For example, the one for SV/04 · El Bocal, on the cooperative's farm:

1234

1. 1
   The rotation: each crop with its botanical family. If one repeats the family of the previous crop, it is flagged and a warning suggests alternating.
2. 2
   New crop on this plot.
3. 3
   The crops by season: the garlic is already planned for when the tomato finishes.
4. 4
   Each crop with its number, family, dates, area, kilos and kilos per hectare. Press to open it.

Alternating families (here borage, a Boraginaceae; tomato, a Solanaceae; garlic, an Alliaceae) breaks the cycle of soil-borne pests and diseases. The Vigour tab (further down), Notebook (everything recorded on the plot, as for the farm), Analyses, Documents and Changes complete the record.

#Satellite vigour

Every few days, the Sentinel-2 satellite of the European Copernicus programme photographs the Ribera with 10-metre detail. From those images Ceres calculates each plot's NDVI (normalised difference vegetation index) over its SIGPAC parcel: a number from 0 (bare soil) to 0.8-0.9 (a dense, healthy crop) that tells you how much green, active vegetation there is. Only clear passes count: clouds, their shadows and haze are discarded.

It does not replace a visit, but it tells you where to look. If part of the plot falls behind the rest, Ceres warns of low vigour —on the record, in the list, on the dashboard and in the adviser's «Your day»—, and whoever visits finds the cause: irrigation, a pest, a disease, weeds, waterlogging…

On the map, the satellite button turns on the vigour layer. This is how María Pilar Sanz's three plots (S-002) look:

123456

1. 1
   The vigour layer, turned on.
2. 2
   S-002/02, the pepper, with a dashed border: it has low vigour. The yellow area in the south-east is the part that has fallen behind.
3. 3
   S-002/03, with a solid amber border: it is within a pre-harvest interval.
4. 4
   Each square is a 10 m pixel, coloured by its NDVI: from sand (soil) to dark green (dense vegetation).
5. 5
   The legend: the NDVI scale, the image shown and how many plots have low vigour. Its ⓘ explains how it is calculated.
6. 6
   The imagery: PNOA (© IGN) and Copernicus Sentinel-2.

With the map zoomed out, each plot is a dot coloured by its mean NDVI; as you zoom in, you see its pixels. Hover over it (or tap it on a phone) to see the plot, its NDVI and its low zone.

On the plot's record, the low-vigour warning appears in the Summary, with the View vigour button:

123

1. 1
   The Low vigour tag in the header.
2. 2
   The warning: 48.8 % of the plot is below 85 % of its average (NDVI 0.35 in the image of 29 September). Visit it to find the cause.
3. 3
   View vigour opens the Vigour tab.

12345678

1. 1
   The low-vigour warning, with the image in which it shows.
2. 2
   The mean NDVI in the latest image (0.35)…
3. 3
   …how much it has changed since the previous one and the crop average since it was planted (0.53)…
4. 4
   …and the low zone: the part of the plot below 85 % of its average (48.8 %).
5. 5
   The evolution: the standing crop, the last 12 months or everything.
6. 6
   The mean NDVI of each clear pass, with the band of its pixels and the crop average; below, the plot's crops (little gem lettuce, broad beans and the pepper, which drops at the end of September).
7. 7
   The last three images with a map and Highlight low zone.
8. 8
   The vigour map: each 10 m pixel in its colour; hover over one to see its NDVI and what share of the average it is.

If the mean NDVI is very low, there is no warning even if the low zone is large: nearly bare soil or a crop with little cover gives differences that mean nothing. That is what happens with the tomato on SV/04, and the record explains it:

1

1. 1
   Why there is no warning: its mean NDVI (0.23) is that of nearly bare soil or a crop with little cover; the warning needs 0.30 or more.

#Drawing or importing the outline

The outline is the plot's boundary on the map. Without it, the plot does not appear on the map (the record warns «The plot has no outline drawn»). It opens with Edit outline in the record (or when adding a plot) and there are three ways to do it:

12345678

1. 1
   Draw: tap the map to add vertices in order; the outline closes by itself.
2. 2
   Import from SIGPAC: tap inside the official parcel and its boundary is copied.
3. 3
   Undo the last vertex or clear them all.
4. 4
   Paste coordinates: «lat, lon» per line, GeoJSON or WKT.
5. 5
   Load the SIGPAC parcel of the plot's reference, in one tap.
6. 6
   The outline, with its vertices. The magenta lines are the SIGPAC parcels.
7. 7
   The outline's area and vertices, updated instantly.
8. 8
   Save outline. If it measures differently from the cultivable area, Ceres warns you so that you check it.

#Adding a plot

New plot (in the list, or in More options of the farm record) starts by placing the outline and continues with the plot form, in blocks:

Ceres warns you as you type: if the cultivable area is much smaller than the parcel («check margins, tracks or landscape features»), if the SIGPAC land use is not a cropping one, if the date of conversion to organic is missing, or what a vulnerable or specific zone implies.

#Tips

A crop (in the database, a planting) is a species and a variety on a plot for a period of time: from sowing or transplanting until the harvest finishes or it is pulled out. Each one has its number (CU-2026-0051) and the whole field log hangs from it: treatments, fertilising, irrigation, field work and harvests.

A crop goes through these statuses:

Crops are grouped by season, which in Ceres runs from 1 September to 31 August. Those that last several seasons (asparagus, artichoke) or cross September also appear in the following seasons while they are still alive.

#The list of crops

The list shows the crops of the chosen season. Here, with the Within PHI filter, the ten that cannot be harvested yet:

12345678

1. 1
   Cropped area and number of crops; on the right, those being harvested, within a pre-harvest interval, the kilos harvested this season and the yield.
2. 2
   The season you are looking at (the current one, by default).
3. 3
   The season's List or Planner (further down).
4. 4
   Filters by status, within pre-harvest interval, without fertilisation plan and finished.
5. 5
   Each crop with its variety, number and system (integrated production, conventional or organic); its plot and the member. Press it to open the record.
6. 6
   Establishment: the date, the days in the field and the last BBCH; Harvest: the planned dates and when it starts or ends.
7. 7
   PHI until: the last day of the pre-harvest interval. Until then it cannot be harvested.
8. 8
   Kg · kg/ha: what has been harvested, the yield and the percentage against the expected yield; if there is no harvest yet, the forecast.

#A crop's record

The record brings together everything about the crop. That of broccoli CU-2026-0051 of Agrícola Ebro Soto (S-007/04 · La Pedrera), transplanted on 17 September and treated on 3 October with TR-2026-0544:

12345678

1. 1
   Number and season, status, species and variety; the plot, the farm and the growing system.
2. 2
   Record in notebook, Change status and Edit.
3. 3
   Area, kilos harvested, kilos per hectare against the expected yield and cost per kilo (only with the costs permission).
4. 4
   The pre-harvest interval: until when and because of which treatment. Open takes you to that treatment.
5. 5
   Shortcuts to record a treatment, a harvest, a fertiliser application, an irrigation or a field task on this crop, with everything already filled in.
6. 6
   The calendar: transplanting, start and end of harvest and end of the crop. Filled dots have already happened; empty ones are the forecast.
7. 7
   Expected yield against the species reference and what has been harvested.
8. 8
   Planting: plot, farm, spacing, density, system, growth stage (BBCH) and protection. Record growth stage updates it.

With the pre-harvest interval in progress, the database will not record a harvest of this broccoli until 17 October (the warning says until when and the treatment that started it). Further down the summary are the planting material and the crop notebook, which are better seen on a crop already being harvested.

#Expected against actual yield

The tomato CU-2026-0023 of Jesús Pérez Ciriza (S-003/01) was transplanted on 8 May and has been harvested since 14 July:

123456

1. 1
   59.5 t harvested: 56,114 kg/ha, 72 % of what was expected; and the cost per kilo.
2. 2
   The actual start of the harvest (the first recorded one) next to the planned one, and the planned end with the last harvest and how many there have been.
3. 3
   Production: the expected one (82.8 t), the species reference, what has been harvested with its progress bar and the kilos per week.
4. 4
   Planting material: establishment, nursery, plant batch, plant passport and whether it is certified or organic material.
5. 5
   Crop notebook: treatments and the last one, nitrogen applied, whether it has a fertilisation plan, irrigation water and hours of work.
6. 6
   The Costs tab: what the crop has cost by item (plant protection products, fertilisers, plants, labour, machinery and water).

#The crop notebook

The record's Field log tab separates what has been recorded on the crop by type, each block with its button to add. For example, that of cauliflower CU-2026-0041 of Jesús Pérez Ciriza (S-003/02), which has a treatment order for today:

1234

1. 1
   The crop's Treatments, newest first; below come fertilisation (with the fertilisation plan), irrigation with the water balance, field work and harvests.
2. 2
   Adds a treatment to this crop.
3. 3
   Each treatment: product, date, pest, BBCH and its pre-harvest interval («PHI 14 d → 5 Oct 2026»: within the interval until 5 October); on the right, its status.
4. 4
   Today's order, still scheduled: it does not start a pre-harvest interval until the application is recorded.

#The crop's vigour

The Vigour tab shows what the Sentinel-2 satellite sees on the plot while the crop lasts, from planting to today: how it grows, when it peaks and whether part of it falls behind. It is the same information as the plot's Vigour tab, but only for this crop's cycle. This is how pepper CU-2026-0034 of María Pilar Sanz (S-002/02) is doing, with a low-vigour warning:

12345

1. 1
   The crop's Vigour tab.
2. 2
   The low-vigour warning for its plot: almost half of it below 85 % of its average.
3. 3
   The NDVI in the latest image and how much it has changed since the previous one.
4. 4
   The cycle's maximum and average: the pepper reached 0.77 and today it is at 0.35.
5. 5
   NDVI over the cycle: from planting (2 June) to today, with the band of its pixels and the cycle average. Below, the vigour map of the last three images.

#Changing the status and recording the BBCH

The growth stage says at what point in its development the crop is, on the BBCH scale: a code from 0 to 99 whose first digit is the principal stage (0 germination, 1 leaves, 4 harvestable parts, 6 flowering, 7 fruit, 8 ripening, 9 senescence…). It matters because many authorised uses of a product only apply at certain stages, and each treatment record includes it.

123

1. 1
   Finish the crop: the harvest is over. It asks for the end date: from that day the plot is free.
2. 2
   Remove the crop: it was pulled out early (a frost, a pest).
3. 3
   Record growth stage: today's BBCH.

123

1. 1
   The BBCH code, from 0 to 99.
2. 2
   Ceres says which principal stage it belongs to (8: ripening).
3. 3
   Save.

Depending on the status, Change status offers one thing or another: for a planned crop, Plant (now in the field); for an established one, Start harvesting (from then on it appears in the harvest forecast and in My day); for one being harvested, finish it or remove it; and for a finished one, Reopen (back to harvesting) in case it was closed too early. Ceres warns you on the record when the harvest should have started or ended according to the calendar, and if you try to finish a crop that still has a pre-harvest interval or has no harvest at all.

#Creating a crop

1234567

1. 1
   The plot (with its farm).
2. 2
   Species and variety (of that species); establishment (sowing or transplanting).
3. 3
   Status: «Planned» if it is not in the field yet.
4. 4
   The sowing or transplanting date; the start of harvest is proposed from the species' cycle.
5. 5
   Expected yield: proposed from the reference yield × the area.
6. 6
   Spacing (between rows × between plants): it calculates the density.
7. 7
   Planting material: nursery, batch, plant passport and whether it is certified or organic.

#The season planner

Planner shows each plot's season on a timeline, week by week: what occupies it, what gaps remain and where a family is repeated. It is the tool for deciding what is planted, where and when.

12345678

1. 1
   The season you are planning.
2. 2
   One farm or all of them.
3. 3
   With a gap, Same family or Free now: only those plots.
4. 4
   Zoom out, see the whole season and zoom in.
5. 5
   Occupancy: what share of the season's area and time has a crop.
6. 6
   Today.
7. 7
   Each bar is a crop, in its species' colour: faint from transplanting to the start of harvest, solid during the harvest; with a border, planned. The amber stripe, the pre-harvest interval.
8. 8
   A free gap: tap it to plan a new crop there.

On the left are the plots grouped by farm, with their area and location name. Press a bar to open the crop or a gap in a row to create a planned crop there, with the plot and the dates already filled in. Bars with a rotation warning repeat the family of the previous crop on that plot.

#Tips

Treatments is the heart of the field log: every plant protection product applied on the plots of the cooperative's farm and its members is recorded here, who recommended it and why, who applied it, with what equipment and in what conditions, and when the crop can be harvested. It is the record the regulations require in electronic form from 1 January 2027, and Ceres keeps it from the recommendation to the adviser's signature.

Some trade terms used in this chapter (all of them are in the Glossary):

• Recommendation: the adviser's integrated pest management proposal: what to treat, why (threshold exceeded, official pest warning, symptoms, preventive) and which non-chemical alternatives were considered.
• Treatment order: what is going to be applied, when, who (the operator) and with what equipment. It appears in the operator's My day on the planned day.
• Application: the treatment once done, with its date and time, the conditions (temperature, humidity, wind) and the product batch used. From then on it counts in the field log and the pre-harvest interval runs.
• Pre-harvest interval (PHI, plazo de seguridad): the days that must pass from applying a product until the crop can be harvested. The product label sets it for each crop.
• Authorised use: each combination of product, crop (or crop group) and pest (or pest group) that the official Plant Protection Products Register of the MAPA allows, with its dose, its PHI, its maximum number of applications and the interval between them.
• IPM (integrated pest management, GIP): spraying only when needed and giving priority to non-chemical methods. The adviser who signs it is registered in the ROPO (official register of producers and operators).
• Spraying licence: the professional user's licence for plant protection products (basic, qualified…), valid for 10 years. ITEAF: the compulsory technical inspection of application equipment, every 3 years.
• BBCH: the crop's growth stage on the BBCH scale (81, for example, is the start of ripening in tomato).

#The list of treatments

When you open it you see all the treatments of the farms assigned to you, newest first: the orders for the coming days at the top and, below, the applications already recorded. Marta, the field adviser, sees the cooperative's farm and members S-001 to S-010.

12345678

1. 1
   The indicators: orders today (and overdue ones), orders in the next 7 days, applications not validated, treatments with a plot within the pre-harvest interval, those recorded late and pending recommendations. Each one filters the list when pressed and its ⓘ explains the calculation.
2. 2
   The search box: by number, member, crop, plot, product, pest or operator.
3. 3
   List or Week: the week shows the orders on a calendar (you see it further down). To its left, Export CSV.
4. 4
   New treatment: a recommendation or an order (with «Recommend treatments» or «Schedule treatments»).
5. 5
   The filters, with their count. Swipe the row to see the last ones: Within PHI and This season.
6. 6
   Each row: number and scope, date (the planned one, with «today», «tomorrow»…, or the application date with its hours), farm, crops and plots with their area, products and pests, and operator and equipment. This is today's order for the cauliflower of S-003.
7. 7
   The status. Next to it, a red clock if it was recorded late and a pen if it is validated with a signature.
8. 8
   PHI until: the last day without harvesting. In amber while it lasts (hover for «Can be harvested from…»); «Not applicable» if the product has no interval.

#The week of orders

With Week (or by pressing the Next 7 days indicator) you see the orders on a Monday-to-Sunday calendar: what has to be applied each day, by whom and with what. It is the foreman's and the adviser's view for sharing out the work.

1234

1. 1
   Previous and next week; Today takes you back to the current week.
2. 2
   Each day, with how many orders it has. Today is highlighted.
3. 3
   An order: number, farm and crop, products and operator. Press it to open its record.
4. 4
   Record: on today's or overdue orders, opens the application record (with the «Apply treatments» permission).

#The treatment record

Press a treatment to open its record. At the top, the number, the farm, the status and the products; below, the tabs Summary, Recommendation, Traceability and Documents (and Changes, with the audit permission). Order TR-2026-0558 is for today: SANAGRICOLA WP against downy mildew on the cauliflower of S-003/02, to be applied by Ander with the PU-01 sprayer.

12345678

1. 1
   Number, farm, status, products and, below, crops, plots and area.
2. 2
   The PDF: the treatment order while it is pending, or the treatment record once applied.
3. 3
   The actions the status and your profile allow: edit, schedule, record the application, validate, assess efficacy or cancel.
4. 4
   The figures: area, plots, products, pre-harvest interval (once applied) and the planned or application date.
5. 5
   The next step in the cycle with its button: here, Record application.
6. 6
   The cycle: recommendation, order, application and validation, each step with its date and its person.
7. 7
   The check against the Register: green if there are no issues; otherwise, the errors (red) and warnings (amber). Here, two customers who ask for extra days on top of the pre-harvest interval (further down, Customer residues and mode of action).
8. 8
   Each plot with its SIGPAC parcel, area and BBCH, and the expected interval if applied on the planned date: «PHI 14 days · harvest from 20 Oct 2026».

Further down, the Summary continues with the products and the application.

123456

1. 1
   The product with its registration number, its active substance and the badge if it is suitable for organic (opens its record in Catalogues).
2. 2
   The mode of action of its active substance: FRAC M 01, that of copper. Hover over it to see the group's name.
3. 3
   Pest, dose and quantity: the estimate while it is an order, the amount used once recorded (with the store batch, if one was chosen).
4. 4
   The operator, with their licence level and expiry (in red if it expires before the treatment date).
5. 5
   The equipment, with its ROMA number and until when its ITEAF is valid (in red if it expires before).
6. 6
   Method and spray volume (litres of water per hectare). Once applied, also the hours and the conditions, with «High wind» if it was above the maximum.

The ⋮ menu changes with the status. On a recorded, not yet validated application, such as TR-2026-0550 (ARAW on the leek of S-010/02, applied yesterday), these are the adviser's actions:

123

1. 1
   Validate and sign (adviser).
2. 2
   Assess efficacy without validating yet.
3. 3
   Cancel: returns the product to its batch and removes the pre-harvest interval.

1

1. 1
   A warning (in amber): it does not prevent the application, but asks you to check the zone's restrictions before spraying.

#Recommendation and traceability

The Recommendation tab gathers what justifies the treatment: the integrated pest management justification, the scope, the recommendation date, the adviser's observations and the non-chemical alternatives considered, the adviser with their ROPO number, the Crop protection visit it came from (if any) and the farm.

1234

1. 1
   Justification (threshold exceeded, official pest warning, symptoms, preventive or other), scope (in crop, post-harvest, store or seed) and date.
2. 2
   The adviser's observations and the non-chemical alternatives. If they are not recorded, the record says so: IPM asks for priority to be given to those methods.
3. 3
   The source visit: the field report where the pest was seen above the threshold. Press it to open it.
4. 4
   The adviser with their ROPO number. If it is missing, a warning appears: complete it in People.

The Traceability tab of an applied treatment answers the question that matters when there is a residue alert: what was harvested on those plots after the treatment and who was it sold to? TR-2026-0517 (ADINA on the pepper of S-010/01, against aphids, applied on 22 September and validated) shows it lot by lot.

1234

1. 1
   Full traceability: opens the Traceability graph with this treatment as the starting point.
2. 2
   Lots harvested on the treated plots since the treatment date, kilos sold, customers and what is still in stock (in amber).
3. 3
   The lots: field lots (LC-…, the crate) and packed lots (LV-…, the box), with their date and kilos.
4. 4
   The customers they reached, with the kilos of each.

While the treatment has not been applied, the tab reads «Traceability available once the application is recorded». In Documents you can attach photos, the product label or the purchase delivery note (see The screen).

#Scheduling a treatment order

New treatment (or Create in the top bar) opens the form. At the top you choose whether it is a recommendation (the adviser's proposal, with a compulsory justification) or a treatment order (with a compulsory planned date). On the right, the live check fills in as you type. Recommendations are also born from a Crop protection visit with Recommend treatment.

1234567

1. 1
   Recommendation or Treatment order. Below, what each one means.
2. 2
   The farm: the cooperative's own farm or the member's. If you only have one, it is already set.
3. 3
   The farm's current crops: tick the ones being treated. Each with its planting, SIGPAC parcel, area, BBCH and status; organic ones carry their seal.
4. 4
   Area (if you only treat part of it) and BBCH: the planting's values and its last observed stage are proposed.
5. 5
   A crop within the pre-harvest interval has the date in amber: the cardoon of S-003/03 cannot be harvested until 17 October.
6. 6
   Planned date and scope. The pre-harvest interval and the quantities are calculated for that date.
7. 7
   The live check: it waits until there are plots and at least one product.

Below come the justification (with the adviser, who is you if you are the field adviser), the observations and the non-chemical alternatives, the products and the work order (operator, equipment, method and spray volume).

Choosing the product among the authorised uses

With the plots chosen, press Choose authorised product… (or Add product for another one). You do not choose from a list of all products, but from those the MAPA Register authorises for the crop on those plots: with its species, whether they are open-field or protected and whether any is organic. Choose the pest and you will see only the products authorised against it.

123456

1. 1
   What it is searched for: the species on the plots, open-field or protected and, if any is, organic.
2. 2
   Search by product, active substance or pest (at least 3 letters).
3. 3
   The chosen pest and the filters: In stock, Organic-approved and Include withdrawn.
4. 4
   Each product with its registration number, the organic seal if suitable, its active substance and function, the stock in the store and how many uses it has. Those in stock come first.
5. 5
   A group use: «Lepidoptera» on «Plant species» is valid for Tuta and tomato, but its conditions restrict it to mother plants for seed. Always read the conditions.
6. 6
   The use for tomato against Tuta: dose 0.26 %, PHI 3 days, max. 3 applications every 7 days. Choose puts it in the order.

When you choose the use, the product line fills in with the pest, the unit and the maximum authorised dose (you can lower it), and below it summarises the use: dose, pre-harvest interval, applications, interval and stock. If you like, choose the store batch it will come from now. The check calculates at once how much product to prepare and from when the crop can be harvested.

12345678

1. 1
   The chosen product, with its registration number, the organic seal and the active substance.
2. 2
   The chosen authorised use: dose, pre-harvest interval, maximum number of applications, interval and stock in the store.
3. 3
   Pest, dose, unit and store batch (optional in the order).
4. 4
   Quantity to prepare for the chosen area: 0.26 % × 1,000 l/ha × 1.06 ha = 2.756 l.
5. 5
   Operator and equipment: without them the order can be saved, but not recorded.
6. 6
   The warnings: the operator and the equipment are missing.
7. 7
   The pre-harvest interval if applied on the planned date: PHI 3 days, harvest from 9 October.
8. 8
   The product quantity for each line.

#The live check

While you fill in the form, the database tests the order as if it were about to be applied —without saving anything— and returns the errors (in red: they prevent recording the application) and the warnings (in amber: it is recorded, but worth reviewing). The same is repeated when recording the application and in the record. An example: in order TR-2026-0558, raise the SANAGRICOLA WP dose from 0.202 % to 0.5 %, set Daniel Aranda as operator and the AT-07 sprayer.

123456

1. 1
   The dose raised to 0.5 %: the product line turns red.
2. 2
   That line's error: above the maximum authorised on cauliflower against downy mildew (0.4 %).
3. 3
   Daniel Aranda: his licence expired on 7 August (the selector already flags it with ⚠).
4. 4
   The AT-07 sprayer: its ITEAF is not valid (it was due on 22 August).
5. 5
   The three errors, explained: with any of them the database will not record the application. Below, the customers' warnings, the expected pre-harvest interval and the recalculated quantity (now 4.17 kg).
6. 6
   The summary in the footer. You can still save the order (it asks you to confirm), but not apply it until it is fixed.

This is what is checked, always against the Register loaded in Ceres and the cooperative's data:

On an order not yet assigned, a missing operator is a warning (it can be saved), but when recording it is an error.

#Customer residues and mode of action

The check also gives two warnings that do not prevent recording, but are worth looking at before spraying:

• Customers' residue requirements. Some customers ask for more than the law: a maximum number of active substances detected, a maximum percentage of the maximum residue limit (MRL), substances they do not accept or extra days on top of the pre-harvest interval (they are entered in each customer's record). If, with this treatment, what is harvested on those plots would no longer be fit for one of the customers who usually buy that crop, Ceres warns you. In today's order for the cauliflower (TR-2026-0558), the school canteen asks for 7 extra days and Frutas Bidasoa for 3: the cauliflower of S-003/02 will be fit for them from 27 and 23 October, not from the 20th.
• Mode of action. Each active substance belongs to a group according to how it acts: IRAC for insecticides, FRAC for fungicides and HRAC for herbicides. Repeating the same group over and over selects resistant pests and fungi. Ceres counts how many times in a row and how many times in the crop cycle that group has been used and warns if it exceeds the recommendation (2 in a row and 3 per cycle, unless Settings says otherwise). Low-risk groups —multi-site ones, such as copper or sulphur, and biologicals— do not count.

Order TR-2026-0556 (SCORE 25 EC, with difenoconazole, on the asparagus of SV/01) has both warnings:

12

1. 1
   Residue requirements: Frutas Bidasoa does not accept difenoconazole, so the lots of this asparagus would no longer be fit for it.
2. 2
   Mode of action: it would be the tenth application of FRAC group 3 in the asparagus cycle, against a recommended maximum of 3. It is worth alternating with another group.

In the form, each product shows its group (FRAC 3, IRAC 4A, HRAC…) in a tag —hover over it for the name of the mode of action— and, below, the rotation line if it repeats:

1234

1. 1
   The active substance's mode-of-action group: FRAC 3, the sterol biosynthesis inhibitors (DMI).
2. 2
   The rotation: how many times that group has been used on the planting and what is recommended.
3. 3
   The same warnings in the live check: they do not prevent saving the order or recording it.
4. 4
   Add product opens the selector, which now sorts the products by mode of action.

With a planting chosen, the authorised products selector lists first those that alternate group with what has already been applied, and last those that repeat beyond the recommendation. These are the ones authorised against Stemphylium on the asparagus of SV/01:

1234

1. 1
   Which planting they are sorted for and how: those that alternate first.
2. 2
   Alternates: its group has not been used (or does not count) on this planting. Here, a biological (FRAC BM 02).
3. 3
   Each product with the groups of its active substances and, if it repeats beyond the recommendation, the warning in amber.
4. 4
   The stock in the store and how many uses it has for this crop and this pest.

1

1. 1
   Without the permission, the warning only says how many customers it affects and whom to ask: the adviser or sales.

#Quantities to prepare and pre-harvest interval

#Recording the application

When the treatment is done, it is recorded: usually the operator does it when finished, from My day on the phone, but it can also be done from the record or from the week of orders with Record application. The dialog brings what was in the order and proposes the weather conditions for those hours, from the cooperative's hourly weather data (see Weather).

1234567

1. 1
   Date and hours of the application: today is proposed, from an hour ago until now. It cannot be a future date.
2. 2
   Operator (compulsory) and equipment, those of the order; you can change them if it was not so.
3. 3
   The weather in those hours: temperature, humidity, wind and delta T, with «Suitable» if wind and delta T were fine throughout. Use copies the values into the fields.
4. 4
   The wind, with the maximum from Settings below: above it, a drift risk warning.
5. 5
   Dose and total quantity of each product: calculated or, if you change it, what was actually used.
6. 6
   The store batch it came from: when recording, its stock is deducted (here there are two SANAGRICOLA WP batches; choose the one used).
7. 7
   Record application: the database checks it again and, if there are errors, refuses it.

#Validating with a signature

The last step belongs to the adviser: they check that what was applied matches their recommendation, assess the efficacy and sign on screen with a finger or the mouse. It needs the «Validate treatments» permission and the user to be linked to their People record, because the signature is in their name. Marta validates TR-2026-0550, applied yesterday against leek rust:

123456

1. 1
   What you validate: that the recorded application matches your recommendation.
2. 2
   The efficacy: effective, partial or ineffective (or pending assessment).
3. 3
   What you saw afterwards: pest level, regrowth, damage…
4. 4
   The signature box. Clear starts it again; without a signature it cannot be validated.
5. 5
   The signature is saved as an image with your name, the date and the time. Once validated, it can no longer be cancelled.
6. 6
   Validate and sign closes the cycle.

To cancel a treatment, Cancel in the ⋮ menu asks for the reason. A recommendation or an order are simply cancelled; a recorded application returns the product to its store batch and removes the pre-harvest interval from its plots. A validated treatment can no longer be cancelled.

The PDF of the order and of the record

The PDF icon in the header generates the treatment document, which opens in the browser's print dialog (from where it is printed or saved). While it is pending it is the Treatment order, with the «Recommendation» or «Pending order» stamp, to give to the operator; once applied, it is the Treatment record (with the «Not validated» stamp until the adviser signs). It contains:

• the application date and hours (or the planned one), the recommendation date and when it was recorded;
• the farm with its IPM system, the operator with their licence and its expiry, the equipment with its ROMA number and ITEAF, and the adviser with their ROPO number and the source visit;
• the treated plots: SIGPAC reference, crop, hectares, PHI in days and harvest from;
• the products: name, registration number, active substances, pest, dose and quantity;
• the application conditions, the IPM justification, the adviser's validation and the signature boxes of the operator and the adviser.

The PDF order warns in its footer that the interval and the quantities are those expected if applied on the planned date, and both remind you that Ceres helps you comply and keeps a record, without replacing the label or the adviser.

#What changes depending on the profile

Jesús, the member of S-003, sees only his treatments and read-only: no New treatment and no actions in the record. It lets him know what has been applied on his plots and when he can harvest.

123

1. 1
   The same filters, with the counts of his farm.
2. 2
   List and Week, but no New treatment: the member neither recommends nor schedules.
3. 3
   The cardoon of S-003/03 is within the interval until 16 October: it can be harvested from the 17th.

#Tips

Fertilisation is where you record everything that adds nutrients or organic matter to a crop's soil: the base dressing before planting, the top dressings, fertigation (fertiliser dissolved in the irrigation water), foliar feeds and soil amendments (manure, compost). Each entry is an application with its number (FE-2026-…).

For each application Ceres calculates the fertiliser units (UF): the kilos of N (nitrogen), P₂O₅ (phosphorus) and K₂O (potassium) that reach each hectare, from the amount of product and its analysis (the «15-5-30» on the bag). It also separates organic N (from manure and compost), which is what counts towards the vulnerable zone limit.

The section has two views, at the top left:

• Applications: each fertiliser application, with its units, its store batch and its warnings.
• Fertilisation plans: one plan per crop, with what it needs according to the expected yield and what has been applied so far.

Since 1 January 2026 each application is recorded within one month and since 1 September 2026 each crop needs its fertilisation plan (RD 1051/2022). Ceres warns you of both, and of the vulnerable-zone limit, as you type, before saving.

#The plan and the record

#The list of applications

12345678

1. 1
   The two views: Applications and Fertilisation plans. The ⓘ next to them explains the section.
2. 2
   Applications done in the current season (since 1 September). Press it to see them.
3. 3
   N applied per ha: kilos of nitrogen per fertilised hectare in the season, not counting that from water or soil.
4. 4
   Without fertilisation plan: current crops that do not have a plan yet, out of all of them. Red if any is missing; press it to go to the plans.
5. 5
   Entered late: more than a month between the application and its entry. The first figure is for the season; the second, for all history.
6. 6
   Vulnerable zone: plots above 80 % of the organic N limit, out of all those in a vulnerable zone. Press it to see the detail.
7. 7
   New fertilisation opens the form. To its left, Export CSV.
8. 8
   The filters, with their count: the season, scheduled, done, fertigation, organic, recorded late, vulnerable zone, cancelled and all.

Each row is an application:

The search box finds by plot, crop, fertiliser, batch, operator or number. The footer adds up the applications you see and the kilos of N (and organic N) they carry. Press a row to open its record.

#Recording a fertiliser application

Record each application as soon as you do it, and within a month at the latest. On the cooperative's farm the foreman does it; each member records their own from their own user (they only see their crops). Press New fertilisation (or Create in the top bar). This is how Jesús, member S-003, fills it in for the fertigation of his tomato:

12345678

1. 1
   The planting: the crop and its plot (with ZV if it is in a vulnerable zone). It brings in the crop's area.
2. 2
   Done if it has already been applied (it counts in the totals and deducts the batch) or Scheduled if it is planned.
3. 3
   The type: base, top dressing, fertigation, foliar or amendment. The application method is proposed automatically and can be changed.
4. 4
   The fertiliser from the catalogue, with its N-P-K analysis; if you choose the batch first, it fills in by itself.
5. 5
   Rate per hectare: with the fertilised area it calculates the total quantity, and vice versa.
6. 6
   Fertilised area: the crop's area; change it if you only fertilise part of it.
7. 7
   Store batch: if the fertiliser comes from an Inputs batch, saving it as done deducts it from its stock.
8. 8
   Save records it. The database checks everything again.

#The warnings when saving

At the end of the form, Ceres calculates what the rate supplies and warns you of anything that does not add up before saving. Here Marta tries 10 t/ha of sheep manure on the aubergine of S-007/03, a plot in a vulnerable zone that is already over the limit:

1234

1. 1
   The total quantity resulting from the rate times the area: 15,300 kg on 1.53 ha.
2. 2
   Supplies per hectare: the fertiliser units of this rate, N, P₂O₅, K₂O and, separately, organic N.
3. 3
   Vulnerable zone: the plot's organic N over the last 12 months would exceed 170 kg/ha (in red; in amber if it exceeds 80 %).
4. 4
   Fertilisation plan: the crop would reach more N than its plan allows for.

Warnings do not prevent saving, except in two cases that the database rejects:

• A fertiliser not allowed in organic farming on an organic (or in-conversion) crop or plot.
• An application done with a future date (schedule it instead) or with more quantity than is left in the chosen batch.

If you save with warnings, the «FE-… saved with warnings» window opens with what the database has detected: vulnerable zone above 170 kg/ha, more than 10 % above the plan, crop without a fertilisation plan or entry recorded late. They are the signal to talk to the adviser and, if needed, correct it.

#An application's record

12345678

1. 1
   The application's number and type, its status, the fertiliser and, below, the crop, the plot and the farm.
2. 2
   Edit and Cancel. A scheduled one also has Mark as done.
3. 3
   The band: N, P₂O₅, K₂O and organic N per hectare, and the rate.
4. 4
   The warning: the plot already adds up to 204 kg/ha of organic N in the last 12 months and is over the vulnerable-zone limit.
5. 5
   Application: date, crop (press it to open it), plot with its ZV, area, type, method, equipment and operator.
6. 6
   Product and rate: the fertiliser's analysis, the quantity, the store batch and whether it is allowed in organic farming.
7. 7
   The crop's fertilisation plan: what has been applied against the N, P₂O₅ and K₂O target. View plan opens it.
8. 8
   Vulnerable zone: the plot's organic N in the 12 months before this application, against 170 kg/ha.

In this example the plan bars are amber: with 26 t/ha of manure, the aubergine has more N (244 of the 104 kg/ha planned), P₂O₅ and K₂O than its plan allows for, and the plot is over the vulnerable-zone limit. That is exactly what the record wants you to see in time. The Documents tab keeps the manure delivery note, the product analysis or a photo (see The screen).

Further down, Logbook entry says when it was recorded and how many days passed since the application, against the deadline. If the application is scheduled and its date has passed, the record warns you: mark it as done (if it was) or change its date.

Cancel leaves the application in the field log as cancelled, with its number: it stops counting in the plan, the vulnerable zone and the totals, and if it came from a batch, what was used goes back to the store. What is cancelled is not deleted: it is part of the record.

#Plots in a vulnerable zone

Nitrate vulnerable zones are designated by each region: they are those draining into waters polluted by nitrates or at risk of being so. In them, manure and other organic fertilisers cannot supply more than 170 kg of N per hectare per year. Each parcel's vulnerable-zone mark is in its Plots & map record. Press the Vulnerable zone indicator to see how each plot is doing:

123

1. 1
   What is measured: organic N over the last 12 months per hectare of plot, against 170 kg N/ha·year.
2. 2
   In red, above the limit: the aubergine of S-007/03 received 26 t/ha of manure in April (204 kg/ha of organic N).
3. 3
   In green, below 80 %. The vertical line on each bar is the limit.

#Fertilisation plans

The fertilisation plan says, before starting, how much nitrogen, phosphorus and potassium a crop needs and how much has to be supplied with fertilisers. Ceres keeps one per crop (per CU-… planting). In the Fertilisation plans view you see all the season's crops with their plan and what has been applied so far:

12345678

1. 1
   With approved plan: current crops with an approved plan and what share of the total they are.
2. 2
   Without fertilisation plan: those that do not have a plan yet. It is the first thing to sort out.
3. 3
   N above plan: crops with more than 10 % N over what was planned.
4. 4
   Organic N > 170 in ZV: vulnerable-zone crops over the limit.
5. 5
   The filters: current, no plan, drafts, approved, above plan, vulnerable zone and finished.
6. 6
   Production: the plan's expected yield, in t/ha.
7. 7
   N, P₂O₅ and K₂O: what has been applied against the plan's target, with its bar. The line is the target; amber if it is exceeded by more than 10 %.
8. 8
   Plan: approved, draft or No plan (in red). Without a plan, the row gives the N applied to date.

#A crop's fertilisation plan

Press a crop to open its plan (also from an application's record, with View plan). This is the one for Jesús's Rosa de Barbastro tomato on S-003/01, which Marta drew up in April:

1234567

1. 1
   The crop (CU-…), the plan's status, the plot, the member, the area and the season.
2. 2
   Edit fertilisation plan and View planting. On a draft, also Approve plan.
3. 3
   The band: N to apply and applied, P₂O₅ and K₂O (applied / requirement) and organic N.
4. 4
   Requirements and applied: each nutrient against its target, with the percentage.
5. 5
   How it is calculated: the plan step by step, from the expected yield to the N to apply.
6. 6
   Proposal with today's data: it appears if any figure has changed since the plan was made (here, the soil mineral N, from a more recent analysis). Apply to plan updates it.
7. 7
   The Applications tab: the crop's fertiliser applications, newest first, with New fertilisation.

Further down, Plan details says who drew it up, its date, its status, the expected yield and the soil analysis it uses (press it to open it in Lab analyses). On a vulnerable-zone plot there is also the Vulnerable zone card with the organic N applied to the crop.

#Creating a crop's plan

A crop without a plan opens its record with the warning in red and a calculated proposal with the data Ceres already has: the crop's expected yield, the plot's latest soil analysis and its water nitrates. This is Jesús's cardoon on S-003/03:

123456

1. 1
   The warning: no plan since 1 September 2026, and on irrigated land there is no exemption for size.
2. 2
   Expected yield: the crop's (27.0 t on 0.72 ha = 37.5 t/ha).
3. 3
   N requirement: yield × the crop's uptake (37.5 t/ha × 3 kg N/t = 113 kg N/ha).
4. 4
   The contributions deducted: soil mineral N (analysis AN-2025-0005), N from irrigation water (nitrates 47.3 mg/l) and amendments from the previous year.
5. 5
   N to apply with fertilisers: 113 − 23 − 43 − 0 = 47 kg N/ha. Below, the P₂O₅ and K₂O requirements.
6. 6
   Create plan opens the form with these values.

123456

1. 1
   Expected yield: changing it recalculates the requirements with the crop's uptake.
2. 2
   Requirements for N, P₂O₅ and K₂O in kg/ha: you can adjust them by hand.
3. 3
   The N contributions from the soil, the irrigation water and earlier amendments.
4. 4
   The status: as a Draft it does not count as the season's approved plan.
5. 5
   Plan notes: previous crop, application timing and methods, measures to reduce emissions…
6. 6
   The N to apply, recalculated as you type.

#What each profile sees

#Tips

In Irrigation each irrigation of each crop is recorded: the day, the hours, the cubic metres applied and, if the plot has a meter, its reading. If the water carried dissolved fertiliser, the irrigation is marked with fertigation (and the fertiliser is also recorded in Fertilisation). With that, Ceres calculates the m³ per hectare, the water depth in millimetres (1 mm = 10 m³/ha) and the nitrogen supplied by the water, which the fertilisation plan then deducts.

The section has two views, at the top left:

• Irrigations: the list of irrigations done and scheduled.
• Water balance: how much water each crop has needed and how much it has received, day by day, with a recommendation of how much to irrigate.

Irrigations are recorded within a month of being done (RD 1051/2022). Scheduled ones also appear in My day, where whoever irrigates marks them as done from their phone.

#The list of irrigations

12345678

1. 1
   The two views: Irrigations and Water balance.
2. 2
   The season's water: the m³ of irrigations done since 1 September.
3. 3
   m³ per ha: the season's water divided by the irrigated area.
4. 4
   The season's irrigation hours.
5. 5
   Fertigations: the season's irrigations with fertiliser. Press it to filter them.
6. 6
   Scheduled: today's (or overdue, in amber) and tomorrow's. Press it to see them.
7. 7
   New irrigation opens the form.
8. 8
   The filters: the season, scheduled, done, with fertigation, the last 7 days and all.

Each row is an irrigation:

The search box finds by plot, crop or meter. The footer adds up the irrigations you see, their m³ and their hours (and the water cost, with «See costs»).

#Recording an irrigation

Press New irrigation (or Create in the top bar) and choose the planting: Ceres proposes the plot's irrigation system, the meter from the last irrigation with its reading and the usual flow rate. You only need to enter the hours, or the meter reading at the end: