Continuous improvement
Check sheet vs checklist: examples and uses
Compare a check sheet with a checklist. Use a published order-inspection example to separate event counts from task completion.
A check sheet collects observations in a form that makes them easy to count or analyse. A checklist confirms that specified actions or conditions have been checked.
The marks can look similar. Their units tell you what the record means.
ASQ's check-sheet guidance starts with defining the event, collection period and recording method. That definition prevents a completed task from being mistaken for evidence that no defects occurred.
Count defects in a published example
Minitab's printing-order example inspects 50 orders. It records two incomplete orders, one order that is both damaged and incorrect, and three orders with typos. Six orders have problems, containing seven defects.
The same order contributes two different defect observations. That is legitimate in this check sheet because the sheet counts defects, not unique defective orders.
| Defect category | Count |
|---|---|
| Incomplete | 2 |
| Damaged | 1 |
| Incorrect | 1 |
| Typo | 3 |
| Total defects | 7 |
Keep completion checks separate
A checklist for conducting an inspection would record whether the required checks were completed. Completing every checklist item does not establish that every inspected order passed.
| Record | Unit represented by a mark | What a blank means |
|---|---|---|
| Defect check sheet | One observation under a defined counting rule | Requires a declared distinction between zero observations and missing data |
| Task checklist | A completed or verified item | Usually an incomplete or unrecorded check, depending on the procedure |
Keep the inspected volume with the counts. Seven defects among 50 orders means something different from seven defects among a much larger sample. The DPU and DPMO guide follows the denominators through the calculation.
Design the sheet around the next analysis
Retain the date or period, product and other grouping fields needed to investigate the result. A grand total with no useful grouping may leave the team unable to examine where the problem occurs.
Choose whether a record can enter several categories. If it can, do not later add the category counts and call the sum unique orders. If it cannot, document the rule for deciding which category takes priority.
The Pareto guide shows why counts, delay and cost can produce different priorities. The collection sheet must preserve the information needed for the measure you intend to use.
Trial the form before collecting a large dataset
Ask the people doing the work to record a short run of actual observations. Compare how they interpret the categories and handle blanks or multiple defects. Revise unclear instructions before extending collection.
Use the check sheet to answer how often the defined events occur. Use a checklist to confirm the required work. Keep both records when the process needs both answers.