Questions, answered

Click Get started, then use Proto to configure Precision Agriculture Platform for your business. Start with a small set of fields, one active crop cycle and a real task your manager can review.

A field has a name, code, location, area and availability status. Its boundary record adds dated geo JSON geometry and surveyed area.

Yes. Each cycle links to a field and carries its own crop, variety, dates and status. Tasks and harvests reference the intended cycle.

Record them as field observations with date, type, value, unit and notes. Keep the field reference accurate so the manager sees the right history.

Farm Manager reviews a Planned task’s field, cycle, owner and due date before changing it to Approved.

After the clerk checks an eligible lot and the manager approves the task, input use records the task, lot and quantity while reducing the lot balance. A field application separately records what was applied, where and by whom.

Stock Clerk checks the input name, lot, unit, expiry and quantity on hand against the planned task.

Harvest Reviewer checks the dated harvest’s quantity, unit, grade and linked cycle, with the named reviewer on the harvest record.

Yes. Agree the field reference, date, area or measurement unit and source mapping before bringing records into the field history.