One Master Document, Zero Panic: Version Control for the Dissertation Endgame

There is a specific kind of dread that arrives around the six-weeks-to-go mark. Your supervisor has sent back a chapter with forty comments. The library has emailed about an overdue interlibrary loan. And somewhere in your downloads folder there are now four documents called things like Chapter3_FINAL.docx, Chapter3_final_ACTUAL.docx and Chapter3_final_use this one (2).docx, and you genuinely cannot tell which one you last edited.

None of this is a sign that you are bad at dissertations. It is a sign that you have hit the stage where the work stops being about writing and starts being about logistics. That is normal, and it is fixable in an afternoon.

One master, everything else is a photocopy

The single most useful decision you can make this week is to nominate one file as the master document. Not a folder. Not a ‘latest version’. One file, with the whole dissertation in it: title page, abstract, chapters, references, appendices.

Why one file? Because the alternative — a folder of separate chapter documents — is where dissertations quietly go wrong. You fix a citation in Chapter 2, but you fixed it in the copy you sent to your supervisor, not the copy you are now calling the master. Multiply that by six weeks and you have a bibliography with two personalities.

So: assemble everything into a single document now, even if it is ugly. Even if the headings are inconsistent and the page numbers are nonsense. You can fix formatting in an hour. You cannot easily fix a version split that has been running since March.

From this point on, every edit happens in the master. If your supervisor wants to comment on Chapter 4 alone, you export Chapter 4 out of the master, send that, and paste their comments back in. The master never leaves your sight.

Name your exports like an adult

Dated exports are your safety net. Every time you send something to a supervisor, a proofreader or a friend, save a copy of exactly what you sent, named with the date and the recipient.

Something like Dissertation_master_2026-10-14_sent-to-supervisor.docx is unglamorous and slightly tedious. It is also the only reason you will be able to answer the question ‘did I include the new methodology section before or after that meeting?’ in three weeks’ time.

A simple naming convention works better than a clever one:

• Master files: Dissertation_master_YYYY-MM-DD.docx
• Sent files: Dissertation_export_YYYY-MM-DD_sent-to-[name].docx
• Reviewed files: Dissertation_returned_YYYY-MM-DD_from-[name].docx

Note the ISO date format. It sorts properly in any folder, which means your files line up in the order things actually happened. It also removes the ambiguity of 03/04 versus 04/03, which matters if anyone outside the UK ever looks at your files. They won’t, but still.

One rule: never overwrite yesterday’s export. Disk space is cheap; reconstructing an argument you deleted at 1am is not.

The change log that fits on one page

You do not need Git. You do not need a version-control system designed for software engineers. You need a table with four columns and about twenty rows.

Create a document called CHANGELOG.docx and add a row every time you make a change that a reader would notice. Columns: Date, What changed, Where, Why.

That last column is the one people skip, and it is the one that saves you. ‘Cut the paragraph on Bourdieu from Chapter 2 — supervisor said it repeated the lit review.’ Six weeks later, when you cannot remember why that paragraph vanished, the log tells you. It also protects you if an examiner asks why a section was removed: you have a dated, reasoned record, not a vague memory.

Keep it short. A change log that takes four minutes to update will get updated. A change log that requires a paragraph of prose will not.

Backups: three places, one of them off your laptop

You have heard this before and you will hear it again, because it keeps being true. Keep your work in three places:

1. Your laptop, obviously.
2. A cloud folder — OneDrive, Google Drive, iCloud, whichever your university gives you. Check that version history is switched on; it has rescued more dissertations than any study guide.
3. Something offline — an external drive, or even a monthly email to yourself with the master attached.

Do a deliberate backup at the end of every working session, not just when you remember. Two clicks. Then close the laptop.

A quick word on university systems: if your institution uses a platform for submissions, treat it as a delivery mechanism, not a storage system. Never let the only copy of your work live inside a web portal you cannot easily export from.

Keep your voice when the comments pile up

The version-control routine exists to protect something more important than tidiness: your argument and your voice.

When you work through supervisor comments, do it in one sitting per chapter and log the substantive changes as you go. If a comment asks you to soften a claim, note the original wording in your change log before you cut it. If you are unsure whether a suggestion improves the work, keep both versions in the log and decide later, when you are not tired.

This is also where a dated export earns its keep. If you ever need to show that a sentence was yours, written before a particular conversation, the dated file does that quietly and without argument.

Handing over the right file

In the final week, you will send your dissertation to at least three people: possibly a proofreader, certainly the submission portal, and probably yourself, as a final sanity check.

Before each handover, do a sixty-second check:

• Is the file name clear and dated?
• Is the title page correct, with the right year and course code?
• Are track changes and comments switched off in the export?
• Does the reference list match the in-text citations?
• Have you saved a copy of exactly what you sent?

Then open the file on a different device. It takes two minutes and it catches the formatting gremlins that only appear when a document leaves the laptop it was written on.

The last six weeks of a dissertation are stressful enough without a folder full of mystery files. One master document, dated exports, a one-page log and three backups will not write the thing for you. But they will make sure that when you press submit, the file you send is the one you actually meant to send — and that you can prove it.