1. How it usually happens
A defence memo rarely springs to life in one go.
It starts as a draft, goes through internal reviews, client comments, consultant suggestions, cuts, additions, and second thoughts.
In the middle of all this, anything goes:
- versions saved with creative names like final_def_v3_latest
- paragraphs rewritten after a 7:30 PM call
- comments scattered across emails and chats
- attachments that change while the document evolves
A typical episode: two professionals work on the same memo. One sends an "almost final" version, the other tweaks some parts and sends it back. Weeks later, a dispute arises over a critical paragraph. Each is convinced the other inserted that sentence.
There's also a less intuitive angle: documenting a memo in progress isn't just for conflict scenarios. It serves to maintain internal control, especially when the document passes through many hands.
2. What you need to prove
Here, the focus is on the document's lifespan.
You must be able to reconstruct:
- when a certain version existed
- what it contained at that moment
- how it changed over time
- who contributed modifications or guidelines
In concrete terms:
- existence of a specific file version
- precise content of a draft on a given date
- sequence of major edits
- presence or absence of certain clauses
- contributions received via email or chat
- any instructions or intermediate approvals
The more sensitive the memo, the more useful this becomes.
3. What to collect
This requires tidy collection, designed to narrate the document's evolution.
Useful material:
- all versions of the document (Word, PDF, etc.)
- files with active tracked changes or visible comments
- chat exports where edits are discussed
- emails with attachments and instructions
- voice notes or recordings of relevant meetings
- any supporting documents cited in the memo
- auto-saved intermediate drafts
- before/after screenshots of key passages
A practical detail: always keep the "imperfect" versions. Often, they are the ones that best tell the story of what happened.
4. How to proceed
The goal is to turn a pile of drafts into a linear story.
Start by creating a dedicated folder for the defence memo.
Inside, organize everything by date.
Then:
- save each version with a date and brief description
- keep files in their original format
- place related communications next to each version
- note the major edits between one version and the next
- highlight the most delicate passages (additions, removals, tone shifts)
At this point, build a simple timeline:
"Version 1 → sent to client → edits requested → Version 2 → internal review → Version 3"
A small operational trick: when making a major edit, immediately save a copy of the previous version. It's like taking a picture before moving the furniture.
Finally, lock the key versions of the document in time, especially those shared or approved.
5. Mistakes to avoid
A good part of work quality is determined here.
Common mistakes:
- constantly overwriting the same file
- losing intermediate versions
- working on different copies without syncing them
- saving documents without dates or descriptions
- altering already shared files without keeping a copy
- relying solely on the software's auto-versioning
Helpful tips:
- clearly separate drafts, shared versions, and the final version
- maintain consistency in file names
- keep communications alongside documents
- avoid "scrubbing" the edit trails too cleanly
A tidy documentation of versions makes it much easier to explain what happened if doubts arise. Free certification allows you to lock delicate steps in time without burdening the workflow.
6. After the documentation
Once everything is organised, you can use this material strategically.
Depending on the situation:
- share the timeline with involved colleagues or partners
- prepare a summary for the client
- make key versions available to a technical consultant
- use the documentation to clear up any discrepancies
Practical advice is to always keep a "tellable" version of the story, brief and clear, backed by a complete archive.
When a defence memo has a well-tracked history, even the most complex discussions become manageable.