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.
- Farm Management System
- Features
- Field work
Field work
Plan assigned tasks and follow the manager approval into execution.
OverviewPlanned Field Tasks×
Farm Management System · Field work
New
Planned Field Tasks
Approval waits for the farm manager
| Task type | Due date | Field | Cycle | Assigned to | Status | |
|---|---|---|---|---|---|---|
| Planting | 12 Oct | FLD-6664 | CC-4201 | Planned | ||
| Irrigation | 23 Oct | FLD-2925 | CC-4219 | Planned | ||
| Feeding | 20 Oct | FLD-4361 | CC-1741 | Planned | ||
| Inspection | 20 Oct | FLD-8843 | CC-8936 | Planned | ||
| Harvest | 06 Oct | FLD-5371 | CC-2801 | Planned |
6 of 6 records
FLD-6664Field tasks · FT-29473
PlantingDue date12 Oct
CycleCC-4201
StatusPlanned
What you can do
Work from the field record
Every task names its type, due date, field, crop cycle and assigned person. A manager reviews planned work before approval. The approval starts the field-work workflow, which checks live field and cycle state and resolves the operator through the person record and user account.
How the work is organized
- Identify the work. Start from the task type, due date, linked field and crop cycle.
- Record the event. Keep the assigned People record linked to the operator account.
- Review the result. Farm Manager approves the task after checking current field, cycle, operator and lot.
Agree who maintains assignments, how completed dates are entered and when cancelled work is distinguished from unfinished work. The task types are planting, irrigation, feeding, inspection and harvest. Review task priority using the due date and cycle stage together.
What to agree during setup
Agree who assigns tasks and who records progress and completion dates. Farm Manager should review changed assignments again before approving a task. Keep the linked People and Users records current so the named operator or reviewer can be found during the rehearsal.
Check the handoff on an actual case
For an irrigation task, confirm that the field and crop cycle are still active, that the assigned operator is the intended person and that the selected input lot has enough stock in the matching unit. After approval, follow the task through work in progress and completion; inspect the linked usage and stock balance.
Have Farm Manager approve the current task, then ask Field Operator to open the assignment and enter progress and a completion date. Compare any usage with the approved task. Open the live record again after a deliberate change and agree who corrects it before the next step.
If the operator assignment changes, Farm Manager should reopen the current task before approving it. The approval checks the person through the linked user account. Field Operator can then follow the due date and current status from the task rather than relying on an earlier instruction from the crew.
What your team sees
- Planned Field Tasks — Shows tasks waiting for the manager decision, with their due dates and assignees.
- My Field Tasks — Shows the operator tasks linked to that person record.
Follow the work through
See the field-to-harvest flow and the data model. The implementation guide gives a small rehearsal scope before a wider operating cycle.
What it keeps track of
Data model- Field tasks
- Planned and executed field work assigned to a person for a specific cycle
- Fields
- Farm fields and plots with area, location and availability status
- Crop cycles
- Crop cycles per field from planned planting through growing, harvesting and close
- People
- Farm staff, operators, reviewers and managers with their authenticated user account and role title
- Input usage
- Input quantities consumed against a field task
Who uses it
Permissions- Farm Manager
- , Field Operator, Admin.
- Farm Manager
- Owns approval; Field Operator records the work; Admin maintains account links.
Set up Farm Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.