Key points at a glance
- One identified master copy prevents competing final versions.
- Separate the editable source, review PDF and approved release.
- Check the selected file and upload preview before submission.
Why “final_new_really_final” is not a release process
Near submission, feedback, layout corrections and new PDF exports can arrive together. When several files are called final, the name no longer tells you which changes are included. The problem is an unclear approval state rather than untidy naming alone.
Identify one editable master document. Review and apply changes there, then export a new PDF. Avoid independently patching the PDF while leaving the corresponding source unchanged, because the next export would reintroduce the older content.
Use a simple naming convention
An original example is “Surname_Thesis_2026-09-23_v03.docx” for the source and “Surname_Thesis_2026-09-23_v03_REVIEW.pdf” for its export. After inspection, keep a clearly identified release copy. This is an organisational suggestion, not a required filename for your examination portal.
Where the university specifies a naming scheme, follow it for submission. Record which checked internal version was submitted under that name. This preserves the connection even when the official filename does not permit a version number.
Separate working copies, feedback and released files into clear locations. Retain useful older versions without leaving them beside the current print file in the folder used for selection.
Distinguish version records from backups
Give important versions a short change note, such as “corrected Table 4; added Appendix B; refreshed contents”. This makes a later export traceable to actual edits. A modification timestamp alone does not establish that particular feedback was incorporated.
A synchronised service may offer older versions, but that is no reason to skip an additional checked backup. Establish what restoration is available in your environment and try opening an older copy. Keep confidential research material only in storage approved for the project.
Perform a concrete release check
Open the PDF from the location you will use for upload. Inspect the filename, page count, cover, recent corrections and end of the appendices. Look for comments, visible markup and placeholders. Only then identify that version as approved.
After selecting a file in the submission portal or printing configurator, compare the displayed name, extent and preview where available. If the submitted file can be downloaded, inspect it too. A receipt records a submission event; it does not verify the contents for you.
Handle changes after approval explicitly
Create a new version and repeat the affected checks. A change to the reference list can move pages in the appendix, so the review may need to extend beyond the sentence you edited.
If the file has already been submitted or released for printing, establish the permitted correction process with the responsible office or provider. Do not assume that uploading again replaces the earlier file or stops production already in progress.
Final submission context
Formal details can feel like a separate writing task, but they matter just as much for a printed submission. Anything missing, misplaced or inconsistently formatted in the document will also appear in the bound copy.
Use this guide together with your cover page, table of contents, page numbers, source notes and appendices. Prepare the final PDF for printing and binding only after the complete file has been checked.
Practical check before PDF export
- Do headings, chapter structure and page numbers match?
- Are sources, figures and tables included completely?
- Are required elements such as declarations, appendices or the cover page included where required?
- Did you open and check the final PDF after exporting it?
Checklist
- There is one identified master document.
- Source and PDF correspond to the same version.
- Recent changes are recorded and checked.
- The submission filename meets the requirements.
- The file actually selected has been inspected.
Common mistakes
- Labelling competing versions final without a clear release state.
- Editing the PDF and source independently.
- Treating an upload receipt as a content check.
Your checked release file is ready
Select that exact file in the configurator and review the PDF, options and preview before approving the order.
Configure the final PDFRelated content
Explore related guidance on thesis structure, sources, formatting and final submission.
Frequently asked questions
What filename should I use for submission?
Follow the examination portal or department naming rules. Otherwise, use a short, unambiguous name and retain its connection to the checked internal version.
Can I identify the final copy by modification time?
Not reliably. Copying, renaming and saving can change timestamps. A version identifier and concise change note are more informative.
Can I simply replace an uploaded file?
That depends on the system and processing stage. Check the official correction process before relying on a second upload.