Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Farm Management System
- Survey source
- User identity
Farm Management System links a named field to its crop cycles, assigned tasks, input use and harvest records. A farm manager can plan a crop and the work due for it, then follow field progress on the Crop Cycles board.
Crop cycles in one list
Farm Manager decides whether planned field work can proceed after the live checks.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep field identity, area, location and surveyed geometry together.
Planted waits for the farm manager
| Field code | Name | Area hectares | Location | Status | |
|---|---|---|---|---|---|
| NF-01 | North Field | 920 | North of packing shed | Available | |
| RP-02 | River Plot | 570 | Beside lower irrigation pond | Available | |
| EB-03 | East Bench | 20 | East terrace below windbreak | Available | |
| TUN-02 | Tunnel 2 | 230 | High tunnel row 2 | Available | |
| OE-05 | Orchard Edge | 500 | Along west orchard boundary | Available |
Follow each crop and variety from plan through harvest and close.
Approval conditions
| Crop name | Variety | Field | Expected harvest | Status | |
|---|---|---|---|---|---|
| Spring romaine, North Field | Little Gem romaine | River Plot | 17 Oct | Planned | |
| Summer sweet corn, River Plot | Golden Crest sweet corn | Tunnel 2 | 11 Oct | Planned | |
| Autumn carrots, East Bench | Nantes carrot | North Field | 24 Oct | Planned | |
| Winter spinach, Tunnel 2 | Bloomsdale spinach | Creek Row | 26 Oct | Planned | |
| Spring peas, Orchard Edge | Sugar snap pea | Tunnel 2 | 27 Oct | Planned |
Plan assigned tasks and follow the manager approval into execution.
Approval waits for the farm manager
| Task type | Due date | Field | Cycle | Assigned to | Status | |
|---|---|---|---|---|---|---|
| Planting | 20 Oct | Creek Row | Spring peas, Orchard Edge | Leila Haddad | Planned | |
| Irrigation | 31 Oct | South Block | Summer sweet corn, River Plot | Sofia Chen | Planned | |
| Feeding | 28 Oct | River Plot | Fall kale, Hill Field | Rafael Mora | Planned | |
| Inspection | 28 Oct | North Field | Winter spinach, Tunnel 2 | Sofia Chen | Planned | |
| Harvest | 14 Oct | River Plot | Spring romaine, North Field | Owen Brooks | Planned |
See which lot supplies a task and how much remains after use.
Start waits for the field operator
| Task type | Due date | Field | Cycle | Assigned to | Status | |
|---|---|---|---|---|---|---|
| Planting | 27 Oct | Hill Field | Summer sweet corn, River Plot | Rafael Mora | Approved | |
| Irrigation | 25 Oct | Hill Field | Spring peas, Orchard Edge | Mina Park | Approved | |
| Feeding | 19 Oct | South Block | Winter spinach, Tunnel 2 | Sofia Chen | Approved | |
| Inspection | 16 Oct | Orchard Edge | Spring strawberries, Creek Row | Priya Nair | Approved | |
| Harvest | 01 Nov | North Field | Winter spinach, Tunnel 2 | Rafael Mora | Approved |
Keep dated quantity, unit, grade and reviewer with the crop cycle.
Harvests
| Harvested at | Quantity | Unit | Grade | Cycle | Accepted by | |
|---|---|---|---|---|---|---|
| 18 Oct | 340 | kg | Grade A | Spring strawberries, Creek Row | Rafael Mora | |
| 23 Oct | 330 | tonnes | Grade B | Fall kale, Hill Field | Jonah Reed | |
| 21 Oct | 300 | liters | Processing grade | Fall kale, Hill Field | Mina Park | |
| 16 Oct | 300 | hectares | Fresh market premium | Winter spinach, Tunnel 2 | Jonah Reed | |
| 20 Oct | 930 | bushels | Juice grade | Spring romaine, North Field | Amara Bello |
Capture field measurements and named input applications.
Field observations
| Observed at | Observation type | Value | Unit | Field | |
|---|---|---|---|---|---|
| 19 Oct | Pest pressure | 260 | kg | South Block | |
| 11 Oct | Soil moisture | 100 | tonnes | South Block | |
| 13 Oct | Leaf color | 380 | liters | Creek Row | |
| 17 Oct | Irrigation coverage | 170 | hectares | East Bench | |
| 17 Oct | Disease symptoms | 710 | bushels | River Plot |
Field plan to harvest record ships ready to use. 2 steps need a named approval before the work moves on: Approve field work (Farm Manager) and Review harvest (Harvest Reviewer).
Name the plot, location and area before planning a crop.
Link crop, variety and expected harvest to the field.
Give the task a date, field, cycle and assigned person.
Farm Manager checks the current field, cycle, operator and input lot.
The approved task records consumption against its checked lot.
Harvest Reviewer checks the dated measured record and linked cycle.
Open any crop cycle to see its field tasks, the roles that work on it, its process stages and its approvals on one page.
Variety, Field, Planted at and Expected harvest.
Each line is linked to this crop cycle.
Farm Manager, Field Operator and Harvest Reviewer, each with their own permissions.
Plan field work and Record harvest, with the role that acts.
Approve field work and Review harvest, with who decides.
Little Gem romaine · Planted
| Task type | Due date | Field |
|---|---|---|
| Planting | 20 Oct | Creek Row |
| Irrigation | 31 Oct | South Block |
| Feeding | 28 Oct | River Plot |
Stock Keeper maintains lots; Harvest Reviewer checks harvest evidence.
Signed in as Farm Manager
| Decision | Approver | |
|---|---|---|
| Approve field workFarm Manager checks the current field, cycle, operator and input lot. | Farm Manager | |
| Review harvestHarvest Reviewer checks the dated measured record and linked cycle. | Harvest Reviewer | |
| Approve field tasks | Farm Manager | |
| Approve Harvests | Harvest Reviewer |
Everyone opens Farm Management System to the work that is theirs. Pick a role to see what it starts with.
Owns field availability, crop plans and approval of field work.
This is the first screen this role sees.
Crop cycles · Farm Manager
Carries out assigned field work and records field activity.
This is the first screen this role sees.
Crop cycles · Field Operator
Maintains input lot identity, balance, unit and expiry information.
Reviews dated harvest evidence for the linked crop cycle.
This is the first screen this role sees.
Crop cycles · Harvest Reviewer
Maintains people and user access and can inspect operational records.
Read crop progress, field work, input lots and harvest evidence.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 43 | ||
| Planted | 27 | 63% | |
| Growing | 15 | 56% | |
| Harvesting | 7 | 47% |
Sample counts per stage
Show each field's crop names, varieties, planting dates and cycle status.
Show task type, due date, assigned person, field and status.
Group completed task types and completion dates by crop cycle.
Show each lot's input name, unit, quantity on hand and expiry date.
Group usage quantity and application date by task and input lot.
Group recorded quantity, unit and grade by crop cycle.
Group observation type, measured value and observation date by field.
Group applied input names, quantities and dates by field.
See how Farm Management System fits your kind of team.
Each stage of field plan to harvest record names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare field records and review the next decision.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 11 tablesStart with one team and one process, then add the rest once the basics are running.
Set field codes, names, locations, areas and availability values with Farm Manager.
Record crop, variety, planting and expected harvest dates on a representative field.
Link People to Users, then assign a task to the right person and cycle.
Check the lot unit, balance and expiry; let Farm Manager approve the planned task.
Record dated quantity, unit and grade, then let Harvest Reviewer inspect the live record.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Farm Management System for your business. Begin with one field, one crop cycle, an assigned task, a current input lot and a dated harvest record.
A crop cycle links a named crop and variety to a field. It carries planting and harvest dates and moves through planned, planted, growing, harvesting and closed stages.
A field task connects its task type and due date to a field, crop cycle and person. The operator can follow the assigned work in My Field Tasks.
Farm Manager reviews planned work. Approval starts checks on the live field, cycle, assigned person and input lot before consumption is recorded.
Each stock lot carries an input name, lot number, unit, quantity on hand and expiry date. Usage ties consumed quantity to the lot and field task.
The Crop Cycles screen has a stage board, field, stage and intake-period filters, a chronological cycle list and harvest evidence.
Harvests carry the dated measured quantity, unit and grade for a linked crop cycle. Harvest Reviewer checks the current record.
Yes. Field Observations record a date, type, measured value, unit and notes with the field.
A boundary record links surveyed geometry, survey date and area to a field. Agree the survey source and the owner of changes during setup.
Use the roles and linked People and Users records to assign responsibility. Rehearse the permissions with a field task and harvest before a wider rollout.
Start free, then use Proto to change fields, steps and approvals before your team goes live.