WorkFocus
Marketing Ops Blueprint
Designing marketing operations on Adobe Workfront Planning
Ignite Your Content Supply Chain

Section 1 of 9

Start here

A practical guide to designing marketing operations on Adobe Workfront Planning: which structure to build, what to leave where it already works, and the mistakes that cost a quarter to undo.

In plain terms

Planning is where marketing writes down what it is running, for whom, and why. Workfront Workflow is where the work gets done. Keep those two jobs apart and almost everything else in this guide follows.

The one rule

Adobe Workfront Planning is the planning and metadata layer: what marketing is running, for whom, in which market, under which brand. Workfront Workflow is the execution layer: projects, tasks, assignments, proofing, timesheets.

Model campaigns, briefs, taxonomies, and audiences in Planning. Model the work that delivers them as Workfront projects and tasks, connected to those Planning records. Every page in this guide applies that rule to a different job.

Press Play for a short tour, or select any box to jump to it.

The one rule: Planning holds the plan, Workflow holds the workTwo layers. Above, Adobe Workfront Planning holds campaigns, briefs, taxonomies such as brands, regions, and products, audiences, and request forms. Below, Workfront Workflow holds projects from templates, tasks and assignments, proofing and approvals, timesheets, and resource management. An automation in Planning creates the connected Workfront project; the project's status and health come back to Planning as lookup fields. Marketing automation, CRM, DAM, and warehouse systems stay outside, integrated through Fusion rather than copied in.Adobe Workfront Planning — the plan and its labelsCampaignswhat we runBriefswhat is asked forTaxonomiesbrands, regions, productsAudiencesfor whomRequest formsthe front doorWorkfront Workflow — the workProjectsfrom templatesTasksand assignmentsProofingreviews and approvalsTimesheetshoursResource managementcapacity and loadautomation creates the connected projectstatus and health come back as lookupsMAP, CRM, DAM, warehouseintegrated through Fusion — not copied in
Figure 1. The one rule. Blue is Planning, gold is Workfront Workflow, grey is outside both. The same three colors mean the same thing on every page of this guide.
Two layers

Press Play, or select any box in the diagram, to walk through the rule one step at a time.

The most common way these builds go wrong. Rebuilding tasks, assignments, or proofing cycles as Planning record types. It feels tidy on day one and leaves you with two sources of truth and no audit trail by month three. If someone asks for a Tasks record type, ask what Workflow is not giving them first.

Who this is for

Written for the person who will design and run the build — usually a marketing operations lead or a Workfront administrator — and useful to the people they build it for:

The problem it solves

The pain that brings teams to Planning is usually the same: swivel-chair work across many single-purpose tools, no central answer to what is running where, campaign plans in slide decks while execution lives in Workfront projects, capacity invisible until someone burns out, briefs lost in inboxes, and budget versus actual reconciled by hand every quarter.

A second pain is specific to Workfront customers. Teams that have run Workfront Workflow for years often modeled campaigns as projects, or as portfolios and programs, with campaign details in project custom forms. That metadata is trapped: it cannot be sliced by brand, region, audience, and funnel stage. Planning exists to lift that layer out. If that is your situation, section 7 shows how.

How to use this guide

Read sections 1 and 2 first. Then go to whichever job you are trying to fix.

  1. Start here — this page: the one rule.
  2. Scope it first — the three questions to answer before you build anything.
  3. Pick a shape — five structures, from a lightweight tracker to an enterprise portfolio, with a picker that recommends one.
  4. How Planning works — objects, fields, connections, views, and the limits that shape a design.
  5. Workflows — ten playbooks, one page each, plus twelve shorter ones.
  6. Build layers — structure, user experience, execution, and integration.
  7. Moving in — from Airtable, spreadsheets, and Workfront itself.
  8. Don’t do this — the anti-patterns, with reasons.
  9. Quick reference — limits, field types, and API basics.

What Planning is not

Not Workflow

Planning does not do tasks, assignments, hours, proofing, or resource leveling. Workfront Workflow does, and does them well.

Not a DAM

There is no file field. Approved assets live in AEM Assets, Workfront Documents, or the DAM you already run, connected to Planning records.

Not a contact database

A record type holds at most 25,000 records. Contacts belong in the CRM or marketing automation platform; connect summaries.

Not an AI spreadsheet

There is no field type that fills itself in with AI. AI runs through assistants and Fusion scenarios that write into ordinary fields, with a person committing the result.

A note on accuracy

Every number in this guide — record limits, field caps, API rates, package gates — was checked against Adobe’s documentation when it was written. Adobe ships Planning monthly and revises these. Verify anything load-bearing before you build on it, using the sources below.

Sources