A Better Way to Correct Essays

I offer significant points for turning in rough drafts because revision is the most important part of the writing process. I have had much success in getting the students to do this part of the assignment, but one issue lies in how effective my feedback is regarding punctuation and grammar errors, and whether students can, or are motivated to, successfully translate my comments into improved writing and learning.

What not to do: proofread and edit. Not only is this time consuming, it is ineffective. Case in point: On one student's essay, I did comprehensive line editing, pointing out every grammar and punctuation error and providing the correction. Not only was the paper almost unreadable when I was finished, cluttered with the highlights and dialogue boxes, but it had no effect on learning. The paper had the simple errors corrected on the final draft which seemed like a success at first. Then I got to the end of the essay, where the writer had made a great point in the last sentence. I responded, "Indeed!"  Guess what the new last sentence of revised essay was? Indeed.

Insert wah-wah-wah fail music here. Transcribing is not learning. It is difficult for me to turn off my compulsion to correct all errors, but what I do now is use a code for each type of error, say a comma splice, and I do not correct it. The student matches the error code to a provided key, and logs a revision. I might give an example of a correction, but more often, I list the page number in their reference books that explains the concept if I think the student might not know how to correct the error.

They don't always get the corrections right, but they learn far more than mindlessly transcribing my corrections. First, they have to look up what the errors are, and figure out how to correct it on their own. They earn points for correctly revising one example of each type of error they make. Although I see fewer perfectly corrected papers, I see fewer recurrences of problem areas in subsequent drafts, and that's really what it's all about.

To see examples of my codes and logs, or if you want to buy mine instead of making your own, click here.