1. How it usually happens
You write a story idea, maybe a few pages. Then you start a script. You share with a producer, editor, colleague.
From there the journey begins:
- file is forwarded
- calls, meetings, pitches are made
- someone takes notes, someone else reworks
Months, sometimes years later, something familiar appears: similar plot, characters reminding yours, a narrative structure sounding too familiar.
A little-discussed point: many ideas aren't copied word for word. They are "absorbed". Names change, scenes move, but skeleton remains.
An author told of presenting a story with a very specific protagonist and peculiar narrative structure. Two years later sees different project, modified plot, but same central mechanism. Problem wasn't proving similarity, but proving that structure existed beforehand.
2. What you need to prove
In these cases, point isn't proving someone copied you. First step is much more concrete: proving your work already existed in a certain form.
Concretely:
- that story or script were already written
- that they included distinctive elements (plot, characters, structure)
- that they existed in a certain version on a certain date
- that any subsequent developments derive from that base
- that it's not a vague idea but developed content
In practice:
"This story, with these elements, was already defined before."
3. What to collect
For stories and scripts, strength lies in showing process besides result.
Collect:
- original files (Word, Final Draft, PDF)
- intermediate story and script versions
- synopsis, pitch document, treatments
- email or messages sharing material
- development notes
- any feedback received
- recordings or pitch notes (if available)
- drafts with comments or revisions
- any attachments sent together (moodboard, references)
An important detail: even an "imperfect" but dated version can be very useful. Shows idea was already structured.
4. How to proceed
Goal is building a clear timeline of your creative work.
When you have a significant version:
- save file in stable format (PDF or equivalent)
- assign clear name (title + version + date)
- also keep source file
Then:
- use ExistBefore to timestamp that version
- repeat process for every important step
- link every version to a communication (email, sending, pitch)
During development:
- avoid working always on same file overwriting it
- maintain distinct versions
- keep even minor modifications if they affect structure
A useful habit:
treat every story evolution as a "stage". Every documented stage makes creative path more readable.
5. Mistakes to avoid
Some behaviours make proving prior existence difficult:
- keeping only latest script version
- not saving previous versions
- sharing files without keeping identical copy
- using generic names like "final_script.docx"
- modifying already sent files without trace
Useful precautions:
- always maintain a version history
- keep surrounding materials too (pitch, synopsis)
- avoid relying solely on online platforms without exports
Free timestamping lets you quickly secure every version, so your work's temporal sequence remains clear.
6. After documenting
Once you have documented your work, you can use it more consciously.
You can:
- present project with greater confidence
- better manage collaborations and developments
- have a clear base in case of similarities with other projects
- organise your creative archive over time
If doubtful situations emerge:
- compare materials
- identify common elements
- evaluate direct confrontation based on documented contents
When creative path is tracked, explaining where a story comes from and how it developed over time becomes much simpler.