Franklin was a printer, and it shows in how he talks about his own life. Near the start of the Autobiography, he says he would gladly live it again if he could correct the faults, the way an author fixes errors in a second edition. He also kept a small book where he marked each lapse against his list of virtues. Both habits point toward the same idea: you cannot fix mistakes you have not tracked.

Student writers face the same problem. Most get papers back with comments scattered across every page. They glance at the grade, read a few notes, and start the next assignment with the same habits. Without a record, there is no way to see that the same comma splice showed up in six essays.

An error log fixes that. It is a simple running document where students list the recurring issues from each graded paper, along with a corrected example. Over a semester, the log becomes a personal guide to that student's writing.

The idea is not new, but Franklin's version is a useful frame for students. It treats mistakes as data instead of judgments. That framing makes the log easier to keep and less discouraging.

Building an error log students keep

Keep the format small. A table with three columns works well: the error, the fix, and the essay where it appeared. Ask for two or three entries per returned paper, not every mistake. A short log gets updated, and a long one gets abandoned.

• Students choose entries from your comments, focusing on issues that appeared more than once.
• Each entry includes the original sentence and a corrected version in the student's own words.
• A short note explains the rule or reasoning behind the fix.
• Students review the log before starting each new essay.
• You check the log briefly at the midpoint and end of the term.

Sorting errors by pattern, not count

Ten scattered comma errors can hide one misunderstanding about how clauses work. When you comment, name the pattern instead of fixing each instance. A note like "you join two complete sentences with only a comma" teaches a rule that covers all ten. Students then find the rest on their own.

Patterns also show up in higher-level writing. Many students repeatedly summarize when they should analyze, or place their thesis at the end of a paragraph instead of the beginning. Log these alongside surface errors, since they often matter more.

Making the log part of the grade

Students take the log seriously when it counts for something. A small portion of the grade, tied to completion and quality of reflection, is usually enough. Grade the thinking, not the number of entries. A student with four thoughtful entries deserves more credit than one with twelve copied comments.

Tie the log to revision. Before a student submits the next essay, ask for a line saying which logged issue they checked for. It closes the loop Franklin cared about, which is correcting the next edition.

Spotting patterns faster with tools

Finding patterns across a student's work is tedious to do by hand, especially when you teach over a hundred students. AI feedback tools that apply your rubric consistently can make recurring issues easier to see, since comments follow the same language from paper to paper. Use that consistency to build a shared vocabulary for common errors.

Whatever you use, the teacher's judgment decides which patterns matter most for each student. A tool can tally. You decide what to teach next.