These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Plantation Management
- Features
- Field work
Field work
Assign planting, irrigation, feeding, inspection and harvest work to people and cycles.
OverviewInput Usage Log×
Plantation Management · Field work
New
Input Usage Log
Input usage
| Task | Input | Quantity | Applied at | Input unit | Input lot number | |
|---|---|---|---|---|---|---|
| FT-9117 | IS-39167 | 180 | 08 Oct | IU-852 | L26-5814 | |
| FT-1200 | IS-90872 | 590 | 11 Oct | IU-616 | L26-9191 | |
| FT-9620 | IS-87905 | 690 | 13 Oct | IU-971 | L26-4491 | |
| FT-8602 | IS-78001 | 880 | 14 Oct | IU-719 | L26-2156 | |
| FT-7890 | IS-82983 | 250 | 05 Oct | IU-396 | L26-3700 |
6 of 6 records
IU-852Input usage · IU-87420
TaskFT-9117
InputIS-39167
Quantity180
Applied at08 Oct
Input lot numberL26-5814
What you can do
Put each job against its field and crop
A field task records the kind of work, due date, assigned person, field and crop cycle. Planting, Irrigation, Feeding, Inspection and Harvest are separate task types, giving the supervisor a way to plan the field week and review what has finished. A task can be Planned, Approved, in progress, Completed or Cancelled. The manager’s approval is the decision to release planned work; the operator executes approved work after the field and cycle checks pass.
The field and cycle links matter together. A task pointed at the right person but the wrong crop produces misleading activity and input totals. The supervisor should compare the cycle’s field with the task field before approval. Restricted field status warrants a separate review. A due date helps plan a day of work, while the completion date shows when the task actually finished. The schedule is a due-date calendar, rather than a timed shift reservation.
How the work is organized
- Assignment. Plantation Manager selects task type, field, cycle, due date and the person who will do the work.
- Decision. Plantation Manager reviews the context and approves a planned task when it is ready to proceed.
- Completion. Field Operator records applied input where relevant and finishes or cancels the task with the right status.
What to agree during setup
Define which tasks require input quantities and who maintains the lot reference. Agree what makes a task Approved and how a supervisor handles a task that should be cancelled rather than completed. Establish whether an inspection produces a field observation and when the measurement should be recorded. Match the People directory to active plantation staff and their platform users, especially when one person works across several fields. Set a practical daily review of overdue planned and approved tasks.
Check the handoff on an actual case
For a growing cycle on North Ridge, create an irrigation task assigned to a staff member for tomorrow. Check the field, cycle and assignee before the manager marks it Approved. The operator executes the approved task. If it needs input, the application uses the first-expiry eligible lot, records usage and reduces that lot balance once before completion. The task should then show a completion date and status. Compare its input quantity with the usage entries and the lot balance. If the field becomes Restricted or the crop cycle is no longer in an active stage, correct the field or cycle before attempting execution. This case keeps the planned job, the applied quantity and the responsible person connected.
What your team sees
- Open Field Tasks — Review planned, approved and in-progress jobs that still need attention.
- Field Task Board — Compare task status across the field workload.
- Field Tasks Schedule — See due dates with field, cycle and assigned person.
Follow the work through
What it keeps track of
Data model- Field tasks
- Scheduled and executed field work assigned to plantation staff.
- Fields
- Registered plantation fields with area, location and operational status.
- Crop cycles
- Crop cycles planted on a field, from planning through harvest closure.
- People
- Plantation staff and crew members referenced by operational records.
- Input usage
- Input quantities applied against field tasks, with lot traceability.
Who uses it
Permissions- Plantation Manager
- , Field Operator, Stores Clerk and Admin.
Set up Plantation Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.