What to Check Before Sending a Chapter to Your Supervisor

Start with structure, not sentences

Most students begin their pre-submission review at the sentence level — running spell-check, tightening phrasing, catching grammatical slips. That instinct is understandable, but it is the wrong place to start.

Supervisors read for architecture first. Before they reach your prose, they are asking a different set of questions: Does this chapter have a clear argument? Does the introduction promise what the body delivers? Does each section earn its place relative to the whole?

Structure problems are the expensive feedback to receive. They require rethinking and reorganising, not just editing. Catching them before submission means the conversation with your supervisor is about refinement — not about going back to fundamentals.

Before you send, work through these questions:

• Can you state the chapter's central argument in two sentences? If you cannot, your supervisor will struggle to follow it too.
• Does your introduction tell the reader what the chapter will argue and why it matters? Not just what topics it covers — what it actually claims.
• Does your conclusion deliver on that promise? A conclusion that introduces new ideas or drifts from the chapter's argument is a structural warning sign.
• Does each section have a clear function? Try writing one sentence describing what each section does for the chapter's argument. If you cannot, the section may be in the wrong place — or may not need to be there at all.
• Are your subheadings accurate? A heading that does not describe what the section actually does is a sign that the structure has drifted from the original plan.
• Is there signposting throughout? A busy supervisor should be able to glide through a well-signposted chapter. Each section should open by orienting the reader in the argument, and close with a transition that makes clear what comes next. The introduction should include a brief roadmap. Signposting is not padding — it is the architecture of how a reader moves through the work.

Check your argument before your prose

Once the structure holds, move to the argument. This is distinct from structure — structure is about the chapter's architecture, argument is about whether your thinking is actually present inside it.

The most common weakness at this level is not absence of ideas, but absence of voice. Many PhD students write chapters that describe what other scholars have said without making it clear what they think about it, how those sources relate to each other, or why any of it matters for their own thesis.

Check for these specifically:

• Is your analytical voice present throughout? Your interpretation should appear in each section, not just in the final paragraph of the chapter.
• Are you synthesising sources or just summarising them? Source summaries stacked one after another is the single most common form of weak academic writing. Synthesis means comparing, connecting, and evaluating — not reporting.
• Does each paragraph have a claim? Purely descriptive paragraphs — ones that relay information without making an analytical point — are worth scrutinising. They may belong elsewhere, or may not be needed.
• Are your transitions doing logical work? Words like "furthermore" and "additionally" connect sentences but do not advance arguments. Transitions like "this suggests," "in contrast," and "building on this" indicate your thinking is moving somewhere.

What your supervisor is actually reading for

It helps to understand what a supervisor or committee is doing when they read a chapter draft. They are not primarily proofreading. They are asking whether the candidate understands their field, whether the argument is original and defensible, and whether the work is moving toward something that could survive examination.

The most engaged supervisors — and the most demanding committees — tend to give the most specific feedback. That feedback can be uncomfortable to receive. But specificity usually means investment. A supervisor who tells you the argument in section three does not follow from section two is fighting for your success, not against it. That is the kind of feedback worth going back for.

If you have ever left a supervisor meeting wishing you had caught something yourself, you already know why the pre-submission review matters. The goal is not to produce a perfect draft before your supervisor sees it. The goal is to arrive at that conversation having dealt with the avoidable problems — so the feedback you get is the kind that actually advances your work.

Check your citations

Citations are easy to overlook in a pre-submission review because they feel administrative rather than intellectual. They are not. A supervisor who spots a missing citation, an inconsistent format, or a claim without support will question the care that went into the whole chapter.

Work through these before you send:

• Every claim that needs support has a citation. Pay particular attention to strong or contested claims — these are the ones an examiner will want to see sourced.
• Every source cited in the text appears in the bibliography. And vice versa — sources in the bibliography that are never cited in the text should not be there.
• Format is consistent throughout. Switching between citation styles mid-chapter, or between footnotes and author-date within the same document, signals a draft that has not been properly reviewed.
• Direct quotes include page numbers. This is a basic requirement in most academic styles and one supervisors notice immediately when it is missing.
• You are not over-relying on a single source for major claims. If a key argument in your chapter rests entirely on one scholar, that is a vulnerability worth addressing before your supervisor points it out.

Grammar and clarity: last in your process, first in theirs

Grammar is not where you should start your review — but it is one of the first things your supervisor notices. A supervisor who encounters rough prose early in a chapter will struggle to get past it, even if the argument underneath is sound. That is not a character flaw; it is how reading works. Poor grammar creates cognitive friction, and cognitive friction makes everything harder to evaluate fairly.

The reason grammar comes last in your review process is practical: if your structure needs work, you will rewrite sections. Polishing prose you are about to cut is wasted effort. Fix the architecture first, then clean the surface. But when you reach this layer, take it seriously.

When you do reach this layer, a few things to check:

• Read the chapter aloud. This is underrated. Your brain autocorrects silently; it cannot do that as easily when speaking. Clunky sentences, unclear transitions, and unintentional repetition all surface quickly.
• Watch for hedging that undercuts your argument. Phrases like "it could perhaps be argued that" signal uncertainty where confidence is appropriate. Hedge when you genuinely are uncertain; do not hedge as a reflex.
• Check for consistent terminology. If you use three different terms for the same concept across a chapter, a reader — including your supervisor — will wonder whether you are distinguishing between them deliberately or just being imprecise.
• Look at passive voice. Not all passive constructions are wrong, but heavy passive voice often hides your analytical presence. Where your interpretation is the point, active voice makes it clearer that you are the one making the claim.

A pre-submission habit, not a one-time fix

The most useful thing about this process is not the checklist — it is the consistency. Every chapter goes through the same submission cycle. Building a systematic pre-submission review into your workflow means you apply the same framework repeatedly, and over time your self-editing sharpens because you know what you are looking for.

It also changes the nature of your supervisor relationship. When you arrive at a review meeting having already caught the structural and argumentative problems yourself, the conversation shifts. Your supervisor can spend the time on the things you genuinely could not see — the gaps in your field positioning, the implications you missed, the questions an examiner would ask. That is a more useful conversation than one spent on issues you could have caught with an extra hour of review.

Some doctoral writers use AI-assisted tools to apply this kind of structured review before submission. Research Think's AI scoring evaluates chapters on the dimensions that matter most — argument coherence, structure, evidence integration, and academic register — so you can see where a chapter stands before it goes to your supervisor. It is not a replacement for that conversation. It is preparation for it.

For a broader look at how to build this kind of structured review into your thesis workflow, see how to set up a thesis project in Research Think. And if you want to understand what quality signals actually matter beyond word count, the thesis writing tips guide covers the dimensions that examiners actually evaluate.