What is the difference between editing and proofreading?
Editing is rewriting: cutting a paragraph, reordering an analysis, fixing a rule statement that does not match the cases you cited. Proofreading is verification: confirming that what is on the page is accurate, consistent, and correctly formatted. If you try to do both at once you will do neither well, because rewriting a sentence introduces new typos in a section you already checked.
Finish substantive editing first. Then stop. Then proofread. If you rewrite anything during the proofreading passes, re-read the full paragraph you touched, not just the sentence—dropped words and orphaned commas cluster around late edits.
Build in time. A memo you finish at 2 a.m. and submit at 2:15 a.m. will contain errors you are literally incapable of seeing, because you are reading your intended text rather than your actual text. Even a two-hour gap and a walk helps.
What order should the passes go in?
Work from largest unit to smallest. Fixing a sentence inside a paragraph you later delete is wasted effort, and formatting a heading you later rewrite is wasted twice.
Pass one is structural. Read only your headings, topic sentences, and the Brief Answer. Do the topic sentences, read alone, tell the whole story of your analysis? Does the Brief Answer actually answer the Question Presented, and does the Discussion reach the same conclusion? Mismatched conclusions between the Brief Answer and the end of the Discussion are one of the most commonly flagged memo errors.
Pass two is paragraph-level. Confirm each CREAC (or IRAC) unit has a rule, support, application, and conclusion, and that no paragraph is doing two jobs. Confirm no fact appears in the Discussion that is absent from the Statement of Facts—that is a substantive foul, not a style preference.
Pass three is sentence-level mechanics. Pass four is citations. Pass five is document format and submission mechanics.
How do you catch typos your brain skips?
Your brain autocorrects familiar text, so you have to make the text unfamiliar. Each of these techniques works by forcing your eye to slow down or by breaking the pattern you memorized while drafting.
Spellcheck will not save you. It passes 'statue of limitations,' 'trail court,' 'pubic policy,' 'defendant' where you meant 'plaintiff,' and every misused 'its/it's' and 'affect/effect.' Run targeted searches for your own known weaknesses.
- Print it. You will catch errors on paper that are invisible on screen.
- Read it aloud, slowly, or use your word processor's text-to-speech. Your ear catches dropped words and run-ons that your eye glides past.
- Change the font and font size temporarily; the new line breaks defamiliarize the text.
- Read the Discussion section paragraph by paragraph in reverse order, so you evaluate each paragraph on its own rather than riding the argument's momentum.
- Use Find to check specific hazards: double spaces, ' ,' and ' .', 'statue,' 'trail,' 'pubic,' the opposing party's name, and any placeholder like 'XX' or 'CITE.'
- Search every open quotation mark to confirm it has a closing mark and a citation.
How do you proofread the citations?
Do this as a dedicated pass with your citation manual open, and check the cite against the source, not against your memory. The core sequence for a case cite is case name, reporter volume, reporter abbreviation, first page, pincite, and a parenthetical with court and year—for example, Erie Railroad Co. v. Tompkins, 304 U.S. 64, 78 (1938), or Palsgraf v. Long Island Railroad Co., 162 N.E. 99, 100 (N.Y. 1928). Note that the second cite includes the state because the reporter alone does not identify the court.
Check each of the following, one category at a time across the whole document, rather than checking every element of one cite before moving to the next. Batching by category is faster and catches inconsistency.
Rule numbers shift between Bluebook editions, so confirm against the edition your school assigns; many schools use the ALWD Guide instead, and a few professors use a local court's citation rules. The underlying elements are the same either way.
- Pincites: every proposition drawn from a specific page needs one. A bare first-page cite for a specific holding is a standard deduction.
- Short forms: 'id.' is only proper when the immediately preceding citation contains a single authority; otherwise use a case short form. The Bluebook does not permit 'supra' for cases, statutes, or constitutions.
- Signals: no signal means the source directly states the proposition; 'see' means it supports the proposition by inference. Do not decorate every cite with 'see.'
- Quotation accuracy: open the source and compare character by character. Bracket every alteration, use ellipses correctly, and add '(citation omitted)' or '(internal quotation marks omitted)' where required. Quotations of fifty or more words are block quoted, indented, and unquoted.
- Case name abbreviations differ in text versus in citations; textual sentences abbreviate far less. Check the abbreviation tables rather than guessing.
- Currency: run each principal case through KeyCite or Shepard's. A red flag on your lead case is a substantive failure, not a proofreading one, but the final pass is your last chance to catch it.
What memo-specific problems should you look for?
A memo is predictive, not persuasive. Read your Discussion hunting for advocacy: 'clearly,' 'obviously,' 'the court will surely find,' and one-sided characterizations of adverse authority. If you would not want a partner to rely on your prediction and be surprised in court, the tone is wrong. Confirm you have addressed the strongest counterargument explicitly.
Check tense discipline. What a court did is past tense ('the court held'); what a rule requires is present tense ('a plaintiff must show'). Mixed tense within a case discussion reads as sloppiness.
Check that party labels are consistent and unambiguous. If your client is 'Ramirez' in the Facts, she should not become 'the plaintiff' in one paragraph and 'our client' in the next, and 'the defendant' should never be ambiguous as between the case you are discussing and your own matter.
Verify that the rule you state in the Discussion is the rule your cited case actually announces, and that you have not silently converted dicta into a holding. Also confirm the Question Presented names the jurisdiction and the legally significant facts, and that the Statement of Facts contains no legal conclusions.
What is the final mechanical checklist before you submit?
These are the errors that cost points for no analytical reason, which makes them the most painful ones to make.
Do this checklist on the file you are actually uploading, opened fresh, after any final save.
- Page or word limit, verified with the correct setting (word count excluding or including footnotes, per your professor's instruction).
- Anonymous grading number in the header or footer—and your name nowhere in the document if grading is blind.
- All comments, tracked changes, and highlighting accepted or removed; check document properties for author metadata if anonymity matters.
- Required margins, font, line spacing, and page numbers; consistent heading levels and consistent indentation.
- Correct memo header block: To, From, Date, Re, and a Re line that identifies the client matter and the legal question.
- Correct file format and file name per the assignment instructions, and a confirmation that the upload actually succeeded.
Should you use software or another reader?
Westlaw's Quick Check and Lexis's Brief Analysis will flag some citation formatting and negative-treatment problems, and Word's editor catches some grammar issues. Treat all of them as a first sweep, never as verification. They do not know whether your pincite supports your proposition, and they routinely miss short-form errors.
Check your school's policy before running your memo through any generative AI tool. Many legal writing programs prohibit it for graded assignments outright, and 'I only used it for proofreading' is not a recognized exception at most schools. When in doubt, ask your professor in writing.
A human reader is more valuable than any tool, but confirm collaboration is permitted—most first-semester memos are closed assignments, and having a classmate read your draft can be an honor code violation even if the feedback is purely mechanical. Where outside readers are allowed, ask them to read for one thing only: whether they can restate your conclusion and your reasoning after a single read.