A campaign brief is the contract between strategy and execution. When an agent drafts it, the brief still needs a brand owner and a legal owner before anything ships. Dock holds the brief as a structured row, links back to the HubSpot campaign, Marketo program, or SFMC journey, and records who approved what. Nothing leaves Dock until both approvals land.
HubSpot, Marketo, and Salesforce Marketing Cloud stay the system of record for the raw data. Dock is the system of record for what the agent interprets. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
The brief row
| Campaign | Platform record | Agent draft summary | Brand reviewer | Legal reviewer | Status |
|---|---|---|---|---|---|
| Q3 retention nurture | HubSpot campaign 8841 | Win-back for dormant Pro accounts; tone empathetic, no discount language | Priya R. approved 05-28 | Marcus L. approved 05-29 | Ready to build |
| Spring launch teaser | Marketo program 2207 | Pre-announce v4 to opted-in list; FTC disclosure on roadmap claims | Priya R. approved 05-27 | Marcus L. requested edits | In revision |
| Enterprise webinar push | SFMC journey ENT-114 | Three-touch sequence; legal flagged unverified ROI stat in touch 2 | Open | Marcus L. blocked 05-30 | Blocked |
The row holds the draft, the strategy doc, the cited guideline sections, the platform pointer, and the approval trail. The agent never edits its own draft after submission; revisions create a new row version with a diff.
The workflow
- A marketer files a request through the intake form.
- The agent reads the linked strategy doc and the current brand guidelines, then pulls the platform record from HubSpot, Marketo, or SFMC.
- It drafts the brief into a new row with citations to the guideline sections it relied on.
- Brand review fires first. Priya sees the draft, the cited guideline paragraphs, and the agent identity.
- Legal review fires next, scoped to claims, disclosures, and competitor mentions.
- On dual approval, the row flips to Ready and the build team picks it up. The build hand-off mirrors the one in Dock for design.
If the agent cannot resolve a guideline conflict, it flags the row and stops. Humans decide.
Why this matters
Briefs fail when the source of truth drifts. The agent writes faster than a human, but speed without attribution creates the same problem at higher volume. Dock preserves the chain: which guideline version, which strategy doc, which agent, which reviewer, which platform record. That chain is what makes the workflow auditable later, and it is the same chain we use for agent audit and compliance across other functions.
Brand research from Marq describes how inconsistent presentation degrades trust. The CMO Council library tracks adjacent patterns in content governance. Row-level reviewer attribution is the cheapest way to keep agent-drafted work inside the lines.
The marketing motion sits next to the sales motion described in Dock for sales. Reviewers and agents both authenticate the same way; see agent identity for the underlying primitive.
Run the campaign-brief workflow in Dock.
FAQ
Who owns the brief once the agent drafts it? The requesting marketer owns it. The agent is attributed as drafter, not author. Approval rights sit with named brand and legal reviewers.
What happens when brand guidelines change mid-review? The row records the guideline version the agent used. If guidelines update, the row is flagged stale and the agent re-drafts against the new version. The previous draft stays in the history.
Does the agent ever push to HubSpot, Marketo, or SFMC directly? No. The row stores the brief and the platform pointer. A human or a separate build agent applies the change to the platform after dual approval, and that handoff is logged.
How is reviewer identity verified? Reviewers authenticate through the same workspace identity system the agent uses. The pattern is described in agent identity.
