Superdirector editorial worksheet · N10026-002

Turn a creator request into one client decision

Preserve the client's request, propose one choice that changes the creator brief, and record the evidence and answer. This is a decision handoff, not a generic campaign checklist.

This file has no save or send function. Copy your entries into your own document before leaving, or use the downloadable CSV. A browser may retain local form data; avoid entering confidential client information on a shared device.

Download CSV template and fictional example

Blank decision record

1. Preserve the request and buyer task

Client request, verbatim

Keep the original words and requested count, even if the count later changes.

Product and version to be shown

Write “unverified” if the usable build is unknown.

Buyer task

What must a specific buyer understand or do?

Audience

Name a buyer role or group, not “everyone.”

Desired organizational result

A desired result is not yet a measured outcome.

2. Make one choice and expose uncertainty

Proposed campaign decision

A choice that would change the first creator shortlist or brief.

Alternatives and why deferred

Evidence available now, with source and date

Evidence still missing

Candidate observable signal and verification status

Do not label an untested event “measured.”

3. Record the client's answer

Decision owner and date

Decision record version

Client disposition

Accept, amend, reject, or pending; quote the change.

Reconsideration trigger

What new evidence would change the choice?

Invented teaching case · no client or campaign result

Fictional completed example

The example shows an amended, still conditional direction. It does not show a launched campaign or verified product claim.

Request, verbatim: “Can we get 12 creator videos next month?”
Product/version: Fictional scheduling app; releasable build not yet verified.
Buyer task: A café operations manager reviews an uncovered shift.
Audience: Café operations managers considering scheduling tools.
Desired result: More qualified demo conversations; desired, not observed.
Proposed decision: V2 pending: explain the manager-review task; show any product screen only after the product-owner build check. This replaces unapproved v1: “show software automatically detecting uncovered shifts and alerting a manager.”
Alternative deferred: Generic testimonials, because this fictional buyer question concerns one workflow. Revisit if buyer research points elsewhere.
Evidence available: Fictional client intake note F-INTAKE-01, dated 2026-10-27: buyer task and qualified-demo goal, unverified automation wording, and an offered product walkthrough. The walkthrough has not been viewed.
Evidence missing: Offered walkthrough, product-owner confirmation of the releasable screen and permitted wording, and destination and demo-request event checks.
Candidate signal: Demo-request submission from the campaign destination; instrumentation unverified.
Owner/date: Fictional marketing lead; sample date 2026-10-28.
Version: Example v2 after client amendment; returned for acceptance, with no real approval.
Client disposition: Fictional reply F-REPLY-02, dated 2026-10-28: AMEND — remove the automatic-detection claim and describe a manager reviewing an uncovered shift. V2 is not yet accepted.
Reconsideration trigger: The workflow is absent from the releasable product, or buyer research identifies a different first task.

This original worksheet accompanies “How to turn a vague creator request into one client decision.” It is informed by AMEC's distinction between communication outputs and outcomes but does not reproduce AMEC's planning worksheet.