A mock demo for certified organic operations
Keep the record file ready. Inspect it any day.
InspectionFile follows one synthetic operation with crop fields and a small goat group: input logs checked against a prohibited-substance list, medication withdrawal records, and a completeness view that assembles it all into an inspection pack.
All data on this site is simulated. 3 of 14 sample inputs are flagged on purpose.
7 of 13 items ready in the seeded file. Open the pack to close the gaps.
Records as you go, not at the end
Same synthetic operation, two very different weeks before an inspection.
Try it: the week before the inspection
- Field historynot started
- Input recordsnot started
- Livestock and withdrawalnot started
- Sign-offsnot started
Receipts, field notes, treatment records and signatures live in different places, so nobody knows what is missing until the pack is built by hand.
What it shows
Field history
Planting, input, grazing and harvest events in date order for each field, with gaps in the look-back period called out.
Prohibited-substance check
Every input in the log is matched against a list, so a prohibited product is flagged the day it is entered, not at the inspection.
Withdrawal gate
Treatment records set a hold date for milk and meat; slide the date to see when each animal clears.
Completeness view
One percentage and a short list of what is still missing, grouped by section, assembled into a pack on demand.
From a daily log to a finished pack
Step 1
Record
Log fields, inputs and treatments as work happens, with the label or receipt attached.
Step 2
Check
Each entry is checked at once against the substance list and the withdrawal periods.
Step 3
Assemble
Generate the pack when it is needed and see exactly what is still missing.
Want this on your own records?
This demo is a sketch of what is possible. Algoshred builds tailored versions for organic operations and the teams that support them.
Talk to Algoshred