the Workshop

Ask Hugo for the current link.

the Workshop

Build one regional package, then hand it to Ad Ops. Approval opens the roadmap and sign-up desk.

Edit an existing package

Pick a package to load it. Its key stays locked after the first save.

New package

Start with the package itself. Dates, billing, ads, and report language come next.

A short, permanent name that connects this package to its roadmap, desk, and reports. It is not an Airtable record ID. Use lowercase letters, numbers, and hyphens.
Ad Ops approval opens sign-up. After approval, this tracks the package from open through wrapped.
This sets the downstream task shape. It does not limit the tactics, dates, audience, event, or billing.
National shows in every region. Pick one region to keep the package local.
Leave blank when this package is not tied to an event.
Choose either or both. This does not change the tactics or billing.

Dates and signup window

Sign-up deadline defaults to 3 business days before ads go live. Adjust when needed.

Price and billing

Minimum $400. Drafts can leave this blank.
One total price covers the whole package instead of charging each agent or region separately.

The ad ops build

The channels this package actually runs. This is what Ad Ops builds from.

Tick a channel to include it. Tick "John builds this by hand" when John builds that channel himself instead of the shadow setup doing it.
Under each ticked channel, add one ad set per audience it targets. A single Meta campaign often runs one ad set at consumers and another at Compass agents; this is where that gets written down instead of explained later.
Agents can still send custom creative on any package. This choice sets the expected starting point; it does not block their work.

What the report leans on

The tactics the report copy emphasizes. It starts from the channels above, and it is a separate job from the build: you can run four channels and have the report lean on two of them.

One per line. Starts with the channels selected above. Once you edit these words, the Workshop stops changing them.
This is report copy, not the build. Editorial placements are part of Display now rather than a channel of their own, so if the report should lean on them, describe them in plain language here.
Feeds the roadmap's "How It Works" section.

What the report will say

Drafts can skip this section. Before sign-up opens, fill it in and read the exact words below.

Report preview

Your report headline will appear here

The opening sentence will appear here.

What's running
  • Your selected tactics will appear here.

Reports land: cadence will appear here

The closing note will appear here.

Every package needs an explicit traffic report or no traffic report decision before handoff.
Sets the report type. It does not print anywhere on the roadmap.
Defaults to the package name. Change it only when the report should say something else.
Feeds the roadmap's page-one title and its opening sentence.
Feeds the roadmap's "Who We Reach" section.
The words the report uses for where the ads ran. Example: the Peninsula or the North Shore.
Feeds the roadmap's "Editorial Placements" section, and only when the package runs display or CRM ads.
Feeds the Traffic Report headline. It does not appear on the Roadmap.
Feeds the Traffic Report closing note. It does not appear on the Roadmap.
Reports refresh daily. The email goes out on this schedule.
Sets the email schedule. It does not print anywhere on the roadmap.
Leave this unchecked while the package is a draft. It must be checked before sign-up opens.

Tagline choices

We build the creative for this package, so the agent picks from lines you approve.

Offered only to an agent promoting a listing.
Offered only to an agent promoting their brand.
Offered on both. Lines typed before the listing/brand split live here.
Leave all three blank and neither form shows a tagline question at all.

Supporting links

Everything ad ops has to go looking for. These print into the build task.

One per line. A label and a link, or just a link. The ET sheet, location targeting addresses, data lists, placements.
Renders across the top of the agent sign-up form. Leave it blank and the form shows no image.
Usually the ET sheet or location targeting address list. Shows as a "Targeting detail" link on the MA roster only; agents never see it. Leave it blank and the roster shows nothing.

Internal notes

John sees this with the build when you hand off the package.

Ad Ops approval

Save the package, then hand it to John when every section is ready.

Buy-in desk links

These links open two different doors into the same package.

The official external link for emails, landing pages, and other agent-facing outreach.
The shared roster for the Marketing Advisor running the package. Do not use it in public outreach.
The working plan for the MA and Compass leadership. Regenerated from this package every time you save.