The Anatomy of a Document Disaster

Document disasters in marketing agencies come in a few reliable flavours. The specifics vary — the industries, the clients, the exact document — but the underlying failures are consistent. Here's a catalogue of the most common ones and what they reveal about systems that could have prevented them.

Scenario 1: The Wrong Version in the Board Presentation

A marketing agency delivers a quarterly strategy deck to a CMO who presents it internally to the board. The deck contains a section with preliminary projections that were superseded in a revision sent two days before the presentation — but the CMO printed the attachment from the original email.

The board questions the numbers. The CMO is caught off-guard. The agency gets blamed for the confusion, even though they did send the updated version.

What failed: Email-based delivery creates version fragments with no hierarchy. When a revision is sent as a new email, there's no mechanism to deprecate or withdraw the original.

The fix: Portal-based delivery where the document at the stable link is always the current version. No new email needed for revisions; the portal updates in place.

Scenario 2: The Proprietary Framework in the Wrong Hands

A fractional CMO develops a go-to-market framework during a client engagement and delivers it (along with supporting documents) via Google Drive. The engagement ends. Months later, the CMO meets with a prospect in a different company — who casually mentions they've seen "basically the same framework" from someone who used to work at the previous client.

What failed: Document access wasn't revoked at engagement end. The former client had the proprietary framework in their Drive indefinitely. When employees move between companies, the documents go with them.

The fix: Time-bound access on sensitive documents. Engagement close that revokes all permissions. For proprietary frameworks — "Never Share" tagging that keeps them out of client-accessible folders entirely.

Scenario 3: The Live Document Shared Before It Was Ready

A junior team member shares a Google Doc link with a client "to get their thoughts on the direction" — before the document has been reviewed internally. The client reads a draft that includes an internal note ("this client will probably push back on pricing here") and a comment thread that was meant to be private.

What failed: Sharing a live Google Doc gives the recipient access to all comments and revision history, including anything marked as internal.

The fix: Never share live Google Doc links with clients. Share through a portal that controls exactly which content is visible, stripping internal comments and history.

Scenario 4: The Engagement That Never Closed

A client engagement ends somewhat ambiguously — the client goes quiet rather than formally terminating. Six months later, the agency realises the client has been downloading files from the original shared folder (including a new strategy document for a different client that was accidentally placed in the wrong folder).

What failed: No engagement close process. Without a deliberate wrap step, the access simply continued indefinitely.

The fix: A close checklist that's non-optional — no engagement is done until the portal is wrapped, access revoked, and the folder archived.

---

Frequently Asked Questions

What are the most common document management mistakes in marketing agencies?

The most common mistakes are: sharing live Google Doc links that expose internal comments, sending document revisions as new email attachments without deprecating the original, failing to revoke access at engagement end, and mixing files across client folders during busy periods.

How can a marketing agency prevent IP from reaching competitors?

The most effective technical controls are: access expiry dates on all sensitive documents, an explicit engagement close step that revokes all permissions, "never share" tagging for proprietary frameworks (keeping them out of client-facing folders), and using a portal rather than raw Drive links so you retain control of what the client sees.

How do you handle it if a client still has access to documents they shouldn't?

If you discover active zombie access, revoke it immediately via Google Drive's sharing settings or your portal's access controls. Then communicate proactively: "As part of closing out our engagement, I've cleaned up document access — all files from our project have been archived. Your portal remains available in read-only mode for your reference." This frames revocation as a professional service, not a punitive action.