Chronology should explain scholarly change
A list of file dates rarely captures how a dissertation developed. The informative events are intellectual transitions: a broad interest becomes a defined question; search results become a reasoned literature set; raw material becomes an analysis release; reviewer feedback produces an identifiable revision. Each entry should therefore state both an outcome and its consequence.
The timeline is an index to existing records, not a diary invented once concerns have arisen. Emails, approved proposals, search logs, field notes, code commits, draft releases, comments and submission receipts may be used only where they genuinely exist and can lawfully be disclosed. A technical timestamp should never be treated automatically as evidence of who performed the work.
The responsible academic body decides what matters in a formal process. Confidential research, third-party personal data and protected communications require careful handling. The workflow below is practical record organisation, not legal advice and not a forecast of an examination decision.
Match the strength of each record to the claim
An approved proposal can establish the authorised topic on a date, but it says little about daily writing. A draft records text at a saved state, not necessarily every preceding step. Version histories reveal changes, yet synchronisation, imports and time-zone conversion may alter metadata. For each evidence type, state what it supports and what lies beyond it.
Give records stable IDs and maintain a separate register containing filename, location, release, sensitivity and a short description. The timeline should cite that register rather than embed every attachment. Checksums can identify the supplied copy precisely, but they do not prove authorship or the historical time of creation.
For emails, an accurate description of the decision, date and sender role is often sufficient. A disclosure copy can minimise private side discussions and addresses while the original remains protected. Institutional rules concerning access, redaction and procedural fairness take priority.
Ask different questions at each stage
- Brief and question: When were title, scope and supervision agreed? Which boundary changed?
- Literature search: Which search round introduced a concept or altered the corpus?
- Methods and material: Which approval, pilot, data release or selection decision mattered?
- Analysis: Which run produced reported results, and what was rejected with reasons?
- Writing and review: Which chapters were reviewed and how was feedback handled?
- Closure: Which checks produced the final package and how is the submitted file identified?
Research streams often overlap. Literature work need not stop before analysis, and drafting may begin during fieldwork. Do not force a linear story. Stream labels such as L for literature, A for analysis and W for writing can keep simultaneous activity legible.
Represent missing and conflicting metadata fairly
State a gap directly: “No contemporaneous record; reconstructed from draft D-004 and meeting agenda.” An honest absence is preferable to an inferred date presented as fact. If two services display different times, preserve both and describe a possible technical cause as a possibility rather than a conclusion.
Use the resolution the evidence warrants. “May 2026” is correct where only the month is known; “17 May at 14:32” is not. Cloud dates may refer to upload rather than creation. A Git commit identifies a repository event, but does not by itself attribute every line to one person.
Test the route against originals and submission
For every row, perform a backwards check. Does the evidence ID open the named release? Is the date recorded there or inferred later? Does the next version show the stated consequence? Then verify both endpoints: the timeline begins with the actual brief and ends with the exact file that was submitted.
Ask someone unfamiliar with the project to follow three sampled entries. They should understand what changed, which record supports it and why it mattered. Define technical abbreviations in the register. Explain contradictions rather than silently normalising them.
The source-note trace sheet supplies detail for the literature stream. The authorship viva questions help turn records into a calm explanation. Related tools sit in the examination procedures hub. The sole foundation route here is the guide to interpreting similarity evidence.