✨ upCampo Platform Overview

upCampo is a platform specialized in farm operations management, focused on making the field team's routine easier and improving the quality of the information generated for decision-making.

This documentation presents an organized path for using the system, starting with the basic records and moving on to complete operations, dashboards and reports.

The platform is made up of:

• 🌐 Web portal: access through the browser at www.upcampo.com.br (use the login area at the top of the page, which redirects you to portal.upcampo.com.br)
• 📱 Android app: designed for use in the field, available on the Google Play Store, with offline mode support. Download the app on Google Play
• 📱 iOS app (iPhone): also available on the App Store, with the same main features for data collection and execution, also with offline mode support. Download the app on the App Store

📦 Main modules

❓ Frequently asked questions

🌐 Navigating the Portal

Getting into upCampo is a three-stop path: the login screen, the choice of company, farm and season (which the system often skips on its own) and the Home Screen. This article walks through that path and shows how the portal is organized after it.

🔑 The login screen

The portal is at portal.upcampo.com.br; the login area on the www.upcampo.com.br website takes you there. There are two fields and two choices:

• Username or e-mail: either one works.
• Password: the eye icon at the end of the field shows what you typed. Useful on a phone and to avoid getting it wrong again after a password error.
• Idioma/Language: Português, Spanish or English. It applies to the whole system for that session.
• Appearance: Light or Dark.

Then just click Sign in.

🏢 Company, farm and season

upCampo always works within a context: a company, a farm and a season. That context decides which data you see and where your entries go, which is why it is set right at login.

When there is more than one option, the Farm selection screen opens and asks, in order:

1. Select a company: the list shows the trade name and the legal name. The one you pick becomes a green button at the top; the ✕ next to it undoes the choice if you made a mistake.
2. Select a farm: same list, trade name and legal name. If the chosen company has only one farm, it is already selected.
3. Select a season: only appears when there is more than one active season. With just one, the system goes ahead with it.

As soon as all three are set, you land on the Home Screen.

The choice applies to the whole session, on every screen. To switch farm or season, log out and log back in, using the Log out button at the right end of the menu bar.

🏠 The Home Screen

Once you log in, you reach the Home Screen, where you find:

• Dashboards with summaries of activities, yield and indicators
• Handy shortcuts for quick access to the main features
• The list of reports enabled for your user, with a search field

From any screen in the system, the upCampo item (the first one on the menu bar) brings you back to it.

🧭 The menus

At the top of the screen there is a horizontal bar with the "Menu" button. That button shows the platform's main groups of features:

• File: management of companies, farms and users
• Basic: records such as Pests, trap group, tax settings, etc.
• Crops: everything related to crops, for example crop, varieties, fields, season planting, traps, rain gauges and scouting
• Inventory: products, transactions, locations, transfers, stock count
• Operations: work orders, crew, activity type, agronomic prescription
• Fleet: fleet units, fueling, maintenance, plans
• Financial: accounts payable, receivable, cost center, financial reports
• Budget: season projections, comparative scenarios, crop planning
• Reports: data extraction in report format

When you click a menu group, the screens you have permission to access are shown.

🖥️ Screens / forms

Each screen, such as Company, opens a list (grid) with the items already registered. On that screen you can:

• Create a new record: click the "New" button (usually at the top)
• Edit an existing record: click a row in the list to open the details

Inside the form you'll find the Save, Cancel and Delete buttons. If any of them is disabled (grayed out), it means you don't have permission for that action.

These permissions are controlled by a user in your organization (company) with access to the File > User screen.

❓ Frequently asked questions

🏠 Home Screen: dashboards and shortcuts

The Home Screen is the first thing you see after logging in: a dashboard with twelve tabs showing how the farm is doing today (scouting, rainfall, operations, fleet, checklists, inventory and storage), plus shortcuts to the everyday screens and the list of reports.

It is not a data entry screen: nothing is typed here. It is for looking, filtering and, with one click, going where the work happens.

📍 Location in the system

It is the screen that opens when you log in to the portal. From anywhere in the system, the upCampo item, at the left end of the menu bar, brings you back to it.

🗂 The tabs, one by one

🏷️ Home

The session's identification card: the farm logo (the same one set in the Farm record; without it, the upCampo logo appears), the farm name, the selected season and the Log out button. If the numbers on any dashboard look odd, this is where you check, in two seconds, whether the farm and season are the ones you expect.

🔗 Shortcuts

Colored buttons grouped by crop stage: Tillage (Plowing, Harrowing, Subsoiling, Chiseling, Ratoon removal), Fertilization (Broadcast, Pneumatic, By fertigation, By spraying), Planting (Season Planting, Planting W.O., Irrigation, Weather & Stations & Rain Gauges), Crop protection (Pesticide application, Pest Scouting) and Harvest (Harvest W.O., Bale tracking, Inbound Load Ticket, Outbound Load Ticket). Below, in gray, the shortcuts for Fleet / Farm Assets (Fleet, Maintenance work order, Requisition, Fueling) and Other (Work Order/Activity, Inventory, Transfer between storage locations, Transaction).

Each button opens the Work Order/Activity screen already filtered by that operation: clicking "Harrowing" takes you to the harrowing list, not to a blank screen.

🎓 Help

Two buttons: General documentation and Request help via WhatsApp, which opens a conversation already addressed to upCampo support.

🐛 Scouting

The board of recent scouting records, with one column per scouting record and, in the rows, field, crop, variety, days after planting and after emergence, growth stage, scout, rainfall over the previous 15 days, the last order generated and what was found (pests, diseases and weeds, each with its value).

• View: Default, Pest x Field or List.
• Show filters: opens the date range and the field selection; after choosing, use Apply filter.
• Show only pests found: checked by default, and it's what keeps the board readable; without it, every monitored pest shows up, including the ones at zero.
• Period: from the last day up to the last ninety days.
• Map and Details, on each column, show where the points were and the point-by-point breakdown.

🪤 Trap

Trap collections on the map or in a table, filtered by season, period, sector and trap group. The table shows group, sector, date and rating.

🌧️ Weather & Stations & Rain Gauges

Rainfall by field, in the most direct way to look at it: the farm map colored by rainfall range, with the legend No rain, Low, Medium and High, and the average in millimeters for the period. You can switch to Chart or Table, filter by period and sector, and turn the field name and sector on the map on or off.

The data comes from the rain gauges entered in the app and from the integrated weather stations.

🚩 Operations

The progress of work orders in the period. At the top, one bar per subtype showing what is Finished and what is Pending, next to the "Fields per day — Overall" chart. Below, a gauge per subtype (with total, finished and pending) and the fields-per-day chart for that operation, which can be viewed By day, By field or by Work Order/Activity.

• Type: All, Tillage & Fertilization, Planting, Pesticide application, Harvest, Irrigation, Agronomic schedule, Other and Manual; the list shows only the activity types enabled for your user.
• Sector, Start date and End date.
• Unit: Hectares or By no. of fields (number of fields).
• Group by: Short ID (Subtype) (the short identification) or Activity type.

🚜 Fleet

Six display modes, chosen at the top: Summary, Type, Consumption, Hours/KM driven, Cost and Hectares worked. All filtered by period and by equipment classification/type.

The Summary shows the fleet cards: total items, how many are fleet units/machines, implements and farm improvements; the percentage with a maintenance plan (with the number of items with and without a plan); the split between preventive and corrective orders; and how much of the maintenance work orders is finished or pending in the period.

📋 Checklist

The completed checklists in the period, as a Chart or Table, filtered by checklist template. The table shows code, date, template, identifier (the license plate or the equipment), the work order generated and the status of the service request, with a Print button on each row.

The New button opens a new checklist to fill in right from here.

📦 Inventory

The balance by storage location and by product class, in a column chart. Filter by sector and by location; when you choose a specific location, the chart opens on that location's details. The Refresh button reloads the numbers.

⚖️ Storage

One block per stored product, with Current balance, To ship and Available; available is what is left after subtracting what is already committed under contract. The pie chart shows that split, and next to it is the list of contracts, which can be filtered by Sale, Purchase or All.

At the top: unit (Bags (60 Kg) or Kilo (Kg)), season and storage location; the latter accepts more than one location at a time.

📑 Reports

All the reports enabled for you, grouped by topic (Crops, Weather, Scouting, Operations, Inventory, Costs, Fleet…) in collapsible sections. Each button shows the code and name (EST.01.01 (formerly 012) - Local X Estoque (Saldo atual), for example; the code tells you the report's area and subject; see how the code is built) and opens the parameters window to run it.

At the top there is the Search field: start typing the code or part of the name and the report appears, without opening topic by topic. This list is managed on the File > Report screen.

How to fill in the filters, what changes between the three output types and how to export to Excel is covered in the Reports Quick Guide.

🚪 Which tab each user lands on

The tab that opens at login is set per user and per farm, in the Default home screen field of File > Users. Someone who works with spraying can land straight on Operations; someone who handles storage, on Storage.

Today the options that lead to the matching tab are Home, Weather Dashboard, Operations Dashboard, Fleet Dashboard and Storage Dashboard. With Default or Schedule, the screen opens on Shortcuts. The other options open on Home; either way, every tab is still one click away.

❓ Frequently asked questions

🔰 Getting started: the upCampo Base Structure

To use the upCampo platform correctly, it is essential to start by creating the base structure. This structure organizes the data and ensures that all future information (such as work orders, product usage, scouting and harvests) is correctly linked to each season.

1. 🏢 Company and Branches

• Company: represents the main grouping of the operation.
  This is in the File > Company menu.
• Branches (Farms): the company's production units. Each branch can have its own separate areas, inventories, crews and operations.
  This is in the File > Farm menu.

2. 👥 Users

• Register the users who will have access to the system and set their permissions.
• A user can have access to one or several farms, as needed.
  This is in the File > Users menu.

3. 🌱 Setting up the Crop Structure

After the administrative structure, start registering the crop elements:

• Season: represents the crop cycle (e.g., Season 2024/2025).
  This is in the Crops > Season menu.
• Crop: which crops your farm grows (e.g., soybean, corn, cotton).
  This is in the Crops > Crop menu.
• Variety: the specific cultivars of each crop (e.g., BRS 1010). It can be registered later, as needed.
  This is in the Crops > Variety menu.
• Field: subdivisions of the farm, usually used as management units. Each field belongs to a single farm (branch).
  This is in the Crops > Field menu.

4. 🌾 Season Planting

This is the central record of the operation. There is a dedicated article for this screen here.

In Season Planting, you will:

• Link the Field to a Season, a Crop and one or more Varieties
• Enter the planted area and other characteristics of this planting
• Define how data will be split by variety, if applicable

This is the central foundation of the platform. Everything else builds on it.

❓ Frequently asked questions

🗄️ Quick Guide - File (structure and setup)

The File menu is the foundation of the system: it's where you define who the company is, which farms it has, who logs in, what each person can do and how upCampo behaves for that group. Almost everything here is set during implementation and reviewed only a few times a year, but every change affects everyone's routine.

This menu also holds the support screens that don't belong to any specific module: the file center, the contact book, notifications and the two integration screens.

📍 Location in the system

Menu: File

🏗️ The implementation order

If you are setting up the system from scratch, follow this sequence; each step depends on the previous one:

1. Company

The company is the owning group, the top of everything. Each company has its own records, and nothing from one appears in another. Only the legal name is required.

2. Farm

Inside the company are the farms, where the operation actually happens. Besides the address, two fields pay off: Latitude and Longitude, which center the dashboard maps, and the logo, which appears in report headers. A farm cannot move to another company once saved.

3. Tax settings

Only for those who issue invoices through the system. The tax settings hold the CNPJ (Brazilian company tax ID), the state registration, the A1 digital certificate and the e-mail server that sends the invoice to the recipient. The same farm can have more than one. Keep an eye on the certificate expiration column.

4. Users

In Users you create who logs in and define, screen by screen, what each person can view, add, edit and delete. The time-saving shortcut is to apply one of the ready-made profiles (agronomist, applicator or manager) or to copy the access of someone already set up. Remember: access is per farm.

To change a user (e-mail, password, phone), select the person in the list and click User details. Opening the registration tab directly brings up an empty form, which creates a new user when saved.

5. Company/Crop Settings

Finally, the Company/Crop Settings, which decide how the system behaves: whether the work order requires a storage location, how products leave inventory (average cost or last cost), the name fields are given on the screens, what the scout measures in each crop and which reports are sent by e-mail automatically.

⚖️ Company setting or user setting?

Several options exist in both places (requiring a storage location on the work order, for example). The rule to keep it straight:

• Does it apply to everyone? Company/Crop Settings
• Does it apply to just one person? The General settings tab of the Users screen

When a behavior shows up for just one person, it's almost always a user setting. When it shows up for everyone, it's a company setting.

🧰 The support screens

Access log

The farm's usage trail: who logged in, when and what they did (opening each screen, report run, spreadsheet exported, import). In Access log you search by period, with a search on each column and export to Excel. It's the screen that answers security questionnaires and audit requests without opening a support ticket.

Report

The catalog of the company's reports, with the code the Help Center cites in its articles (CLI.01.03, EST.01.09: area, subject and position; see how the code is built). In Report you remove a report from the menu, organize topics and clone an existing report to customize it without breaking the original.

File Center

All of the company's attachments in a single list, with the Source column telling which screen each one came from. It also accepts standalone files. See File Center.

Contact and Notification

Contact is the address book: phone numbers, e-mails and WhatsApp groups. Notification is the sending itself, with the delivery and read status of each message. To reach the whole team, register a contact of the WhatsApp Group type.

The two integration screens

They only matter if you exchange data with another system:

• From X to - Integration: the dictionary that translates the external name into the upCampo record. It's what makes spreadsheet imports stop flagging "field not found".
• Integration issues: the list of what didn't come in, with the equipment and field check already done.

❓ Frequently asked questions

📘 Screen: Company

The company is the top of the structure in upCampo: it's the group that brings the farms together. "Agropecuária Santa Clara", "Fazendas Reunidas Boa Esperança", "Grupo Rio do Peixe": each of these is a company, and inside it are the farms/branches where the operation actually happens. Even someone with just one farm also has a company: it's what ties the records together.

Almost everything in the system is separated by company: products, fields, seasons, users, reports. Switching companies is switching worlds: nothing from one appears in the other.

📍 Location in the system

Menu: File > Company

🧩 Main function

Register and maintain the owning group (legal name, address and contact), which is the level above the farms. It's a record you set up once, during implementation, and rarely come back to.

📝 Main fields

The list shows Legal name, Trade name, City and Active, with a search field on each column.

🔒 What the screen won't let you do

You can't delete the company you are logged into. To take a company out of use without deleting anything (the recommended way), uncheck Active.

🏗️ Where the company fits in

The implementation order is always the same:

1. Company: the group (this screen)
2. Farm/Branch: each unit, with or without its own CNPJ
3. Tax settings: only if the farm issues invoices
4. Users: who logs in and what each person sees
5. Company/Crop Settings: how the system behaves for that group

❓ Frequently asked questions

📘 Screen: Farm/Branch

The farm is where the operation happens: fields, seasons, inventory, fleet and work orders all depend on it. "Fazenda São Camilo", "Complexo São Pedro", "Syngenta MT": each property or unit becomes a farm within the company.

In the system, farm and branch are the same thing. The double name exists because the unit is both the rural property and the tax and financial level: when you log in to upCampo, you choose the company and then the farm, and that pair decides everything you'll see from then on.

📍 Location in the system

Menu: File > Farm

🧩 Main function

Register each unit in the group, with address, coordinates, time zone and logo, and (on the Tax settings tab) the details of whoever issues invoices for it.

📝 Main fields

The list shows Code, Legal name/Name, Active and Trade name, with a search on each column.

🗂 Tax settings tab

Inside the farm record there is the Tax settings tab, with the list of settings already registered for that unit and the form to add another. It's the same content as the Tax settings screen in the menu; the difference is that here you see the settings for the farm that is open, while from the menu you see those of the farm you're logged into.

Watch out: the farm must be saved before you save the tax setting. If you try to save both at once, the system warns you.

🔒 What the screen won't let you do

• Delete the farm you are logged into
• Change the company of a farm that has already been saved

To take a unit out of use, uncheck Active; the history can still be consulted.

❓ Frequently asked questions

📘 Screen: Tax settings

The tax setting is who signs the invoice: the CNPJ, the state registration, the address and the digital certificate that will be used for issuing. A farm can have more than one; a common case is a property that sometimes issues under the company's CNPJ (Brazilian company tax ID) and sometimes under the grower's CPF (individual taxpayer ID), or a group with different state registrations in the same unit.

A farm that doesn't issue invoices through the system doesn't need to fill in this screen for that. But a CPF tax setting has a second role: it represents the grower in the tax cash book. That's why the CPF one has the Exploited properties tab, explained further below.

📍 Location in the system

Menu: File > Tax settings

The same content appears on the Tax settings tab inside the Farm record. From the menu, you see the settings of the farm you're logged into; from the tab, those of the farm open in the list.

🧩 Main function

Store the issuer's details and the A1 digital certificate, so that NFE Transmission and the MDF-E have what they need to sign and transmit the document.

📝 Main fields

📥 Manifestation type

When you import an invoice by its access key, in Transaction, SEFAZ doesn't always return the full document. In many cases it returns only a summary (number, amount, issuer) and holds the full XML until the recipient makes a manifestation about that transaction. The manifestation is that reply: the recipient telling the tax authority what it knows about the invoice.

The Manifestation type field defines, once and for all, what upCampo replies in these cases:

🔐 Certificate

The Certificate block holds the file and the passwords:

When you save a setting that has a certificate, the system validates the certificate before saving. If the password is wrong, the file has expired or there is no valid certificate inside it, the save doesn't go through and the message tells you which of the three it is.

In the list, the Certificate expiration date column shows the expiration of each setting; that's where you find out, without opening anything, that the farm's certificate expires next month.

✉️ E-mail settings

The E-mail settings block is the outgoing server used to send the issued invoice to the recipient: the message Subject and Text, HOST, PORT, User, Password and the AUTH, TSLS and SSL options. The E-mail test button asks for a recipient and sends a test message; use it after any change, instead of finding the error when sending a real invoice.

🏞 Tab: Exploited properties

This is where you state how this grower operates each rural property: whether the land is theirs, leased, worked in partnership or joint ownership, and with what percentage. It's the basis for the allocation in the tax cash book and in the LCDPR (Brazil's Digital Rural Producer Cash Book). The property itself (name, CIB, CAR, registrations) is registered once in File > Rural property; here you only link the grower to it.

The exploitation fields

The same property can appear more than once for the same grower, with different types: part of the land owned and part leased, for example.

Participants

The other CPFs or CNPJs that share the exploitation, each with Participant type, CPF/CNPJ, Name and Percentage. The types are 1 - Co-owner, 2 - Lessor, 3 - Partner, 4 - Lender, 5 - Other and Spouse. The tab shows the Declarant + participants total, so you can check that it adds up to 100%.

The rules upCampo checks when saving:

• Individual: the declarant has 100% and there are no participants.
• The other types (or a declarant percentage below 100%) need at least one participant, and declarant + participants must add up to 100%.
• Lessor and lender get 0%: they lend or rent out the land, but don't share in the result of the activity, so they don't count toward the 100%.
• Spouse: only one per exploitation, with a CPF, and only in 50/50 or 100/0 splits (declarant/spouse).
• The declarant themselves isn't entered as a participant.

The cash book grower is the tax setting

There is no "Growers" screen in upCampo. For the tax cash book and the LCDPR, the grower is the individual (CPF) tax setting: it supplies the name, CPF and address that go into the file, which is why LCDPR generation requires a complete address, number, district, state, municipality, ZIP code and e-mail here.

• The same CPF can have a tax setting at each farm. In the cash book, it appears only once: the book belongs to the CPF, not to the farm.
• A joint-ownership or partnership participant doesn't need their own tax setting. It's enough to be registered as a participant, with more than 0%, in another grower's exploitation: they appear in the cash book and receive their share of each of the holder's titles.
• If each co-owner issues their own invoices, register each one's exploitation as individual, in each one's tax setting. Then every title belongs only to whoever issued it, and there is nothing to split.

⚠️ The farm must be saved

A tax setting belongs to a farm. If you create the farm and try to save the setting without saving the record first, the system warns that "the farm must be saved". Save the farm first, then the setting.

❓ Frequently asked questions

📘 Screen: Rural property

The rural property is the land the grower operates, registered just once in upCampo: Fazenda Santa Rita, with its CIB, CAR number, area and registry office deed registrations. It's the basis for the tax cash book and the LCDPR (Brazil's Digital Rural Producer Cash Book): it's how upCampo knows on which property each payment took place and, when the land is operated in partnership or joint ownership, how much of each amount belongs to each grower.

This screen stores only the land. Who operates the property, in what form (owned, leased, partnership…) and with what percentage is kept on the Exploited properties tab of each grower's Tax settings. The separation is intentional: the same land can be owned by one grower and leased by another.

📍 Location in the system

Menu: File > Rural property

It comes right after Tax settings, where the exploited properties that use this record are. The screen has its own permission: it only appears in the menu for those who have been granted access in File > Users.

🧩 Main function

Register the company's rural properties, with the deed registrations of each one. One rule decides how many properties to register:

📝 Main fields

The list shows Name, CIB, City, Area (ha), the number of Registrations and Exploitations linked to the property, and whether it's active.

🗂 Tab: Registrations

Each registry office deed registration that makes up the property: Registration (the number, required), Registry office and Area (ha) of that registration.

The area and the registrations

Below the list you'll see the Sum of registrations. As long as nobody types a different area over it, the property's Area (ha) follows that sum: add, change or delete a registration, and the area adjusts. If you type a different area (because the current survey doesn't match the deeds, for example), it stops following the sum and keeps the value you entered. The Use the sum as area button sets the area back to the sum of the registrations.

🗑 Delete or deactivate

A property that is already used in an exploitation in Tax settings can't be deleted; upCampo warns "This property is used in an exploitation in the Tax configuration and cannot be deleted. Deactivate it." Uncheck Active instead of deleting. Deleting only makes sense for a property registered by mistake, and it takes its registrations with it.

❓ Frequently asked questions

📘 Screen: Users

This is where you create the people who log in to upCampo and define what each one sees and can do: the technician who only enters scouting from a phone, the warehouse clerk who receives products, the manager who approves work orders, the consultant who only looks at reports. The screen is called User Settings/Access Control and does both things at once: the person's record and their permission on that farm.

The point that confuses people at first: there is only one user, but access is per farm. The same login can exist on three farms of the group with different permissions on each one.

📍 Location in the system

Menu: File > Users

🧩 Main function

Register the people who use the web portal and the app, grant screen by screen what each one can view, add, edit and delete, choose which reports they see and adjust their work preferences.

🧭 How the screen is organized

The screen is a staircase: you go down one step at a time:

1. Select a company, in the list at the top
2. Select a farm, which appears next
3. On the Users tab, click the person's row
4. With the user selected, the Access Control, Reports and General Settings tabs open below

Until the company, farm and user are chosen, the tabs below stay hidden: it is not a bug, it is the screen's sequence.

👤 Users tab: the list

Shows who has access to that farm, with Name, First Name, E-mail, Login, Phone, Sectors, Active, the Disable button and Reference/Integration ID. Each column has a search box.

📝 User Registration tab

This tab is where the person's data is entered, and it behaves in two ways, depending on the button that opened it:

• Opened with Show user details, it comes with the record loaded: whatever you change and save changes that person.
• Opened with New user, or by clicking the tab directly, it comes empty: whatever you save creates a new person.

When in doubt, look at the Full Name field before typing: if it is blank, you are creating someone.

The buttons on the tab are Save/Add, Cancel, Delete User and Import Users; the last one brings users marked as Public, to copy from a ready-made template.

🔐 Access Control tab

It is the list of every screen in the system, grouped by menu (File, Basic, Crop, Inventory…), with four checkboxes per row: View, Add, Edit and Delete. Unchecking View for a screen makes the item disappear from that person's menu.

Checking one by one is rarely needed: the toolbar has shortcuts:

📊 Reports tab

Lists the company's reports with Code, Description, Show (opens the report right away, so you can check what it is), Theme and the Allow checkbox. Only the checked ones appear in that user's reports menu.

The Copy report access button repeats, for the current user, another user's report permissions.

⚙️ General Settings tab

Careful not to mix them up: these are the settings for that user on that farm. The ones that apply to the whole group are in Company/Crop Settings. After changing anything here, click Save General Settings.

🚪 Disable, remove from the farm or delete?

• Disable: the person left the group. Blocks access on all farms and keeps the history.
• Remove User from Farm: the person moved to another unit. Loses access only to this farm and keeps the others.
• Delete User: deletes the record. It only makes sense for a user created by mistake who has not entered anything yet.

❓ Frequently asked questions

📘 Screen: Access log

The access log is the usage trail of the upCampo web portal: every time someone opens a screen, runs a report, exports a spreadsheet or imports a file, the system records a line with the date and time, the name of who did it, the screen and the action. This screen is where the farm looks up and exports that trail, without having to ask support for anything.

It is read-only: it does not create, change or delete anything. What it shows is always for the company and farm selected at the top of the system, for the period you choose.

📍 Location in the system

Menu: File > Access log

🧩 Main function

Answer three audit questions with evidence in hand: who logged in to the farm's system, when and what they did. It is also the practical answer to security questionnaires and data protection requirements (such as Brazil's LGPD) that ask for "access logs and recorded events": the farm itself looks them up and exports them.

📝 Main fields

The bar at the top of the screen builds the query. Next to the title is the count, N record(s), which follows the filters.

📋 The list columns

All columns can be sorted by the header and resized. Below the header there is a search box in Date, User, Screen, Action and Notes: it filters what is already on screen, instantly, without querying the system again; it is the quick way to isolate a person or a screen within the period. The Success column has no search box; for it, use sorting.

⏱ The record does not appear right away

Actions are accumulated and saved from time to time, usually within 15 minutes. This is on purpose: saving every click right away would make the system slower for everyone.

🔍 What goes into the trail, and what does not

Included: opening each screen, running each report (with the report's name), exports to Excel, spreadsheet imports, finalizations, approvals and rejections made through a link, logging out of the system and the access reason.

The content of the change is not included. The trail records that the person was on the screen and which action they performed; it does not store that a product's price went from one value to another. To find out who created or changed a specific record, look at the record itself, which stores the user who created it and the user who changed it.

✍️ Markers that appear in Notes

• ACESSO VIA <name> (access via): the action was done by someone who logged in to the system as another user, a feature used by the administrator and by support to reproduce a problem. The line is under the name of the assumed user, and the marker tells who actually was operating.
• ACESSO LOCAL (local access): the action came from a run outside the production server, a work situation of the upCampo team.
• Access reason: on farms that require a reason for access, the text written by the person is stored here, in the action of the same name. The requirement is turned on with two checkboxes: in the farm record and in the record of each user you want to require it from.

🚨 Security alerts in the list

Besides what people do, the list may include lines generated by upCampo's automatic monitoring. They appear with the screen MonitorSeguranca, the action Alerta de seguranca and Success = No, and the alert text is in Notes; for example, an access made from an unusual country, with city, user and IP. The same alert is not repeated within one hour, so it does not flood the list.

The monitoring follows other signals that are not tied to a farm, such as sequences of wrong password attempts, and those are handled by the upCampo team. The whole set is described in Information security in upCampo.

📤 Export to Excel

The Export to Excel button sends to the spreadsheet exactly what is in the list: the period queried, with the column filters already applied. They are the same six columns: Date, User, Screen, Action, Notes and Success.

The system opens the File ready window, with the number of records and the Click here to download button; the file is named upCampo_log_acessos_<data>_<hora>.xlsx. With an empty list, nothing is generated and the system warns "No records found for the selected period.".

This is the spreadsheet you attach to a security questionnaire, an internal investigation or an audit request.

🔑 Who can see this screen

The menu item only appears for those with view permission on it, granted per farm on the Access Control tab of the Users screen. There is only view: the screen does not add, edit or delete, so there is nothing else to grant.

When the feature was delivered, the permission was given to those who already saw the Users screen: whoever manages the farm's access is usually the one who needs to audit it.

❓ Frequently asked questions

📘 Screen: Company/Crop Settings

This is the screen that decides how upCampo behaves in that company: whether the work order requires a storage location, whether fueling asks for the hour meter, whether the field is called "field" or "block", how many decimal places a hectare has, which measurements the technician takes in each crop and which reports go out by e-mail every morning.

When an article in this Help Center says a behavior "depends on the company settings", this is what it is talking about. It is a setup screen: it is changed rarely, but each checkbox changes the routine of everyone.

📍 Location in the system

Menu: File > Company/Crop Settings

At the top of the screen you choose a company and a farm before anything else: that pair defines whose settings you are looking at.

🧩 Main function

Adjust how the web portal and the app behave for the company, set up what is measured in each crop during scouting and schedule automatic report delivery by e-mail.

🗂 The three tabs

• General company settings: how the system behaves, in blocks
• Crop Settings: what is measured in each crop
• Automatic sending: reports and alerts by e-mail

⚙️ General company settings tab

The settings come in blocks that open and close. After making changes, click Save: it applies to the whole screen, not per block.

Pest Scouting

The first three fields are about vocabulary: Display name for 'Quadra', for 'Variedade' and for 'Setor' change the name shown on the screens and in the app. If the farm says "block", type "Block" there and the system starts talking the way the farm does.

In the same block: Dynamic mode when adding pests, Manual Point (APP), Show pest scientific name (APP), Show point opening (APP), Show disabled fields (APP), Do not send data automatically in the APP and Observation updates last scouting date; the last one makes an observation count as a visit, for the purpose of the field's last scouting date.

Crop & Fields

• Allow multiple active seasons: for those who have the main season and the second crop running at the same time
• Show grouping column: shows the Grouping field on the Field screen
• Allow changing Bale during collection
• Decimal places for Ha: how many decimals the area carries in calculations and on screens
• Generate fallow automatically when finishing season planting and the Fallow Crop to be used in that case

Stations & Rain Gauges

The ranges for Low, medium and high rain level, in millimeters. You type only the start of each range: the To field of each one is filled in automatically from the start of the next range. This is what colors the rain gauge on the dashboards.

Operations

The largest block on the screen, divided into six:

Other blocks

Two fields may appear without a translation, showing the internal key instead of the name (!pt: bloquear_totan, in the W.O. Inventory block, and !pt: relatorio_padrao_coliteras, in Default reports, which is the default report for bale collection). It is a label issue, not a functional one: if you do not use these features, ignore them.

🌱 Crop Settings tab

This is where you define what the technician measures in the field, per crop. On the left, the list of the company's crops (Code and Description); choose one and the form appears on the right. Each crop has its own settings: soybeans do not need the same measurements as cotton.

At the top: Default plants/meter, Manual point and Show 'Number of plants' field for phenology. Below comes the list of measurements, each one with a checkbox to turn it on:

Height · Number of Nodes · Distance between Nodes · STAND · Number of Stems · Number of Pods · First Pod Height · Grains per Pod · No. of squares · No. of Small Bolls · No. of Medium Bolls · No. of Large Bolls · Ht. 1st to 5th node · No. of Bolls Pos. 1 to 5 · Rotten Boll · Open boll · Plants/meter · No. of Bolls · Boll weevil.

Once a measurement is on, its settings open, always the same ones:

When you are done with the crop, click Save Crop Settings. The button saves the crop that is open: each one is saved separately.

📧 Automatic sending tab

This is e-mail scheduling: the rain report that reaches the manager at 7 a.m., the list of work orders by sector that goes out every morning, the alert for fields without scouting. The list at the top shows what is already scheduled, with Type, Category, Subject, Report, Hour, Minute, E-mails, Active and Last immediate send date.

The buttons are Save, Cancel, Delete, New and Clear last sending; the last one resets the last-sending marker, so that the next run sends everything again (useful when the e-mail got lost or the only new records option blocked the sending).

❓ Frequently asked questions

📘 Screen: Report

This is the screen where the system's reports are registered and organized, not where they are run. Each row here is one of the reports that appear in the Reports menu: CLI.01.03 - Controle Pluviométrico - Geral, EST.01.09 - Dashboard Visão Geral Local x Estoque, POS.06.01 - Armazenagem - Extrato. This is where the code the Help Center cites in its articles comes from.

It is a setup screen, usually changed together with the upCampo team. What the farm does often on it is something else: check a report's code, remove it from the menu, change the theme it appears under or request a new report to be installed.

To run a report (filters, output types and export to Excel), see the Reports Quick Guide.

📍 Location in the system

Menu: File > Report

🧩 Main function

Maintain the company's report catalog: the report file, where it appears in the menu, which filters it asks for before running and who can see it.

📝 Main fields

The list shows Code, Old code, Description, Theme, Subject, Format, Type, Company and Active, with search on each column.

How to choose the code for a new report

The New button no longer suggests a number: the code depends on the area and the subject, and only the person registering knows which they are. The way to do it:

1. Area: the one for the menu where the report's source screen is (load ticket → POS, work order → OPE).
2. Subject: one the area already has. A new subject only if none fits, and it goes at the end of the area.
3. Number: the next free one in the subject. A report customized for one farm uses the next free P for that farm.
4. Also fill in Subject and Format.

A report that already existed and still has an old code keeps saving normally; the rule applies to new ones.

🔘 Buttons

Clone and Set as default company require the report to be saved already.

🗂 Filters and Queries tabs

These are the two tabs that make the report ask questions before running and fetch the data.

Filters is the list of questions that appear before running: season, period, field, technician. Each filter has a Name, Order, Type, whether it is Required, whether it Shows search, whether it accepts only one value, the Default value and the query that feeds the list of options.

Queries holds the queries the report runs, with Name, Order and Active.

Both tabs are technical territory: changing them without knowing the database structure breaks the report for everyone in the company. Ask the upCampo team and, if you want to experiment, do it in a Clone, never in the original.

👀 Who sees each report

Being registered here is not enough for a user to see the report: permission per person is on the Reports tab of the Users screen, where you check Allow report by report. And the report sent automatically by e-mail is chosen on the Automatic sending tab of Company/Crop Settings.

❓ Frequently asked questions

📘 Screen: Mapping - Integration

The mapping is the translation dictionary between the name that comes from outside and the upCampo record. The external system calls the field TH-014; in upCampo it is Talhão 14 - Boa Vista. The scale's spreadsheet brings the variety as M8210; in the record it is M 8210 IPRO. Without this translation, every import stops at "not found"; with it, the system finds the match on its own.

It is a behind-the-scenes screen: it is used by whoever handles the integration with the ERP, the scale or the technology partner, not by day-to-day crop work.

📍 Location in the system

Menu: File > Mapping - Integration

🧩 Main function

Store, for each upCampo record, the equivalent name and code in the external system, so that data imports find the right record even when the names do not match.

📝 Main fields

The list repeats these columns (Code, upCampo table, upCampo description, upCampo ID, External table, External description, External ID, Supplier and Active), with search on each one.

🔎 Where the translation is used

The most visible case is importing harvest load tickets from a spreadsheet, on the Inbound Load Ticket. When reading the spreadsheet, the system first looks for the field and the variety by the exact name in the record; if it does not find them, it looks in the mapping for an active line whose External description equals the one in the spreadsheet (ignoring upper and lower case) and uses the record that line points to. Only if both searches fail does the line go into the problem list as "not found".

The other translations serve the integrations that use these records. If you do not have an integration in place, this screen stays empty, and that is how it should be.

When the integration is with the Operations Center, it is worth seeing how the upCampo integration with John Deere works.

❓ Frequently asked questions

📘 Screen: Notification

This is how the office talks to people in the field: it sends a WhatsApp message to the operator, tells the technician there is scouting to do, pushes the day's order list to the app. And this is where you see what has already been sent, to whom, and whether the person received and read it.

The screen works both ways: creating the message and tracking what the system sent on its own; the approved order notice, for example, when that notification is turned on in the company settings.

📍 Location in the system

Menu: File > Notification

🧩 Main function

Send a WhatsApp message or an in-app notification to a user, a team or a contact, and track delivery and read status.

📝 Main fields

The list shows Date, Title, Sender user, Recipient, Contact, Status, Delivery date, Read date, Type and Text.

✅ What the screen requires

• Message always: without text, it does not save
• For the Whatsapp type: the phone
• For the Notification type: the recipient user (they are the one with the app)

Once the notification is saved, sending is handled by the messaging service; that is why the status starts at Processing and changes on its own. If the message gets stuck, the number is the first suspect: WhatsApp requires the country code, as in 5561999999999.

❓ Frequently asked questions

📘 Screen: File center

It is the farm's filing cabinet inside the system: the supplier's invoice as a PDF, the photo of the flooded field, the soil analysis spreadsheet, the signed contract, the lab report. Everything that was attached on any upCampo screen appears here in a single list, and you can also upload a stand-alone file that does not belong to any entry.

The benefit is not depending on anyone's computer: whoever has access to the system has access to the document, from anywhere.

📍 Location in the system

Menu: File > File center

The title inside the screen is just File.

🧩 Main function

Gather in one place the company's files (those attached on screens and the stand-alone ones) to look up, download and organize.

📝 Main fields

The list shows Title, Name, Description, Origin, Extension and a view button on each row. The form toolbar has the Download button.

📍 The Origin column

It is the most useful column on the screen. It tells where the file came from: the attachment of a purchase order, an entity, a stock movement, a quotation. A file uploaded directly on this screen, not linked to any entry, appears as Avulso (stand-alone).

👁 Open and download

The row's view button opens the file in another browser tab. Spreadsheets (.xlsx, .xls) open inside the system itself, without downloading. For other formats, the browser decides: PDFs and images open on screen, the rest is downloaded.

❓ Frequently asked questions

📘 Screen: Contact

It is the system's address book: phone numbers, e-mails, WhatsApp numbers and WhatsApp groups that upCampo sends messages to. The "Season Operations 2026" group, the consulting agronomist's WhatsApp, the accounting firm's e-mail: each one becomes a contact, and then you just choose it on the Notification screen.

A contact is not a user. A user logs in to the system; a contact only receives messages. The consultant who follows the crop without using upCampo is a contact.

📍 Location in the system

Menu: File > Contact

🧩 Main function

Store the farm's message destinations (number, e-mail or WhatsApp group) so the system's notices have somewhere to go.

📝 Main fields

The list shows Code, Description, Type, Address and Active, with search on each column.

💬 WhatsApp groups and the Get group ID button

A WhatsApp group is not identified by a number: it has its own identifier, which nobody types from memory. That is why, when you choose the WhatsApp Group type, the Get group ID button appears: it lists the groups the upCampo WhatsApp number has already been added to, and the group you choose fills in the field automatically.

So the order is:

1. Add the upCampo WhatsApp number to the group, from your own phone
2. On this screen, choose the WhatsApp Group type
3. Click Get group ID and select the group in the list
4. Save

Once that is done, the group appears as a destination on the Notification screen: that is how a notice reaches the whole crew at once.

❓ Frequently asked questions

📘 Screen: Integration problems

When the farm exchanges data with an external system (machine telemetry, the manufacturer's platform, an ERP), not everything gets in. An operation arrives from equipment that is not registered, or from a field whose name upCampo does not recognize. Instead of disappearing, these records stop here, with a description of what blocked them.

It is a read-only screen: it shows what got stuck and helps you find out why. The fix is made in the records, or in Mapping - Integration, when the problem is just a different name.

📍 Location in the system

Menu: File > Integration problems

🧩 Main function

List the records the integration could not import and show, for each one, whether the equipment and the field that came from outside exist in upCampo's records.

📋 The list

Shows Sorting, Date, Description (the reason for the problem), Type, Equipment, Variety/Cultivar, Field, Field ID and JD ID, with search on each column. The Reload button refreshes the list.

🔍 Diagnosing the record

When you select a row, the form shows the data as it came from the external system (date, description, equipment, variety, field, the identifiers and the raw content received) and, below a divider line, two check fields:

• Equipment - upCampo: the system looks up the matching fleet by chassis number. If it finds it, it shows "Equipment found!" right below the field; if not, "Equipment not found!"
• Field - upCampo: the same check for the field

That pair of messages shows the way: "not found" means the record is missing in upCampo, or it exists under another name, and in that case the mapping solves it.

The screen changes nothing: there is no save or delete, only Cancel to go back to the list. After fixing the record, the integration itself reprocesses the item.

❓ Frequently asked questions

🧱 Quick Guide - Basic (base records)

The Basic menu gathers the records that the other modules use and that almost never change once set up. They are of two very different kinds, which is why the menu looks like a mix: on one side, the base for pest scouting (class, pest and group); on the other, the tax base for invoices (nature of operation, CFOP, CST and series). In between, the sector, which divides the branch into units.

The good news is that almost everything here is set up only once. After it is built at the start of the contract, you come back to these screens only a few times a year.

📍 Location in the system

Menu: Basic

🐛 The scouting base

1. Pest Class

Start here: the class is the drawer that organizes pests for people in the field ("Caterpillars", "Stink bugs", "Rust", "Broadleaf"), and it is a required field for the pest. Each class has a type (Pests, Diseases, Weeds or Evaluation) and an order, which sets the sequence it appears in on the phone.

2. Pest, weed and diseases

Before registering by hand, use the Import standard pests button on the Pest screen: it brings, from a library maintained by upCampo, pests with scientific name, class and counting method already set. Then adjust what the farm does differently, mainly the selection method in the APP (typed quantity, by sizes or by predefined levels) and the action thresholds per crop.

3. Pest group

If the decision to spray looks at the total of several species together ("defoliating caterpillars", "stink bugs"), set up the group. It adds up the counts into a single number and has its own action thresholds, which are what color the map and trigger the alert e-mail.

4. Trap group

If you work with traps, register the groups in Trap group, which appears both in the Basic menu and in the Crop menu.

🗺️ The sector

The sector divides the branch into units: "Boa Vista", "Nascente", "São João". It does not need to be created here: it is born when someone types a new sector in the Sector field of the Field record, and only then does it appear in this list.

The screen is auxiliary, and you open it for two reasons: to fill in the Grouping, which combines several sectors into a single view, and the Reference/Integration ID, when the farm exchanges data with an external system.

🧾 The invoice tax base

These four records exist so that issuing invoices no longer depends on case-by-case questions. The content is dictated by the property's accountant; the screen only stores what they indicated.

1. Nature of Operation

The phrase printed at the top of the invoice explaining why it exists: "Other outbound", "Sale of the establishment's production". Register it in Nature of Operation, with the NF-e (Brazilian electronic invoice) purpose and whether the invoice is inbound or outbound. The description is limited to 60 characters. It is asked for only in NFE Transmission: the regular Stock Movement screen does not show this field, and a few natures are usually enough.

2. CFOP

The four-digit code that classifies each item on the invoice for the Brazilian tax authorities. Register in CFOP only the ones the farm uses, usually between five and fifteen.

3. CST

The code that tells how each item is taxed, per tax. On the CST screen, first choose the tax in the ICMS / PIS / COFINS / IPI selector and only then click New: it is the selector that defines which tax the code belongs to.

4. Series

The invoice numbering sequence. Register in Series the series the branch uses, with the Last number field that prevents repeated invoices or gaps in the sequence.

🔗 Screens the Basic menu shares with other modules

• Trap group: also in the Crop menu, and documented under Pest Monitoring
• Active ingredient: documented under Inventory, which is where it is used in the product record

❓ Frequently asked questions

📘 Screen: Sector

The sector groups the farm's areas together — "Boa Vista", "Nascente", "São João", "Entre Rios". In practice, sectors are created by the Field record: when someone types a new sector in the field's Sector field, it starts to exist and shows up in this list on its own.

That is why this is an auxiliary screen, not the starting point. You come here for two reasons: to say which group each sector belongs to, and to enter the Reference/Integration ID when the farm exchanges data with an external system. Day to day, the New button is almost never used.

📍 Location in the system

Menu: Basic > Sector

🧩 Main function

Complete the information on sectors that were already created from the field records — the group and the integration code —, and let you deactivate a sector that is no longer in use.

🌱 Where sectors come from

From the field. In the Field record, the Sector field accepts a new value typed on the spot, and that is how the farm builds up its internal division: each field gets the name of the unit it belongs to. The list shown there combines the sectors already used in fields with the ones that exist in this record, so both sides always see the same set.

The practical consequence is that if a sector is spelled two ways in the fields ("Boa Vista" and "BOA VISTA"), it becomes two sectors. Standardizing the spelling in the field is what prevents a duplicated list here.

📝 Main fields

The list shows Code, Description, Group, Zoom, Latitude, Longitude, Active and Reference/Integration ID, with search on each column.

🧾 Where the sector shows up

Besides the crop sector filters — which read the sector saved on the field —, the sectors in this record feed the Sector field in the header of Inventory Movement (Inbound & Outbound). That field only appears on the screen when at least one sector is registered.

❓ Frequently asked questions

📘 Screen: Pest Class

The class is the "drawer" where each pest is kept: Caterpillars, Mites, Beetles, Fungi, Bacteria, Viruses, Nematodes, Broadleaf Weeds, Grass Weeds. Instead of working with a loose list of sixty items, scouting works by class — and the class is what organizes the choice in the field app, the order in which items appear and how the results are read afterwards.

It is the first scouting record: without a class you cannot register a pest, because the class is a required field of Pest.

📍 Location in the system

Menu: Basic > Pest Class

🧩 Main function

Group pests, diseases, weeds and assessments into categories, defining the order in which they appear to the person in the field.

📝 Main fields

The list shows Code, Description, Type, Order and Active, with search on each column.

🧭 How to divide the classes

A good division is the one the crop scout already has in mind. A well-built base usually looks something like this: Caterpillars, Beetles, Mites and Others on the pest side; Fungi, Bacteria, Viruses and Nematodes on the disease side; Broadleaf Weeds and Grass Weeds for weeds.

Notice they are few and obvious. A "Pests" class with thirty items inside, or fifteen classes with two pests each, get in the way just the same. If scouting is slow because the crop scout scrolls through the list looking for the item, it is almost always the classes that are poorly divided.

This is also the place for things that are not crop enemies but are measured at the point — such as a class like Detailed Cotton Phenology, used to record the plant's growth stage along with the rest of the scouting.

❓ Frequently asked questions

📘 Screen: Pests, weeds and diseases

This is the record of what the crop scout will monitor in the field: bollworm, two-spotted spider mite, alternaria, volunteer cotton — and also measurements that are no enemy at all, such as plant height and stand. Each item registered here becomes a line in the scouting done in the field app.

It is the most complete screen in the Basic menu, because it does not just define the name: it defines how each target is measured — and there are many ways to measure. Per plant, per meter, per leaf, per fruit, per square meter: this is where you choose which one applies to each pest, whether the count is split by size, which ready-made options the scout sees on the phone and, above all, from what number that count stops being normal.

📍 Location in the system

Menu: Basic > Pests, weeds and diseases

🧩 Main function

Register pests, diseases, weeds and assessments, defining how each one is counted and the control levels that color the map and trigger the alert.

📥 Start by importing the standard pests

Before registering anything by hand, use the Import standard pests button, above the list. It opens a pest library maintained by the upCampo team — already with scientific name, class and counting method — and brings into your company the ones you check. There is a filter by type (All, Pests, Diseases, Weed, Assessment) to find them faster.

This is the recommended path: the imported pest comes already configured in a way that works, and you only adjust what your farm does differently.

📝 Main fields

Next to Allow decimals are Has Sizes and Predefined levels. They are grayed out on purpose: they are not fields to check, but indicators that the screen itself turns on according to the selection method set right below.

🎚 Selection method in the APP

This is the most important decision in the record, because it changes what the crop scout sees on the phone. There are three paths, and each one unlocks a different tab:

• No sizes or levels — the scout types the quantity found. No extra tab
• By sizes — the count is split by instar. Unlocks the Size tab
• By predefined levels — the scout picks a ready-made option instead of typing. Unlocks the Predefined levels tab

Size is the instar — the pest's development stage. Each size becomes its own field at the point, and the scout records how many were found at each stage. Egg, Small, Medium and Large are one possible example: how many stages to separate, and what to call them, is your decision, pest by pest. Use it when the decision to spray depends on the instar, not just on how many there are.

A predefined level is a ready-made scale — Low, Medium, High is the most common case. On the phone the options become single-choice buttons, in the order registered, and the number field disappears. Use it when an exact count makes no sense and does not help, as in disease assessment by visual scale.

The two paths can be combined: a size can have its own predefined levels (that is the Yes = choose levels selector on the Size tab). When that happens, the levels of that size apply, and not those of the pest.

🧮 How the count at the point becomes the field's number

The crop scout records pest by pest at each point along the walk. What turns those separate entries into a single number for the field is the calculation method. Two pieces of scouting information go into almost every calculation: the number of points walked and the quantity assessed per point (how many plants, how many meters) entered by the scout in the app.

The summary is closed per day and per season planting, not per scout: if two people walked the same field on the same date, both people's points go into the same calculation. Along with the result, the system stores the value from the previous scouting, and that is where the comparison from one date to the next comes from.

The Size tab has its own Calculation method field, for when one instar needs to be treated differently from the rest of the pest.

With predefined levels the calculation is different: it is a percentage of points. The system counts how many points chose each option and divides by the total number of points. In a scouting with 10 points where 2 were marked as Low, the summary shows Low = 20% — and the other options show their own percentages, adding up to 100% across all the ones used. That is why this format answers "how much of the field is in situation X", while the numeric count answers "how much is there".

🗂 Additional tabs

📊 Size

Only makes sense when the selection method is "By sizes". Each line is an instar — a development stage of the pest. Egg, Small, Medium and Large are an example; the farm decides how many stages to separate and what to call them. Each line has Name, Order (the sequence in which it appears on the phone), its own Calculation method and Active. The list shows Name/Description, Order, Active and Levels.

A No = typed value / Yes = choose levels selector decides whether that size is typed or picked from a list. Choosing Yes opens a second block right below to build the options for that size, with Name, Order, Value and Active — for example, the "Egg" size offering only "Present", with value 1.

The tab's toolbar has Save Size, Cancel, Delete, Delete all sizes, Import (copies the sizes already built for another pest, so you don't redo the same setup), Deactivate All and Formula, which opens the "Formula builder" window to build a calculation combining the sizes.

The Advanced menu checkbox, on the same toolbar, reveals the fine-tuning fields: Default value, Number of repetitions, Formula (optional) and its Translated version, Maximum value, Abbreviation, plus the checkboxes Show in field detail (app), Calculate entry automatically, Keep last value, Required, Hide in summary (dashboard and app) and Hide in entry.

📉 Predefined levels

Only makes sense when the selection method is "By predefined levels" — Low, Medium, High is the most common example. Each line is an option that the crop scout sees on the phone as a single-choice button, with Name, Order (the sequence in which the buttons appear), Value (the number stored behind the option) and Active. The toolbar has Save, Cancel, Delete, Import and Delete all.

The summary for this kind of pest is a percentage of points: each point marks an option, and the system shows how much of the walk fell into each one. Ten points with two marked as Low become Low = 20%. That is why it pays to keep few, clearly separated options — a long list dilutes the percentage and does not help you decide.

📈 Control Levels

This is the most important tab on the screen — and what separates scouting that turns into a decision from scouting that turns into a spreadsheet. The control level is the number from which the pest stops being a presence and becomes a problem: the threshold that research and consultants set for that crop, at that growth stage, for that insect size.

Without it, the system shows "8 caterpillars per meter" and each person reads it differently. With it, the system itself classifies: 8 is High. The agronomist doesn't need to remember the threshold for each pest at each crop stage by heart — the whole farm uses the same criterion, including whoever just joined the team.

The tab itself says what they are for: they are the "control levels for dashboard display, map legend and emails". In practice, what you see today is the scouting dashboard: at the pest × field intersection, the result is highlighted in the color of the range it fell into, and that is what makes anything over the threshold jump out — without anyone interpreting numbers by hand. The dashboard map shows the collected points; the field itself is not filled in by control level.

Each range is registered with:

• Crop — required; it is what loads the list of growth stages
• Scouting type — Plant, M2 or Both
• Size — when the pest is counted by size, the range applies to one specific size
• Start stage (from) and End stage (to) — required, and chosen from the crop's growth stages: PP - Pre-planting to R8 - Full maturity in soybean, V0 to C30 in cotton. The stage compared is the one the scout entered when opening the scouting — it applies to all pests that day; the stage is not chosen pest by pest
• Description — the situation the range represents: Low, Medium or High
• From and To — the count range. In the list the columns appear as From (=<) and To (>): the From value belongs to the range, the To value already belongs to the next range. That is why the ranges sit right against each other with no number left between them — 0 to 2, 2 to 5, 5 to 100

In practice there are three lines per combination, each one touching the next. In cotton, for the "Small" size between V0 and C30: Low from 0 to 2, Medium from 2 to 5, High from 5 to 100 — and the same trio repeated for the "Large" size. The last "To" is usually a very high number (100) precisely so that no count falls outside the last range.

It takes work because the same pest's tolerance changes as the crop grows: ten caterpillars in newly emerged cotton don't carry the same weight as ten caterpillars once bolls are formed. That is why the range is registered by growth stage, and why it pays to register at least the targets the farm actually tracks, instead of trying to cover everything at once.

The numbers don't come from the system: they come from the technical recommendation the farm follows — research, cooperative or consultant. The record just makes sure that recommendation is applied the same way in every field. Without a control level registered for the crop, size and growth stage of the scouting, the field gets no color.

🧭 Default Type (Pest x Type)

Defines, by Crop and range of growth stages, whether the count for that pest is Plant, M2 or Both. This is what makes the app open in the right type instead of the crop scout choosing at every point — and what prevents the same pest from being counted per plant in one field and per meter in another. The list shows Crop, Start st., End st. and Type.

🌱 Crop

The list of crops in which that pest occurs — ALGODÃO, SOJA. It keeps the crop scout from seeing, in soybean scouting, a pest that only occurs in cotton. When the target is generic, the Include all crops button fills in the tab at once.

📄 Text

A free-text field for the pest's technical description — symptoms, when it occurs, notes from the consultant. It is the support text that people in the field look up when in doubt.

📷 Image

The photo shown in the app comes from the Standard Pest chosen in the record, and is not uploaded here. The tab makes this explicit: the image is optional.

🔎 Filters and bulk actions

Above the list, two checkboxes change what the screen offers:

• Show filters (as displayed in the APP) — shows the filter by type and by class the way the crop scout sees it on the phone, with the Apply filter and Clear filters buttons. It is how you check the record through the user's eyes
• Advanced menu — unlocks the record's secondary fields (Code, Short description for reports, Description in English, 'Plant count' field name, Export alias and Export order) and the bulk actions toolbar. Alongside them appear Image and Previous image ID, for reference only: they show the file that came from the standard pest

Each bulk action opens its own window, all with the same filter by type (All, Pests, Diseases, Weed, Assessment) and a list with a checkbox on each line — Description, Scientific Name, Class, Type, Active, Size and Levels:

• Change class (bulk) — reclassifies the checked pests at once
• Copy to another company — takes the records to another company
• Delete several records at once — confirmed with the Confirm deletion of selected button
• Deactivate/Activate several records at once — has a Deactivate / Activate selector at the bottom, so it works both ways

These are housekeeping actions, which is why they are hidden behind the advanced menu. Always use them with the filter applied first.

The main list shows Description, Scientific Name, Class, Type, Active, Code, Size and Levels.

❓ Frequently asked questions

📘 Screen: Pest Group

A pest group combines separate counts into a single number. The most common use is to add up the sizes of the same species: if you count small and large helicoverpa in separate fields, you create the group "Helicoverpa Armigera Total" to see the total for the species. You can also combine similar species — "Heliothinae Family Total", "Soybean Looper Total".

Whoever decides on spraying usually looks at that total, not the size-by-size count — and that total is what this screen defines.

Besides adding up, the group has its own control levels: the "Low", "Medium" and "High" ranges that color the map legend, feed the dashboard and trigger the alert email.

📍 Location in the system

Menu: Basic > Pest Group

🧩 Main function

Define groups that add up the counts of several pests and set, by crop and growth stage range, the control levels for that total.

📝 Main fields

🗂 Additional tabs

🐛 Details (Pest)

This is where you say what goes into the group. For each line:

• Pests — required. The pest that starts counting toward the group
• Size — only appears after you choose a pest that works by size, and then lists its active sizes. This is how you build the most common case: one line for "Small" and another for "Large" of the same pest
• Group — required. The group this line goes into
• Active — uncheck it to take the line out of the calculation without deleting it

The tab's list shows Group, Pests, weeds and diseases, Size and Active. When the group adds up sizes of the same pest, the Size column is what tells the lines apart.

It helps to know how the total is produced: each pest is first calculated by its own calculation method, and the group adds up those finished values. It is not a sum of raw counts — if one pest is measured as a percentage of plants and another as individuals per meter, adding both in the same group does not produce a number that means anything. Group pests that are counted the same way.

A pest set up with predefined levels (Low/Medium/High) is left out of the group calculation: its result is a percentage of points, and it does not go into the sum.

The group does not replace the pest. Each pest keeps its own value and its own color; the group gets one more value and one more color, calculated in parallel.

📈 Control Levels

These are the ranges that translate the counted number into a situation — this is what makes the result appear highlighted in the range's color on the scouting dashboard. Each level is registered by crop, because what is "high" in soybean is not "high" in cotton:

• Crop — required; it is what loads the list of growth stages right below
• Type — whether the count is per Plant, per m2 or Both
• Start stage (from) and End stage (to) — the development range in which that level applies. Either you enter both, or neither. The stage compared is the one the scout entered when opening the scouting
• Start value (From) and End value (To) — the count range. In the list the columns appear as From (=<) and To (>): the From value belongs to the range, the To value already belongs to the next range
• Description — the situation that range represents: Low, Medium or High. It is what sets the color
• Order — the range's position in the legend. If left blank, the system fills it in on its own based on the description: Low 1, Medium 2, High 3
• Send alert email — check it so the system sends an email when the count falls into that range. It is usually checked only on the High level

The list shows Crop, Start st., End st., Description, From (=<), To (>), Type and Order.

A soybean group looks like this, with the three ranges covering the whole cycle: PP - Pre-planting to R8 - Full maturity, Low from 0 to 1, Medium from 1 to 2, High from 2 to 200. You don't have to break it down by growth stage — only do so when the threshold really changes over the cycle.

The system does not allow two overlapping ranges for the same crop, same type and same description, nor a start stage later than the end stage — when this happens, it warns you and does not save.

❓ Frequently asked questions

📘 Screen: Nature of Operation

The nature of the operation is the phrase printed at the top of the invoice stating why that invoice is being issued: "Other outflows", "Sale of the establishment's production", "Shipment for storage", "Purchase return". This is where those phrases are registered, along with what type of invoice each one generates.

This record is used for issuing electronic invoices (NF-e, the Brazilian electronic invoice). The nature is only asked for on the NF-e Transmission screen — the regular Inventory Movement, which only records inventory inflows and outflows, does not show this field. If you don't transmit NF-e through the system, you don't need to touch anything here.

📍 Location in the system

Menu: Basic > Nature of Operation

🧩 Main function

Standardize the natures offered in the NF-e Transmission header and, along with the phrase, define two pieces of information that go on the invoice without anyone typing them: the purpose and whether the invoice is inbound or outbound.

📝 Main fields

The list shows Code, Description, NF-e Purpose, Operation type and Active, with search on each column.

🧾 What each field does on the invoice

Choosing the nature in NF-e Transmission fills in three things at once, which is why it pays to register it properly:

• the description becomes the nature of the operation printed in the invoice header;
• the purpose tells the Receita Federal whether that invoice is normal, supplementary, an adjustment or a return;
• the operation type declares the invoice as inbound or outbound.

In NF-e Transmission the nature is required, and the field shows the phrase together with the purpose — "Other outflows - 1 - Normal" —, so two natures with similar text aren't confused. Only the active natures of the company you are in appear.

You don't need many: most farms handle their day-to-day with one or two phrases. Register a new one only when the purpose or the type really changes.

❓ Frequently asked questions

📘 Screen: CFOP

The CFOP (Código Fiscal de Operações e Prestações, the Brazilian tax operation code) is the four-digit number that states, on the invoice, what is happening with the goods: 5102 is an in-state sale, 5949 is another unspecified outflow, 1102 is a purchase for resale, 5905 is a shipment to a warehouse. This screen is the list of CFOPs the farm uses — nothing more than code, description and active.

You don't need to register the more than 400 CFOPs in the official table: register only the ones that appear on the invoices the farm issues and receives. In practice there are only a few, and the farm's accountant can tell you exactly which ones.

📍 Location in the system

Menu: Basic > CFOP

🧩 Main function

Keep the list of CFOPs available to choose from on the items of NF-e Transmission and Inventory Movement (Inbound & Outbound). Without the CFOP registered, the invoice item lacks the information the tax authority uses to classify the operation.

📝 Main fields

The list shows Code, Description and Active, with a search field on each column.

🧾 Where the CFOP is chosen

On the invoice item, together with the taxes — not in the header. Each product entered can have a different CFOP: it is common for the same invoice to carry the sale on one item and the freight or shipment on another. Only active CFOPs are offered.

Next to the CFOP chosen from the list there is also a free-text field, used when an imported invoice carries a code that is not registered yet.

In an Inventory Movement of the Inbound with invoice type the field does not appear: that invoice's CFOP comes from the supplier's XML.

❓ Frequently asked questions

📘 Screen: CST - ICMS, PIS, COFINS, IPI

The CST (Código de Situação Tributária, the Brazilian tax status code) is the code that states, for each tax, how that item is taxed: whether it pays in full, has a reduced base, is exempt, or is under tax substitution. This screen is the list of CSTs the farm uses, split by tax — ICMS, PIS, COFINS and IPI — with the rate each one usually applies.

It is a record dictated by the farm's accountant: they say which codes go in and at what rate, and here you just register them so issuing the invoice no longer depends on case-by-case lookups.

📍 Location in the system

Menu: Basic > CST - ICMS, PIS, COFINS, IPI

🧩 Main function

Keep, per tax, the list of CSTs available in the tax block of each item in NF-e Transmission and Inventory Movement, with the default rate and base reduction already filled in.

The tax block does not appear in an Inventory Movement of the Inbound with invoice type: there the taxes come from the supplier's invoice XML, and there is nothing to choose.

🔀 The ICMS / PIS / COFINS / IPI filter

Above the list there is a selector with the four taxes. It does two things at once, and it is the most important detail on the screen:

• It filters the list, showing only the CSTs for that tax
• It sets the tax of what you are saving — a new CST is tied to the tax that is selected at that moment

In other words: before clicking New, choose the tax first. Registering a PIS CST with the selector on "ICMS" makes the code show up in the wrong tab when you issue the invoice.

📝 Main fields

The list shows Code, Description, Default rate and Active, with search on each column.

🧾 Where the CST is chosen

On the invoice item: each tax has its own block — ICMS, PIS, COFINS and IPI —, and each one has the CST for that tax next to the tax base, the percentage and the amount. Each block only offers the CSTs registered under that tax that are active.

Choosing the CST fills in the rest: the default rate goes to the item's percentage, the base reduction to the reduction field and, for ICMS, the BC method is carried along too. All of this is a starting point — it can be adjusted on that item without changing the record.

❓ Frequently asked questions

📘 Screen: Series

The series is the numbering "track" for the branch's invoices. Every invoice has a number and a series: series 1 might be for sales invoices, series 2 for shipments, and each one runs its own sequence — invoice 1,250 of series 1 has nothing to do with invoice 1,250 of series 2. Many farms work with a single series, simply called "1".

This record is used for issuing electronic invoices (NF-e, the Brazilian electronic invoice). The series is asked for — and is required — on the NF-e Transmission screen; the regular Inventory Movement does not show this field.

📍 Location in the system

Menu: Basic > Series

🧩 Main function

Register the invoice series used by the branch, so NF-e Transmission knows which sequence to number the invoice being issued in.

📝 Main fields

The list shows Description, Code, Last number and Active, with search on each column.

🔢 How the invoice number is proposed

In NF-e Transmission, as soon as you choose the series the system fills in the number on its own: it looks for the highest number already issued in that series, for that branch, and proposes the next one. For the first invoice of a series, the proposal is 1.

The proposed number can be edited. So if the farm is coming from another system and needs to continue from a specific number, the place to set that is the first invoice issued in the series — from then on the sequence continues on its own. Only the active series of the company you are in are offered.

❓ Frequently asked questions

Quick Guide - Crop Setup (Start of the Season)

This guide is for you if you have just created the farm and want to start using the system for the crop side.

Below is the correct sequence and basic guidance for each step. This flow is required to enable the app and the other features.

📘 1. Crop

📘 2. Variety

📘 3. Field

📘 4. Season

📘 5. Season Planting

❓ Frequently asked questions

📘 Screen: Crop

The Crop screen is used to register the crops grown on the farm, such as soybean, corn, cotton, and others.

This record is essential so that field operations and scouting can be correctly tied to the production cycle.

📍 Location in the system

Menu: Crops > Crop

🧩 Main function

Each registered crop serves as the basis for:

• Season Planting
• Pest scouting
• Classifying varieties
• Harvest and production load tickets

📝 Record fields

The list, on the left, shows Code, Description, Active, Color and Reference/Integration ID, each column with its own search field.

🐛 "For pest scouting" section

Just below the main fields there is a collapsible section called For pest scouting. It only matters to those who use the scouting module — that is why it starts collapsed:

🌱 Tab: Stage

Sets up the crop's growth stages — R4, V2, pre-planting. Fields:

• Code (e.g. R4, V2, PP)
• Description (e.g. "Pod fully developed", "Pre-planting")
• Order: sets the sequence in which the stages follow one another
• Default type: Beat cloth, Plant or Meter — the method suggested at that stage
• Active: lets you retire a stage without erasing history

The list below the form shows Code, Description, Order and Active, with search by column.

🌱 Tab: Sub-Stage

Practically the same as the stage, but one more level of division — some crops need it. The fields are Code, Description, Order and Active. This tab has no import from another crop.

🔍 Tab: Pests - For pest scouting

On this tab you can link the pests that affect the crop.

Features:

• View and manage the pests linked to the crop — the list shows Pests, Type, Class and Active
• Link one pest at a time, choosing it in the Pests field (required) and saving
• Or use the Import several pests button, which lets you check several at once

This link gives you more control and focus in scouting, avoiding needless display of irrelevant pests.

📈 Tab: Ideal Veg. Growth

On this tab you can define the ideal vegetative growth standards for the crop. Each line has three fields:

• Days after emerg. — DAE, days since plant emergence
• Plant Height
• No. of Nodes

This data is used to check whether the plant is growing as expected.

During pest scouting, when opening a point in the app, the scout enters DAE, height and number of nodes, allowing this comparison.

This control is especially important for cotton, where tracking growth is key to adjusting management.

Additional features:

• View chart: shows the registered ideal growth curve as a chart
• Import: copies the vegetative growth already registered for another crop
• Generate in bulk (height): fills in several DAEs at once — you enter Start D.A.E, End D.A.E and Height per D.A.E, and the system builds the curve
• Delete all: clears the whole curve for that crop, so you can start over

📊 Related reports

Crops are the basis for many reports on the platform. Some of them are:

These reports support strategic analysis and technical and financial tracking of the season.

❓ Frequently asked questions

📘 Screen: Variety/Cultivar

The Variety/Cultivar screen is used to register the cultivars of each crop grown on the farm — TMG 31 B3RF for cotton, NEOGEN 690 I2X for soybean, P3845VYHR for corn.

This information complements the Crop record and is essential for Season Planting, allowing more precise control of production and of the agronomic behavior of each genetic material.

📍 Location in the system

Menu: Crops > Variety

🧩 Main function

Each registered variety can be linked to:

• A specific crop
• One or more season plantings
• Technical information such as cycle, yield, weight and germination

📝 Record fields

The list, on the left, shows Code, Name/Description, Crop, Cycle Days, Technology, Active, Macro, Generation, Strategy, Color and Reference/Integration ID.

🌾 "Harvest" section

A collapsible section with three Estimated weight (KG) fields — 1, 2 and 3. These are the yield estimates for that cultivar.

🌱 "Planting" section

Also collapsible, it gathers what guides planter calibration:

📈 Tab: Ideal Veg. Growth

Just like on the Crop screen, you can define the expected development curve — except here it is per cultivar, which is where differences in behavior really show up. Each line has:

• D.A.E. — days after emergence
• Plant Height
• No. of Nodes

These values are used in scouting to check whether development is within the expected standard.

Tab buttons:

• View chart: shows the registered growth curve
• Import: copies the curve already built for another variety
• Generate in bulk (height): fills in several DAEs at once — enter Start D.A.E, End D.A.E and Height per D.A.E
• Delete all: clears the whole curve, so you can start over

❓ Frequently asked questions

📘 Screen: Field

The Field screen is where you register the plots or subdivisions of the farm. These records are fundamental to all crop management in the system, because they are the smallest unit for planning and carrying out activities.

📍 Location in the system

Menu: Crops > Field

🔧 The field list

The list shows Code, Name/Description, Sector, Area, Has map? and Active, each column with its own search box. The Has map? column tells you at a glance which fields already have their boundary registered — it's how you find out what still needs to be mapped.

Next to the buttons is the Total (ha) and Qty totalizer, which adds up what is being displayed: filter by sector and the total becomes that sector's total.

• Reports ▼: opens the reports linked to the Field screen
• Import from Excel: bulk registration from a spreadsheet (see below)
• Map: opens the Farm map window with the fields that have a registered boundary, drawn on the map. There are two options at the top — Show sector and Show hectares — that write that information on each field, and a Grid for pest map button

🧩 Registering one field

To register a new field, click New. The form has four main fields:

⚙️ "Advanced" section

A section that opens and closes, above the main fields. Nothing here is required — these are refinements to area and planning:

📥 Importing from Excel

You can register several fields at once using the "Import from Excel" button.

• The file must contain the columns: Code, Description, Sector, Area, Active — the order doesn't matter
• Accepted extensions: .xls and .xlsx
• Delete empty rows from the file before importing
• A sample template can be downloaded directly from the screen

🗺️ "Coordinates" tab

This is where the field gets its boundary on the map. First choose the file Type — the field is required and defaults to KML:

• KML (.kml) — the Google Earth format
• Shapefile — upload the .shp, .shx and .dbf files together (the .prj is also accepted), or a single .zip containing all of them

Then use Upload File... to send the file. The system processes it and draws the boundary on the map — which switches between Map and Satellite — so you can check it before saving with 2 - Save Coordinates.

The other features on the tab:

• Clear/Delete coordinates: erases the field boundary so you can import it again
• Export KML: downloads the boundary already registered — useful for taking the farm map to another system or to Google Earth
• Show all fields: also draws the neighboring fields, so you can check whether the new boundary fits without overlapping
• Center Latitude and Center Longitude, below the map: the center point of the field

Registering the coordinates correctly is essential for the mapping and traceability features of the platform.

🗂 Other tabs

🔗 "Integration" tab: the field in the external system

This is where you tell the system that field 08 – CAMPINAS in upCampo is the same as field 08 in John Deere — or in another system the farm exchanges data with. Without this link, upCampo doesn't look in the Operations Center for what the machines did in that field.

The John Deere Integration ▼ menu, next to the buttons, saves you from typing the code by hand:

📊 Related reports

Fields are the basis for many reports on the platform. Some of them are:

These reports help with strategic analysis and with technical and financial tracking of the season.

❓ Frequently asked questions

📘 Screen: Field Map Importer

The Field Map Importer registers the whole farm at once, from a single KML file. If the agronomist handed over a Google Earth file with the farm's 80 fields drawn, each drawing in that file becomes a field in the system, already with its boundary and the area in hectares calculated — no typing field by field.

📍 Location in the system

Menu: Crops > Field Map Importer

🧩 Main function

It is the bulk import of the farm map. Each area drawn in the KML (what Google Earth calls a Placemark) becomes a field with its coordinates. The screen shows everything it read from the file before saving, so you can check it and only then confirm.

🗺️ How it differs from the import on the Field screen

Both screens import KML, but they solve different problems:

• On the Coordinates tab of the Field screen you import the boundary of one field that is already registered (and shapefile works there too)
• Here you import several fields at once, creating the records that don't exist yet — but only in .kml

📝 Step by step

1. Upload the .kml file in the screen's upload area
2. Check the list the system builds — one row per area read from the file
3. Click "Import fields" to save

Large files take a few seconds: the progress bar shows how many fields have already been processed.

📝 List columns

🚦 The four statuses

Only rows with the first two statuses are saved. When the import finishes, the list keeps on screen only what was not imported — so you can see the reason, fix the file and try again.

🔐 Permission

The screen uses the add permission of the Field record. Users without that permission can see the screen but can't upload the file or import.

❓ Frequently asked questions

📘 Screen: Season

The season is the farm's production cycle — "Summer Season 2027/2028", "Second Crop 2030". In upCampo, it's the cut that separates one crop year from the next: every work order, every load ticket and every entry is tied to a season, which is why the cost and yield of one cycle don't get mixed with those of the previous one.

This is also where the harvest parameters live, by crop and product — which discounts appear on the inbound load ticket and which table each one looks up. Without that record, the harvest of that crop can't be entered.

📍 Location in the system

Menu: Crops > Season

🧩 Main function

The season is the reference point for crop entries. It is linked to:

• Season Planting
• Work Orders
• Harvest Load Ticket
• Sales Contract
• Movement of Products

📝 Record fields

To register a season, in practice only the Name/Description is required — but it's worth filling in the dates, which define the cycle:

⚙️ The four season controls

Four checkboxes, right below the name, control what can be done in that cycle:

• Active: keeps the season in use
• Hide on login: keeps the season from being shown on the initial selection screen when logging in. Ideal for old seasons that are already closed.
• Block entries in Season Planting: prevents creating or editing plantings linked to that season.
• Block entries in W.O.: prevents that season from being used in new work orders. Useful to avoid wrong entries in seasons that are already finished.

🔄 Connect to this season

A shortcut button that switches the current season without having to log out and back in. It appears in two places: as a column in the list, with a Connect button on each row, and as the Connect to this season button at the top of the open record. When you click it, the system confirms the switch and the chosen season applies to all navigation.

🔧 The list and the view

The list shows Code, Description, Start date, End date, Active, Hide on login, Reference/Integration ID and the Connect to this season column.

At the top of the screen, next to the title, there's the View selector:

• Default: the list and the record, as described here
• Dashboard: swaps the screen for a panel of season indicators, which refreshes on its own every so often — you can choose which dashboard to show, pause the automatic refresh or reload right away

🌾 Tab: Harvest parameters

This tab is used to set up the standard discounts applied during harvest. There's one row per crop: soybeans have one set of discounts, corn has another.

These parameters are applied automatically at the time of the load ticket and directly affect the calculation of the net weight that goes into inventory.

🧬 Tab: Variety - Greenhouse

This tab is used mainly in research and trial settings.

It lets you register:

• Variety grown in a greenhouse — required
• Total Area (ha) under cultivation
• Quantity per variety
• Active, to take it out of use without deleting the record

These records can later be linked in the Season Planting, ensuring traceability and control of the trial units.

📂 Tab: File

The File tab lets you organize the documents related to that season. The files are integrated with a specific Google Drive folder.

Each file has a Date, File name and Description, and the Show button opens the document in another browser tab.

Ideal for keeping the season's document history centralized and accessible — sales contract, map, technical report, all the paperwork the season produced.

❓ Frequently asked questions

🧩 Screen: Season Planting

The season planting is the record of what was planted in each field: which crop, which variety, on how many hectares and on what date. In upCampo, it's the intersection of field, season, crop, variety and area — and it's what makes the field exist in that cycle. With no planting entered, the field isn't available for work orders, scouting or load tickets.

It's also where the results come back: as harvest load tickets and bales come in, the field's total harvested and average yield are updated automatically, with no one typing them.

📍 Location in the system

Menu: Crops > Season Planting

🧩 Main function

Registering the season planting is essential so that:

• Fields show up in the mobile app
• Entries are linked to a specific season
• Reports and dashboards can correctly separate information by season and by variety

👁 The four views

At the top of the screen, the View selector completely changes what you see:

• By season (default): the list of fields in the current season with the record beside it — this is the mode described in this article
• By field: flips the axis, starting from the field
• Season timeline: shows the succession of seasons, useful for seeing what came before and after in the same field
• Dashboard: swaps the screen for a panel of indicators

🔎 The left panel

Besides the list of fields, the left column holds the filters and bulk actions:

• The Season dropdown and the Show season only option
• The Total (ha) and Qty totalizer, which adds up what is being displayed
• Allow the same field more than once: lets you register the same field in two plantings in the same season — for growers who plant two crops back to back
• Status: All, Not Finished or Finished
• Show only with more than 1 variety: isolates fields with more than one cultivar

📝 Header (main information)

The form is split into three tabs at the top — Header (main information), Additional Information and Others. The header is what ties everything together:

The header also has two sections that open and close, Planting and Harvest, with summarized dates and areas.

🌿 One variety or several

The How many varieties field decides the format of the record:

• One: pick the variety and the cycle days right there, in the header
• More than one: the entry moves to the Variety/Cultivar tab, one row per cultivar, each with its own area

The sum of the variety areas can't exceed the planting area.

Variety/Cultivar tab

Each cultivar gets Variety/Cultivar Area (ha), Cycle Days, Location, Display name, Quantity and Active (variety), plus the subsections:

• Planting: Planting Date, Emergence date and Planted area
• Harvest: Harvest Date, Harvested area and Harvest Finished

The grid below shows what has already been entered and pulls in the variety's technical data — PN, PMS, % Ger., Pits/m, Stes/m, KG/ha and Qde KG. The tab's buttons include Generate Several, to create several rows at once, Delete all and Finish variety harvest.

🧪 Separate by variety

When enabled, scouting and work order records are separated by variety in the app and in reports.

The separation is chosen per entry type, not all at once — there are ten independent options: In scouting (MIP), In Planting W.O., In Seed Treatment W.O., In Fertilization W.O., In Crop Protection Application W.O., In Soil Prep W.O., In Harvest W.O., In 'Other' W.O., In Evaluation W.O. and Manual. That way you can separate by variety in scouting and harvest but keep soil preparation unified — which is how most growers work.

📋 Tab: Additional Information

The form's second tab, organized in blocks that open and close:

This tab also holds Reference/Integration ID, Cycle Reference ID and the trail of who touched the record: Created by, Changed by and Finished by, each with date and time.

🧭 Quick actions on the Season Planting screen

The left column offers important shortcuts for bulk actions. They all open a window with two lists — available on the left, added on the right — and arrows to move fields between them:

• Quick/dynamic field import: choose a crop, optionally a variety and the planting date, and apply them to several fields at once. The Show only unused fields option — checked by default — hides fields that already have a planting in that season, so the list shows only what's missing. At the bottom, the Show in MIP and Show in Crop Work Order options come checked on the records created.
• Change variety: changes the crop and variety of several existing plantings. The list shows what each field has today — crop, variety, area and planting date — so you can check before changing.
• Change grouping: changes the grouping of several plantings at once.
• View variety map: shows a map with the fields and the colors assigned to the varieties, making it easy to see the geographic distribution of varieties.
• Link Proj./Var.: links projects and varieties, used in trial areas.
• Finish multiple harvests: closes the harvest of several fields at once (see below).
• Reports ▼: opens the reports linked to the screen.

How upCampo calculates field yield

The Total harvested KG and Final harvest average fields aren't typed: each load entered updates them automatically, the moment it's saved. What changes is the source of the load and the unit divisor.

The divisor is the unit that production is traded in: 60 kg is the bag and 15 kg is the arroba — neither one is configurable.

Since the area is the divisor, a wrong area on the planting means a wrong yield — and the error doesn't show up right away, only when someone questions the average at the end of the season.

What "finishing the harvest" does — and what it doesn't

The window itself warns you, and it's worth repeating:

• The Harvest Date entered in the window is saved on the selected fields. To not change the date already there, leave the box empty.
• Generate new record (e.g., fallow): automatically creates a new planting right after — this is how you record fallow or the next crop in the same field.
• Show all (including finished): also shows what has already been closed, useful for checking or correcting.

You can also finish one planting at a time, with the Finish button at the top of the form, or a specific variety, with Finish variety harvest on the Variety/Cultivar tab.

📊 Related reports

The Season Planting screen is the basis for many reports on the platform. The two main ones are:

These reports help with strategic analysis and with technical and financial tracking of the season.

❓ Frequently asked questions

🐛 Quick Guide - Pest Monitoring

Pest monitoring — or IPM, integrated pest management — is going out to the field to find out what's happening inside the field before deciding whether it's worth spraying. The scout walks into the crop, covers the area and stops along the way; at each stop, they look at the plants around them and record what they found. In upCampo this record is made on the phone, stop by stop, and the web portal combines it all into one number per field — the number the agronomist compares with the action threshold to decide whether it's time to spray.

If you've never seen this whole flow, it works like this:

1. The scout goes out to the field with the app on their phone. They pick the field and start walking it.
2. At each stop, they open a point and record what they saw: the crop stage, the plant phenology and the count of pests found.
3. Back in signal range, the phone syncs. All the points in that field on that day make up one scouting record.
4. The web portal calculates the field result and compares it with the action threshold the farm registered for that pest, crop and stage.
5. The agronomist reads the result on the scouting panel and decides: spray, wait, or scout again in two days.

The field app

Data collection happens in the upCampo app, installed on the scout's phone:

• 📱 Download on Google Play (Android)
• 📱 Download on the App Store (iPhone)

The login is the same as the web portal — the scout signs in with the username and password they already use in the system; there's no separate registration for the app. What must exist is access granted: a user created for them in Users, with permission on the farm they'll scout. Without that, the app opens but shows no fields.

And it works without internet. Fields rarely have signal. The app stores everything on the device and syncs on its own when the connection comes back, so the scout doesn't need to worry about coverage in the middle of the crop.

In the app, monitoring is under the Scouting (IPM) menu. The list shows the season's fields with the crop and how long ago each one was last scouted. The scout taps the field, then the orange + button and New Scouting.

What gets recorded at each stop

There are two moments, always in this order: first the point opening, then the pest count.

The point opening records how the crop looks at that spot, and brings together two pieces of information:

1. The crop stage — where the plant is in its cycle: V4, R5, and so on. This isn't red tape: the stage entered at the opening decides which action threshold range applies, because two caterpillars per meter mean different things at different points in the crop.
2. Phenology — measurements of the plant itself, not the pest: height, number of nodes, internode length, stand, plants per meter; in soybeans, pods and seeds per pod; in cotton, squares, bolls and open bolls. This is what lets you track whether the crop is growing as expected for that variety.

In the app, the new point opens in the Point Opening block: the scout picks the Stage from a list, fills in the plant measurements and taps OPEN POINT. The screen already shows the Planting Date and Days After Planting, which come from the Season Planting.

Which measurements appear depends on the crop. Each opening field is turned on per crop in File > Company/Crop Settings, and can also be limited to a range of days after planting and to certain points of the walk — all, only the first, or a fixed interval. In the cotton season in the example below, besides Plants/m Phen. and STAND, the scout enters Height, No. of Nodes and White Flower Pos. — that's what cotton calls the field that appears as 1st node height in other crops.

The pest count comes next. For each pest found, the scout enters the counting method used, how many plants were checked, the pest, the size of the individual when it's counted that way — small, medium, large caterpillar — and the quantity. When the pest is registered with preset options, they don't type a number: they mark Low, Medium or High. The app stores the coordinate, time, who did it and photos along with it.

In the app, after the opening, the same screen shows the counting Type (Plant, with the number of plants checked) and the Select a Pest/Disease field. On the first entry of the point, the app confirms the number of plants; then it opens the pest list, filtered by Type (Pest, Disease, Weeds) and by Class. Each pest opens as an accordion with the counting fields — by size, with the preset options from the record, or by number, with the − and + buttons. CLOSE POINT is at the top of the screen, and FINISH SCOUTING at the bottom. Each pest has its own Save button, which appears after something is filled in: if you don't tap it, the count doesn't go into the point. The scout's step by step, from the field to the finished scouting, is in How to scout for pests and diseases in the app.

Detailed cotton phenology, node by node

In cotton, phenology can be recorded plant by plant and node by node, marking what's at each position on the fruiting branch. In the app, in the point's pest list, the Detailed Cotton Phenology class has the items Plant 1, Plant 2 and so on — one per plant checked. Tapping a plant opens its own screen:

1. Enter the Height, Veg. Nodes Qty (vegetative nodes) and Veg. Buds Qty (vegetative buds).
2. Tap + once for each fruiting node — − removes one. The + only works once the vegetative nodes are filled in. Total Nodes Qty is calculated automatically (vegetative + fruiting).
3. Each fruiting node becomes a row in the grid, numbered from the last vegetative node — with 6 vegetative nodes, the fruiting ones are Node 7, Node 8, Node 9… —, with positions 1 to 5 on the branch.
4. Tap each position until you reach what's there. Each tap moves to the next state, in legend order: Abs. (absent) → Square → Flower → Boll → Open (open boll) → Abor. (aborted) → back to Abs. The position's color shows the state.
5. Tap SAVE and move on to the next plant.

Once the plant is saved, the records show up in the point, under Found at Point, and in the field history. The history shows the day's summary — how many fruiting nodes have a square, flower, boll and open boll, the height and the nodes — and the detail for each plant, with Fruiting Squares Qty, Fruiting White Flowers Qty, Fruiting Bolls Qty, Fruiting Open Bolls Qty and Fruiting Abortions Qty

What's done with this measurement afterwards — the dashboard that draws the plant tree node by node and the node-by-node phenology reports — is in Node-by-node phenology mapping.

Counting methods

The method is how the pest was counted at that point — and it's what gives the number its meaning. Counting five caterpillars in one meter of row isn't the same information as finding five caterpillars in a hundred plants examined. There are three:

What the system does with it

All the stops made in that field on that day form one scouting record — even when two scouts monitored the same field on the same date: both of their points go into the same calculation. The total number of points walked becomes the divisor of the averages, which is why stopping more often gives a truer picture of the area: with three stops, a hot spot in one corner can go unnoticed or become the whole average.

From there the system calculates one number per pest and compares it with the action threshold registered for that crop and stage. The result appears on the scouting panel of the home screen, in the pest × field matrix, with the number highlighted in the color of the range it fell into — that's what makes anything over the limit jump out, without reading row by row.

A badly entered stop doesn't just spoil itself: it goes into the average of the whole field for that day. That's why the web portal has the Scouting screen — so the agronomist can check and correct what came in from the field.

From here on: getting the system ready

Up to here was the field routine. The rest of this guide is the setup order — the sequence of records that makes this routine work, each one with its article linked along the way:

• Steps 1 to 4 — setup. They define what will be monitored, how it's counted and at what number the farm takes action. It's a one-time job: done at implementation and reviewed every season, when the crop or the strategy changes.
• Step 5 — the routine. What needs to be enabled for the scout to monitor day to day.
• Steps 6 and 7 — reading the results. Where the agronomist checks what came in and sees the big picture.

Much of this comes ready-made. upCampo maintains a pest library with scientific name, class and counting method already set up, and importing from it takes care of most of step 2. What each farm actually customizes is shorter than it looks:

• which pests to monitor — the list for your crop, not the whole catalog;
• how each one is counted — the method and the calculation method, which decide what the number means;
• at what number to act — the action thresholds, by crop and by stage. It's the one part nobody can fill in for you: it's the farm's agronomic decision;
• what gets added together — pest groups, when the decision is made for the group rather than the species.

🧱 1. Pest Class

🐛 2. Pests, weeds and diseases

📈 3. Action threshold

🧮 4. Pest group (optional)

📱 5. Field data collection

🔬 6. Scouting: from the point to the field number

📊 7. The scouting panel

🪤 Traps: the other way to count

📷 Observation: the free-form record

Want to understand the whole module, including what it does on the scout's phone? See the up.Monitora page on the upCampo website.

❓ Frequently asked questions

📘 Screen: Trap Group

The Trap Group screen is used to register the types of traps used on the farm, grouping them by purpose or target pest. Besides naming the group, this is where you define what that trap catches and from what count a catch becomes an alert.

📍 Location in the system

Menu: Crops > Trap Group

🧩 Main function

Each group represents a general classification of the trap, such as the type of pest it monitors.

Common examples:

• Boll Weevil Trap
• Caterpillar Trap
• Leafhopper Trap

This group is selected later when registering a Trap x Season.

📝 Registration fields

🐛 Tab: Details (items)

This is where you say what that trap catches. Each row links to the group a Pest, weed or disease that is already registered, with a free-text Description and the Active checkbox.

A pheromone trap for boll weevil, for example, has a single item; a generic light trap group can have several, because it catches more than one species. This list defines what the operator will be able to count when reading the trap in the field.

📊 Tab: Levels

Levels turn the count into decision-making information: instead of the scout seeing "37 insects" and having to remember whether that is a lot or a little, the system classifies the catch into ranges you define.

The buttons on this tab are Save Levels, Cancel Levels and Delete Levels, so they are not confused with the header buttons.

The level color

Each level also stores a color, and that is what the app uses: the colored bar on the side of each trap in the list and its pin on the map come from the range the last collection fell into. This lets the scout see, without opening anything, where in the area the catch went up.

An example of a group set up for the cotton boll weevil, with ranges named in BAS (boll weevils per trap per week): 0 BAS in green, 0 to 1 BAS in blue, 1 to 2 BAS in yellow and Above 2 BAS in red. The complete path for this pest is in How to monitor the cotton boll weevil.

In the app, the trap list uses these levels to visually highlight the traps that are in an alert range — whoever looks at the phone sees right away which traps need attention, without comparing number by number.

❓ Frequently asked questions

📘 Screen: Trap x Season

The Trap x Season screen is used to register and georeference the traps installed on the farm during a specific season.

Each trap registered here is linked to a group and ready to be used for collections through the app, the web portal or integrations with electronic traps.

Once registered, it is ready to generate collections.

🔍 What it is

An agricultural trap is a device used in crops to catch insects and identify the pests present in the field. Traps work as a form of monitoring, helping the grower know when and where a given pest is showing up.

Traps often use a pheromone, a substance that attracts the target insect and makes the catch more effective.

Traps are usually spread around the fields. Ideally, the traps should cover at least each side of a field, ensuring efficient monitoring that represents the area.

📍 Location in the system

Menu: Crops > Trap x Season

🧩 Main function

Lets you register physical or electronic traps linked to a season, grouping them by type and location.

These traps can be used for:

• Manual collections through the app
• Manual entries through the web portal
• Integrations with sensors or digital traps

📝 Registration fields

The Sector appears as a column in the list, but it is not typed here: it comes from the selected field. The list shows Number, Sector, Trap Group, Field and Active, with a Season filter right above it.

📥 Tab: Collections

After the trap is registered, the user can record the collections made throughout the season.

Collections can be made in four ways:

• App: manual collection by the scout in the field, directly on the phone, with or without internet.
• Web portal: through the Collections tab on this screen, ideal for corrections or additional entries.
• Electronic trap integration: if the customer has sensors installed, the catch data is synchronized automatically with the system.
• Import Collections from Excel: a button on the list, for those who keep the records in a spreadsheet (see below).

Each collection records:

Import Collections from Excel

A button on the list that brings in the collections from a spreadsheet all at once. The file must be .xls or .xlsx and must have two required columns:

• data — the collection date
• quantidade — in numeric format

The window itself has an instructions section that repeats this format.

📱 Collecting in the app

The phone is where collecting really happens: the scout walks the traps with the app open, records what was found in each one and syncs when there is signal. In the Trap menu the screen opens in two tabs, LIST and MAP.

The list shows one trap per row, with the number, the sector and how long ago the last collection was — Today, N days ago or Never, for one that has not been checked yet. When the group has pests registered, the row also shows how many were found and which ones. The colored bar on the side of each row is the group's level range, and it is the same color as the pin on the map. At the top are the Trap Group, Sector, Field and Order filters.

Tapping a trap opens its record with two tabs: COLLECTIONS, with the history, and LOCATION, with the map. Each collection in the list shows the date, who made it, the quantity, whether there were pests and the classification. The (+)NEW COLLECTION button opens a new entry.

The collection screen has two fields that exist only in the app:

The NEW TRAP (+) button, at the top of the list, registers a trap from the phone itself, right where it is being installed: you choose the group, the number, the sector and, if the farm uses it, the QR Code. The location comes from the device's GPS.

📊 What is it for?

The collection is the starting point for the system to turn raw data into useful information for the manager.

From the collections, the system:

• Automatically updates the pest dashboards and reports
• Shows maps with the geographic distribution of catches
• Shows week-by-week trend charts
• Points out trends, infestation peaks and comparisons by field or sector

This lets the manager judge whether it is time to step in, take preventive measures or apply, based on concrete data and not just on impressions.

📊 Related reports and dashboards

• MON.05.01 (formerly 002.P) - Trap scouting
• MON.05.02 (formerly 002.Q) - Trap scouting per week per sector
• MON.05.03 (formerly 002.R) - Trap scouting per week per field
• Trap trend

The Trap tab on the home screen

The portal's home screen has a Trap tab that brings together the collections from all traps in one place. It has its own filters — Season, Start date, End date, Sector and Trap Group — and two modes under Display mode: Map, which opens by default and places each collection at the point where the trap is, and Table, with one row per collection: group, sector, date, classification, field and quantity.

Besides these reports, the home screen has a dedicated tab, called Traps, for viewing the collections made.

❓ Frequently asked questions

🌧️ Screen: Rain Gauge

The Rain Gauge screen lets you register fixed weather data collection points on the farm, whether they are Rain Gauges or Weather Stations.

📍 Location in the system

Menu: Crops > Rain Gauge

🧩 Main function

Lets you register the farm's rain gauges and weather stations, defining location, coverage and type of measurement (manual or automatic). These records are essential for:

• Historical weather analysis
• Agronomic decisions based on rainfall
• Technical monitoring of the fields

📝 Registration fields

The list shows Code, Description, Sector, Fields, Last Collection Date, Type, Has Temp., Has Hum., Has Wind Speed, API Link and Active, each column with its own search box. The Last Collection Date is the shortcut to find out which rain gauge stopped being read. The Reports ▼ button, at the top, opens the reports linked to the screen.

Fields that only appear for stations

When you choose a type other than Manual, the screen shows the integration fields — which stay hidden for a manual rain gauge:

🗂️ Available tabs

1. 🌾 Field

Lists the fields covered by this rain gauge. This ensures that, when you look up data for a field, the system knows which station to use as the reference.

You can link one field at a time, choosing it in the Field box and saving, or use the Import button: it opens the farm's list of fields, with Description, Sector and Code, so you can check several and bring them all in at once with Import selected.

2. 📍 Location

Defines the latitude and longitude of the point, allowing it to be shown on the map and used with GPS in the app.

• It can be filled in manually or captured through the app with geolocation

3. 🌧️ Collections

Lets you record rainfall collections:

• Manually in the web portal
• Automatically through the station integration
• Through the app, entering the rainfall volume collected

Each collection records:

Recording rainfall, step by step

1. Open the rain gauge in the list and go to the Collections tab.
2. Fill in the Date of the reading.
3. With Rained? set to Yes, enter the Millimeters. If it did not rain, select No and choose the weather Classification.
4. Click Save, on the Collections tab bar.

📱 The rain gauge in the app

In the field, the reading is entered through the upCampo app, in the Rain Gauge/Station menu. The list shows each rain gauge and station with the accumulated millimeters, the date of the last collection and of the last rain, and the fields it covers; stations also show temperature, humidity and wind. The other tabs are SUMMARY (rainfall charts per rain gauge), MAP and COLLECTIONS (the most recent readings from all of them).

Recording rainfall in the app

1. Tap the rain gauge in the list and, on the COLLECTIONS tab, tap (+)NEW COLLECTION.
2. Check the Date, leave Rained? set to Yes and enter the Millimeters.
3. Select the Type — Rain or Irrigation — and, if you have them, the maximum temperature, minimum temperature and humidity.
4. Tap SAVE.

📊 Reports and dashboards

Available reports:

Weather & Stations & Rain Gauges dashboard

On the platform's home screen, there is a dashboard dedicated to weather tracking:

• It shows the rain gauges on a map with the rainfall recorded at each location
• It also offers a table view with historical data

Rainfall ranges

To classify rainfall as low, medium or high, the system uses:

• An automatic average based on the minimum and maximum values recorded
• Or ranges defined manually on the company settings tab

❓ Frequently asked questions

📘 Screen: Scouting

Scouting is the record of pest monitoring done in the field: the scout walks the field, stops at a few points along the way and records what was found at each stop. There is no fixed grid or position set by the system — where to stop and how many times is up to the scout and the farm's routine. In upCampo this work is done on the phone, point by point, and this screen is where the agronomist reviews, corrects and — occasionally — adds what came in from the app.

From these points the system builds the field's result: the average occurrence of each pest and the comparison with the registered action threshold, which tells you whether it is time to spray. Since the total number of points walked is the divisor of the averages, stopping more often gives a truer picture of the area. And a point entered wrong doesn't spoil only that point — it goes into the average for the whole field on that day.

📍 Location in the system

Menu: Crops > Scouting

🧩 Main function

Scouting is done in the field, with the app — that is where the scout opens the point, counts the pest and takes the photo. This web portal screen exists for what the app doesn't handle: reviewing what came in, correcting a wrong entry and making an occasional addition, when someone scouted without the phone or forgot to enter it.

It is ideal for:

• Reviewing the data received
• Correcting small pieces of information
• Occasionally adding a point that was not entered in the app
• Deleting wrong records

Each record contains:

• Date and time of the scouting
• Crop, field, variety
• DAE, plant height and nodes
• Collection points and quantities of pests found
• Photos taken at the time of collection

🔎 The list

The list opens filtered by Season and Date — the date is required, and it defines the scouting day you are reviewing. The columns are Field, Variety, Crop, Date, Stage, User, Point, Opening, Pests, Size, Preset Value and Value, each with its own search box.

📝 Record fields

🔀 "Point Opening": two different records on the same screen

The Point Opening checkbox swaps the whole form. It is what separates the record of the plant from the record of the pest:

Unchecked — pest count

This is the entry for a pest found at the point:

• Type: Plant, Beat Sheet, Meter or Assessment — the method used for the count
• Plant Qty: how many plants were assessed
• Pests: the pest, weed or disease found
• Size: the stage/size of the individual, when the pest is counted that way (small, medium, large caterpillar)
• Value: the count

When the selected pest or size has preset values registered, a list of ready-made options to select appears instead — this speeds up counting in the field and feeds the Preset Value column in the list.

Checked — plant data

This is the point opening record, with the growth measurements. Everything related to pests disappears and a grid of checkbox + value pairs appears: you check what was measured and enter the number next to it. The fields cover:

• Growth: height, number of nodes, internode distance, height of the first to the fifth node and depth
• Population: stand, plants per meter and number of stems
• Soybean: number of pods, height of the first pod and seeds per pod
• Cotton: squares, bolls (small, medium, large and total), bolls by position — from 1 to 5 —, rotten boll, open bolls and boll weevil

These are the measurements that feed the comparison with the ideal vegetative growth of the variety and the crop.

🧮 How upCampo turns points into a result

What the scout enters is the count at each point. The number the agronomist looks at — and that is compared with the action threshold — comes from a calculation over all the points in that field on that day. The form of that calculation comes from the Calculation method field in the pest record:

An example: 10 points walked, pest found in 4 of them, 20 individuals counted in total.

The difference between the two averages is what usually causes confusion: Average per point spreads the pest across the whole field and answers "what is the average pressure on the area"; Average per occurrence looks only where it appeared and answers "where there is some, how much is there". A concentrated hot spot gives a low average per point and a high average per occurrence — and that contrast is exactly what indicates a localized infestation rather than a widespread one.

In the IPM Standard, the result depends on the type of scouting: for beat sheet and m², it is the average per point; per linear meter, the value is expressed per meter; for counting per plant, it becomes a percentage.

📊 Dashboards and overall view

On the platform's home screen there is a dedicated dashboard called Scouting, where the data is analyzed in a consolidated way.

There the agronomist can:

• See scouting grouped by date and field
• Analyze each collection point in detail
• See the map with the georeferenced points
• Check the photos taken in the field
• Check the crop stage at the time of collection
• Access the pest history by field, with comparative data

📱 Scouting in the app

What this screen shows in the web portal starts in the app, in the Scouting (IPM) menu. That is where the scout opens the points and counts the pests — the step by step, with screenshots, is in the Quick Guide - Pest Monitoring. Besides collecting, the scout can look up on the phone itself what has already been done:

• Field history — tapping the field, the app shows the map of the area and, on the IPM HISTORY (SUMMARY) tab, each scouting with the date, who did it, the stage, days after planting, number of points and the values recorded, with the REPORT and DETAIL buttons. Next to it are the WORK ORDER/APPL. and DETAILS tabs.
• MAP — the farm's fields on the map, with a sector filter and legend.
• IPM MGMT ANALYSES — the management view of scouting, by period and user.

📊 Related reports

Crops serve as the basis for several reports on the platform. Some of them are:

Scouting on the phone is up.Monitora, upCampo's pest monitoring module.

❓ Frequently asked questions

🧩 Extra: Node-by-node phenological mapping

Node-by-node phenological mapping is the plant-by-plant record of what is at each position of each reproductive node of the cotton plant: square, flower, boll, open boll or aborted structure. In upCampo it has three parts: collection in the app, done by the scout in the field; the phenology dashboard, which draws the plant node by node from that collection; and the reports, especially MON.02.01 (formerly 001.N) - Summary Phenology and MON.02.05 (formerly 001.M) - Detailed Phenology.

What this map answers is where the plant is holding its load and where it is losing it: at which nodes the bolls set, at what height on the plant abortion is concentrated, how much has already opened. That is information the count of squares and bolls per meter doesn't give, because it says how much there is, but not where.

1. The scout measures the plant in the app, within the scouting: height, vegetative nodes and, node by node, what is at each position on the branch.
2. The phone syncs and, within a few minutes, upCampo turns each plant into a drawing of the plant.
3. The agronomist reads the plant on the dashboard, in the field summary or plant by plant, and compares dates or fields side by side.
4. The reports bring the same data in numbers and on paper: MON.02.01 (formerly 001.N) with the field's percentages and averages, MON.02.02 (formerly 001.M2) with each plant's drawing.

📍 Where each part is

1. Collection in the app

App: Scouting (IPM) > New Scouting > Detailed Cotton Phenology

The measurement happens within a regular scouting. After opening the point, the scout selects the Detailed Cotton Phenology class in the pest list, chooses the plant (Plant 1, Plant 2…) and fills in its screen:

1. Height, Veg. Node Qty (vegetative nodes) and Veg. Square Qty (vegetative squares).
2. One tap on + for each reproductive node. The grid gets one row per node, numbered from the last vegetative node — with 6 vegetative nodes, the first reproductive one is Node 7. The Total Node Qty is calculated automatically.
3. On each node, positions 1 to 5 on the branch, from closest to the stem to farthest. Each tap advances one state: Abs. (absent) → Square → Flower → Boll → Open (open boll) → Abor. (aborted).
4. SAVE.

The complete step by step for the plant screen, with all the screenshots, is in the Quick Guide - Pest Monitoring.

⚠️ One plant per point. The dashboard draws one plant for each scouting point of each scout. If the scout enters two plants at the same point, the nodes of both fall into the same drawing, one on top of the other. The routine is to open a new point for each plant measured — that is how the Cotton 2026 collections were done.

Absent positions are not saved. The app saves one record for each measurement and one for each position marked with a state; whatever was left as Abs. does not become a record. This matters when reading the percentages, further below.

💡 The class doesn't open the plant screen? The app opens that screen for the pest whose record has Algodão in the 'Plant qty' field name field, under Basic > Pest. Without it, the pest opens as a regular count and the dashboard doesn't see it.

Counting structures per meter

A second measurement goes into the same scouting; it is not by node and feeds the MON.02.03 (formerly 001.O) report: the Structure per meter pest. It appears in the point's pest list, inside the class of the same name, and instead of a grid it opens four fields to type in:

Field	What to enter
Meters assessed	The stretch of row walked at that point. How much to measure is up to the farm — in the cotton scouting for the 2026 season, most use 5 meters per point.
Total plants	How many plants there are in that stretch. This is where the report's stand per meter comes from.
Total structures	How many structures were counted in the stretch.
Average weight	The average weight of the structure, in grams. It goes straight into the arroba estimate; in the 2026 season the values entered range between 4 and 5.5 g.

The report adds up the field's points: with 6 points of 3 meters, for example, it shows 18 meters assessed and the total plants and structures from all of them. This count produces the stand, the average per meter and the estimated @ in MON.02.03 (formerly 001.O).

💡 These are independent measurements. Node-by-node mapping measures a few whole plants; the per-meter count walks a stretch of row. One does not replace the other, and nothing prevents doing both at the same point — that is what the farm in the example does in the Cotton 2026 season.

2. The phenology dashboard

Phenology page (the farm's dedicated address)

The dashboard shows the cotton plant as it is in the field: the stem in the center, the reproductive nodes rising and alternating sides, and on each branch positions 1 to 5 with the letter and color of what was found. It opens with the header and an empty comparison area.

In the header:

Item	What it does
Legend	B Square (orange), F Flower (white), M Boll (green), C Open boll (blue), A Abortion (dark red) and P Rotten (brown). The app doesn't have the Rotten state in the plant grid, so it doesn't show up in collections made there.
Side by Side / Vertical	How comparisons are arranged: all in the same strip, one next to the other, or one below the other.
Add comparison	Opens another comparison area (Comparison 2, 3…), each with its own filters.

In each comparison:

Field	Description
Field	The field, variety and scouting date, on a single line — for example, 03 - … - TMG 21 GLTP - 30/06/2026. Each measured date is one item: the same field appears once per collection day.
Type	Summary, Summary with % or Per plant (point by point) — explained below.
Zoom	Size of the drawings, from 50 to 200. Increase it to read the percentages.
Date	Filters the Field list to show only scouting from that day. Left empty, the list shows all dates.
Remove	Takes the comparison off the screen.

Each drawing has, in the corner, the ‹ and › arrows, which change the order of the drawings, and the ✕, which removes that drawing from the screen. None of this changes data: the dashboard is view-only, and whatever you rearrange goes back to normal when the page is reloaded.

Summary

A single plant drawing, representing the field on that day. At each node and position, the most frequent state among the plants measured appears. It is the quick read: where the load is, where the abortion is.

Summary with %

The same drawing, but at each position all the states found appear, stacked, each with its percentage. In the example below, position 1 on Node 25 shows A 50% and M 50%: half the plants had an aborted structure there, half a boll.

⚠️ The percentage is out of the plants that had something at that position. Since absent positions are not saved, they don't enter the calculation for Summary or Summary with %. A position 4 that existed on only one plant, with a boll, appears as M 100% — and that doesn't mean all plants had a boll there. To know how many plants had the position, look at Per plant.

Per plant (point by point)

One drawing for each scouting point — that is, for each plant measured. The title of each drawing shows the date, the scout who measured and the point number. This is where you check the variation between plants and find a measurement that is out of line.

Comparing dates or fields

With Add comparison, the screen gets a second area with its own filters. The most common use is the same field on two dates, to see the plant develop; it also works for putting two fields, or two varieties, side by side on the same date.

When the measurement shows up. The drawings are not built the moment the page opens: an upCampo routine prepares them every 7 minutes, from what has already synced. Counting the phone's sync, a plant measured in the field usually shows up within a few minutes. The dashboard reads the data when it opens — to see what came in afterwards, reload the page.

Height, and ideal height, on the dashboard

Web portal: upCampo > Scouting

The Scouting tab on the home screen shows each scouting in a column, with the field, crop, variety, days after planting and after emergence, stage and who measured — and, further down, the plant measurements.

Among the measurements are STAND, Height, Node Qty and a -- Ideal Height row: the height the crop should have on that day, according to the registered curve. In the example, the plant is at 96.28 cm and the ideal for that moment is 100 cm — in other words, practically as expected.

💡 The Ideal Height row only appears if the curve is registered. It comes from the Ideal Veg. Growth table, a table of days after emergence × height that the farm fills in under Variety or Crop. The web portal looks for the row with the exact DAE of the scouting: with no curve for that day, the row is not shown — and the measured height appears on its own.

Value history, day by day

The value in the grid is a button. Clicking the height — or any other measurement in the column — opens the Value History window, with the whole season for that field in a single chart:

• the Height line, with what was measured at each scouting;
• the Ideal Veg. Growth line, which is the registered curve;
• the Work Order/Activity bars, marking the days when there was an application.

The bottom axis shows the date and DAE of each point. Below the chart, a table repeats the numbers and adds the Difference from previous, the Average per day and the Average per DAE — the growth between one scouting and the next. The Map tab, at the top, shows where the points were taken.

This is the reading that shows the pace: two equal measurements can mean different things depending on how the plant was growing before — and the work order bars help connect a change of pace to an application.

⚠️ Filtering a single day returns nothing. The period compares the date and time of the scouting, and the day's scouting has a time. Select Show filters, enter the Start date and an End date of the next day, and click Apply filter.

3. The reports

Web portal: Reports → Survey theme

The reports below ask for the same filters (MON.02.03 (formerly 001.O) also has Estimated weight): Date (period, required), Quadra(s) and Sector. Quadra is the old name for a field; left blank, all are included. They only consider the cotton phenology pest — the same one the dashboard uses. How to run and export reports is in the Quick Guide - Reports.

MON.02.01 (formerly 001.N) - Summary Phenology
The field in numbers: one row per field and scouting date, with Variety, D.A.E and D.A.P (days after emergence and after planting, counted from Season Planting), Pla. (how many plants were assessed), Last STAND (the last stand recorded up to that date), Last White Flower Pos. and the averages of Veg. Node Qty and Rep. Node Qty. Then comes a block for each state found in the period — Square, Flower, Boll, Open boll and Aborted —, each with three columns:

• Average — how many structures of that state per plant;
• Total — how many were marked in the field;
• % — that state's share of all structures marked in the field on that day.

A state that didn't appear in the period gets no block: at the end of the cycle, for example, the report shows only Boll, Open boll and Aborted. This is the report for following the season field by field and comparing dates.

MON.02.05 (formerly 001.M) - Detailed Phenology
Each plant's sheet, grouped by field and by point (with the scout who measured): Height, Total Nodes, Veg. Nodes, Veg. Squares and Rep. Nodes, and the count of Square, Flower, Boll, Open boll, Aborted and the Total for that plant. At the end of each field, a Summary (average) of the measurements. It is for checking the collection plant by plant. To see the plant drawn node by node, use MON.02.02 (formerly 001.M2), just below.

MON.02.02 (formerly 001.M2) - Detailed Phenology - Plant Map
The most complete report for node-by-node mapping, and the one that takes the dashboard's plant drawing to paper. It opens with two tables for the period:

• Summary phenology — the same numbers as MON.02.01 (formerly 001.N) (plants, Last STAND, nodes and, per state, Average, Total and %), field by field;
• By position (average) — for each state, how many structures per plant there are at each position on the branch, from 1 to 5. This is where you see, for example, that abortion is concentrated at positions 1 and 2 and barely reaches 4.

Then comes each plant, by point: the measurements (Height, Total nodes, Veg. Nodes, Veg. Squares, Rep. Nodes), the drawing of the plant — nodes alternating sides, as on the cotton plant, and the letter and color of the state at each position — and the count of Square, Flower, Boll, Open boll, Aborted and Rotten. The drawing shows positions 1 to 3 on each branch.

MON.02.03 (formerly 001.O) - Structures per meter
It doesn't use the node-by-node measurement: it reads the Structure per meter pest, entered in the same scouting in the app. The report shows, by field and date:

• STAND — total plants ÷ meters assessed;
• Average per meter — total structures ÷ meters assessed;
• Estimated @ — the estimated yield in arrobas per hectare, using the calculation below.

The optional Estimated weight filter replaces the average weight entered in the field — it lets you simulate the estimate with a different open boll weight.

Estimated @ = average per meter × average weight (g) ÷ 1,000 × 11,111 ÷ 15

The 11,111 is the meters of row per hectare at 0.90 m row spacing, and that number is fixed in the calculation — for a field planted with a different spacing, the estimate has to be adjusted by hand. The 15 converts kilograms into arrobas. In the screenshot example, 90.89 structures per meter × 5 g ÷ 1,000 × 11,111 ÷ 15 gives 336.62 @/ha. The numbers are from a real field and are there to show the calculation, not as a yield benchmark.

Other cotton phenology reports under the same theme, for those who need a specific cut: MON.02.P05 (formerly 001.Qb) - Phenologies: Height, STAND, Node Qty, MON.02.P06 (formerly 001.R) - White Flower Position & Node Qty and MON.02.11 (formerly 001.H) - Phenology - Summary - Last of each WEEK.

❓ Frequently asked questions

📘 Screen: Observations

The Observations screen works as a complement to pest monitoring. It shows records entered directly from the app, containing free-form notes, evidence and photos taken in the field.

📍 Location in the system

Menu: Crops > Observations

🧩 Main function

Like the Scouting screen, this screen is not for adding new records, but for:

• Viewing observations recorded in the app
• Adjusting or deleting information, if needed

Observations can include:

• Free descriptive text
• Field and crop
• Photos taken at the time of the note
• Location and date

📊 Dashboards and overall view

Observations are analyzed from the Scouting home dashboard, where they appear grouped together with the scouting.

On the dashboard, the agronomist can:

• View observations by date and field
• Analyze the images captured
• See the map with the georeferenced points
• Follow the crop's growth stage
• Look up the history of the observed pest by field, if there is a reference

❓ Frequently asked questions

📘 Screen: Analyses

The Analyses screen stores in the system the results of samples collected in the crop: the field's soil analysis before planting, the leaf analysis done mid-cycle, the compaction test. Each analysis is tied to the field, the season and the variety, with the levels at each sampled point and the lab report attached.

📍 Location in the system

Menu: Crops > Analyses

🧩 Main function

To centralize the farm's analysis history. Instead of the lab report sitting in an email or a folder on the computer, it is recorded on the field it belongs to — with the levels typed in point by point and the original PDF attached. In the next season, you can open the field and see what the analysis showed.

📝 Main fields

🗂 Additional tabs

Details (analysis points)

This is where the results go. An analysis usually has several collection points within the same field, and each point is a row on this tab:

Levels are typed in as the lab report gives them — the system doesn't convert units or recalculate anything. Each point is saved separately, with the tab's own Save button.

File

Attaches the original report to the analysis: the lab PDF, the spreadsheet with the results, the photo of the soil pit. Each attachment has a Title, Description and Notes, and the View button opens the file in another tab. PDF, images, spreadsheets, text documents, audio, video and compressed files are accepted.

🔧 List features

The list shows Number, Collection date, Type and Field, with search by column. At the top there is a quick filter by type — All, Soil Analysis, Leaf Analysis, Compaction and Other — which comes set to All.

❓ Frequently asked questions

📘 Screen: Bales

The bale — or module — is the roll of seed cotton the picker leaves in the field. In upCampo, each bale is a record with a number, field of origin, variety and harvest date: it is the traceability unit of cotton, which lets you go from a lint bale sold months later back to the field that produced it.

The bale is created here without a weight. It gets its weight at collection, when the truck that takes it to the gin is weighed — and that weight is what adds to the total harvested from the field. A bale recorded with the wrong field means wrong yield in two fields at the same time.

📍 Location in the system

Menu: Crops > Bales

🧩 Main function

Each bale is recorded with its agronomic and geographic characteristics:

• Season
• Field
• Crop
• Variety
• GPS location
• Date the bale was produced

These records can be used later for traceability and logistics control, and they are the basis for collection and storage operations.

🔎 The list and the totals

The screen is called Cotton bales/Tracking item and opens filtered by Season, Start date (from) and End date (to). Next to the filters are three totals for what is being displayed: Farm weight, Gin weight and Qty — the quick way to close out production for a period.

The list shows Code, QR Code/Barcode, Date, Field, Variety/Cultivar, Farm wt., Gin weight, Hectares, Collected?, Bale collection, Fleet, Collection date, Start user, Check user, Collection user, Origin, Border, Burst, Notes and Reference/Integration ID.

📝 Bale fields

⚡ Batch tools

Bales are a high-volume record — one season can run past a thousand. That is why the screen has tools to handle many at once:

Generate multiple in batch

Creates several bales at once, for when the harvest has already happened and nobody entered them bale by bale. Enter Field, Variety, Number of bales, Date, Farm wt., Hectares, shift and border.

• The Get auxiliary qty from WO executions button pulls the quantity from what has already been executed in the harvest work orders — instead of you counting
• Initial QR Code: leave it blank to not generate QR Codes. If you enter one, the system increments it for each bale (0050, 0051, 0052…)

Batch adjustment

Corrects one field on many bales at once. Choose what to change — Field, Variety/Cultivar, Shift, Border, Burst, Farm weight, Gin weight or Hectares —, enter the new value, check the bales in the grid and confirm. It is the way to fix a repeated mistake: the wrong field for a whole shift, the shift entered incorrectly.

View on Map

Shows the bales positioned on the map, based on each one's latitude and longitude — useful for planning the pickup route and for finding a bale that was left behind.

📲 Where records come from

1. From the app

The most common way to record bales is in the app:

• The technician enters the bale as soon as the picker produces it
• Usually a QR Code is stuck on the bale
• The code is scanned later for tracking. For this, you can print numbered labels with report POS.04.02 (formerly 009.A) - Bale labels

In the app, the menu is Bale/item tracking. The BALE/ITEM LIST tab filters by Status, Fleet, Sector and Field, shows the Total items and, for each bale, the number, field, variety, up code, farm weight, status and date. The SUMMARY tab adds up the quantity, pending bales, weights and the average per hectare, with a breakdown by field.

Tapping a bale opens its record: up code, QR Code/Barcode (with the CAPTURE button next to it), Field, Notes, Fleet/Equipment, Operator/Employee, Date, Status, shift (1st Shift or 2nd Shift), Border, farm weight, gin weight and ha. The list's NEW (+) opens the same form blank, already with the next up code, and the button at the bottom is SAVE + NEW, so you can enter one bale after another.

2. From the web portal

• Manual entry by the team, filling in the data

3. Through the John Deere picker integration

• Requires setup by the upCampo team to enable the integration and sync the data automatically
• The Origin column in the list shows where each bale came from — Manual for those entered by hand
• The Import without module button opens the Import JD bales without module window, which lists what John Deere recorded without the module identifier, with date, field, equipment, variety, hectares, weight and operator. Force selected brings those bales in anyway

4. From the machine file

• The Import bales from machine Excel file button, next to the filters, loads the bales from the file generated by the picker itself

🔗 After ginning: the lint bales

When the module goes to the gin and is ginned, the resulting lint is pressed into lint bales — which have their own screen, a GS1 code and separate weights for lint, seed, linters and trash. Each lint bale points to its source module, and that is how traceability runs from the sale back to the field.

🔗 Relationship with Bale Collection

After the bale is recorded, it moves to another stage of the process: bale collection.

• The bale is weighed at collection (manually or through the integration)
• If the picker reports the weight automatically, it is taken into account too
• The recorded weight is used to calculate the field's yield, one of the most important agronomic indicators
• Collection is done in another menu, where you enter where the bale was taken, weight, type of loading, etc.
• Both records are linked and form the bale's complete history

📊 Related reports