← Book examples

Everyday work

Check More Often, Follow Up Better

A review of around 300 partner websites became a weekly process, with evidence and exceptions for a person to examine.

A companion to the book

A recurring check that took a week

Nathan’s business reviewed around 300 partners’ websites to check how they promoted finance. A quarterly review could occupy one person for a week.

In the admin chapter, he describes giving AI a checklist and asking it to produce a spreadsheet of findings. The business could then run the review weekly and concentrate its attention on the issues found.

Make the evidence usable

A finding needs the page address, the check applied and evidence of what appeared on the page. Record when it was checked. An inaccessible page belongs in an unverified list, so someone can follow it up.

Use current requirements supplied or confirmed by the responsible person. A review against a checklist is not a certification of compliance. Nathan’s example concerns his own workflow, rather than a universal set of rules for other businesses.

Start with a sample

Run the checklist against a small group you can manually review. Compare what was found, adjust ambiguous instructions and decide who will handle exceptions. Only then expand the process.

Use the review checklist.

TRY THE PROMPT

Review these [pages/documents] against the checklist I supply. Record the source, date checked, requirement, evidence and finding for each item. Mark inaccessible or ambiguous items as unverified. Do not mark a requirement as passed without evidence. Prepare an exceptions list for the responsible person to review.