A useful PhD progress report explains what your research is trying to establish, what has changed since the last review and what evidence supports your account of progress. It also shows the work still required, the obstacles that affect it and the decisions or support you need.
This guide includes a copyable report template, an annotated fictional example and a checklist for preparing your submission. Use your university’s form, assessment criteria and deadline first. The template is a writing aid, not an official form or a guarantee that your report meets a particular programme’s requirements.
What is a PhD progress report?
It is a structured account of the development of your research over a defined period. Depending on the programme, you may prepare it for supervision, an annual progression review, a thesis committee or a funder. These processes can require different documents and assess different things.
The University of Edinburgh describes annual progression reviews as opportunities to record research and thesis development, recognise achievements and discuss development needs. A report can therefore cover training and support as well as research outputs.
Do not assume an annual review is the same as an upgrade or confirmation assessment. For example, UCL’s upgrade guidance sets out a written report, a supervisor report and a viva, with requirements for substantial work towards the thesis. Its student report includes research context, literature, questions, methods and a plan for remaining work. Those are UCL requirements, rather than universal rules for every progress report.
Check the requirements before you start writing
| Check | What you need to establish |
|---|---|
| Purpose and audience | Routine update, annual assessment, upgrade, thesis committee or funder report? |
| Required format | Official form, narrative report, chapter extract, presentation or a combination? |
| Assessment criteria | What must the work demonstrate at this stage? |
| Length and attachments | Word limit, reference treatment, figures, appendices and permitted supplementary material. |
| Dates and submission route | Review date, submission deadline, system or recipient and any supervisor review time. |
| Confidentiality | Who will read it and how restricted data or personal information should be handled. |
Ask your supervisor or programme office when guidance is unclear. Edinburgh’s student annual-review introduction directs students to their School’s guidance and explains that written and oral requirements can vary. Download or record your own current instructions so you can check the draft against them.
A copyable PhD progress report template
Copy this structure into a document, then rename or remove sections to match your required form. The prompts in brackets are instructions to replace with your own information. If your programme requires a substantial chapter or literature review, a short summary in this template does not replace it.
| Section | Copyable prompt |
|---|---|
| Report details | [Name; programme; study mode; supervisors; working project title; reporting period; review date.] |
| 1. Summary | [Current research question; most important progress; main limitation or obstacle; next milestone.] |
| 2. Project context and objectives | [Problem addressed; relevant literature; intended contribution; scope and any agreed changes.] |
| 3. Progress against the previous plan | [For each objective: intended output; current status; evidence; reason for any change or delay.] |
| 4. Methods and research work | [Work carried out; rationale for methods; relevant approvals; changes; quality checks and limitations.] |
| 5. Findings or emerging interpretation | [What the evidence currently supports; what remains tentative; alternative explanations or unresolved questions.] |
| 6. Outputs and development | [Drafts, datasets, code, creative work or other outputs; accurate publication status; training and its relevance.] |
| 7. Risks, dependencies and support | [Obstacle; likely effect; action already taken; proposed response; decision or support needed.] |
| 8. Next-period plan | [Deliverable; target date; dependency; success criterion; contingency if the dependency is delayed.] |
| 9. References and permitted appendices | [Verified references; labelled supporting documents; required declarations or forms.] |
Keep the research question visible throughout. If it has become too broad, use the guide to narrowing a research question before making promises about the next phase.
Show progress with evidence, not just activity
“I spent the term reading” describes effort. “I compared how the key studies define the concept and identified a disagreement that changes my sampling strategy” explains what the reading contributed. Attach or point to the comparison where your submission format permits.
A simple status table helps you separate completed work from work in progress. Use labels consistently. A draft is not an approved chapter, submitted work is not an accepted publication and a pilot dataset is not the final study.
| Previous objective | Status | Evidence | Implication |
|---|---|---|---|
| Compare two analytical approaches | Completed | Comparison memo with assumptions and limitations | One approach needs further checks before selection. |
| Draft the methods chapter | In progress | Draft contains design and sampling sections | Analysis section awaits the method decision. |
| Begin recruitment | Not started | Required approval remains pending | Revise timing and raise the dependency. |
This table is illustrative. In your report, identify the actual documents or records supporting each entry. If the previous plan has changed, explain the reason and whether the change has been agreed, proposed or still requires approval.
For work based on published literature, the literature review matrix can help you preserve the connection between sources, comparisons and your developing argument.
Annotated PhD progress report example
The following is a fictional excerpt from a three-month research update. The project, counts, outputs and dates are invented to demonstrate writing choices. It is not a real study, a complete annual-review submission or a model of the amount of work every student should complete. A real report would include its actual references and evidence.
Example summary
Project: How do municipal heat-action plans assign responsibility for supporting vulnerable residents?
Reporting period: 1 July–30 September 2026.
During this period, I refined the document-selection criteria and screened 12 public plans, of which seven met those criteria. I produced a screening log and an initial coding framework, then tested the framework on two included plans. The pilot identified ambiguity between a general commitment to act and an action assigned to a named organisation. I have proposed a revision to the coding definitions, but have not yet applied it to the full set.
Why this works: the summary names the question, describes identifiable outputs and distinguishes pilot work from completed analysis. It identifies a methodological problem without claiming a substantive finding about municipal policy.
Example progress and limitations
The screening log records an inclusion or exclusion reason for each document. The pilot memo includes the passages used to test each code and notes cases where the current definitions were difficult to apply. Two included plans refer to appendices I have not yet located. Until those appendices are obtained or an alternative is agreed, I cannot determine whether the main documents contain all relevant responsibility assignments.
The current analysis can support a description of what the selected documents state. It cannot establish whether the stated actions were implemented or whether residents received support. Those questions would require different evidence and are outside the present document-analysis design.
Why this works: it connects claims to records, identifies incomplete material and states what the design cannot establish. It gives reviewers a concrete issue to discuss rather than disguising uncertainty as a minor inconvenience.
Example decisions and next-period plan
I request feedback on whether the revised definitions distinguish general commitments from assigned actions clearly enough to proceed. I also request agreement on how to handle missing appendices if they cannot be obtained. Both decisions affect the scope of the next coding stage.
| Proposed deliverable | Target date | Dependency or check |
|---|---|---|
| Revised coding definitions and pilot memo | 23 October 2026 | Supervisor feedback on the proposed distinction. |
| Updated document-access record | 6 November 2026 | Locate the two appendices or agree a documented alternative. |
| Next coding-stage summary | 20 November 2026 | Definitions agreed; document scope resolved. |
| Contingency if access remains unresolved | Discuss at the next meeting | Continue work on accessible material without treating missing text as evidence of no action. |
Why this works: the plan specifies deliverables, dates and dependencies. It asks for a decision before committing to work that depends on it. The dates are illustrative targets, not an institutional timetable.
Use the supervisor meeting agenda to discuss the decisions behind your plan. After feedback, record the agreed changes with the supervisor feedback action plan.
How to report delays, failed experiments or little progress
Describe what happened, its effect on the project and what you have done in response. Keep the explanation factual. “The equipment was unavailable for three planned sessions, so these measurements remain incomplete” is clearer than “the experiment has been difficult”. Include a revised proposal and the support needed to make it feasible.
A failed experiment or an unsupported hypothesis may still produce useful knowledge about the method or question. Explain what the work rules out, which assumptions remain uncertain and what follows. Do not describe a technical failure as a negative research finding unless the design and evidence justify that interpretation.
If personal circumstances affected progress, use your institution’s appropriate support or confidential reporting channels. You can describe the effect on availability without putting unnecessary personal detail into a document circulated to an assessment panel. Ask what formal process applies to extensions, adjustments or interruptions rather than assuming the report alone changes a deadline.
Adapt the report to your research stage
Early stage: show how the question, literature, design and feasibility have developed. A well-supported change of direction can be important progress. Explain its implications for the schedule.
Middle stage: distinguish completed data collection or research activity from analysis and interpretation. Explain quality checks, emerging limitations and what still needs testing.
Writing stage: identify chapter status and the remaining tasks, including unresolved argument, evidence, revision and submission work. A word count alone cannot show whether a thesis is ready.
The PhD timeline guide offers a broad planning perspective, but your programme’s milestones and your own project schedule should determine the report’s priorities.
Prepare the report for someone outside the immediate project
Give the reader enough context to understand the question and the significance of your progress. Define specialist terms, introduce abbreviations and explain what a figure demonstrates. Do not make reviewers search through a folder of attachments to discover your main point.
Use descriptive headings and captions. Refer to appendices by label where permitted, and check that linked material is accessible to the intended readers. Keep confidential research files in the approved systems and share only the material appropriate to the review.
A final check before submission
| Check | Question to ask |
|---|---|
| Requirements | Have I answered the official prompts and supplied every required item? |
| Evidence | Can the reader connect each important claim to a result, draft or record? |
| Status | Have I labelled drafts, submissions, acceptances and approvals accurately? |
| Limits | Have I separated preliminary interpretation from established findings? |
| Feasibility | Do dates allow for approvals, feedback, access and other dependencies? |
| Consistency | Do the summary, tables, figures and appendices use the same dates and counts? |
| References | Have I checked every citation against a real source I used? |
| Submission | Is the correct file going to the correct place before the deadline? |
Frequently asked questions
How long should a PhD progress report be?
Follow your programme’s word limit and format. A brief supervision update may be short; a formal progression assessment may require substantial writing and supporting work. There is no universal length that makes a report sufficient.
Should I include unsuccessful work?
Include it when it matters to the research question, method, schedule or decisions being reviewed. Explain the evidence, limitations and next step. An honest account of what did not work can be more useful than a list containing only completed successes.
Can I use this template for an annual review?
Use it to organise your thinking, then map the content to your institution’s official requirements. Add the required chapter extracts, presentations, training records or forms. Do not submit this outline in place of a mandatory form without checking.
Do I need publications to demonstrate progress?
Check the criteria for your review. Progress can be evidenced through the research work itself, including analysis, design development, drafts, data, code or creative outputs. Report publications accurately if relevant, but do not assume a particular publication count is a universal requirement.
Start by gathering the previous plan, your actual outputs and the current review instructions. Write the status table first. It will usually reveal the progress worth explaining, the uncertainty worth acknowledging and the decisions your next plan needs.
Featured photo: Nick Morrison on Unsplash.