Buyer readiness

Campaign readiness dashboard

Published July 3, 2026. Updated July 4, 2026. Status: evergreen worksheet.

Use this dashboard when a contextual, private marketplace, or direct campaign is almost ready to launch but the team still needs one shared view of package proof, creative approval, destination QA, inventory contracts, reporting fields, and readout limits.

A campaign can be attractive and still be unready. The dashboard separates the parts that need commercial agreement, ad operations, buyer handoff, and measurement judgment so the launch decision is not hidden inside a campaign name or a loose email thread.

Editorial launch packet board organizing campaign scope, inventory, creative, destination, measurement, and owner records before launch. — Readiness is a packet, not a feeling. A campaign should not move to trafficking until scope, inventory, creative, destination, measurement, and ownership are visible in one shared record.

Use intake worksheet

Launch packet snapshot

Before the worksheet becomes an approval record, name the five records that decide whether this campaign is ready, needs revision, or should stay on hold.

Scope

Commercial scope is fixed

Buyer objective, package ID, eligible context, exclusions, format mix, and package owner are visible before launch work starts.

Inventory

Trafficable record is visible

Placement IDs, accepted sizes, device rules, refresh expectations, report keys, and seller-path checks match the package.

Creative

Offer and destination are approved

Display or native files, click URL, backup assets, landing-page QA, source capture, and routing have an approval trail.

Measurement

Readout language is bounded

Primary signal, comparison rule, buyer-side fields, closeout timing, and strongest allowed claim are named before data arrives.

Owner

Open fixes have owners

Required fixes, launch ticket, approval status, next owner, and review date are attached to any revise or hold decision.

The first pass is a triage, not a score. A red item means the campaign should stay on hold when the missing record changes what was bought, what can be served, or what the report can fairly claim. A yellow item means the campaign can move only after a named owner proves the fix.

Three-lane campaign readiness matrix showing hold, revise, and ready states across launch checkpoints. — The matrix keeps a small fix from looking like full readiness. Hold means the campaign contract or readout boundary is not safe yet; revise means a named owner can close a specific gap before traffic starts.

1. Campaign record

Campaign name, buyer contact, and owner

Launch window and decision date

Package ID, deal key, and reporting key

Decision this campaign should inform

3. Evidence links to attach

Record	What it proves	Link or owner
Audience intent map	The reader job and clean-fit category match the buyer offer.
Package proof sheet	The package, eligible URLs, exclusions, placements, and reporting grain are visible.
Inventory readiness matrix	Placement IDs, ad-unit paths, accepted sizes, refresh rules, and reporting keys match.
Creative acceptance record	Display files, native fields, click URLs, labels, active dates, and backup sizes are approved.
Landing-page QA record	Destination speed, message match, form path, source fields, consent, and routing are ready.
Reporting field dictionary	Package, placement, creative, device, traffic-quality, outcome, and conclusion fields are named.

4. Launch controls

Eligible and excluded contexts are written in the campaign brief. Every creative size maps to an accepted placement and device class. Every paid unit has a clear advertising or sponsorship label. UTM, placement, creative, package, and destination fields will survive into reporting. Viewability, invalid-traffic, refresh, and device rules are visible before launch. The report cannot upgrade from descriptive language to lift language unless a comparison was designed before launch.

5. Decision record

Ready to launch: no material package, creative, destination, inventory, or reporting gap remains. Revise before launch: the campaign can proceed after the named fix is verified. Hold: the campaign should not launch until the package, destination, or readout boundary is rebuilt.

Required fixes before traffic starts

Strongest allowed readout language

Next owner and due date

Approval record or launch ticket

Build the launch packet

The dashboard is most useful when it produces a small packet that can survive handoffs between sales, ad operations, analytics, and the buyer. Save the fields that changed the launch decision, not every draft note. The final packet should make three things clear: what was bought, what can be trafficked, and what the first readout is allowed to say.

Launch packet folder connected to evidence cards for audience fit, package proof, inventory, creative, destination, and reporting fields. — Evidence links make the launch decision portable. The buyer, ad operations team, and analyst should be able to trace the launch packet back to the records that define what was bought, what can be served, and what the first report may say.

Packet item	What to attach	Launch risk it controls
Commercial scope	Buyer objective, package ID, eligible page set, exclusions, and promised format mix.	Prevents a broad campaign name from hiding a narrower delivery contract.
Inventory contract	Placement IDs, accepted sizes, device rules, refresh expectations, and report keys.	Prevents trafficking against inventory that differs from the buyer-facing plan.
Creative and destination proof	Approved files, click URL, backup assets, landing-page QA, form path, and source capture.	Prevents avoidable underperformance from broken or mismatched handoffs.
Measurement boundary	Primary signal, comparison rule, buyer-side fields, data close date, and strongest allowed claim.	Prevents descriptive delivery from being rewritten as causal lift after launch.
Owner record	Named owner, required fixes, approval ticket, and next review date.	Prevents a revise decision from becoming an unowned launch delay.

Escalate before launch when

The package changed. Reopen the intake worksheet if the buyer objective, eligible context, exclusions, format mix, or pricing basis changed after the original proposal.

The destination changed. Recheck page speed, message match, source capture, consent language, and lead routing before paid traffic starts.

The report language changed. Rebuild the measurement boundary if a descriptive campaign is now expected to support lift, incrementality, or quality claims.

The owner is unclear. Hold the launch decision when a required fix has no owner, due date, approval record, or buyer-side dependency deadline.

How to read the dashboard

A ready campaign has a stable package, a trafficable placement contract, approved creative, a working destination, and report fields that match the claim the buyer expects to make. A revise decision is useful only when the fix is small, owned, and visible in the approval record. A hold decision protects the buyer and publisher when the missing item would change what was bought, what can be served, or what the report can fairly say.

Final campaign launch decision board showing ready, revise, and hold outcomes after package, creative, destination, inventory, and measurement checks. — The final decision should be boring in the best way: ready when every launch record is aligned, revise when one owned fix remains, and hold when the missing item changes the campaign promise or the strongest supportable readout.

Worked example: revise instead of launch

Suppose a buyer has approved a contextual package and creative files, but the landing page was changed the morning before launch. The team can still use the dashboard without turning the meeting into a long debate: separate the stable records from the changed record, then decide whether the change alters the buyer promise or only needs a bounded fix.

Dashboard signal	Decision	Reason	Owner before traffic starts
Package proof and eligible page set are unchanged.	Ready	The buyer-facing scope still matches the proposal and deal key.	Sales owner keeps the approved package record attached.
Creative files, labels, and backup sizes are approved.	Ready	The units can be trafficked without changing the public sponsorship presentation.	Ad operations attaches final files and active dates.
Landing page changed after QA.	Revise	The destination may still be acceptable, but speed, message match, form path, source fields, and consent need a fresh check.	Marketing owner reruns destination QA and adds the result to the launch ticket.
Readout language depends on buyer-side leads.	Revise	The source field must survive the new form path before the report can describe lead quality.	Analytics owner confirms captured fields before the campaign starts.
No owner can confirm the changed destination.	Hold	A missing owner turns a small revise item into an unbounded launch risk.	Publisher lead holds launch until the approval record is complete.

Launch routes

Choose the next readiness check.

Use these routes when the dashboard exposes a missing buyer, package, inventory, creative, destination, or readout field.

Audience fitConfirm reader intentCheck whether the offer belongs with the reader job before the package is priced. IntakeRebuild the proposal recordLock objective, package lane, creative handoff, floor inputs, and readout boundary. InventoryCheck placement contractsMatch placement IDs, sizes, device classes, refresh rules, and reporting keys. CreativeApprove assets before trafficVerify file specs, claims, labels, active dates, backup sizes, and click paths. DestinationTest the post-click pathConfirm page speed, message match, form path, consent, source fields, and routing. ReadoutPreserve the claim boundarySeparate delivery, response, comparison strength, and next action before renewal language.

Pair with

Start with the audience intent map, media kit, private marketplace buying terms guide, and advertiser intake worksheet. Then attach the contextual package proof sheet, private marketplace package brief template, private marketplace deal review checklist, inventory readiness matrix, creative asset acceptance checklist, landing-page QA worksheet, reporting field dictionary, campaign readout QA checklist, and creative and destination troubleshooting matrix before the final report becomes a renewal or retest decision.

Keep reading

Choose the next guide

After the launch dashboard, move into the deal gate, reporting fields, or final readout QA that preserves the campaign record.

Deal gateConfirm activation readinessCheck proof, identifiers, placement scope, reporting fields, exceptions, and launch thresholds. Report fieldsName the fields before launchKeep package, placement, delivery, traffic quality, outcome status, and comparison fields aligned. Readout QAAudit the final reportSeparate delivery, response, quality, comparison strength, and next action before renewal language is written.