ExistBefore
IT

Creative

How to protect a ghostwritten text

In ghostwriting your name disappears, but your work remains. To prevent the boundary between collaboration and reuse becoming blurry, you need to document well what you wrote and when. Here is a practical method to do it without complicating your life.

3 min read

1. How it usually happens

Ghostwriting has an implicit rule: text comes out with someone else's name.

You write articles, books, LinkedIn posts, newsletters. Receive inputs, calls, voice notes. Then turn everything into coherent content.

In the daily flow:

  • client integrates text with modifications
  • content is adapted into other formats
  • text parts are reused in new contexts
  • other collaborators touch your files

At some point distinguishing becomes difficult:

what originated from you and what was added later.

A typical case: ghostwriter prepares an article series. Client uses them as base for a book. Project grows, involves other professionals, and initial contribution becomes invisible. Nobody openly disputes it, it simply gets lost in the process.

2. What you need to prove

In ghostwriting, point is not claiming text publicly. You need to be able to prove your contribution precisely and documented.

Concretely:

  • that text was written by you in a certain form
  • that it already existed before subsequent modifications
  • that it included specific structure, tone, and contents
  • that it was delivered on a certain date
  • that any developments derive from that base

In practice:

"This content already existed like this, before being adapted or integrated."

3. What to collect

For ghostwriting it's fundamental linking text to work process.

Collect:

  • original text files (Word, exported Google Docs)
  • intermediate versions with modifications
  • received briefs (email, chat, documents)
  • transcripts or notes from calls and interviews
  • delivery emails or messages
  • any client revisions
  • shared document screenshots
  • work notes (outline, bullet points)

A useful detail: keeping content sources too (voice notes, interviews) helps show transformation work, not just final result.

4. How to proceed

Key is building an orderly trace of your contribution, without interfering with client's flow.

When you have a significant version:

  • save text in stable format (PDF or equivalent)
  • assign clear name (project + date + version)
  • also keep source file

Then:

  • use ExistBefore to timestamp that version
  • repeat step for main stages
  • link every file to a communication (send, revision, approval)

During work:

  • keep versions separate (draft, revision, final)
  • avoid overwriting same file always
  • also keep client modifications

A useful habit: think of ghostwriting as invisible but traceable collaboration. Every important step deserves saving.

5. Mistakes to avoid

Some behaviours make reconstructing your contribution difficult:

  • working only on shared docs without saving local copies
  • keeping only final version
  • not archiving brief and starting materials
  • using generic file names
  • losing track of revisions

Useful precautions:

  • keep your own copy of every relevant version
  • keep context too, not just text
  • clearly separate client input and your output

Free timestamping helps you secure every key step, so your work remains recognisable even when your name doesn't appear.

6. After documenting

Once you have documented your work, you have a solider base to manage collaboration.

You can:

  • better clarify perimeter of your contribution
  • manage revisions and expansions more orderly
  • have a reference in case of extensive reuses
  • build a professional archive of your work

If unclear situations emerge:

  • compare versions
  • reconstruct contribution sequence
  • evaluate direct confrontation based on concrete elements

In ghostwriting visibility is limited, but documentation can be very precise.