Crewlever Research

Brand deal follow-up workflow

A practical workflow for reconciling new brand messages with an existing sponsorship plan without losing changed deliverables, dates, rights, or payment terms.

Direct answer

Treat a brand follow-up as a change to the existing deal: preserve the previous version, identify additions and conflicts, check material terms, accept only confirmed changes, and then set one concrete next action.

Short answer

A brand follow-up should be handled as a change to an existing deal, not summarized as if it were a new conversation.

Keep the previous version, identify what the latest message adds or changes, check the material terms, ask the brand to resolve conflicts, and update your working plan only after you accept the change. Then choose the next action: clarify, revise the plan, produce, submit, publish, invoice, or follow up again.

This matters because a short message such as “one small update” can change the actual work, schedule, rights, or payment conditions without restating the rest of the agreement.

Why a follow-up is a change request

Brand-deal requirements rarely live in one perfect document. The initial pitch may arrive by email, the brief as a PDF, a date change in a chat message, and final approval in another thread.

The problem is not simply extracting information from the newest message. The real question is:

What changed between what I was working from and what the brand is asking for now?

If you replace the old summary with a new one, you can lose a requirement that the follow-up did not repeat. If you keep both without reconciling them, you can act on contradictory dates or scope. The safer workflow preserves history and makes every material change explicit.

1. Preserve the previous state

Before processing the follow-up, keep the current working version of the deal. It should contain, where available:

  • Deliverables and quantities.
  • Draft, approval, publish, live-link, invoice, and payment dates.
  • Compensation and payment trigger.
  • Usage rights, duration, channels, territory, and edit rights.
  • Approval steps and included revisions.
  • Exclusivity, cancellation, and scope-change terms.
  • Open questions and the current next action.
  • A reference to the source that supports each important term.

Do not silently overwrite this version. You need it both to detect changes and to explain later why the plan changed.

2. Identify the new source

Record enough context to understand the follow-up:

  • Who sent it.
  • When it arrived, including timezone when dates are sensitive.
  • Which campaign and deliverable it refers to.
  • Whether it is a request, clarification, approval, revision, cancellation, or payment update.
  • Whether the sender appears authorized to change the deal.

A message from a reviewer saying “Could we try a different opening?” may be feedback, not an accepted scope change. A message from the campaign owner saying “The publish date is now Friday” is more likely to replace the previous date. When authority or intent is unclear, keep the proposed change pending.

3. Classify each difference

Compare the latest message with the saved plan and put every relevant item into one of five groups:

ClassificationMeaningWhat to do
AdditionA new requirement or term appearsAssess its effect before accepting it
ReplacementA previous value is explicitly changedPreserve both values and mark the new one pending
RemovalA previous requirement is explicitly cancelledConfirm that the removal is intentional
ConflictTwo sources cannot both be trueAsk which version controls
UnchangedThe follow-up confirms the existing planKeep the current value and source history

Do not interpret silence as removal. If the original brief required two videos and the follow-up discusses only the first video, the second video has not disappeared.

4. Check the material fields

Review the changes in the areas most likely to affect the work or commercial agreement.

Deliverables and scope

Check platform, format, quantity, length, creative direction, talking points, links, mentions, disclosures, assets, raw files, and reshoots.

Ask: Does this add work? Does it change work already completed? Is it a revision within the agreed scope or a new deliverable?

Dates and milestones

Check every dependent date, not only the date named in the message. A moved publish date may also move the draft, approval, live-link, invoice, or payment date.

Ask: Is the new schedule feasible? Does the brand still have enough approval time? Which timezone applies?

Compensation and payment

Check fee, currency, affiliate or bonus terms, expenses, invoice timing, payment trigger, and due date.

Ask: Does the added work have added compensation? Did a schedule change alter when the creator can invoice or expect payment?

Usage rights and exclusivity

Check organic use, paid media, whitelisting or boosting, edit rights, raw footage, ownership, duration, channels, territory, sublicensing, competitor category, and exclusivity period.

Ask: Is the brand requesting a new commercial use that was not in the accepted terms? Has a vague phrase such as “share on our channels” become paid use or extended use?

Approvals and revisions

Check who approves, turnaround time, revision rounds, reshoots, and what counts as a scope change.

Ask: Is this ordinary feedback under the deal, or has the review process itself expanded?

Campaign status and next action

Check whether the campaign is tentative, confirmed, in production, awaiting approval, scheduled, published, invoiced, paid, paused, or cancelled.

Ask: What is now blocking progress, and who owns that action?

5. Resolve ambiguity before updating the plan

Not every difference needs a meeting. A focused written question is often enough. State the old value, the proposed new value, and the decision you need.

For a conflict:

I noticed this update lists the publish date as August 18, while the approved brief lists August 15. Can you confirm which date is final?

For added scope:

The current scope includes one edited video. This follow-up also requests the raw footage. Can you confirm whether raw-file delivery is being added to the scope and terms?

For a dependent deadline:

I can move publication to Friday. To keep the review window workable, can we confirm draft feedback by Wednesday at 3:00 p.m. JST?

For an unclear revision:

Can you confirm whether this replaces the approved concept or is optional feedback within the existing direction?

The purpose is not to make the exchange formal for its own sake. It is to create a clear decision that the working plan can safely use.

6. Accept or reject each proposed change

Once the intent is clear, make an explicit decision for every material change:

  • Accept: update the active plan and retain the previous value in history.
  • Reject: keep the active plan unchanged and record why.
  • Pending: do not use the proposed value until the brand confirms it.

Accepting one change does not mean accepting every change in the message. You may accept a new publish date while leaving an added usage-rights request pending.

After acceptance, note the source and decision date. This creates a usable record without pretending that every message is a formal contract amendment.

7. Recalculate the next action

A reconciled plan should end with one concrete next action. Examples include:

  • Send one clarification question.
  • Confirm a scope or fee change.
  • Update production and review dates.
  • Revise the draft.
  • Send the deliverable for approval.
  • Schedule publication.
  • Send the live link.
  • Issue the invoice.
  • Follow up on overdue approval or payment.

Assign an owner and a date when possible. “Waiting” is a status; “follow up with the campaign owner on August 13 if approval has not arrived” is an action.

Worked example

This is a synthetic example designed to demonstrate the workflow. It is not a published creator case study.

The saved plan says:

  • One short-form video.
  • Draft due August 12.
  • Publish August 16.
  • One revision round.
  • Thirty days of organic brand reposting.
  • Payment due 30 days after invoice.

The brand follows up:

Please publish on August 14 instead. Could you also send the raw clips so our paid team can test a few versions? Everything else looks good.

The comparison should produce:

FieldPrevious stateProposed changeDecision needed
Publish dateAugust 16August 14Can production and approval move safely?
Raw footageNot includedSend raw clipsIs this added scope and how will files be used?
Usage30-day organic repostingPaid-team testing mentionedWhat paid rights, duration, channels, and compensation apply?
Other termsSaved plan“Everything else looks good”Keep unchanged; do not recreate or discard them

The creator can accept the date only if it is feasible, while asking the brand to clarify and agree to the raw-footage and paid-use terms. Until those terms are accepted, the saved rights remain active.

The next action is not “send raw clips.” It is “confirm scope, paid usage, duration, and compensation for raw clips, then update the plan.”

Follow-up checklist

Before acting on a brand follow-up, confirm:

  • The previous version is preserved.
  • The sender, time, campaign, and message type are known.
  • Additions, replacements, removals, conflicts, and unchanged terms are separated.
  • Deliverables, dates, compensation, payment, rights, approvals, and status were checked.
  • Silence was not treated as removal.
  • Material ambiguity was sent back as a specific question.
  • Each proposed change is accepted, rejected, or pending.
  • Accepted changes retain their source and history.
  • The plan ends with one owned, dated next action.

Try the workflow on your next follow-up

Try the free Sponsor Brief Check to compare a new brand message with the sponsorship plan you already saved. You can redact names, fees, contacts, or other private details before pasting a source.

If you manage paid collaborations yourself, request a creator workflow interview. We are studying where follow-ups break down and which parts of this workflow are genuinely useful in real deals.

What Crewlever still needs to validate

This playbook is based on Crewlever's current workflow decomposition, product research, and implemented follow-up reconciliation model. It expresses a working operating hypothesis, not a measured industry benchmark.

We still need permissioned real-workflow evidence to learn:

  • Which follow-up channels create the most missed changes.
  • Which fields creators most often need to reconcile.
  • Whether explicit comparison helps creators reach a useful next action.
  • Whether creators return with a second source or later follow-up.
  • Where the workflow adds unnecessary effort.

Crewlever's current validation thresholds are 10 qualified creators attempting a real source, five reaching the first workflow value, and three showing repeat intent or behavior. Until those thresholds are met, we will not claim prevalence, time savings, or outcome improvements.

Limitations

  • This workflow is operational guidance, not legal, tax, accounting, or platform-policy advice.
  • A message comparison cannot determine whether a term is legally enforceable or commercially fair.
  • The worked example is synthetic and should not be read as evidence of frequency.
  • High-risk changes involving ownership, paid usage, exclusivity, cancellation, or disputed payment may require a manager or qualified adviser.

Methodology and limitations

This working playbook combines Crewlever's current workflow decomposition, product research, and implemented follow-up reconciliation model; the worked example is synthetic. It is not legal advice or a quantified industry benchmark, and its effect on real creator outcomes has not yet met Crewlever's validation thresholds.