Returning from research leave can feel like opening several doors at once. Your ordinary responsibilities resume, colleagues want to hear what happened and the project may still be developing. A research leave outcomes report helps you bring these threads together: what you intended, what you actually achieved, what changed and what should happen next.
This is a practical reason why English matters in academic work. A sabbatical report is not simply a polished account of being busy. It is a readable comparison between an approved plan and a documented research state. Clear writing lets a reviewer recognise meaningful progress without mistaking activity for completion or a promising draft for an accepted publication.
This guide focuses on the report after leave, rather than the application for leave. Its cases are invented teaching examples, and its suggested structure is not a universal form. Follow your institution’s current instructions. English can make evidence easier to understand, while research in other languages, long-term scholarship and quieter forms of progress deserve equally careful recognition.
Choose your reading route
Start with the task closest to yours, or continue through the full article.
- Find requirements and baseline — Chapters 1–3
- Compare evidence and outcomes — Chapters 4–6
- Explain incomplete and shared work — Chapters 7–9
- Write the account and next steps — Chapters 10–12
- Review, discuss and practise — Chapters 13–15
Open the chapter index · Read the wider Why English Matters guide
Find the section you need
Find requirements and baseline
Compare evidence and outcomes
Explain incomplete and shared work
Write the account and next steps
Review, discuss and practise
The final sections contain reader questions and useful next reading.
Begin with the governing instruction
Check the leave approval, current policy and any departmental reporting form. Locate the deadline, recipient, length, required headings and attachments. If the approval refers to an older policy version or the instructions conflict, ask the responsible office which requirement applies to your case.
As checked on 14 October 2026, UCL’s Research Leave Policy and Procedure, marked January 2026, requires a report restating intended outcomes and confirming achievement, submitted to the Head of Department within four weeks of return. It also recognises that progress on less visible, longer-term work may need context such as a memo or writing samples. These are UCL provisions, not a deadline for every institution.
Identify what the report is for
The reader may need to review progress, understand future research or close an administrative requirement. Read the stated purpose. Do not turn a concise outcomes report into an unrelated funding application or a personal career manifesto.
If the document will be discussed at a meeting, prepare the written comparison first. A conversation can add nuance, but the report should remain intelligible to someone who was not present. Important dates, states and changes should not exist only in spoken explanation.
Start a short reporting checklist from the actual instructions. Include the submission route and whether a receipt or acknowledgement is expected. Knowing the requirement early helps you devote attention to the research meaning rather than discovering at the last minute that the wrong form was used. English matters from the first reading: it helps you understand what this particular report must accomplish.
Find what you originally committed to
Bring together the approved proposal, decision and any documented amendments. Identify the objectives and intended outcomes that actually governed the period. A preliminary idea discussed before approval may not be the final baseline, and a later authorised change should not be lost simply because the original document is easier to find.
Use the baseline’s own meaning, even if you improve the wording for readability. Do not quietly redefine an objective to match what happened. If you proposed to complete an analysis but completed a source review instead, explain the difference rather than making both activities sound equivalent.
Where the approved objective was broad, state how you understood it during the work and what evidence supports that interpretation. Avoid pretending that a precise target existed when the original document did not contain one.
Keep amendments traceable
An invented academic planned archival work, then received agreement to change the collection after access became unavailable. The report should name the original objective, the agreed change and the outcome of the revised work. It should not present the substitute collection as if it had always been the plan.
Distinguish a documented approval from an informal possibility discussed with a colleague. If a material change was not formally confirmed, describe its status honestly and use the relevant process to resolve any outstanding question.
The baseline is not a weapon for punishing every deviation. It makes learning visible. Once the reader can see where the work began, they can understand why a change mattered and whether it was reasonable. Without that starting point, even a positive report can become difficult to evaluate because there is nothing stable against which to compare the achievement.
Name the level of the claim
An activity is something you did: visited a collection, held a workshop or tested a method. An output is something produced: a catalogue, analysis, draft or documented protocol. An outcome describes a resulting change relevant to the research purpose. These distinctions are useful writing tools, not a demand that every discipline use one identical evaluation model.
For an invented project, attending three meetings is an activity. Producing an agreed coding guide is an output. Being able to compare previously inconsistent records may be an immediate outcome, if the evidence supports it. The report should explain the connection rather than assuming the activity proves the outcome.
Some valuable work may not yet have generated a public output. Describe its research state precisely. A clarified question or ruled-out approach can be meaningful, but the reader needs to understand what changed and how you know.
Avoid inflating the vocabulary
Words such as impact, transformation and breakthrough can outgrow the evidence quickly. If your achievement is a well-developed draft, say so. Explain why that draft advances the project rather than disguising it as a completed external impact.
Did You Know? Changing a single verb can change the achievement being claimed. “Prepared”, “submitted” and “accepted” describe different states. They are not stylistic alternatives you can swap to make a paragraph sound more varied.
Before editing for elegance, underline the result verbs. Ask whether the evidence supports each one. A report that uses ordinary but accurate words gives colleagues a dependable basis for recognising progress. English’s value here is not making the work appear larger; it is making the real achievement easier to see.
Choose evidence for the claim
Gather the material needed to support each reported outcome. A draft supports a drafting claim; a submission confirmation supports a submission claim. A conversation note may support an account of a discussion, but not necessarily a claim that a formal partnership has been established.
For theoretical work, evidence might include a developed argument and a record of unresolved objections. For empirical work, it might include a checked analysis and a description of what remains untested. For creative scholarship, it might include an appropriate work sample and an explanation of the process. Follow disciplinary and institutional expectations where specified.
Keep the evidence proportionate. The report should not become a dumping ground for every file created during the leave. Select the material that helps the reviewer understand the stated achievement.
Record versions and dates
If an output is evolving, identify the version represented in the report. “Chapter draft, version dated 8 October” is more useful than “chapter completed” when further substantial revision is planned. This lets the reader understand the state at the reporting point.
Where the evidence contains confidential, personal or restricted information, describe it through an approved route. Do not attach sensitive raw material simply to make the report look thoroughly documented. Ask what can be shared and with whom.
Create a simple private index linking objective, claim and supporting record. It helps you check the narrative before submission, even if the institution does not require the index as an attachment. Evidence should make the account inspectable, not bury the reader. Clear English and careful selection work together: the reader can find the reason to believe the claim without being asked to reconstruct the entire project from a folder of files.
Give each objective a short comparison
For every objective, state the intended outcome, actual state, evidence and remaining work. This structure makes differences visible without requiring a defensive tone. It also prevents a major incomplete objective from disappearing beneath a long account of unrelated accomplishments.
An invented objective was to draft two chapters. The actual state is one complete first draft and an evidence outline for the second. State that plainly, then explain the reason and next step. Calling both chapters “advanced” may be technically true but hides a distinction the reviewer needs.
Use headings or concise paragraphs that preserve the objective’s identity. If a prescribed form already provides the comparison, follow it. Do not create a competing format merely because another report online looks attractive.
Recognise completion without overselling it
When an objective was completed, explain what completion means in this context. A finished internal analysis may still require collaborator review. A completed catalogue may be ready for research use without being publicly released. The achievement is real, and its boundary should remain visible.
If several objectives depend on the same work, explain the connection without counting one result as several independent achievements. For example, one dataset might support both a draft and a method note. Describe the different uses while acknowledging the shared foundation.
The comparison should allow a reader to answer, “What is now different from the beginning of the leave?” If they can only identify a list of activities, add the state change. If they think every outcome is externally final, repair the status wording. Accurate comparison gives the report its distinctive purpose.
Describe the sequence of change
When the project changed, state the original approach, new information, decision and resulting work. This sequence helps the reader distinguish a reasoned adaptation from an unexplained drift. Use the information you had at the time rather than narrating every decision as if the eventual outcome had been obvious from the start.
An invented researcher planned a large comparison but found that the available records used incompatible definitions. They investigated the mismatch, narrowed the comparison and documented a more defensible method. The report should explain the incompatibility and the revised question, not merely say the project “evolved”.
Avoid blaming people or organisations when the relevant issue can be described factually. “Access was not confirmed during the leave period” is clearer and more proportionate than a personal account of an administrator’s supposed motives.
Keep the approval status accurate
If a change was agreed through the required route, record that confirmation appropriately. If not, do not imply that the adaptation was formally approved. Explain what happened and clarify any remaining administrative requirement through the institution’s process.
Changes can create useful knowledge. A failed assumption may reveal why a proposed method is unsuitable. Describe the evidence and its implication, while keeping the distinction between learning something and achieving the original target.
This is a mature English skill: explaining a decision with enough context to be fair, without making the account endless. The reader should understand why the change occurred and how it affects the project now. They do not need every frustration, email delay or moment of uncertainty unless it is necessary to evaluate the reported outcome.
State what remains
An incomplete objective needs a precise description. “More work is needed” gives little guidance. “The analysis is complete, but the comparison with the second dataset remains outstanding” tells the reader where the project stands.
Identify the reason in proportion. It might be a dependency, a methodological issue, a change in evidence or a planning estimate that proved unrealistic. Distinguish factors within your control from external decisions without turning the report into an argument that nothing was your responsibility.
Where the original estimate was too ambitious, acknowledge the lesson. Explain how the next plan will be different. A specific adjustment is more useful than either excessive self-criticism or a confident claim that the same schedule will work next time.
Make progress and limitation coexist
An invented manuscript is drafted but not submitted because a key robustness check remains. The report can recognise the substantial drafting achievement and explain why submission should wait. That is more responsible than presenting premature submission as proof that the objective was completed.
If an external decision is pending, name it as pending. Do not claim a future acceptance or grant outcome in order to create a neat ending. Your controllable achievement may be the completed submission, not the eventual decision.
End the account with a realistic next step and its dependency. If a date is only a target, say so. Incomplete work is easiest to discuss when its remaining shape is visible. Clear English allows the reader to recognise both what has been accomplished and what still requires attention, without forcing the project into a false choice between success and failure.
Show the change in understanding
Some research develops through extended reading, conceptual work or careful revision. A leave period may not end with a publicly visible product. Describe what changed in the argument, source base, method or question, and provide appropriate evidence where permitted.
An invented historian refines an interpretation after identifying a contradiction between collections. The achievement is not merely “read extensively”. It is a revised account of the problem, supported by a source note and a clear explanation of the remaining question.
For conceptual work, explain which uncertainty became clearer. Did you distinguish two ideas previously treated as identical? Did an objection reveal a weakness in the initial argument? Did a proposed explanation become less plausible? These are possible descriptions, but use only those supported by your actual record.
Avoid converting quiet progress into imaginary impact
Do not claim that the work transformed a discipline simply because the question became clearer to you. The immediate outcome may be a stronger foundation for later scholarship. Explain that foundation and why it matters to the next phase.
If the institution permits a sample or progress memo, select one that illustrates the change. Give enough context for the reviewer to understand it. An isolated page of specialist prose may be difficult to evaluate without a short explanation of its role.
The report can be optimistic while remaining unfinished. It can say, “The revised structure now supports a coherent first chapter; the next task is to test the interpretation against the remaining material.” This shows direction and achievement without pretending the final work exists. English is useful because it gives developing knowledge a readable shape before that knowledge becomes a finished publication.
Identify who contributed what
Leave outcomes may involve collaborators, hosts, students, librarians or technical staff. Acknowledge the contributions relevant to the achievement and distinguish your own work where evaluation requires it. A report should not make a shared result look like an individual accomplishment merely because one person is writing the account.
Use concrete roles. “The host team provided access guidance; I completed the source comparison” is more useful than a vague declaration of international collaboration. If the relationship is exploratory, call it exploratory. A meeting does not automatically establish an ongoing institutional partnership.
Be careful with claims about other people’s future involvement. Record confirmed arrangements and describe proposed ones as proposed. An enthusiastic discussion can be valuable without obliging anyone to a future project.
Recognise continuity without changing the report’s focus
If teaching or supervision continued under an agreed arrangement, report relevant facts where requested. Do not assume the research report is also the place for a detailed evaluation of every person who provided cover.
An invented academic wants to thank a colleague who supported students during the leave. A concise acknowledgement can recognise that contribution. Any confidential student issue should remain in its appropriate system rather than becoming a narrative detail in a general research report.
Fair attribution makes the account stronger. It shows how the achievement was produced and gives the reviewer a more accurate understanding of the network that supported it. English helps distribute credit precisely, while avoiding both self-erasure and overclaiming. You can explain your own achievement confidently and still make the shared work visible.
Summarise the research state
The opening should identify the leave period, main purpose and overall state of the work. It should not announce that everything was successful before the reader has seen what success means. A concise, bounded summary gives the report a useful centre.
For an invented project: “During the approved leave period, I completed the source catalogue and a first chapter draft. The planned comparative chapter remains in development after a change in collection access. The report explains those outcomes and the next research steps.” This tells the reader what to expect.
Avoid beginning with a long itinerary unless travel itself is the required reporting subject. Places visited may matter, but the report’s main question is usually what the time enabled and what resulted, as defined by its actual instructions.
Match the overview to the body
After drafting, compare the opening with the detailed sections. Does it preserve the biggest incomplete objective? Does it correctly describe the status of outputs? Does it imply an external result that the body says is pending?
A positive opening can still include a limitation. “The leave established a stronger evidence base, while the final analysis remains outstanding” is a useful statement if supported. It does not require either promotional exaggeration or a discouraging tone.
Read the opening to an informed colleague. Ask what they think has been completed and what remains. If their understanding differs from the record, revise the summary. The opening is the report’s first compression test: can the project be made shorter without losing the conditions and distinctions that matter?
Let the evidence set the next task
The next plan should follow from where the work now stands. If the leave exposed a methodological problem, the next step may be resolving it before proceeding. If an output is ready for collaborator review, do not describe an unrelated new project as the immediate priority.
Name the next action, responsible person where appropriate and material dependency. Avoid assigning work to another person unless it has been agreed. “I will discuss the revised analysis with the collaborator” is different from “the collaborator will complete the revision”.
Separate a near-term task from a longer research direction. The reviewer should be able to tell what can happen now and what would require new support or approval. Do not use the report to imply that a future leave period or funding request has already been authorised.
Choose honest milestones
Milestones can describe controllable states: a checked analysis, a revised draft or an agreed protocol. An external acceptance is not a milestone you can promise simply by setting a date. If an external submission is planned, make the distinction visible.
An invented academic writes, “I aim to complete the outstanding comparison by the end of term, subject to confirmed access to the remaining material.” That sentence preserves the target and dependency. If the dependency is unresolved, explain the alternative route rather than treating the qualification as a decorative caveat.
The next-step section gives optimism a practical form. It shows how the leave’s actual achievement can feed into further work, including lessons from what did not proceed as expected. Clear English allows a reviewer to see continuity rather than a disconnected list of future ambitions.
The initial paragraph
An invented academic, Sofia, writes: “The sabbatical was highly productive. I travelled to two institutions, attended several seminars, developed international links and made excellent progress on the book.” The paragraph sounds positive, but a reviewer cannot identify the output state or compare it with the approved objectives.
The approved plan contained three intentions: complete a source index, draft two chapters and establish the feasibility of a comparison. Sofia actually completed the index, drafted one chapter and discovered that the proposed comparison used incompatible categories. These facts give the revision its structure.
The revised account
Sofia writes: “The source index is complete and available in the approved project folder. One chapter is at first-draft stage. The second chapter remains outlined because the planned comparison requires a revised method after the category mismatch was identified.” She then explains the evidence for the mismatch and the next methodological step.
Her visits and seminars appear only where they contributed to those outcomes. She describes one relationship as exploratory rather than established. She acknowledges the colleague who helped test the revised categories, without presenting their contribution as her own.
Why the revision is better
The report now shows accomplishment, incompleteness and learning in one coherent account. It does not turn the incomplete chapter into a completed one, nor does it dismiss the leave because the initial comparison was unsuitable.
Try revising a similar invented paragraph yourself. Replace every broad success adjective with a research state and supporting reason. Keep a warm, confident tone. The task is not to remove positivity; it is to give positivity something concrete to stand on.
Check the words that carry status
Highlight completed, agreed, submitted, accepted, established and approved. Verify each against the record. Then inspect future verbs such as will and target. Are you stating a commitment, a plan or a hope? Use the wording that matches.
Look for compressed phrases that hide a distinction. “Publication completed” might mean a draft is finished, a paper is accepted or the article is publicly available. Replace it with the actual state. “Collaboration secured” might mean a meeting was held, a project was agreed or an agreement was signed. Again, name what happened.
Keep dates, titles and document references consistent. If the output changed its working title, explain only where necessary to help the reader find it. An attachment should be the version described in the narrative.
Remove what does not help the reader
Cut repetitive activity lists and unsupported claims about significance. Keep the evidence and reasoning required to evaluate the objectives. If a detailed appendix is allowed, the main report should still contain enough information to understand the outcome.
Check privacy before sharing. Remove unnecessary personal information about students, research participants or colleagues. Do not use an unapproved external tool to edit restricted material. An invented practice report is a safer way to test a tool’s editing behaviour.
Read the exported document, not only the editing screen. Check headings, page breaks, attachments and whether the recipient can access referenced files. Precision is not only a sentence-level achievement. It includes making sure the actual submitted package carries the same meaning as the version you intended to send.
Bring the comparison, not a performance
If a discussion follows the report, prepare to explain the main achieved outcome, the most important change and the next action. These are useful conversation anchors. You do not need to narrate every day of the leave unless a particular detail is relevant.
Listen for whether the reviewer is asking about evidence, planning, workload or future development. Answer that question directly. If the issue requires an administrative decision, distinguish the discussion from a confirmed approval.
Where feedback identifies a weak claim, return to the evidence rather than defending an adjective. You might clarify the output state, provide an authorised sample or revise a sentence that implies more than intended. A correction can make the shared record more useful.
Capture useful follow-through
After the discussion, record agreed actions through the appropriate process. Identify who will do what and which items remain proposals. Do not treat silence or a positive comment as approval of every future plan mentioned.
An invented researcher discusses a possible new collaboration. The meeting supports further exploration, not immediate resource access. The follow-up note should say that the researcher will contact the relevant office to assess feasibility, rather than declaring the collaboration operational.
The return conversation can connect the leave to teaching, supervision or professional development where relevant. Explain the connection specifically: a new source base might enrich a seminar, or a revised method might inform supervision. Avoid promising a benefit that has not yet been tested. English helps the report become a practical conversation about what can happen next, not merely a document filed at the end of a period away.
Compare a plan with what happened
Students can learn the same reporting skill through a project reflection. Begin with the intended task, describe the actual work and identify evidence of the result. A CCA event, reading project or small investigation gives enough material for an age-appropriate version.
For an invented school project, the group planned to test three designs but tested two because one required unavailable materials. A useful report names the tested designs, what the comparison showed and how the untested design limits the conclusion. It does not claim that the group found the best design among all three.
Parents can ask, “Which part is finished, and which part is still a plan?” Invite the student to show the work rather than supply a more impressive description. This supports honest reflection without making every unfinished task feel like failure.
Use a compact practice routine
Choose one completed activity and answer:
- What did I intend to achieve?
- What is the actual result now?
- What evidence shows that result?
- What changed, and why?
- What would I do next?
Then write a short account that keeps those answers connected. Ask another reader to identify the result and its limit. If they cannot, revise the explanation rather than adding decorative vocabulary.
The secondary English reading and expression guide offers a school-level connection, while Why English Matters explains the wider role of meaning and coordination. The habit can be developed in more than one language. What matters is preserving the difference between intention, action and achievement when communicating with the reader.
Is the report the same as the leave proposal?
No. The proposal describes intended work and its justification. The outcomes report compares that intention with what actually happened. Refer to the approved baseline, including documented amendments, rather than writing a new proposal as if it were the result.
Must every leave end with an accepted publication?
Follow your institution’s actual requirements. Do not assume one universal outcome for all disciplines or leave types. Describe the real output state and supporting evidence, especially where longer-term work remains in development.
How should I describe an objective that remains incomplete?
State what is complete, what remains, why it remains and the next realistic step. Recognise genuine progress without changing the original target retrospectively. Keep external decisions and unresolved dependencies visible.
Should I list every seminar and meeting?
Include activities where the instructions require them or where they explain an outcome. A long itinerary does not by itself show research progress. Select details that help the reader understand the achievement and its relationship to the approved purpose.
Can I attach confidential research material as evidence?
Only through the permitted route and with the necessary authority. Ask what the reviewer can receive. A bounded description or approved sample may be more appropriate than raw personal, restricted or unpublished material.
Can AI help edit the report?
Use approved tools and protect restricted information. Check every revised sentence for changed status, certainty and attribution. AI may make prose smoother while accidentally turning a draft into a completion claim; you remain responsible for the record.
Read writing a sabbatical leave proposal for the earlier planning stage, and writing an academic research statement for the longer research agenda. Explaining scientific evidence develops the connection between a claim and its support.
Consult UCL’s official policy only for its own applicable requirements; use your institution’s instructions for your report. Begin with one objective and write its actual state in a plain sentence. A dependable account of progress starts there.