From Email Attachments to a Single Source of Truth

The most expensive workflow in your organisation is the email chain titled “Contract_DRAFT_v7_final_REALLY_final.docx”. By the end of the thread, three people are commenting on three different versions, one of which lives in Outlook on someone's laptop in Mombasa.

Papyrus eliminates this — not by banning email, but by replacing the attachment with a stable link.

The pattern that breaks

The broken pattern looks like this:

Drafter emails Word doc to Reviewer A
Reviewer A makes changes, emails to Reviewer B (with Drafter cc'd, sometimes)
Reviewer B makes more changes, emails back to Drafter
Drafter merges (mostly), emails to Approver
Approver requests one change, replies-all with marked-up PDF
Drafter sends “final” version to Counterparty
Six months later, in dispute: “which version did we actually sign?”

By the end, you have seven copies of the document, none of which are authoritative.

The pattern that works

The Papyrus pattern is the same conversation, but with a link instead of an attachment:

Drafter uploads to Papyrus, shares link with Reviewer A
Reviewer A makes changes in the same file, increments minor version
Drafter sees the new version in their notification feed
Both reviewers comment in the document, not in a parallel email thread
Approver clicks the email's one-click approval link, signs digitally
Counterparty receives a one-time, expiry-bounded external share link
Forever after, “the contract” is one URL

What you get for free

By making the document the single source of truth, you also get:

An audit trail of every edit and view — who, when, from where, with what comment
Permissions that actually work — share-by-link doesn't bypass RBAC; the recipient sees what they're allowed to see
No “I never got the latest version” — there is only one version; previous ones are accessible as version history
Search across all collaboration — comments and @mentions are indexed alongside document content

What email is still good for

Email is still the right tool for:

Notifying people that a document is ready for their attention (Papyrus does this for you)
Short conversations that aren't about a document
Communicating with people outside the tenant who shouldn't have a Papyrus account

The trick is to use email to point at the document, never to transport it.

A 14-day pilot

If you want to test this without committing the whole company, run a 14-day pilot with one team that produces a high volume of documents. The change-management heavy-lift is teaching them to say “I shared a link in Papyrus” instead of “I sent it to you”. The rest is muscle memory within two weeks.