Field work & work orders
One living record of field work. Assign, execute, verify.
What hurts today
Tasks are assigned over WhatsApp and nobody knows who worked which block yesterday.
The field notebook gets lost, gets wet, or stays in the supervisor's truck while he's on vacation.
There is no photo or timestamp of when a pruning or application happened: audit depends on memory.
The weekly management report is assembled by hand every Monday, two days late.
What the module does
- Work orders created per block and date from the browser, assigned to a team member or a free-text name (a day laborer or contractor with no account).
- Mobile execution with photo, geolocation, real timestamp and the owner's signature.
- Task states: draft, submitted and reconciled, filterable from the list.
- Attachments per task: a photo of the job, notes and whatever measurements the template defines (boxes, bins, hours…).
- Automatic linking to the block and its cost center.
- Filters by status, farm, block and date range, plus free-text search over notes, farm, block and template.
Why WhatsApp and the notebook no longer cut it
For Chilean export fruit, the field-work record is no longer a notebook: GlobalG.A.P. (the IFA v6 norm) and market audits require evidence of every task with date, owner and traceability to the block. Coordinating over WhatsApp and spreadsheets works at 20 hectares; across several farms and dozens of blocks, the data gets lost, gets wet, or stays in the supervisor's truck while he's on vacation.
The notebook and the WhatsApp group don't scale because they aren't queryable: nobody can answer in seconds which blocks still have pending tasks this week or who executed a pruning. And the management report is assembled by hand every Monday, two days late, with data nobody can verify anymore. The field-work record is the foundation for everything else: it feeds costing, compliance and per-person productivity.
The real problem (no marketing)
In an operation with in-house and contractor crews, task control fragments across WhatsApp groups, notebooks and the foreman's memory. Chile's fruit industry has worked against standards like GlobalG.A.P. for years, and there every traceability gap becomes an audit finding or a claim you can't contain.
The underlying cost isn't the paper: it's that every work order without a reliable record breaks the chain to per-block costing and to workforce & payroll. If you don't know for sure which crew did which task, you don't know what it cost or whether the pre-harvest interval was met.
How this module solves it
The module turns every task into a queryable work order: you assign it per block and date from the browser to a team member or a free-text name, it's executed from mobile with a photo, geolocation and real timestamp, and it keeps a clear status, available as GlobalG.A.P. evidence. The flow is the same for in-house and contractor crews:
You assign the work order
Per block and date from the browser, with the task and the notes the owner needs, assigned to a team member or a free-text name.
It's executed from mobile
It logs start and end with a photo, geolocation, real timestamp and the owner's signature. It works in the field even on intermittent signal.
It keeps a status
Draft, submitted or reconciled, filterable from the list and available as evidence for your compliance.
Because each order stays tied to the block and its cost center, labor flows automatically into workforce & payroll and into per-block costing.
Integration with your current stack
Most Chilean crews already coordinate over WhatsApp, so the module doesn't ask you to drop it overnight: it coexists with your tools and becomes the single source the rest feeds from.
That single-source approach only works because block and task are shared master data: what you record here is exactly what postharvest & traceability sees and what reaches costing, with no spreadsheets reconciled by hand.
How to adopt it without slowing the operation
The digital field-work record is adopted mid-season on a Chilean farm without stopping the field: you start with one farm or one task type, not the whole operation at once. A crew learns to clock and close orders from mobile in under a workday, because the interface looks like what they already do on WhatsApp and the supervisor stays the control point.
The field rarely has good signal, so mobile execution works offline: the crew records photo, time and signature at the block, and the data uploads when the phone regains signal. That eliminates the "I'll note it on paper now and enter it later" pattern, which is exactly where data gets lost or altered.
The biggest operational change isn't technological, it's a habit: the supervisor stops forwarding messages and starts assigning and reviewing orders on one screen. Questions that used to take a round of calls —what's pending, who worked which block, how long a task took— now get answered with a filter, and the field lead reclaims the hours that went into coordinating and reconstructing.
As the field-work record becomes the single source, the weekly management report stops being assembled by hand every Monday: it's live and filterable by block, status or task. When the GlobalG.A.P. audit arrives, the evidence for each work order —photo, time, owner— was already recorded, ready to back your compliance folder with no last-minute scramble to reconstruct papers.
That's the underlying difference: moving from an operation that documents when forced to audit, to one that audits what it was already documenting automatically. The first month shows in the Monday report; the first audit is where the field-work record pays for itself, because initial conformity stops depending on anyone's memory.
Metrics you'll move
A digital field-work record moves operational metrics nobody used to measure: the share of orders closed with photo and geolocation, the average time between assigning a task and completing it, and initial conformity when GlobalG.A.P. arrives. These are the numbers that separate an operation that reacts from one that controls.
Each metric unlocks a concrete decision:
| KPI | What it answers | Decision it unlocks |
|---|---|---|
| % WOs with evidence | What share of tasks have photo, time and signature | Where to reinforce records before an audit |
| Mean close time | How long a task takes from assigned to done | Which block is dragging the week's backlog |
| Pending tasks per block | What's left unexecuted as of today | How to redistribute the work before backlog piles up |
That traceability is the foundation of compliance: the same evidence you see here is what backs the audit in postharvest & traceability and the real cost in cost per block.
AgroMind for this module
Sample questions you can ask and get answered in seconds.
- > Which blocks have pending tasks this week?
- > Show me the work orders closed yesterday in block B7.
- > Who executed pruning on block B7 and how long did it take?
You don't need to switch systems to start
It doesn't matter what you use today to track this: if it exports to Excel or CSV, it's in. The Import module — included with your account at no extra cost — uses AI to map your spreadsheet's columns to the right fields, no matter their order, name or language.
Using another system with an API or data export (ERP, HR, BI)? We'll evaluate connecting it directly during your pilot.
What changes in your operation
Full traceability of every task with photo, timestamp and owner.
Frequently asked questions
What does the Field work and work-orders module solve?
How is it different from coordinating tasks over WhatsApp and a notebook?
How do you verify a task was actually executed?
Do I have to drop WhatsApp, Excel or my ERP to use it?
How much does this module cost?
Does it work if I use external contractor crews?
Related modules
Workforce & payroll inputs
Workday records, productivity and piecework per person, backed by field evidence.
Harvest control
From picker to packing with no paper and no double entry.
Postharvest & traceability
The full harvest → packing → dispatch → exporter chain —with shrinkage, discard and audit-ready evidence— in one place.