Checklist
A verified list of steps used to prevent omissions.
A list so nothing gets missed.
What It Is
You will find Checklist in the Execution layer, alongside the rest of Systems. What it actually refers to is a verified list of steps used to prevent omissions.
It is a repeatable structure, which means it only pays off when it is actually followed through instead of quoted. Once it is defined that clearly, arguments about it usually stop.
How It's Used
Most of the time Checklist is used in project delivery, scheduling and the handover between people doing the work. It is usually discussed together with Standard Operating Procedure, Quality Assurance and Launch Plan. The practical test is whether anyone can follow it without the person who wrote it in the room.
Why It Matters
Ignoring Checklist rarely fails loudly — it fails slowly. When it is unclear, work still happens — it just happens twice. It is worth pinning down before anyone builds on top of it.
Think of a recipe. Follow the steps and you get a predictable result. A list so nothing gets missed.
Termshift™
How the meaning shifts depending on who is using it, and where.
Practitioners use Checklist as shorthand and expect no explanation — a verified list of steps used to prevent omissions.
Outside the industry, most people would just say: a list so nothing gets missed.
The Bottom Line
If you only keep one thing about Checklist: a list so nothing gets missed. Everything after that is detail.