Overview
This Google Docs source-of-truth auditor helps marketing teams find drift across shared briefs, messaging docs, campaign plans, and process notes. It is for the workspace where everyone is collaborating, but nobody is fully sure which document is final.
Juno reviews the relevant Google Docs, spots stale owners, duplicate briefs, conflicting guidance, missing approval status, and unclear next actions, then produces a cleanup register. The result is a practical audit table plus a short summary of what to fix first.
Why you should reduce document drift
Shared documents are useful because they are easy to create and easy to change. That same ease can create quiet chaos: old launch plans stay discoverable, draft messaging gets reused, and ownerless docs keep circulating after decisions have moved on.
Google Docs supports collaboration and version history, which helps teams understand document changes when the right file is already known: Google Docs Editors Help. This playbook focuses on the harder marketing question: which files should still be trusted at all?
Run it before a planning cycle, sales enablement refresh, website rewrite, product launch, or campaign reset. The cleanup register gives the team a fast path to archive stale docs, merge duplicates, clarify owners, and mark the real source of truth.
Step-by-step
- 1Confirm the marketing area to audit, such as campaign planning, product messaging, content operations, sales enablement, or launch process.
- 2Search Google Docs for relevant briefs, plans, messaging files, process notes, approval records, and likely duplicate documents.
- 3Review each document for owner, status, last meaningful update, approval language, links to newer guidance, and conflicts with nearby docs.
- 4Classify each issue as stale, duplicate, conflicting, ownerless, unclear, or ready to keep, then assign a practical risk level.
- 5Create or update a cleanup register with the document title, owner, status, issue type, risk, recommended action, and next person to confirm.
- 6Summarize the biggest patterns so the team can decide what to update, merge, archive, or mark as final.
Frequently asked questions
How large should the audit be?
Start with the highest-risk document set: active campaigns, messaging, customer-facing claims, launch timing, and process docs that multiple teams rely on. A focused audit beats a giant inventory nobody will clean.
What counts as a stale document?
A useful default is no meaningful update in the last 90 days, but the real test is whether the document could mislead current work. Old reference material can stay if it is clearly labeled.
Does Juno delete or archive documents?
No. The default output is a cleanup register with recommendations. A human owner should approve archive, merge, or status changes before anything is treated as final.
