Most writers who search for a self-editing checklist end up downloading the same list everyone else has. It tells you to cut adverbs, watch your passive voice, and vary your sentence openers. You skim it once, nod, and then keep making the exact mistakes you made before you found it. That’s not because the list is wrong. It’s because the list wasn’t built for you.
A generic checklist is written to catch every writer’s faults at once, so it ends up catching almost nothing about any single writer. You don’t overuse adverbs and passive voice and long openers and weak verbs in equal amounts. You have your own small set of tics, usually no more than four or five, that show up again and again in your drafts. Nobody else’s checklist knows what those are. But you already have the proof sitting in your own folders.
I’ve spent the last five years writing daily, mostly long-form pieces that go through several drafts before anyone else sees them. Somewhere around year two, I noticed I kept fixing the same three problems in every single edit pass, no matter what the topic was. That repetition is what pushed me to stop editing from memory and start editing from evidence pulled out of my own old files. This piece walks through the exact method I built from that habit, called the error harvest, and how you can run it on your own drafts in under an hour. Rohan Ratnayake has been exploring and writing about Digital Writing Workflows & Craft for years, bringing research, cultural context, and clear explanations to readers.
Why Downloaded Checklists Don’t Match Your Writing
A checklist made for the average writer is trying to solve an average problem, and no writer is average. Think about two people who both write blog posts. One of them writes in short, choppy sentences and needs to be told to combine ideas. The other writes long, winding sentences and needs to be told to cut them apart. A generic checklist that says “watch your sentence length” is technically true for both of them and useful for neither, because it doesn’t tell either writer which direction to correct in.
The deeper issue is that a checklist built from someone else’s habits is really a checklist built from someone else’s writing samples. Editing advice comes from books, courses, and articles written by people describing patterns they noticed in their own drafts or their students’ drafts. Those patterns are real, but they belong to a different set of writers. You inherit their fixes without inheriting their actual problems.
There’s also a volume problem. Most downloaded lists run fifteen to thirty items long, covering grammar, structure, tone, and formatting all at once. When a list is that long, your eyes glaze over by item eight, and the items that would have actually caught your mistakes get buried under items that never apply to you. A checklist only works if you can hold it in your head while you edit. Once it turns into a document you have to reread every time, you stop using it.
Here’s a quick comparison of what a downloaded checklist tends to look like against a checklist built from your own drafts:
| Feature | Generic Downloaded Checklist | Checklist Built From Your Drafts |
|---|---|---|
| Number of items | 15–30, covers many writers | 5–8, covers your actual habits |
| Source of rules | Other people’s writing patterns | Your own archived drafts |
| Wording style | Broad virtues (“be concise”) | Specific actions (“search for ‘very'”) |
| Update frequency | Rarely updated, feels static | Reviewed and revised every few months |
| Time to apply during editing | Long, easy to skip sections | Short, fits in one editing pass |
| Catches your top mistakes | Sometimes, by chance | Reliably, because it was built from them |
The Error Harvest Method, Explained
The error harvest is a short process where you read a sample of your own old drafts, not to edit them again, but to mine them for patterns. You’re not looking for every mistake in the draft. You’re looking for the mistakes that show up more than once, because those are the ones costing you time and quality in every piece you write, not just this one.
The name matters because it changes how you approach the drafts. You’re not rewriting them. You’re not judging them. You’re walking through old work the way a farmer walks a field after harvest, picking up what’s left behind and useful, not tending anything that’s still growing. This distinction keeps the process fast. Most writers who try to “review old work” end up rewriting paragraphs and losing an afternoon. A harvest has one job: extract patterns, then leave the draft alone.
Which Drafts to Pull
Pick drafts you finished and moved past, not work still in progress. You want pieces where the mistakes are settled, not pieces where you’re still actively deciding what the sentence should say. Aim for five to eight pieces spread across a few months, not five pieces from the same week. A single week of drafts will only show you what you were tired of or excited about that week. A spread across months shows you what sticks around regardless of mood or topic.
Mix the types of writing you actually do. If you write both emails and articles, pull some of each. A tic that shows up in both formats is a real habit. A tic that only shows up in one format might just be a feature of that format, not a personal pattern worth fixing.
What Counts as a Pattern Versus a One-Off
This is the step most writers skip, and it’s the one that makes the whole method work. As you read, mark anything that feels off, but don’t add it to your checklist yet. Keep a rough tally instead. A mistake becomes a pattern once you’ve marked it in at least three of your sampled drafts. If it only shows up once or twice, it’s a one-off, a mistake you made that day for reasons specific to that day, not a habit worth building a rule around.
This rule matters because it keeps your checklist small and trustworthy. If you add every mistake you spot to the list, you end up back where you started, with a long document nobody actually uses. The three-draft threshold forces you to separate real habits from ordinary human error, which happens to every writer on any given day and doesn’t need a permanent rule.
How to Phrase Each Line
Once you’ve confirmed a pattern, write it as an action you can perform, not a quality you’re supposed to have. “Be concise” tells you what to want. It doesn’t tell you what to do. “Search for ‘very’ and cut it or replace it with a stronger word” tells you exactly what to do, and you’ll know the moment you’ve done it.
Action-based lines work because editing happens under time pressure, usually right before you publish or send something. You don’t have room to interpret a virtue in that moment. You need a step you can complete and check off. Here’s the shift in practice:
- Virtue-based (avoid): “Write with more confidence.”
- Action-based (use): “Search for ‘I think’ and ‘maybe’ in the first three paragraphs and cut or replace them.”
- Virtue-based (avoid): “Improve sentence flow.”
- Action-based (use): “Read the last sentence of each paragraph out loud; if you run out of breath, split it.”
- Virtue-based (avoid): “Reduce repetition.”
- Action-based (use): “Search for any word used twice in the same paragraph and swap one instance.”
A Worked Harvest: Three Drafts, One Tic
Reading about the method only gets you so far. Here’s what a small harvest looks like in practice, using three short invented excerpts that share a recurring tic.
Draft excerpt one, from a piece about setting up a home office: “The desk was very small for the room. It felt very cramped once the chair and shelves were in, and honestly the whole setup looked very unfinished.”
Draft excerpt two, from a piece about a weekend hike: “The trail was very steep near the top, and the wind made it very hard to hear anyone talking. By the last mile we were very tired and very ready to sit down.”
Draft excerpt three, from a piece about a recipe test: “The sauce turned out very thick, almost too thick to pour. It also tasted very salty, which was very surprising given how little salt the recipe called for.”
Read those three side by side and the pattern jumps out fast: “very” shows up ten times across three short excerpts, and in every case it’s propping up a weak adjective instead of a strong one being chosen in the first place. “Very small” could be “cramped.” “Very steep” could be “steep enough to slow us down.” “Very salty” could be “oversalted.” The word isn’t adding information. It’s covering for a word choice that hasn’t been made yet.
That pattern, confirmed across three separate drafts on three separate topics, earns a checklist line: “Search the draft for ‘very’ and either delete it or replace the adjective it’s modifying with a stronger single word.” Notice the line doesn’t say “avoid weak intensifiers,” which is the kind of virtue-based phrasing that sounds smart but gives you nothing to actually search for. It gives you a literal search term and a literal fix.
Turning Your Five Tics Into a Working Checklist
Once your harvest is done, you should have somewhere between four and eight confirmed patterns. Write each one as a search-and-fix line, the same way the “very” example works above. Keep the whole list on one page, ideally something you can glance at in ten seconds. A sample checklist built this way might look like this:
| Checklist Line | What It Catches | How Often It Fired (last 10 drafts) |
|---|---|---|
| Search for “very” and replace or cut it | Weak intensifiers propping up vague adjectives | 8 of 10 |
| Read final paragraph out loud, check if it repeats the intro | Restating the opening instead of closing with new ground | 6 of 10 |
| Search for “just” and “really” | Filler words that soften statements without adding meaning | 9 of 10 |
| Check every list for a repeated first word | Starting each bullet the same way, making the list monotonous | 5 of 10 |
| Search for questions in the body text | Rhetorical questions used as a crutch instead of a direct claim | 4 of 10 |
Run this list at the end of your editing pass, not the start. Editing for structure and argument first, then running the tic checklist last, keeps you from fixing small word choices in a paragraph you end up cutting entirely. The checklist is a final pass, not a first one.
The Maintenance Rule Most Checklists Skip: Retire What Stops Firing
Here’s the part almost no editing advice mentions. A checklist line has a shelf life. Once you’ve been catching and fixing a pattern for a few months, it starts showing up less in your drafts, because you’ve trained yourself out of the habit. When a line stops catching anything across several drafts in a row, that’s not a sign to keep it around for safety. It’s a sign to retire it.
This matters more than it sounds like it should. A checklist where every line still confirms you’re doing well feels reassuring, but reassurance is the wrong job for a checklist. If you keep running your eyes down a list of things you no longer do, you start skimming the whole list out of habit, and skimming is exactly how a real, current mistake slips past you unnoticed. A checklist that never changes eventually earns no attention at all.
The fix is a simple review, maybe once every two or three months. Pull ten recent drafts and check how often each line actually fired. Use a rough guide:
- Fired in 6 or more of the last 10 drafts: keep the line active, it’s still catching a real habit.
- Fired in 2 to 5 of the last 10 drafts: keep it, but watch it, since it may be fading out.
- Fired in 0 or 1 of the last 10 drafts: retire it and replace it with a newly confirmed pattern from a fresh harvest.
This keeps your checklist alive instead of static. It also means your checklist grows with you. The mistakes you make at the start of a writing habit are rarely the mistakes you make three years in, so a list frozen from your first harvest will eventually describe a writer you no longer are.
Troubleshooting the Harvest Process
Even a short method like this trips people up in a few predictable spots. Here’s how to handle the most common snags.
- I can’t find three drafts with the same mistake. Widen your sample. Pull from a longer stretch of time, six months instead of two. Some tics take longer to repeat if you don’t write every day.
- Everything I flag feels like a one-off. You might be reading too critically on the first pass. Do a first read purely for tally marks, without judging whether each flag is “bad enough” to count. Judgment comes after you see the tally, not during.
- My checklist is turning into fifteen items again. Cap it at eight and force yourself to rank the patterns by how often they fired. Drop anything below the top eight, even if it’s a real pattern. You can always harvest again later.
- I keep forgetting to run the checklist at all. Attach it to something you already do, like your final read-through before hitting publish or send. A checklist with no fixed moment in your process gets skipped no matter how good it is.
- A line fires on almost every single draft, all the time. That’s fine and even expected for your strongest tic. It doesn’t need to be retired just because it fires often; retirement is for lines that stop firing, not ones that fire a lot.
Frequently Asked Questions
How long should a harvest take the first time I do it? Reading five to eight short-to-medium drafts and tallying patterns usually takes thirty to sixty minutes. It gets faster on repeat harvests because you already know what to look for in your own writing.
Do I need special software to run an error harvest? No. A basic word search in whatever program holds your drafts is enough for most patterns, like counting how many times “very” or “just” appears. Structural patterns, like repeated bullet openers, just need your eyes and a quick tally on paper.
Should I include drafts that other people edited or gave feedback on? Leave those out of your sample. You want to see the mistakes you make on your own, before anyone else’s suggestions shape the piece. Edited drafts will hide your natural patterns behind someone else’s corrections.
What if two of my patterns seem to contradict each other? That can happen, and it’s worth noting rather than ignoring. For example, you might tend to write both overly long sentences in some pieces and overly short, choppy ones in others, depending on the topic. If that’s the case, write two separate checklist lines, each tied to a condition, rather than forcing one general rule that doesn’t fit both situations.
How often should I do a full harvest, as opposed to just the maintenance review? A full new harvest, pulling fresh drafts and starting the tally from scratch, works well once or twice a year. The maintenance review, checking which existing lines still fire, works better on a shorter cycle, every two or three months.
Building a Checklist That Actually Fits You
A checklist only earns its place in your process if it’s built from evidence you can point to, not advice borrowed from someone else’s drafts. The error harvest gives you that evidence directly from your own files, and the habit of retiring lines that stop firing keeps the list honest instead of decorative. None of this requires new software or a big time investment. It just asks you to read your own old work with a different question in mind: not “is this good,” but “what does this keep doing.”
Pull five old drafts this week and run a first harvest. You’ll likely find your real tics aren’t the ones any generic list ever warned you about.
What’s the one mistake you keep finding in your own old drafts, no matter how many times you think you’ve fixed it? Drop it in the comments, I’d like to see how common some of these patterns really are across different writers.
