ExistBefore
IT

Household

How to document handing in a thesis, essay, or project work

The thesis isn't truly finished when you press "Send". It is finished when you can reconstruct, without panic, which file you submitted, when, to whom, and with what confirmations. Before closing the laptop and declaring yourself a new person, create a small orderly trail: it can save you days of hunting the phantom PDF.

6 min read

1. How it usually happens

Handing in a thesis, essay, or project work often has a theatrical moment: the student, pale as a secondary character in a courtroom drama, uploads the file at 11:58 PM. The platform spins. The mouse stays still. The Wi-Fi decides to take a spiritual break. Then a message appears: "Upload completed". Relief. Screenshot? Maybe not. Receipt? Perhaps. File name? "definitive_final_thesis_last_real.pdf", because academic dignity at that hour has already evaporated.

The problem arises when, days later, a small but lethal sentence arrives: "Not received". Or: "The file won't open". Or even: "The uploaded version is not the correct one".

Here comes the second perspective, the one often missing. On the other side are teachers, tutors, admin offices, committees, and platforms. Sometimes they truly see very little: an upload list, a truncated file name, a system-generated date, a shared folder with twenty-seven similar documents. An admin office might face three "project_work_final.pdf" without knowing which is the right one. A teacher might have received the email, but without the attachment because the system blocked it. A tutor might have an intermediate version, maybe sent for review, and confuse it with the final one.

Then there is also the less poetic side: delays, disorganisation, vague communications, shifted responsibilities. The phrase "it does not appear on system" can indicate a technical error, but also a convenient way not to look harder. Documenting well serves precisely to clear fog from the scene.

A typical anecdote: a student submits her project work on a platform that accepts the file, shows a green tick, and then, silently, replaces the original name with a string like "submission_847392_final". She, cautious out of anxiety rather than method, had taken a screenshot showing file name, time, and confirmation screen. When they write her that "the correct document is missing", she retrieves both the timestamped original PDF and the automatic receipt. She doesn't win a lawsuit, she simply prevents turning an upload into a treasure hunt with tired people and overloaded inboxes.

2. What you need to prove

The point is not "proving you are right about everything". The point is much more practical: being able to show that a certain file existed, had a certain content, and was sent or uploaded in a certain context.

In the case of a thesis or project work, you usually need to document:

  • which file was the definitive one;
  • which version you submitted;
  • when the file already existed in that form;
  • when and how you sent or uploaded it;
  • who it was addressed to;
  • what confirmations you received;
  • what submission instructions were communicated;
  • any platform errors or anomalies;
  • any answers from teacher, tutor, or admin office.

The important thing is linking file, context, and communications. A PDF alone says little. A PDF with email, screenshot, receipt, and timestamp becomes much easier to read.

3. What to collect

Before submitting, gather evidence as if preparing a small logbook. No paranoia: just order.

You should keep:

  • original final file, without modifying it after submission;
  • any previous versions, if they can clarify work evolution;
  • complete sent email, with recipients, date, subject, and attachment;
  • any answers received from teacher, tutor, or admin office;
  • platform screenshots before and after upload;
  • screens showing file name, date, time, and confirmation message;
  • automatic upload receipts or internal protocols;
  • official submission instructions;
  • relevant chats or messages, exported or saved readably;
  • possible screen recording of upload, if procedure is delicate;
  • a ZIP archive if sending multiple docs together or preserving the file.

A very concrete trick: also screenshot the folder showing the file with name, size, and date. It's a small thing, but often helps link the kept document with the submitted one.

4. How to proceed

Start with the final file. Give it a human name, readable even by someone not living in your Downloads folder: for example "Thesis_Name_Surname_Date.pdf" or "ProjectWork_Name_Surname_FinalVersion.pdf". Avoid dystopian novel titles like "last_most_final_OK2.pdf".

Then create a folder dedicated to submission. Put inside the file, received instructions, any required attachments, and, if needed, a ZIP version. At this point you can use ExistBefore on the final file or the archive containing the whole submission package.

When sending or uploading the document, document the path too. If sending an email, keep sent mail and verify attachment is present. If using a platform, screenshot most important screens: file selection, completed upload, final confirmation. If receiving an automatic receipt, save it immediately as PDF.

Practical procedure:

  • prepare final file and truly close it;
  • save it in a dedicated folder;
  • create a backup copy;
  • gather submission instructions;
  • timestamp file or ZIP before sending;
  • send or upload document;
  • save screenshots, receipts, and confirmations;
  • keep sent email or platform confirmation;
  • send, if appropriate, a brief summary message.

The summary message can be simple: "Confirming I have uploaded/sent the file [file name] regarding [thesis/project work] on [date]. I remain available should there be opening or reception problems." Sober, useful, un-theatrical. The opposite of your "final_final" folder.

5. Mistakes to avoid

The most common mistake is continuing to touch the file after submitting it. Opening it, converting it, compressing it, renaming it, saving it again: all seemingly harmless activities that can create confusion if you later need to reconstruct what you submitted.

Also avoid relying only on the phrase "the platform logs everything anyway". Maybe yes, maybe logs little, maybe you have no access to that data when needed.

Beware of:

  • modifying file after timestamping;
  • uploading a different version from the timestamped one;
  • using confusing file names;
  • sending overly heavy attachments without checking dispatch;
  • saving only cropped screenshots, without date or context;
  • losing automatic receipt;
  • using chats or apps that compress or alter files;
  • confusing draft sent to tutor with final version;
  • deleting emails, notifications, or confirmations as soon as everything seems resolved.

Besides timestamping, it remains important keeping the original file well, maintaining a clear communication timeline, and creating evidence readable even by those who don't know the story. Free timestamping gives you an extra technical time reference, without turning submission into a complicated administrative ritual.

6. After documenting

After documenting submission, put everything in order. Create a folder with final file, receipts, screenshots, emails, and relevant messages. Make a backup copy, preferably somewhere other than main computer.

If someone disputes reception or version, answer calmly and chronologically. Indicate when you created the file, when you timestamped it, when you sent or uploaded it, and what confirmations you received. Avoid furious messages written at 2 AM: they rarely improve evidence quality, though sometimes improve mood for twelve seconds.

You can turn, depending on the case, to teacher, tutor, admin office, course coordinator, platform technical support, or competent institution office. If matter gets serious, bring an orderly fact reconstruction, with documents and dates.

A clean dossier makes the difference between "let's help this student" and "let's open another ticket".