Work Execution

Work Execution is the part of the AgriERP mobile app where actual operational work happens. A spray crew opens it to see today’s work orders. A harvest worker scans bins against the day’s harvest order. A warehouse worker confirms picks and putaways. A field officer logs a grower visit against a follow-up ticket. Every action they take on the mobile app, in the moment, on the work, lands in the system as a structured record that updates inventory, labor, cost, and operational status across the whole business.

This document describes how that work-execution flow plays out on the mobile app: how work orders appear to the worker, how they are started, updated, paused, and completed, and what gets captured along the way.

1. The work-order list

What the work-order list shows

Capability	What it means in practice
Work order number and type	The unique identifier and the type of work (spray, fertilization, pruning, harvest, packing, maintenance, inspection).
Crop, block, and farm	What crop the work is on, which block, on which farm. Workers see the operational context in one glance.
Scheduled timing	The expected start and duration. Time-sensitive work (spray windows, scheduled maintenance) is flagged.
Crew assignment	Who is on the work order: the worker themselves, their crew, or another team they need to coordinate with.
Priority and dependencies	Work orders that block other work, or that have specific timing requirements, are flagged so workers know which to prioritise.
Status	Current state of the work order: Released, In Progress, On Hold, Completed. The state determines what actions the worker can take.
Distance and route	Where the device GPS allows it, the distance from the worker’s current location, and a route to the work-order location on the map.

Filtering and grouping

• Today’s work first: the default view is work for today. The worker sees what they need to do now, not a wall of upcoming and past work.
• By block: workers moving through multiple blocks can group work orders by block, so they complete all work at one location before moving on.
• By status: filter to In Progress to see open work, Released to see ready-to-start, Completed to see what is done.
• Search: where the worker knows a specific work-order number or wants to find a particular block, search jumps straight to it.

2. Starting and executing work

The standard work-execution flow

• Step 1, open the work order: the worker taps the work order from their list. The detail screen opens, showing the full context: what is to be done, on what block, with what inputs and equipment, and any special instructions.
• Step 2, pre-work checks: where the work type requires pre-work checks (spray protocol acknowledgement, equipment pre-use inspection, safety briefing), the checks appear before the worker can start the work. Each check is captured.
• Step 3, start: the worker taps Start. The work order moves to In Progress. The start time and GPS location are captured. The clock is running for cost and time tracking purposes.
• Step 4, capture as the work happens: during the work, the worker captures whatever the work type requires: chemical batch numbers, fertilizer quantities, equipment hours, bin scans, harvest counts, photos, observations.
• Step 5, pause and resume (if needed): work that is interrupted (weather, equipment issue, crew break) is paused, not abandoned. The pause time is captured; when work resumes, the clock restarts.
• Step 6, complete: when the work is finished, the worker taps Complete. Any required post-work data (final counts, summary photos, supervisor verification) is captured. The work order moves to Completed.
• Step 7, supervisor verification (where required): for work types that require supervisor sign-off (high-value work, regulatory work, quality-critical work), the supervisor verifies on their device. The work order is fully closed only after verification.

3. What gets captured during work

Material and input consumption

• Chemicals and fertilizers: for spray and fertilizer work orders, the worker scans the chemical container or selects from the protocol list. Quantity used is captured by container or measurement. The batch number is recorded for traceability.
• Equipment usage: the equipment used on the work order is captured by scan or selection. Hours-meter readings before and after work are entered, contributing to the equipment’s life-cycle data.
• Consumables: packaging, labels, ties, lubricants, fuel, water, captured against the work order with quantity.
• Bin and pallet identification: for harvest and packing work, every bin or pallet is scanned. The system links the bin to the block, the harvest crew, the date, and the work order automatically.

Output and result capture

• Quantity completed: for piece-rate work and quantity-based work orders, the count of completed units is captured: bins harvested, cartons packed, hectares sprayed, trees pruned.
• Quality observations: where the worker notices quality issues during work (pest pressure, disease symptoms, equipment performance problems), they can flag them on the work order. Photos can be attached.
• Photos: photos taken on the work order are captured against it. Pre-work, mid-work, and post-work photos are common for spray and inspection work.
• Conditions and environment: where relevant (spray work, harvest, irrigation), weather conditions and environmental data are captured: temperature, wind speed, humidity, rainfall. Either entered or pulled from weather integrations.
• Notes and observations: free-text notes for anything that needs description: unusual conditions, follow-up needed, supervisor instructions.

Verification and signatures

• Worker confirmation: at completion, the worker confirms the captured data is correct. Their identity is on the record by virtue of being logged in.
• Supervisor sign-off: where required, the supervisor reviews and approves on their own device. The approval is captured against the work order.
• Third-party witness: for some regulatory or certification work, a third-party witness signs off. Captured with their identity, time, and location.
• Photo verification: for some work types, photo-based verification is the proof: a photo of the completed pruning, a photo of the post-spray block, a photo of the bin tag.

4. Updates, exceptions, and follow-ups

Common exception flows

Capability	What it means in practice
Work cannot start	The crew arrives but conditions prevent starting (rain, equipment issue, missing input). The worker captures the reason; the work order is held with the reason on the record; the supervisor and scheduler are alerted.
Work paused mid-execution	Weather change, equipment breakdown, safety issue. Work is paused; the cause is captured; depending on the cause, the work may be resumed later, rescheduled, or escalated.
Quantity short of plan	The worker completes the work but the actual output is significantly below the planned output. The reason is captured; the supervisor reviews the variance.
Quality concern discovered	During work, the worker spots a quality or pest issue that needs follow-up. A scouting ticket is raised directly from the work order; the agronomist sees it.
Equipment fault	Equipment breaks down or shows a fault during use. The fault is captured against the asset; the equipment is automatically marked as needing maintenance; another piece of equipment is needed to continue the work.
Safety or compliance event	A near-miss, an injury, a chemical spill, an exclusion-period breach. Captured immediately with the right notifications to the safety officer and management.

Automatic follow-up generation

• Scouting tickets: quality and pest observations raised on a work order automatically create a scouting ticket for the agronomist, with photos and location attached.
• Maintenance work orders: equipment faults captured during work automatically create a corrective maintenance work order, with the symptom and any photos from the field.
• Replacement work orders: where weather or other issues prevent completion, the original work order is closed with reason, and a replacement work order is created for rescheduling.
• Supervisor alerts: significant exceptions trigger immediate alerts to the supervisor, not just a record on the system. The supervisor can intervene quickly if needed.
• Investigation tickets: where output is well below plan, where input consumption is well above plan, where quality flags repeat in the same block or with the same crew, investigation tickets are raised for the right person to follow up.

In summary

Work Execution on the mobile app is the layer where the field meets the system. Workers see only their own work, sorted by what matters now. Starting, capturing, pausing, and completing each work order is fast and clear, with the right capture tools (scanners, photo, voice, structured forms) for the job. Material consumption, output, conditions, and verification all land on the work order as it happens. When the work does not go to plan, exceptions are captured cleanly and the right follow-up is triggered automatically.

The result is that the system always knows what is happening in the field, in close to real time, accurately, with the audit trail intact. Everything else AgriERP does, costing, profitability, traceability, compliance, depends on this layer being trusted and used.