The version that helps fits on two pages. It removes the first hour of confusion, which is where most of the damage happens.

Forty questions with a deadline, landing on whoever opened the email. What these documents are really asking, and how to answer once rather than every time.

Every growing business accumulates them for sensible reasons. How to find shared accounts, fix them in order of consequence and keep the list current.

Almost every business says it has backups. Far fewer can say when somebody last restored one. Four questions and a quarterly habit that close the gap.

Your IT provider owns their scope, not your risk. What the ownership role actually involves in a business that has no specialists.

The messages that cost money are the ones filters cannot judge. The control that works is a documented rule about who can change what, and how you verify.

The useful version is a few pages, not a binder. It answers one question: if something we depend on stops working, what do we do in the first day.

Your business runs on other people's software. The questions worth asking before you sign, because almost none of them can be asked usefully afterwards.

When someone leaves, the laptop comes back but the accounts often stay open. How to build an offboarding list that actually closes the gaps.

Annual security modules get completed and forgotten. A lighter approach that ties awareness to the work your team actually does.

Cyber risk gets decided in operating meetings, not server rooms. What leadership actually owns, three questions worth asking, and a practical place to start.