1. How it usually happens
The scene is less epic than thesis submission, but much subtler. You are in a classroom or on a call. The teacher, with an almost confidential tone, says: "For grading, practical cases matter most. Slides are indicative". Someone nods, someone writes, someone is looking for the Wi-Fi link.
Then comes the course WhatsApp group. One writes: "Guys he said long bibliography isn't needed, right?". Cascading answers: "Yeah I think so", "Dunno I understood opposite", "Wait I'll ask the tutor". Tutor answers at 10:47 PM with a 38-second voice note saying three important things and a joke. Next day, nobody remembers the joke and half the people remember the three things wrong.
On the other side, teacher and admin office live a different movie. Teacher explained a criterion, maybe multiple times, but did it verbally or in different contexts. Admin receives inconsistent questions and answers synthetically, often without reconstructing full context. Tutor tries mediating, but moves among scattered messages.
A typical anecdote: during an online course, teacher shares an updated slide saying "This is the correct grading criteria version". A student downloads it. Next day, same slide is replaced on platform with a slightly different version, without notice. At course end, someone disputes grade saying "criteria were different". Whoever had saved the slide and screenshotted the lesson with teacher's comment manages to reconstruct sequence. Others argue from memory, which is a fascinating but unreliable tool.
2. What you need to prove
Here you are not defending an opinion. You are trying to show that certain indications truly existed in a certain form and at a certain time.
Concretely, you might need to prove:
- content of instructions given verbally or via chat
- grading criteria communicated informally
- specific version of slides or course materials
- subsequent modifications compared to initial indications
- promises or clarifications given by teacher or tutor
- context where indications were provided (lesson, call, message)
The goal is linking a phrase or document to a precise moment, preventing it hanging in "I thought that".
3. What to collect
You need to build a small coherent archive, without becoming a professional investigator.
Collect:
- chat screenshots (WhatsApp, Teams, Slack, etc.) with visible date and time
- complete exports of relevant conversations
- emails with instructions or clarifications
- PDFs of slides or shared materials
- platform screenshot with file version and date
- any lesson recordings or clips (if available)
- personal notes, preferably dated
- voice message screenshots with transcription or summary
- different versions of same document, if changing over time
A useful detail: when screenshotting, always include course name, date, and, if possible, context (e.g., chat or platform header). An isolated phrase loses strength.
4. How to proceed
The idea is simple: every time you receive an important indication informally, turn it into something stable and readable by others too.
After a lesson or call, take a few minutes. If something relevant was said, capture it immediately. Chat screenshot, slide save, short note written by you with date and context. If teacher said "this is the correct version", that phrase deserves to be hooked to the material.
Then organise everything in a dedicated course or project folder. Avoid leaving evidence scattered across gallery, downloads, and various apps.
Practical procedure:
- spot important indications as they emerge
- save or photograph content (chat, slide, platform)
- add, if needed, a short contextual note (e.g., "said during lesson on...")
- keep different material versions if they change
- use ExistBefore on files or archives containing these proofs
- maintain simple and readable folder structure
A small gesture making a difference: if receiving vague chat indications, you can write a summary message ("Confirming that for grading practical cases matter most and bibliography is reduced") and see if anyone corrects. Even that answer becomes part of context.
5. Mistakes to avoid
Biggest risk is trusting group's collective memory. Works well for picking where to dine, much less for reconstructing grading criteria.
Beware of:
- saving only fragments without context
- relying on never-re-listened voice messages
- losing previous material versions
- taking screenshots without date or header
- mixing personal notes and official instructions without distinguishing them
- modifying saved files after deeming them "reference"
- ignoring small variations in documents
Besides timestamping, maintaining order, clarity, and consistency among materials is useful. Free timestamping adds a technical time reference helping place those contents in time without complications.
6. After documenting
Once everything is collected and organised, next step is using it smartly.
If doubts or different interpretations emerge, you can share relevant parts with teacher, tutor, or admin, showing what was said or shared and when. This often reduces arguments, shifting confrontation from "who remembers better" to "what shows from materials".
You can also keep everything until course or project end, in case you need to clarify a grade or request.
In a European context, where informal communications and digital tools constantly mix, having an orderly and readable trail makes every confrontation simpler. No need turning every lesson into a dossier: just prevent important info evaporating between one chat and another.