MarketingCampaign asset production and approval workflowMedium

Move the campaign forward. Keep every review in view.

Move from the campaign brief to a review-ready asset package while tracking owners, versions, and blockers.

Works inSharePointTeamsWordPowerPoint
Preview — real Cowork captures and reviews still pending

Not a verified training release. The deck’s prompts and workflows have not yet been run in this environment. Authentic screenshots, translation review, and model approval are still required.

Business context

Does this sound familiar?

The copy is ready. The approval trail is not.

Every campaign brief fans out into dozens of assets, each drafted, reviewed and approved by hand. Review routing lives in email threads, so blockers surface late and owners lose track. Publishing final versions and notifying channel owners is a manual checklist. Asset cycle time, not creative quality, sets the launch date.

The workflow to aim for

One production workflow across assets, versions, and approvals.

Revenue Growth: campaigns reach market sooner, capturing more in-quarter pipeline. Cost Savings: production and review hours recaptured across the marketing team. Risk Mitigation: every asset passes an approval gate before publishing; nothing ships unreviewed.

Revenue opportunityCapacityRisk reduction

What could this be worth to your team?

Value of the time saved each year

USD 80,000

For the whole team, not per person — the salary cost of the hours Cowork could free up. Not cash back.

1,000People in the team
80%Active rate
90%Conservative risk discount

Training deck headline: USD 682K — The deck also counts revenue and risk effects; this estimate counts recaptured time only.

How you would measure success

Asset cycle time · approval latency · blockers resolved · launch readiness

Cookbook defaults

Illustrative model · review pending · not cash savings or net ROI
Cookbook-authored estimate; not the original slide’s benefit figure.

How this is calculated

Under these assumptions, 14,400 annual hours of capacity are valued at USD 80,000.00 after a 90% risk reduction. This is not a promise of cash savings.

Annual hours saved before risk adjustment
14,400
Active users in this function
800
Hourly employee cost (USD)
USD 55.56
Value retained after risk adjustment
10%
  • Campaign asset production: USD 80,000.00
    300 × 25 × 6 × 0.8 × 40% h × USD 55.56/h × 10%

Only labor capacity is monetized. Revenue and risk benefits remain qualitative to avoid unsupported totals and double counting.

Source-informed inputs: deck slide 110. Formula: cookbook capacity model v1, not a reconstruction of the missing pilot formulas.

Is it worth running?

Cost vs value — one run and one month

For the marketing team · one run per campaign

666.7×value for every USD 1 spent on Cowork
MeasureOne runOne month (≈ 25 runs)
Time saved60 h1,500 h
Value of that timeUSD 3,333.33USD 83,333
Estimated Cowork costUSD 5.00USD 125
Value left after costUSD 83,208

It pays for itself if each run saves at least 5.4 minutes of work.

How cost and value are estimated
  • Cowork is billed per use in Copilot Credits. Credits per run are an estimate set by your cookbook admin — actual use depends on how much context is read, how many steps and tools run, and how long the task takes. The credit price is also set by the admin (the pay-as-you-go list price is USD 0.01; prepaid packs can be cheaper).
  • Value here is the salary cost of the time saved. The yearly team estimate above is more cautious and keeps only part of it; on that basis one run is worth USD 333.33.
  • Microsoft Copilot Credit Estimator · How Cowork billing works (Microsoft Learn)

Credits per run are set by the cookbook admin.

What you will work toward

  • Asset production package
  • Review and approval state
  • Publish queue

Why Cowork?

Campaign assets, versions, reviewers and blockers are tracked across a dozen threads. Cowork combines: the campaign brief, asset enumeration and drafting, version and review routing, blocker resolution, and publishing preparation with owner notification, into one production workflow.

On this page

Before you start

What you are asking Cowork to achieve

Move from campaign brief to ready-to-ship assets without losing control of reviews, blockers, or versions. Keep production moving while preserving brand and legal discipline.

Works in

SharePointTeamsWordPowerPoint

Connects to

Campaign brief; SharePoint/OneDrive; asset/messaging library; Teams/Outlook; CMS; tracker

Complexity

Medium Medium. Needs an approved messaging library and a reviewer roster; no custom build.

Good to know

Replace bracketed placeholders with your intended context before submitting. Use only sources you are authorized to access. The original prompts include approval boundaries for sharing, scheduling, publishing, or writebacks; preserve those boundaries. Reading this page does not authorize any action.

Requires the relevant Microsoft plugin, approved connector, agent, API, local-browser path, or governed export. Availability depends on tenant configuration, permissions, region, and source-system controls. Cowork acts only within the signed-in user’s authorized access.

Run it in Cowork — step by step

  1. Open Cowork and start a new task

    In Microsoft 365 Copilot, select the Cowork toggle at the top of the left navigation. Can’t see it? See “Do you have Cowork?” in Getting started, or ask your IT admin.

  2. Fill in the brackets

    The prompt has placeholders in [square brackets]. Replace each one with your own details:

    [Campaign Name]

  3. Copy the prompt and send it

    Copy the prompt, paste it into Cowork, replace the highlighted brackets, then send. This is the original wording from the training deck.

    Prompt · English original
    I’m turning a campaign brief for [Campaign Name] into the full asset package and need one workflow across drafting, review, and publishing.
Read the brief:
Use the campaign brief, the asset library, brand and legal review materials, the publishing system or CMS, the project tracker, and relevant SharePoint, OneDrive, Teams, or Outlook context.
List the assets required, their purpose, and what already exists versus what still needs to be created.
Drive production:
Track each asset through drafting, review, and final approval.
Flag blockers, missing inputs, and version issues before they slow the launch.
Prepare draft review notes or routing messages for the owners who need to weigh in.
Publish when ready:
Create the review-ready package and the publish queue, but hold all final publishing, sends, and writebacks for my approval.

    Copies the exact original text.

  4. Follow Cowork through the workflow

    Cowork works through these stages from the deck. Use them to follow its progress and notice where it asks for missing information.

    1. Read → Campaign brief

      📷 Screenshot coming soon

    2. Enumerate → Assets and owners

      📷 Screenshot coming soon

    3. Draft → Versions and track changes

      📷 Screenshot coming soon

    4. Route → Review and approval

      📷 Screenshot coming soon

    5. Resolve → Blockers with owners

      📷 Screenshot coming soon

    6. Stage → Publishing and notify owners

      📷 Screenshot coming soon

  5. Review before you approve

    The prompt asks Cowork to create the review-ready package and publish queue, but hold all final publishing, sends, and writebacks for your approval.

    Check the result against “What you will work toward”, confirm the cited sources, and look at anything flagged as missing. Only then approve the next action.

What you get back

A production package showing the required assets, draft status, review path, blockers, approval state, and publish-ready outputs, with owners and next actions clearly assigned.

About this material

The deck provides workflow stages and prompts, not a verified click-by-click walkthrough. No additional task prompts or sample datasets are supplied here. Actual Cowork runs and screenshots are still required before this becomes a verified training guide.

Adapted from source slides: 48–49 · Nifty Fifty