Your check frequencies, not ours
- How frequently each device is checked and the next check due date are your own. The file quotes no frequencies from any standard or customer and sets no default.
- A logged check records what was seen on that date. It does not show that the device works at any other time.
What is in the file
- Settings: an as-of date (blank means today).
- Log: check ID, station, device, device type (Sensor, Fixture or locator, Vision, Counter, Other), check method (Master or test part, Function test, Other), checked on, checked by, result (Worked as expected, Did not work, Check not done), next check due, parts made since last good check, parts held, reaction, device restored on, rechecked after repair on, notes.
- A separate check column. Neither the status nor the result hides it, a filled date or number is checked for the cases listed below, and a row can show several notes, joined with a semicolon.
- Counts under the log: rows logged, rows per status, rows with a check note, rows past the next check due date with no later check (any status), a line that should read 0 (rows not in any status), rows per device type and rows per result. No score and no ranking.
How the status is worked out
In this order; the first match wins. A row only reads Restored and rechecked or Next check not due yet when every step before it is filled. Text typed in a date cell counts as blank:
| Status | When |
|---|---|
| Enter check ID | The row has an entry but no check ID. It still counts. |
| Enter station … Enter check method | Station, device, device type and check method (both from a list), in that order. |
| Enter checked-on date, Enter checked by | Date (blank or text counts as blank), then the name. |
| Enter result | Blank, or typed outside the list (Worked as expected, Did not work, Check not done). The result is a dropdown. |
| Enter next check due date | Blank, or text instead of a date. The date is your own entry; the file sets no default. |
| Enter parts made since last good check, Enter parts held | Result Did not work, number blank or not 0 or more. |
| Enter reaction | Result Did not work, reaction blank. |
| Device not restored yet | Result Did not work, restored date blank or text. |
| Recheck after repair not done | Result Did not work, recheck date blank or text. |
| Later check logged | A check with a later date is logged for the same station and device. |
| Check not done | Result Check not done, no later check logged. |
| Next check past due | As-of date after your next check due date, no later check logged. |
| Restored and rechecked | Result Did not work, every step filled, next check not due yet. |
| Next check not due yet | Result Worked as expected, next check due date not passed. |
Check column notes, each followed by "worth a check", on any row whatever its status:
- Next check due date passed, no later check for this device
- Next check due date before the checked-on date
- Device restored before the checked-on date
- Recheck before the device was restored
- Restored or recheck date filled, result is not Did not work
- More parts held than parts made since last good check
- Did not work, 0 parts held
- Parts not a number (0 or more)
- Check ID used on more than one row
- Same station and device checked twice on one date
- A checked, restored or recheck date after the as-of date
- Date not readable (text in a date cell)
- Check not done, nothing written in Notes
- Parts filled, result is not Did not work
Example (fictional)
Made-up stations, names and dates, extract, as of Thursday 22 October 2026 (Thu 22 Oct 2026):
| Check ID | Station | Device | Checked on | Result | Next check due | Status | Check |
|---|---|---|---|---|---|---|---|
| E-01 | Line 1 | Missing-clip sensor | Mon 19 Oct 2026 | Worked as expected | Mon 26 Oct 2026 | Next check not due yet | |
| E-02 | Line 1 | Missing-clip sensor | Mon 12 Oct 2026 | Worked as expected | Mon 19 Oct 2026 | Later check logged | |
| E-03 | Cell 2 | Hole presence pin | Wed 14 Oct 2026 | Did not work | Fri 30 Oct 2026 | Restored and rechecked | |
| E-04 | Line 3 | Label camera | Tue 20 Oct 2026 | Did not work | Tue 27 Oct 2026 | Device not restored yet | |
| E-05 | Press 4 | Stroke counter | Mon 5 Oct 2026 | Worked as expected | Mon 19 Oct 2026 | Next check past due | Next check due date passed, no later check for this device: worth a check |
| E-06 | Line 2 | Torque check | Fri 16 Oct 2026 | Check not done | Fri 23 Oct 2026 | Later check logged | Check not done, nothing written in Notes: worth a check |
| E-07 | Cell 5 | Orientation pin | Wed 21 Oct 2026 | Worked as expected | Tue 20 Oct 2026 | Next check past due | Next check due date passed, no later check for this device: worth a check; Next check due date before the checked-on date: worth a check |
| Line 3 | Part-present sensor | Thu 22 Oct 2026 | Worked as expected | Thu 29 Oct 2026 | Enter check ID | ||
| E-09 | Press 4 | Die-height sensor | Tue 13 Oct 2026 | Did not work | Tue 27 Oct 2026 | Recheck after repair not done | More parts held than parts made since last good check: worth a check |
| E-10 | Line 2 | Torque check | Thu 22 Oct 2026 | Worked as expected | Thu 29 Oct 2026 | Enter checked by |
Worth a check each week
- Devices past your next check due date with no later check logged, whatever the result (red while the status reads Next check past due).
- Rows with Did not work but no restore or recheck date.
- Rows where more parts are held than were made since the last good check, or none are held.
What counts as a good check and what to do with held parts is your call. The file records it and does not judge it.
Related
- Control plan template
- Quality alert log (Excel)
- Production process self-check workbook
- Free 8D and quality tools
Advisory template, in English. Not a customer decision.