What does a checklist maker do?
A checklist maker turns what must be true for a job to go right into a list that people can complete the same way every time. Whatever tool you use, it has to do four things:
- Capture the checks. One line per check, written so two people would give the same answer.
- Record the result. Who completed it, when, where, and the pass, fail or not applicable result for each item.
- Hold the evidence. A photo or note when something is wrong, so whoever fixes it knows what was seen.
- Start the fix. A failed check should lead to an action with an owner and a due date, not just a cross on a sheet.
Most checklists people make at work fall into a few types:
| Checklist type | Example | Who completes it | Typical cadence |
|---|---|---|---|
| Pre-start or pre-use | Machine, vehicle or forklift pre-start | Operator | Every shift or every use |
| Inspection | Area, equipment or 5S inspection | Team leader or technician | Daily or weekly |
| Audit | Layered process audit, safety walk | Leaders at several levels | Daily to quarterly by layer |
| Procedure | Changeover, start-up, shutdown, cleaning | Operator or crew | Each time the task is done |
| Handover | Shift handover, job handover | Outgoing team leader | End of every shift |
How do you make a checklist?
Use the same steps whatever tool you build it in:
- Pick one task, asset or area. A checklist that tries to cover a whole site gets ticked without looking.
- List what must be true. Work from the procedure, the set-up sheet, the risk assessment and recent incidents or defects.
- Write each line as a check. Something the person can see, measure or test, with the standard stated.
- Add the response to a fail. Stop, contain, fix now, or raise an action and tell the team leader.
- Set who and how often. Name the role that completes it and the frequency, based on risk.
- Trial it at the work. Have two or three people use it for a week, then cut or reword the items they answered differently.
- Review the results. Bring failed checks to the team's daily meeting and look for the ones that fail again and again.
What makes a good checklist item?
The quality of a checklist is the quality of its items. Compare these:
| Weak item | Strong item |
|---|---|
| Guarding OK? | All fixed guards fitted and undamaged; interlocked doors stop the machine when opened |
| Check tyres | Tyre pressure within the range on the plate; no cuts or bulges in the sidewall |
| Area clean | Walkways clear and floor dry, matching the 5S photo standard for this area |
| Paperwork done | Batch record signed for each step before the product leaves the line |
Five rules cover most of it: one check per line, make it observable, state the standard, use pass or fail rather than a rating, and say what happens on a fail. Mark the few safety-critical items as hold points, where work must not continue until the check passes.
Checklist maker template
Use this blank layout to draft a checklist before you build it in any tool:
| # | Check | Standard (what good looks like) | Pass | Fail | N/A | Response if failed | Hold point? |
|---|---|---|---|---|---|---|---|
| 1 | ☐ | ☐ | ☐ | ☐ | |||
| 2 | ☐ | ☐ | ☐ | ☐ | |||
| 3 | ☐ | ☐ | ☐ | ☐ | |||
| 4 | ☐ | ☐ | ☐ | ☐ | |||
| 5 | ☐ | ☐ | ☐ | ☐ | |||
| 6 | ☐ | ☐ | ☐ | ☐ | |||
| 7 | ☐ | ☐ | ☐ | ☐ | |||
| 8 | ☐ | ☐ | ☐ | ☐ |
Checklist title: ________ Area / asset: ________ Completed by (role): ________ Frequency: ________ Owner of the checklist: ________ Version and date: ________
Paper, spreadsheet or checklist app: which should you use?
| Paper | Spreadsheet or document | Checklist app | |
|---|---|---|---|
| Quick to start | Yes | Yes | Needs setting up |
| Completed at the work | Yes | Rarely | Yes, on a phone or tablet |
| Photos of what was found | No | Awkward | Yes |
| Recurring schedules and reminders | No | No | Yes |
| Failed checks tracked to closure | Only by hand | Only by hand | Yes |
| Trends across shifts and sites | No | With effort | Yes |
Paper is fine for one area with a leader who reviews every sheet. Once you need evidence, follow-up on fails and a view across teams, a spreadsheet becomes a second job and an app is the better checklist maker.
Why do checklists stop working?
Checklists fail when items cannot fail, when the list is too long to read, and when a ticked fail never leads to a fix. Review each checklist at least once a year with the people who use it: remove items that have not failed unless they are safety-critical, add checks for recent incidents and defects, and keep a version date so everyone knows which list is current.
Step by step
- Choose the scope. Pick one task, asset or area and the standard the checklist protects, such as the procedure, set-up sheet or risk assessment.
- Write the checks. Turn each point into one observable check with the standard it is judged against and a pass, fail or not applicable result.
- Add the response to a fail. For each check, say what to do on a fail, and mark the safety-critical items as hold points.
- Set who and how often. Name the role that completes the checklist and the frequency, based on risk and how fast conditions change.
- Trial and refine. Have a few people use it at the work for a week, then cut or reword items they answered differently.
- Review the results. Bring failed checks and open actions to the team's daily meeting and look for checks that fail repeatedly.
A worked example
A metal fabrication shop in western Sydney had a different paper pre-start sheet for each press brake, written by whoever ran the machine first. The production supervisor used one checklist maker layout to rebuild them as a single 9-item pre-start per machine type, each line with its standard and three hold points: guards and light curtains, emergency stop test and tooling secured. Operators flagged two light curtains that had been muted for months in the first week, and the repeat fails on worn tooling went to the Tier 2 meeting as one maintenance action instead of a string of notes.