1. How it usually happens
Today study paths are told with perfect CVs. Maybe too perfect.
Same courses, same titles, same words: "problem solving", "teamwork", "analytical skills". All correct, all plausible. Also all replicable.
Today you just take an AI and ask it to write the perfect cover letter for a given job request, or task an agentic AI to do everything automatically, select adverts, prepare targeted CVs, and send them.
A recruiter opens ten CVs. All formally perfect for the job. Names change, structure remains. At that point they are no longer reading people, they are reading automated response versions.
On the other side is the student who truly worked: struggled on a project, corrected errors, received feedback, redid things. But all this remains invisible. On the CV it becomes a line.
A simple anecdote: during an interview, two candidates declare the same course and same project work. The first tells it well. The second opens a folder and says: "Here is the first version, here the teacher's feedback, here the revision, here the final submission. Here I changed approach because it wasn't working."
In that moment the difference isn't the project. It's the process.
And the process, today, is the least imitable thing.
2. What you need to prove
Here you are not just proving "what you did". You are showing how you work over time.
The evidence folder must make visible:
- real existence of your works and projects
- evolution of versions (not just final result)
- context where you worked
- received feedback and how you used it
- decisions taken during process
- continuity of your commitment
- consistency between what you say and what you show
In other words: not the perfect result, but the trajectory.
3. What to collect
Here the logic changes: you don't collect "documents", you collect work traces.
Collect:
- different versions of same assignment
- final submitted files
- feedback from teachers or tutors
- emails or messages linked to revisions or submissions
- screenshots of key moments (upload, corrections, comments)
- short personal notes ("here I changed approach because...")
- materials used to build work
- any errors or significant intermediate steps
An important detail: even a well-documented error is worth more than an isolated perfect result.
4. How to proceed
Here comes the key point: you don't build a perfect folder. You build a continuous trail.
Every time you work on something relevant, don't save only the end. Save one or two significant steps. You don't need everything, you need what tells the story.
Organise the folder so it's readable from outside. Whoever opens it must immediately understand what they are looking at.
Practical procedure:
- create a folder per project or course
- keep at least two versions: an intermediate and a final one
- add received feedback or comments
- write a short personal summary (2–3 lines are enough)
- use clear file names with dates
- avoid modifying saved versions
- use ExistBefore to timestamp key work moments
- maintain simple and coherent structure
A step making a difference: the summary. Two lines saying what you did and what you changed. That's where method is seen.
5. Mistakes to avoid
Here errors are all tied to the illusion of perfection.
Beware of:
- keeping only final result
- deleting "imperfect" intermediate versions
- accumulating files without narration
- using incomprehensible names
- reconstructing everything a posteriori
- presenting only "clean" outputs without process
- mixing materials without temporal order
Besides timestamping, method continuity matters. Free timestamping adds a technical time reference anchoring those steps in time, making your path more readable.
6. After documenting
At this point something interesting happens.
The CV remains concise. It's needed. But it's no longer the only level.
If someone wants to truly understand, you can open the folder. Not to show "how good you are", but to show how you work. This changes the conversation type: less declarations, more observation.
You can use it in an interview, an application, or even in a confrontation with a teacher. It becomes a space where your path is verifiable and understandable.
In a context where many contents can be generated, whoever manages to show a coherent trail of their work over time brings something different: a visible method. And that, today, is hard to imitate.