Turning a checklist into a useful note

Most of us have checklists lying around: for packing, for setting up a new laptop, for closing the month's accounts, for preparing a room before guests arrive. They are some of the most useful things we write, and almost none of them would help a stranger. A checklist written for yourself is full of shorthand, missing steps you do without thinking, and silent about why any of it matters.

That gap is an opportunity. Turning a private checklist into a public note is one of the most reliable ways to write something genuinely useful. Here is how we would go about it.

A list is not yet a note

Look at a typical personal checklist:

• Charger
• Backup
• Check the thing with the router
• Email J.

Every line makes sense to the person who wrote it, and none of them make sense to anyone else. "Backup" of what, to where? Which thing with the router? Who is J., and what does the email say? The list works because its author carries the missing context in their head.

A note has to carry that context on the page. That does not mean turning each line into a paragraph. It means asking, for every item, what a reasonably capable reader would need to know to do it without guessing. Sometimes the answer is nothing. Often it is one short phrase.

Start with who it is for and when they will use it

Before you touch the items, write two sentences at the top of your draft, even if you delete them later:

• Who will use this? ("Someone moving their writing from one computer to another for the first time.")
• When will they use it? ("The evening before, with both machines on the desk.")

These two answers decide almost everything else. They tell you which steps you can assume and which you must spell out. They tell you whether the reader is calm and has time, or is in a hurry and needs the short version first. They also give you the opening of the note, because a reader wants to know straight away whether the checklist is meant for them.

Give each item a verb and an end state

The single most effective edit you can make to a checklist is to start every item with a verb and finish it with what "done" looks like.

• "Backup" becomes "Copy your drafts folder to an external drive, and open one file from the copy to check it worked."
• "Charger" becomes "Pack the charger and the cable, and plug them in once before you leave."

The verb tells the reader what to do. The end state tells them when they can stop and move on. Without the end state, people either stop too early or keep fiddling because they are not sure. With it, each item becomes something you can tick with confidence.

Keep the items short. If an item needs more than two sentences, it is probably two items, or it needs its own small section below the list.

Add the why, but only where it matters

Not every step needs a reason. "Pack the charger" explains itself. But some steps look optional to a newcomer, and those are exactly the ones people skip. Give those a short reason, in the same line or right after it:

• "Open one file from the backup. A copy that never opens is not a backup."
• "Write down the old settings before you change them, so you can put them back if something goes wrong."

A useful test: if you have ever skipped a step yourself and regretted it, that step deserves a sentence of explanation. Your own mistakes are some of the best material you have, and readers trust a checklist more when it is clear the author has made the mistakes it warns about.

Order, group and separate the "before you start" items

Private checklists are often in the order things occurred to us. Public ones should be in the order things are done. Walk through the task, or imagine it carefully, and reorder the items to match.

Then look for natural groups. A checklist with twenty items is tiring. The same twenty items under four headings, such as Before you start, Setting up, Checking it works and Afterwards, are much easier to follow and to come back to. Put anything the reader must gather or decide in advance into the first group, so they do not discover halfway through that they needed a password or a cable they do not have.

Headings help in another way on NoteNew. Long notes get a table of contents built from their headings, so a checklist split into clear sections lets a returning reader jump straight to the part they need. The features page describes how that works.

Test it, then keep it current

Before you publish, test the checklist. The best test is to hand it to someone who has never done the task and watch where they hesitate. If that is not possible, put the draft away for a few days and then follow it literally, doing only what each line says. Every time you have to fill in a gap from memory, add what was missing.

A checklist note has a longer life than most writing, because people come back to it each time they repeat the task. That also means it can go out of date. When something changes, update the note and say so with a short line near the top, for example "Updated in October: step 4 now covers the newer settings menu." Readers would much rather see an honest update than discover a stale step on their own.

Two more small things make a checklist note easier to find again. Give it a plain, specific title; our note on titling a note clearly has some suggestions. And tag it with the subject it covers, so it sits on the topic page next to related notes from other writers.

The finished note will probably be three or four times longer than the list you started with. That is fine. Every added word is context you used to carry in your head, now written down where someone else can use it.