Questions, answered

Click Get started, then use Proto to configure Livestock Management for your business. Pilot one pasture cycle with a named manager, operator, feed lot and production reviewer.

Each pasture has a name, field code, location, area and availability status. Agree one code convention before importing older work.

Yes. Link boundary geometry, survey date and measured area to the corresponding pasture, then review any difference from its operating area.

A manager reviews a planned task’s pasture, cycle, assignee and due date before recording Approved. The operator records actual progress and completion separately.

A feed lot holds its on-hand quantity and unit. A usage record connects the consumed quantity and date to the lot and the pasture task.

It is a dated entry for feed applied to a pasture, with quantity, unit and a named applicator. Agree how it relates to a separate lot usage entry.

Record the observation date, type, measured value, unit and notes against the pasture. Use consistent types and units when comparing readings.

The production record links a cycle to the actual date, quantity, unit, grade and accepting team member. The reviewer checks the field evidence before acceptance.

Cycles link to a pasture and retain their own dates, stage, tasks and production records. Agree when a new cycle begins and how overlapping work is handled.

Admin maintains the user and team member links. Rehearse access with a real task and production result before expanding use.