Logbook & work orders

Why WhatsApp and the notebook no longer cut it

For Chilean export fruit, the logbook 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 logbook is the foundation for everything else: it feeds costing, compliance and crew 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, crew and date from the browser, the crew executes it from mobile with a geolocated photo and real timestamp, and it keeps a clear status and immutable history, ready as GlobalG.A.P. evidence. The flow is the same for in-house and contractor crews:

1. 01

   You assign the work order

   Per block, crew and date from the browser, with the task, expected staffing and the notes the foreman needs.

2. 02

   The crew executes from mobile

   It logs start and end with a geolocated photo, real timestamp and the owner's signature. It works in the field even on intermittent signal.

3. 03

   It keeps status and history

   Pending, in-progress, completed or flagged, in a history that isn't edited retroactively and links straight to the compliance folder.

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, crew and task are shared master data: what you record here is exactly what traceability & compliance sees and what reaches costing, with no spreadsheets reconciled by hand.

How to adopt it without slowing the operation

The digital logbook 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 logbook becomes the single source, the weekly management report stops being assembled by hand every Monday: it's live and filterable by block, crew or task. When the GlobalG.A.P. audit arrives, the evidence for each work order —photo, time, owner— is already linked, 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 logbook pays for itself, because initial conformity stops depending on anyone's memory.

Metrics you'll move

A digital logbook 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:

That traceability is the foundation of compliance: the same evidence you see here is what backs the audit in traceability & compliance and the real cost in cost per block.