ExistBefore
IT

Legal

How to prove the prior existence of a professional opinion

A professional opinion is valued not just for what it says, but for when it was formulated. If you want to avoid arguments over "who thought of it first", you need to clearly establish the milestones. This guide helps you document prior existence practically, starting from the files you already have.

4 min read

1. How it usually happens

An opinion originates in a meeting, takes shape in a draft, and gets refined through emails and revisions. Then something happens: another consultant reaches similar conclusions, or the client claims those insights arrived later.

At that point, the question surfaces: when did that opinion actually exist?

Typical scenarios:

  • an opinion sent informally before the official version
  • a solution proposed ahead of other professionals
  • an interpretive approach shared verbally and formalised later
  • a document circulated internally before transmission

A curious case: a consultant discovers the client forwarded their opinion to third parties without indicating the original date. When a dispute hits, the document exists, but the "when" has grown cloudy.

There's also a less obvious angle: often the opinion's true value lies in its early timing. Getting there first changes the weight of the consultancy.

2. What you need to prove

Here the focus is both temporal and content-based.

You must be able to prove:

  • that the opinion existed on a certain date
  • what its content was at that moment
  • that it wasn't constructed after subsequent events
  • how it eventually evolved over time

In concrete terms:

  • existence of the opinion file
  • precise content of the initial version
  • date when that version was already available
  • any differences compared to later versions
  • connection between the opinion and context (email, mandate, request)

If the point is "I had already thought of that earlier", you need a clear, readable trail.

3. What to collect

This builds the evidence package telling the origin story of the opinion.

Useful material:

  • original opinion files (Word, PDF, etc.)
  • prior drafts with similar content
  • sending or sharing emails
  • chats foreshadowing conclusions or reasoning
  • preparatory notes or memos
  • any attachments cited in the opinion
  • subsequent versions with edits
  • client documents that triggered the opinion

A practical detail: even a three-line email can be decisive if it already contains the core of the opinion.

4. How to proceed

The aim is to build a credible, easy-to-follow timeline.

Start by gathering all versions of the opinion and related materials.

Put everything in a dedicated folder.

Then:

  • order files by their real creation or sending date
  • rename clearly (e.g., 2026-02-10_opinion_draft)
  • align each version with related communications
  • pinpoint the earliest trace where the key content appears
  • highlight differences between versions

At this point, construct a narrative sequence:

"Initial request → first draft → internal sharing → sent to client → revision"

A little trick: look for the moment the idea is already fully formed, even if expressed informally. Prior existence is often proven there, not in the elegant PDF version.

Finally, lock the most relevant files of the sequence in time, keeping original versions intact.

5. Mistakes to avoid

Here you risk losing value without realising it.

Common mistakes:

  • keeping only the final version of the opinion
  • overwriting previous drafts
  • separating documents from communications
  • renaming files without temporal logic
  • editing files after sending without saving copies
  • relying exclusively on system file dates

Helpful tips:

  • always keep early versions, even rough ones
  • keep files and context linked (emails, chats)
  • avoid actions that alter original files
  • make the sequence readable even to an external third party

Good documentation makes it clear the opinion already existed during a specific phase of the process. Free certification helps lock these moments down without complicating daily work.

6. After the documentation

Once the timeline is built, use it purposefully.

Depending on the situation:

  • share the sequence with the client to clarify timings
  • make it available to other involved consultants
  • use it in negotiations or confrontations
  • prepare it as backup for potential technical or legal evaluations

Practical advice is to always have a summary version ready: a few clear steps, backed by orderly documents.

When prior existence is well-documented, the value of your work becomes far more visible.