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
- Input stocks and usage
Input stocks and usage
See which lot supplies a task and how much remains after use.
OverviewApproved Field Tasks×
Farm Management System · Input stocks and usage
New
Approved Field Tasks
Start waits for the field operator
| Task type | Due date | Field | Cycle | Assigned to | Status | |
|---|---|---|---|---|---|---|
| Planting | 19 Oct | FLD-8799 | CC-3005 | Approved | ||
| Irrigation | 17 Oct | FLD-7545 | CC-9765 | Approved | ||
| Feeding | 11 Oct | FLD-9421 | CC-2938 | Approved | ||
| Inspection | 08 Oct | FLD-3626 | CC-8499 | Approved | ||
| Harvest | 24 Oct | FLD-9387 | CC-1513 | Approved |
6 of 6 records
FLD-8799Field tasks · FT-85992
PlantingDue date19 Oct
CycleCC-3005
StatusApproved
What you can do
Work from the field record
Input stocks are recorded by input name, lot number, unit, quantity on hand and expiry date. Usage links a quantity and application date to a stock lot and a field task. This lets the team trace a consumed quantity back to the work that needed it.
How the work is organized
- Identify the work. Start from the stock lot number, unit, on-hand quantity and expiry.
- Record the event. Use the task-linked usage row for the amount consumed.
- Review the result. After manager approval, compare the lot balance and usage; the workflow decrements the lot once.
Agree one unit for each lot and make the expiry date part of the approval review. The field-work workflow checks that the lot is unexpired and has enough stock in the matching unit before it appends usage and decrements the balance once.
What to agree during setup
Agree the unit recorded for each lot and who corrects a balance. Stock Keeper checks expiry and quantity before Farm Manager approves field work. 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
Take a feeding task using a named lot. The stock keeper checks the current balance and expiry; the manager approves the task only when its field, cycle, operator and input are valid. Then compare the usage quantity with the changed on-hand balance. A repeated approval should not consume the same quantity again.
Ask Stock Keeper to compare the old and current balance with the new usage row. Check its task and lot references, then repeat the approval case to confirm no second decrement. Open the live record again after a deliberate change and agree who corrects it before the next step.
A stock lot can serve more than one task over time. Review the current balance before each approval and follow each usage row back to its task. An input application records field activity with a named applicator; the task-linked usage remains the record for the stock quantity consumed by approved work.
What your team sees
- Approved Field Tasks — Shows approved tasks that can carry linked consumption.
- Work In Progress — Shows work still underway after the stock decision.
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- Input stocks
- Agricultural input stock lots with quantity on hand, unit and expiry
- Input usage
- Input quantities consumed against a field task
- Field tasks
- Planned and executed field work assigned to a person for a specific cycle
Who uses it
Permissions- Stock Keeper
- , Farm Manager, Field Operator.
- Stock Keeper
- Owns lot records; Farm Manager approves the task; Field Operator follows the work.
Set up Farm Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.