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.
- Livestock Management
- Features
- Production review
Production review
Record produced quantity, unit and grade with the cycle and accepting reviewer.
OverviewProduction History×
Livestock Management · Production review
New
Production History
Production records
| Produced at | Cycle | Quantity | Unit | Grade | Accepted by | |
|---|---|---|---|---|---|---|
| 07 Oct | BC-7286 | 120 | UNT-386 | GRD-444 | ||
| 08 Oct | BC-3119 | 620 | UNT-294 | GRD-594 | ||
| 11 Oct | BC-3106 | 460 | UNT-509 | GRD-164 | ||
| 04 Oct | BC-5353 | 910 | UNT-969 | GRD-797 | ||
| 12 Oct | BC-7104 | 290 | UNT-693 | GRD-296 |
6 of 6 records
UNT-386Production records · PR-32714
Produced at07 Oct
CycleBC-7286
Quantity120
GradeGRD-444
What you can do
Make the output traceable to the cycle
Production Reviewer checks each production record for the date, quantity, unit and grade, then records the accepting team member. The result belongs to a specific cycle, which in turn belongs to a pasture. This chain lets Pasture Manager compare planned timing, completed field work and actual recorded output without treating an observation estimate as produced quantity.
More than one record may be needed when output is collected at different times or grades. Each record should carry the actual date and its own unit. A summary by cycle makes sense only after quantities with different units have been kept separate. The reviewer should inspect the source event before accepting a record; a cycle status change alone cannot establish a produced quantity.
How the work is organized
- Identify the source. Link output to the cycle for the pasture where the work occurred.
- Record the result. Enter the actual production date, quantity, unit and grade.
- Name the reviewer. Preserve the team member who accepted the result on the record.
Production Records support both operational review and reporting. The accepted-by link is important because it lets the team distinguish a field entry from a reviewed result. Pasture Manager should reconcile production with completed tasks, especially when a cycle reaches Harvesting or Closed. Closing a cycle should not erase a later correction or the identity of the earlier reviewer.
What to agree during setup
Agree which physical event creates a production record, who enters it and who may be the accepting reviewer. Decide how the farm grades output and which units are permitted for each product. Define the correction path for a wrong quantity or date; a repeated import or repeated human entry must not be counted as additional production. Choose a reporting cutoff so late entries are recognizable.
The team also needs a rule for partial output. A paddock can yield at more than one date. Each portion should have its own recorded evidence and reviewer. Pasture Manager can then assess whether the cycle is truly ready to close rather than inferring completion from one accepted portion.
Check the handoff on an actual case
Start with a cycle in Harvesting and two completed field tasks. Enter a production result with the actual date, quantity, unit and grade. Production Reviewer compares it with the field evidence and records acceptance. Open Production History and confirm that the cycle and reviewer are visible. Pasture Manager checks whether more work or another portion is expected before closing the cycle.
Repeat with a second portion in another unit. Keep it separate in review and reporting. Finally, present a field observation containing an estimated value and ask the reviewer to distinguish it from the produced quantity. This practical case protects the production total from an attractive but incorrect shortcut.
What your team sees
- Production History — Dated accepted results with cycle, quantity, unit, grade and reviewer.
- Cycle Board — The current cycle stage beside the output review.
Follow the work through
Use production review and pasture planning to connect the result to the next cycle.
What it keeps track of
Data model- Production records
- Produced quantities with unit and grade, accepted by a reviewer
- Breeding cycles
- Breeding cycles per pasture from planned start through growing, production and close
- Pastures
- Pastures and paddocks with area, location and availability status
- Pasture tasks
- Planned and executed pasture work assigned to a person for a specific cycle
- Team members
- Farm staff, operators, reviewers and managers with their authenticated user account and role title
- Livestock observations
- Livestock and pasture observations with measured value, unit and notes
Who uses it
Permissions- Production Reviewer
- Checks output and records acceptance.
- Pasture Manager
- Closes the cycle after reconciling work and production.
- Field Operator
- Supplies the actual field evidence that supports the review.
Set up Livestock Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.