You sent the master copy of your NDA template directly to a counterparty. They signed it and emailed it back. Now your master is signed by Acme Corp, and the next time you want to use it, you've got Acme's signature embedded.
Never share the master. Always share a copy. Here's the discipline.
The master vs the working copy
A master PDF is the canonical version of a document — your template, your branded asset, your reference. It lives in `/Templates/` or `/Assets/`. It does not leave that folder.
A working copy is a duplicate, made for a specific use. It lives in `/Working/`. It's the one that gets edited, signed, sent. When done, it gets archived.
Why this matters for templates
Templates have the highest risk. You use them dozens of times. If you accidentally sign or edit the master, every future use carries that contamination — your NDA template has someone else's signature, or your invoice template has last month's totals.
The discipline: copy first, edit second. `/Templates/NDA.pdf` → copy to `/Working/<client>/NDA.pdf` → edit there, sign there, archive there.
Why this matters for finals
If you have a signed master contract, sharing a copy (rather than the original) protects against the recipient accidentally re-signing, annotating, or editing the original. They get a copy; you keep the canonical.
For maximum protection, flatten the copy before sharing so it's pixel-locked.
The five-second discipline
Right-click → Duplicate. Or `Cmd+D` / `Ctrl+C`. Always work on the duplicate. The master folder is read-only by convention; nothing changes there without explicit intent.
Five seconds per share. Permanent protection against version contamination.
FAQ
What if I accidentally edit the master?
If you have backups (you should), restore the previous version. If not, this is the cost of the lesson — recover what you can and adopt the discipline going forward.
How do I mark a folder as 'master only'?
Operating system permissions can make folders read-only. Naming conventions also help — `_MASTER_` prefix or a separate `/Templates/` folder are common.
Should the team share masters?
Shared masters are fine — read-only access for most, write access only for owners. The discipline applies regardless of solo or team.
What if I need to update a master?
Deliberate action: open in Flint edit, make the change, save back to the master folder. Quarterly review is a good cadence.
Five seconds of discipline. Permanent version safety. Copy first, work second in Flint — every time, no exceptions.