Feedback needs
a next decision.

Decide who can say yes,
before asking for feedback.

A campaign approval workflow is an agreement about decisions: who owns each question, which version they review, what their answer permits and what happens when the work changes. A review platform stores conversations and files. The project team still has to define the authority behind those records. Start with that agreement rather than a list of software features.

Contributors, consolidators and approvers

A contributor provides useful input: an account manager spots an audience mismatch, a designer proposes a stronger hierarchy, or a channel specialist checks an aspect ratio. A consolidator turns those inputs into one coherent response. An approver decides whether a defined piece of work can proceed. One person may hold several roles on a small project, but the roles should remain clear.

For a studio working with a client, name the client decision-maker and a replacement who can act when they are unavailable. If brand, regional marketing and procurement all need to participate, list their questions separately. “Client approval” is too vague when one stakeholder accepts the concept and another controls the budget. The creative lead should not be expected to infer which comment has authority.

Ask each approver to confirm the scope of their decision. A brand lead might accept the visual direction but cannot verify a technical product claim. A producer may confirm that the requested asset can be delivered but cannot authorize media spend. A clear chain makes it easier to involve the right person early without sending every intermediate draft to everyone.

A useful approval request has five parts

Identify the asset and version, the question being decided, the person who owns the decision, the evidence they need and the agreed response process. For example: “Please review landing-page copy v3 against the signed brief and the attached claims list. Confirm the headline and offer language, or list the changes required before design begins.” This request is more actionable than “Thoughts?” and more precise than “Please approve the campaign.”

Keep the reference stable. A link to a document that keeps changing can make a later decision hard to interpret. Use the platform’s available version controls or retain a dated export alongside the decision. If a file is replaced, label the replacement and explain what changed. A typed version label in this page’s worksheet is a reference supplied by you; it does not fingerprint or retain the actual file.

Agree review windows and escalation with the project participants. Do not manufacture an approval because a deadline passed or a reviewer stayed silent. If the decision is missing, record it as missing, explain the impact on production and contact the agreed escalation owner. Whether any contractual procedure allows work to proceed is a separate matter for the people responsible for that agreement.

Review the expensive decisions
while they are still cheap to change.

The five checkpoints above describe the worksheet’s sequential studio process. A campaign may need a more detailed map: brief, concept, copy and execution reviews, with specialist checks running alongside them. Map these decisions to your actual deliverables before starting. Do not force a parallel approval chain into a single-person record and then assume all reviewers have signed off.

Brief: establish the problem and boundaries

Settle the audience, objective, proposition, deliverables, channels and measures of success. State constraints such as supplied footage, licensed photography, mandatory wording and the client’s review responsibilities. Separate a required launch condition from a desirable enhancement. A useful brief decision answers whether the team has enough agreed information to develop the work.

For a fictional membership campaign, a brief might specify a returning customer audience, a seasonal renewal offer, one landing page, two email variants and a short video. An unanswered question about who qualifies for the offer is a blocker to copy, even if the visual direction is ready. Record that dependency rather than burying it in meeting notes.

Concept: choose the direction, not every detail

Show how the proposed idea serves the brief. Include enough reference material or rough execution to explain tone and structure. Ask whether the chosen direction is right and what conditions apply. Avoid polishing several full executions merely to discover that the underlying proposition is wrong. Conversely, an abstract moodboard may be too ambiguous to establish what the client accepted.

Capture the chosen direction and the rejected alternatives with their reasons. This gives later discussions a useful reference. If a stakeholder asks for a different concept after production begins, the team can describe which earlier decision is being reopened and estimate the effect on the remaining work.

Copy: resolve meaning before finished production

Review the offer, claims, headline, calls to action, names, captions and required qualifications. A copy review is especially useful before recording narration or preparing numerous channel adaptations. Provide the text in a readable form, while retaining enough layout context to show what is prominent and what may be overlooked.

In this worksheet, the draft gate can hold that copy decision. If a project needs independent script and layout approvals, keep those distinct records in your real review system. Accepting a script does not automatically accept a later cut containing different language, shortened qualifications or a new end card.

Execution: inspect the actual version intended for use

Review the final asset, not just the earlier idea. Check the agreed formats, links, subtitles, logos, crops and supplied wording. Compare the current version with the last decision and the requested changes. A useful execution review confirms both that the changes were applied and that the asset still meets the brief.

List derivatives explicitly. Acceptance of a landscape master video does not necessarily cover a vertical edit with different framing and a shortened message. Decide which adaptations need individual review and which can follow agreed production rules. Keep that decision visible in the delivery record.

Specialist checks: run beside production with explicit release conditions

Some projects require legal, product, accessibility, rights or market-specific review. Invite those owners while the relevant decisions are still changeable. Give them the claims, intended territories, channels and asset references they need. The required checks depend on the project; this guide does not establish a legal compliance standard.

When several specialist reviews run in parallel, define the release condition: which responses are required, which conditional changes must be resolved and who checks completion. The local actor below cannot model multiple parallel reviewer branches. Record the complete external evidence in its notes only after your actual process establishes the decision.

Turn a comment thread
into an actionable response.

Attach feedback to the work

A vague request such as “make it more premium” leaves the production team guessing. Ask for the location, the observed problem, the intended change and the reason. For a video, identify the time or frame. For a layout, point to the relevant region. For copy, identify the sentence and what it should communicate. Asset-level comments are useful because they preserve context; a disconnected chat message often loses it.

For example, “At 00:18 the subtitle covers the product label; move it above the lower third while keeping the wording unchanged” gives an editor a specific task. “The opening feels slow; can we start on the product shot because this placement has no pre-roll context?” states an observation and the intended audience context without pretending to dictate every edit.

Consolidate without deleting disagreement

Collect the required reviewers’ input before sending the production team a response. Group duplicates, separate corrections from preferences and flag conflicts. If one person wants a shorter opening and another asks for a longer explanation, the consolidator should seek a decision rather than asking the editor to satisfy incompatible instructions.

Retain the original feedback and publish a consolidated change list that points back to it. Give each requested change an owner and a disposition: apply, clarify, decline with reason or defer by agreement. Resolving a comment should show how it was handled. It should not erase evidence or automatically transform a request into approval.

Control late additions and reopened decisions

A new approver can uncover a genuine omission. First establish whether they own a required decision and whether their concern changes the approved scope. If a product specialist identifies an inaccurate claim, reopen the appropriate copy or brief decision. If a new stakeholder offers a stylistic preference after final review, explain the change and its effect before committing production time.

Use a revised reference and an explicit return point. Returning to copy may require a new voice recording and another execution review. Returning only to a delivery gate is insufficient when the underlying message changed. Keep the old decisions as history and label them with their old version rather than deleting them to make the timeline appear tidy.

Close reviews with a readable decision

Write a decision record that another person can understand without reading every message. Include who decided, the exact reference, the question, the outcome, any conditions and the evidence location. If conditions remain, state who resolves them and how the result will be checked. “Approved subject to replacing the offer date” leaves an open action; it is not evidence that the replacement was inspected.

A handoff should identify the delivered assets and destination, plus any exclusions. If the client confirms receipt but has not reviewed the final version, record receipt rather than acceptance. Keep publication and campaign measurement separate. An asset can be delivered correctly while a campaign is still awaiting scheduling, rights clearance or a channel owner’s decision.

A worked campaign,
with a deliberate revision.

This fictional example follows a small studio producing a renewal campaign for a membership organization. It illustrates decision structure, not a recommended universal schedule or a report of customer results. The team has agreed a six-week planning window, with review dates set around the client’s availability. No elapsed time substitutes for a missing decision.

What the change record should say

Suppose the client changes the renewal deadline after the master is accepted. The studio identifies the affected script, landing page, email variants and video end card. The new reference is “Renewal package v6.” The return point is draft review because the offer wording changed. The final execution and delivery decisions must be recorded again for the revised assets.

A useful note reads: “Campaign lead requested a deadline change in the supplied decision thread. Return to draft review for revised offer wording. Existing v5 decisions remain historical. The change affects the end card, landing page and two emails; production owner will provide the revised asset list for execution review.” It identifies cause and scope without inventing acceptance of v6.

Using the local worksheet for this example

Enter the actual project title, initial reference and complete notes, then start the actor. At each gate, enter the reviewer and evidence only when that external decision exists. Save the source JSON before closing the page. A revision requires a new version label and a current or earlier gate; it preserves accepted events and returns the record for new decisions.

The source JSON can be restored and replayed. The history CSV supports a readable decision log, and the handoff notes retain complete input text. None of these exports replaces the source files, reviewer authentication or the client’s chosen approval system. If parallel legal and regional decisions are required, maintain them in that system and reference the evidence here.

Nine platforms,
different review responsibilities.

Choose a system around the assets and decisions you need to preserve. These are interpretations of current public primary documentation, not authenticated product tests or a ranking by measured approval speed. Verify entitlement, external access and your actual workflow before adopting a platform.

Four lighter starting points

For a design-led team, Figma comments keep discussion on the design canvas or prototype. For copy, Google Docs suggestions make proposed text edits visible before acceptance. Both still need a clear project-level decision and a stable reference.

A shared drive can hold the agreed asset versions and a separate decision log when the review chain is simple. Make file naming, permissions and the log owner explicit; storage organization alone does not create an approval process. For video, Vimeo review links offer feedback around the video. Confirm the current review experience and account entitlement with the owner before inviting a client.

Choose a stack you can actually maintain

A solo studio may start with one asset workspace and one decision log. A motion studio may prioritize time-based comments and version comparison. An in-house team may need production tasks and dependencies connected to review. A campaign with several independent release owners may need configurable routing and permissions. The right choice depends on those requirements, not the length of a product’s feature list.

Ask about reviewer friction as well as internal administration. Can an external reviewer open the asset without unexpected account steps? Can they find the question they own? Can an administrator retrieve the accepted version and decision after the project closes? Test those actions with a representative client workflow before migrating active work.

Compare total operating cost: paid seats, guest access, proofing entitlement, storage, integration setup, history retention and the work needed to maintain templates. Do not assume a free collaboration invitation means a free standalone account, or that a trial includes every paid feature permanently. Obtain current terms for your team size and preserve a source export before offboarding.

Find the friction
without inventing performance claims.

Track review starts, actual decisions, revision requests and the reason a gate reopened. Separate waiting for a reviewer from production time and time spent clarifying a brief. If a project needs several rounds, look at the content of those rounds before calling the workflow inefficient. A necessary correction is different from an avoidable mismatch in expectations.

Common causes of rework include incomplete brief decisions, reviewing the wrong version, contradictory instructions, missing decision owners and late discovery of a required reviewer. Use the next project’s template to address the observed failure: add the missing question, clarify authority or link the required evidence. Do not promise that a new platform will remove these problems by itself.

When a review stalls, identify the missing decision and its consequence. Offer the agreed escalation route, explain which production tasks can safely continue and which depend on the answer, and update the plan when the response arrives. A project-specific review window can be useful when agreed in advance; an arbitrary automatic deadline should not turn a missing response into acceptance.

Practical approval questions.