Writing a Thesis Plan
Two drafts of one student's thesis plan, three days apart. What the revision added, what neither reached, and what the plan's own shape reveals about the material it was written from.
The task, and the mismatch inside it
The two drafts
DRAFT AND REVISION COMPARED
| First draft | Revision, three days later | |
|---|---|---|
| Length | 331 words | 389 words |
| Against the 700-word requirement | 47% | 56% |
| Process map | None. Its only embedded image is a 36-pixel decorative artefact | Present — fifteen nodes |
| Timeline | None | None |
| References | None | Two, both external instructional videos |
| Framing | Stages listed in prose | First-person framing added |
Both documents are real student work, anonymised. Faults are recorded as faults in the writing.
The revision is the more interesting document, because what it added is exactly what the task asked for and the draft omitted. Somebody re-read the brief. That is worth crediting, and it is the single most common reason a second draft is better than a first.
The plan itself
The fifteen nodes, in the student's own order, describe a complete arc from title to reported findings. As a piece of thinking it is more coherent than its length suggests.
- Title
- Abstract
- Introduction
- Two literature streams
- Synthesise
- Literature review
- Ethical approval
- Define the gap
- Questions and hypotheses
- Data collection design
- Proposal defence
- Collect and analyse
- Report findings
Three things the plan gets right
Two literature streams, then a synthesis
The plan reads two separate bodies of theory and then synthesises them before writing the review. That is a real analytical move and it is more sophisticated than a single undifferentiated review.
The abstract is written last
Listed second in the map and stated in the draft as written at the end. Getting this right is unusual and it matters — an abstract written early describes the study you intended.
Approval appears as a stage, twice
Ethical approval from institution and workplace, and a proposal defence before approval. The plan treats external sign-off as work with duration, which is exactly what the thesis procedure documents formalise.
What the plan reveals about the material behind it
This is the second time the supplied submissions show the same pattern. An earlier one supplied a coding technique by name, sourced from outside the subject, because the material's own coverage was insufficient for the task set. A reader using student work as a diagnostic will find this is what it diagnoses most reliably: not what learners failed to absorb, but where the material sent them elsewhere.
Writing a better one
The source sets the task and teaches none of it. What follows is this library's construction, built from the plan's own good instincts and from the thesis procedure documented elsewhere in this batch.
A thesis plan that would meet the brief
Start from the gates, not the tasks
List every point where someone else has to say yes: supervisor, ethics committee, proposal defence, examiners. These are fixed points with queue times you do not control. Everything else fits between them.
Put the work between the gates
Now the tasks — reading, designing, collecting, analysing, writing. Each belongs to the gate it must clear.
Attach durations, then dates
This is the timeline half of the task and it is where a plan stops being a list. A stage with no duration cannot be late, which is why plans without durations feel comfortable and predict nothing.
Put float in front of every gate
Sized for at least one rejection. The library records an ethics approval that took five rounds over more than five months; gates take the time they take.
Mark what cannot start until something else finishes
Data collection cannot start before ethics approval — that single dependency has ended more student projects than any other.
Write the abstract last and say so on the plan
The student got this right and it is worth keeping.
On reading student work as an example
Getting it right
Before you call a thesis plan finished
- Every approval gate you must pass is on it, as a stage with a duration
- Every stage has a duration, and the durations sum to less than the time you have
- The dependency from ethics approval to data collection is explicit
- There is float in front of each gate, sized for one rejection
- The write-up is broken into more than one box — analysis, results, discussion, conclusions are different work
- The abstract is last
- You have re-read the brief after finishing, and checked both halves of it
What to carry forward
- The task asked for a process map and a timeline. The revision produced the map and neither draft produced the timeline — and the timeline is the half that makes a plan predict anything.
- Build the plan from the approval gates outward. They are the fixed points you do not control.
- A stage without a duration cannot be late. That is why plans made of stages feel reassuring and forecast nothing.
- The plan's fifteen nodes compress a whole week of analysis and write-up material into two. Where material has not landed as structure, it does not appear in a plan at all.
- A thesis plan is not there to be followed. It is there to tell you, cheaply and early, whether the study fits the time.
Frequently asked questions
What was the task these drafts answered?
Produce a process map of the steps in producing a thesis, using a process mapping tool, with a timeline, in 700 words. It was set at the end of a week about analysing qualitative data and presenting results, and nothing in that week teaches process mapping or names a tool.
How did the revision differ from the draft?
It grew from 331 to 389 words, added a first-person framing and two external video references, and — decisively — added the fifteen-node process map the draft lacked entirely. It still produced no timeline and remained about half the required length.
Why does it matter that the plan compresses the week into two nodes?
Because it shows what had landed as structure and what had not. The plan reached outside the subject for a prospectus stage and a proposal defence, and reduced a whole week of analysis and write-up teaching to 'Collect Data & Analyze' and 'Report Findings'. That correspondence is a comment on the material's emphasis.
How should I actually build a thesis plan?
Start from the approval gates, because you do not control their timing. Put the work between them, attach durations and then dates, and place float in front of each gate sized for at least one rejection. The dependency from ethics approval to data collection is the one that most often ends projects.
Do research plans have to be followed?
No. The subject's own proposal material is explicit that the plans in a proposal are not binding. A plan's value is that it tells you early whether the study fits the time available, which is a return you collect on the day you write it.
References and source attribution
- Two anonymised student submissions supplied with the teaching material: a 331-word thesis-plan draft and a 389-word revision created three days later. Used as observed practice rather than as model answers.
- The supplied teaching source: weekly study notes, slide decks and assessment activities for a master's-level research methods subject in project management. Author, institution and year not stated in the supplied files.
Suggested questions for Ask KEVOS
- How do I build a thesis plan with a realistic timeline?
- What stages should a thesis process map contain?
- Why should the abstract be written last?
- How much float should I leave before an ethics approval?
- What is a thesis plan actually for if plans always change?