A quality problem found at the customer is harder to fix than one found at the bench. But a clipboard check gets skipped when the line is busy. I want a form so short that inspectors fill it in as each batch ends, and so specific that the result is a decision, not a feeling.
Use this when
- You inspect batches or lots of a physical product, in a workshop, a kitchen or a small factory.
- You want a pass, hold or reject decision recorded with the checks behind it.
Skip it when
- You need to store instrument readings in a lab system. The form takes numbers and text, not equipment data.
- You inspect a place, not a product. A safety inspection checklist fits that better.
What is asked, and why
Inspector, date and batch tie the record to a product. Units checked and units failed give a count. The tick lists show which checks passed and which defects appeared. The decision is the one answer a production lead needs, and the last box records what must change.
What the inspector's AI would ask
"Which batch are you checking?" Then "How many units did you check?" Then "How many failed?" It shows the answers and sends them only after a yes. See agent-fillable forms.
Where it fits
Many teams call this a QC form. A kitchen can pair it with a restaurant opening checklist for the start of the day. More tools are in IT and operations forms.
Questions
How do I get a failure rate per product?
Download the CSV and divide `units_failed` by `units_checked` for each row. Group rows by `product_or_batch` to see which product fails most often.
Can I change the list of checks?
Yes. The options are yours to rewrite for your product before you publish. Keep each option short, so it reads well on a phone.
What if a batch needs a recheck?
Send a second entry for the same batch with the new decision. Sort the CSV by `product_or_batch` to see the first check and the recheck side by side.