Workflows · 11 to 22
More workflows
Twelve shorter playbooks for jobs that come up less often. Each is a variation on the shapes in section 3, and each has one rule worth carrying away.
In plain terms
None of these needs a new kind of build. They reuse the same pieces — a record type for the thing you plan, connections to campaigns, a Workfront project for the work — with different nouns.
Agent activity log
When agents run part of a workflow, add an Agent activity record type: Timestamp (created date), Trigger, Action (Suggested, Applied, Escalated, Skipped), Records touched (connection), Confidence, Human decision (Accepted, Overridden, Pending), and Notes.
It gives the copilot pattern an audit trail — what lets it survive a compliance review and a leadership change.
Event planning
An Events record type with Name, Type, Start and End, Venue, Owner, Status, and Budget, connected to Campaigns and Markets. The event’s workback plan is a Workfront project from a template.
Attendee and registration data stays in the event platform. Connect summaries; do not import lists.
PR and press calendar
Outlets and beats as taxonomies, with Last contacted; outreach records connected to Campaigns; embargo dates as a second date field so the calendar view works. Coverage is a URL in a single-line text field plus a status.
Two dates per outreach record, or the calendar view will not show it.
Internal and executive comms
An Internal comms record type with Audience (connected to an internal-audience taxonomy), Channel, Cadence, Owner, and Status, with approval routing through comms and the executive office. Start from the Communications Planning Studio workspace template.
Keep it distinct from PR. It is often the first non-marketing workspace a Planning rollout expands into.
Ad sales and trafficking
For publishers, broadcasters, and retail-media sellers: RFPs, insertion orders, trafficking, pacing, invoice. Model RFPs and IOs as record types connected to advertiser companies through a Workfront Company connection.
Placement-level delivery data stays in the ad server. Connect summaries.
Retail media and in-store
For CPG and retail: an in-store calendar anchored on the on-counter and store-open dates, with vendor coordination and SKU and planogram connections.
That date pair makes the calendar view work and drives the workback templates in Workflow.
Email production
High volume with a tight handoff to the marketing automation platform — Marketo, Eloqua, Adobe Campaign, SFMC. Email campaigns as Tactics or their own record type, audience definitions connected, QA as a multi-select checklist.
The send and all performance data stay in the platform, synced back as summaries through Fusion.
Experimentation and CRO
Two connected record types: Hypotheses (Statement, Owner, Priority score, Status) and Tests (Hypothesis, Variant, Audience, Start and End, Result, Confidence), connected to the campaigns they inform.
The statistical output stays in the testing tool.
Product launches
A Launches record type connected to Products, Campaigns, and the Workfront projects delivering each workstream, with go/no-go gates as approval-field pairs. The Product Management workspace template is a starting point.
That template is built for the product organization, not marketing — trim it accordingly.
Influencers and creators
Talent as a taxonomy (Name, Channels, Audience size, Tier, Vetted) and engagements as records connected to Campaigns, with deliverables, compensation, and performance summaries.
Compensation detail belongs in the finance system. Keep the commitment, not the payment.
Field and co-op marketing
Role- and region-filtered views for a large field force, plus co-op funds: Partner, Period, Budget, Used, and Available as a formula. Distribution is usually a public request form plus a Workfront dashboard.
When the field force has no Workfront access, a thin custom app on the Planning API is the surface.
Higher ed, nonprofit, advocacy
Enrollment marketing, alumni and donor communications, advocacy campaigns: constituencies as an audience taxonomy, outreach as records, cadence on the calendar view.
It is the small or mid shape with different nouns. Resist building something bespoke.
Sources
- Adobe Workfront Planning documentation — terminology, request forms, automations, object limitations: Experience League article index
- Planning API reference, versions 1 and 2: developer.adobe.com/wf-planning
- Package contents and entitlements: Adobe Workfront product description