📘 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