A 12-Point Final Paper Checklist
You are about to submit. The paper is "done." It is 2 a.m. and the file is sitting in the Canvas upload window. You are one click from being free.
Before you click submit, use this checklist to review the argument, evidence, citations, flow, process documentation, and file itself. Your instructor and rubric control the grade, and no checklist can prevent a detector flag, but a deliberate final review can catch issues that are easy to miss when you are tired.
The twelve items below are prompts, not universal rules. Use the ones that fit your assignment, discipline, and instructor's guidance.
(Want this as a printable PDF you can put next to your laptop for future assignments? Download it directly at humatext.com/finals-checklist. No email or account required.)
Argument and structure
1. Your thesis is one sentence and it appears by the end of paragraph two.
If a reader cannot identify your main claim, consider making it more explicit. Phrases such as "this paper will explore" can describe a topic without stating the argument; replace them when a direct claim would be clearer.
What good looks like: "Hamilton's claim that the executive requires energy, read against the Anti-Federalist response, exposes an unresolved tension in the founding-era theory of accountability." Notice the claim, the move (read against), and the stakes (unresolved tension) all sit in one sentence.
2. Every body paragraph opens with a claim, not a quote and not a fact.
In many analytical assignments, stating the paragraph's claim before introducing evidence keeps your reasoning visible. Other disciplines use different structures, so follow the conventions and rubric for your course.
3. Every claim is paired with at least one piece of specific evidence.
A page number. A citation. A direct quotation. A concrete detail. Specific evidence makes a claim easier to evaluate. Search your draft for words such as "many," "most," "often," and "some," then check whether the surrounding claim needs support or more precise wording.
4. Your conclusion does not say "in conclusion."
For many analytical assignments, the conclusion should explain what is at stake rather than only repeat the thesis. Ask what the argument changes about how the reader understands the text, problem, or policy, and follow the conclusion conventions in your rubric.
Voice and flow
5. Read the whole paper out loud.
Reading aloud can reveal awkward phrasing, missing words, and overly long sentences that are easy to skim past silently. Mark any place where you stumble, then decide whether the sentence needs revision.
6. No sentence runs over 35 words.
Review your longest sentences, especially those carrying several ideas or layers of qualification. A sentence over 35 words is a prompt to check clarity, not an automatic error; split it only when doing so makes the reasoning easier to follow.
7. Sentence lengths vary across each paragraph.
Read for rhythm rather than forcing a numeric pattern. A mix of sentence structures can improve flow, but uniform length is not proof of AI use and variation should serve the meaning. Revise only where repeated structure makes the paragraph harder or duller to read.
8. You used contractions where they fit.
Use contractions only when they fit your natural voice and the assignment's level of formality. They can make some prose less stiff, but an instructor or style guide may prefer the expanded form.
Process documentation
9. Google Docs version history is on. Word's Version History is on.
Confirm that your editor is saving revision history. A revision trail, notes, sources, and earlier drafts can help document your process if your work is questioned. They are supporting evidence, not a guarantee that a dispute will be resolved in a particular way.
In Google Docs: File, then Version history, then See version history. In Word: File, then Info, then Version History. Take screenshots of the early entries before you submit, and email them to yourself. Belt and suspenders.
10. Your process follows the course's AI and collaboration policy.
Keep your own notes, outline, sources, and drafts, and disclose tool use when the assignment or institution requires it. If the policy is unclear, ask the instructor before using an AI-assisted tool on submitted work.
Final pass
11. You ran spell-check and grammar-check.
Built-in tools such as Microsoft Editor, Google Docs spelling and grammar checks, Grammarly, or LanguageTool can flag possible issues, but none catches everything. Review each suggestion and do a manual pass as well.
12. You did a phrasing polish on the two or three paragraphs that read stiffest.
This step can be easy to skip when you are tired. Read the paragraphs that feel stiff aloud one more time, then revise only the places where sentence structure, word choice, or transitions make the meaning harder to follow.
If your course permits AI-assisted editing, HumaText can propose a phrasing pass on a short section. Review every change against your sources, intended meaning, and disclosure obligations; automated rewrites can introduce mistakes. The anonymous tier currently accepts up to 250 words a day without an account.
One bonus item
13. Save before you submit. Email yourself a backup.
Save the final PDF to your desktop, your cloud, and your email inbox. The number of "the portal ate my paper" stories from finals week is genuinely depressing, and the recovery process is much shorter when you can forward yourself the timestamped copy. Three minutes of paranoia, hours of saved panic.
How to actually use this
Here is the honest framing. Not every paper needs all thirteen items.
If you are short on time, prioritize the thesis, a read-aloud pass, process documentation, and the paragraphs you found hardest to write. That is a practical sequence, not a guarantee about grades or detector outcomes.
If you have a full day, run all thirteen in order.
If the checklist is useful, adapt it to your rubric and keep the parts that consistently improve your review process.
(Free printable PDF: humatext.com/finals-checklist. No email or account required. The tool itself is free for 250 words a day if you want to try the phrasing polish on item 12.)