These tell you where you are not ready
Not whether you are. A checklist finds gaps quickly before a specific moment — an assessment, a deadline, a review. It is a triage tool, and treating it as anything more is how organisations arrive at an assessment confident and unprepared.
The NCA ECC alone runs to 108 main controls and 92 sub-controls. No checklist covers a framework, and any that claims to is selling you a false position. Ticking every box here means you have not found a gap yet — not that there isn't one.
Checklists
Each one is built for a moment rather than a framework. More are being written — tell us which would help most.
Each checklist carries the date it was last reviewed. Where one refers to a regulatory obligation, the published document from the relevant authority is the authoritative source — these are practical prompts, not legal advice.
Using one without misleading yourself
The failure mode is not a bad checklist. It is a good one used as evidence of readiness.
- 01/05Run it with the people who own the controls
Not alone at your desk. The compliance team's answer to "is access review happening" and the IT manager's answer are frequently different, and the difference is the finding.
- 02/05Treat every unchecked item as a real gap
Rather than something to explain away. The instinct to justify a gap during a checklist is the same instinct that produces a weak answer during an assessment.
- 03/05Write down what you could not evidence
A control you believe operates but cannot prove is a gap, not a pass. This distinction is the whole difference between a programme and a belief.
- 04/05Give every gap an owner and a date
Before you close the page. A gap found and not assigned will be found again next quarter by the same person.
- 05/05Do not report the result upward as a score
"We passed 18 of 20" invites a conclusion the checklist cannot support. Report the gaps and who owns them.
No PDFs, no scores, no forms
Three deliberate omissions, each of which the rest of this category does the opposite of.
And no email gate, here or anywhere else in our resources. If a checklist is useful, it is useful before we know who you are.
- A PDF circulates for years after the requirement changed
- Nobody who has it knows when it was written
- These live on the page, dated, and get updated
- An outdated checklist is worse than none
- A percentage from a checklist is not a compliance position
- It hides which items are missing and whether they matter
- It gets quoted upward and becomes a number nobody can defend
- The gaps are the output — the count is not
Checklist, guide, tool or framework page?
A checklist
A working artefact used during a task, at a specific moment. Scannable, quick, and built to find what is missing rather than to teach you anything.
How to do something end to end, read before the work. Sequenced and opinionated about order. The long one you read properly once.
What a specific framework requires and how it is run. The reference you return to when you need the structure or the scoring.
Interactive rather than static — works out scope, maps controls, counts a clock. Everything runs in your own browser.
What a term means, briefly, for the moment someone uses an acronym in a meeting.
Found a gap you cannot close?
Most of what these checklists surface is ownership and evidence discipline. That is what the platform is for — but the gaps are worth knowing either way.
