Campaign plan.pdf18 pages
Document upload
Start with what’s already been written.
Add a text-based PDF, PowerPoint (.pptx), or a Google Doc you select. Sage pulls the useful details into the draft, cites the source, and flags anything that still needs an answer.
Create your workspaceWhere it came from
Keep the source trail with the detail.
Each pulled answer stays linked to its source—with a PDF page, PowerPoint slide, or Google Doc tab path when available. Sage shows when sources agree and separates conflicting answers for the requester to resolve. The requester chooses whether the original file or Google Doc link stays with the submitted brief.
- Audience
- Existing customers Campaign plan · p. 4
- Deliverables
- 3 social formats + web hero Combined from 2 sources
- Launch date
- Needs confirmation Two dates found
One brief at a time
Choose the workstream before Sage builds the draft.
A planning deck may cover a launch, a partner campaign, and a loyalty push. The requester selects the work this brief is about, and Sage uses only that part of the source.
THIS FILE COVERS MORE THAN ONE CAMPAIGNWhich workstream belongs in this brief?
Spring collection launchPaid social, website, May launch
Retail partner campaignIn-store signage, June launch
Summer loyalty pushEmail, app, July launch
Google Doc updates
Review the latest version before updating the brief.
Sage imports the Google Doc as a snapshot. Re-importing shows a diff and leaves the existing snapshot in place until the requester chooses whether to keep accepted details or recalculate from the new snapshot.
Launch notesImported today at 9:42 AM
Review updateAlready acceptedAudience · Existing customersProtectedNew in sourceFinal photography due April 28Shown in diff
Review the diff, then keep accepted details or recalculate from the new snapshot.
For details you use again and again
Save recurring production specs for the next request.
Keep approved sizes, formats, and production notes in the Specs Library so requesters can choose them with the deliverable.