Guides
Service, safety, client goals: keeping talent agency deliverables straight
Separate service promises, safety duties and client goals in every talent agency roster deal, so nothing vague or implied reaches a signed scope of work.
What to take away
- A deliverable is a promise with a date, an owner and an acceptance test. Anything else is a hope.
- Service, safety and client goals come from three different sources and fail in three different ways.
- Undefined scope is the most common cause of onboarding churn, and it shows up before the first invoice.
- Disclosure duties sit with the agency and the creator, not with the brand alone.
- Every figure below is arithmetic you run with your own numbers, not a benchmark.
This is general business information for representation shops, not licensing, tax, contract or legal advice. Confirm requirements with the California Labor Commissioner, your state licensing authority, the IRS, or a licensed attorney.
Three kinds of promise, three failure modes
A service promise is what the agency does: submissions, negotiation, reporting, content review. It fails when it is written as an intention rather than a task. "Active representation" is not a deliverable.
Three Promises, Three Failure Modes
Service promise
- What it is
- What agency does
- Failure mode
- Written as intention
- Example
- Active representation
- Fix
- Write as task
Safety duty
- What it is
- What agency must not do
- Failure mode
- Fails quietly
- Example
- Disclosure rule
- Fix
- Put in engagement letter
Client goal
- What it is
- What talent wants
- Failure mode
- Never written down
- Example
- Rate floor
- Fix
- Write it down
A safety duty is what the agency must not do, or must do regardless of the client's wishes. It fails quietly, because nobody complains until an audit or a claim.
A client goal is what the talent wants: a brand tier, a rate floor, a category they will not touch. It fails when it is never written down and the agency guesses.
Sort every line of your onboarding scope into one of the three. A line that fits none of them is padding.
Where the three collide
The collisions are predictable, and they are where onboarding breaks.
Where the Three Collide
Collision
- Fast brand deal vs disclosure
- Safety line in engagement letter
- Excluded category vs pitch everything
- Resolve at signing
- Safety duty costs money
- Pricing input in fee
Resolution
- Fast brand deal vs disclosure
- Excluded category vs pitch everything
- Safety duty costs money
A client who wants a fast brand deal and a disclosure rule that requires a clear, conspicuous label are not in conflict until the brand asks for the label to be softened. That is a safety line, and it belongs in the engagement letter before the first pitch.
A talent who wants a category excluded, and a service promise to pitch everything in their wheelhouse, is a scope conflict. Resolve it at signing, not at the third declined offer.
A safety duty that costs money, such as accessibility of a ticketed event or a public appearance, is a pricing input. If it is not in the fee, it comes out of margin.
Build the scope so it can be checked
Write each deliverable as a row, not a sentence. Four columns carry the whole thing:
Four Columns for Checkable Scope
- Outputnamed deliverable, owned by account lead
- Duedate or trigger, owned by account lead
- Acceptanceone testable line, owned by client and agency
- Evidencewhere record lives, owned by operations
Column / What goes in it
- Output
- The thing handed over, named specifically · Account lead
- Due
- A date, or the trigger that starts the clock · Account lead
- Acceptance
- What makes it done, in one testable line · Client and agency
- Evidence
- Where the record lives · Operations
A row that cannot be filled in is not ready to be promised. A row whose acceptance test is "client is happy" is not a test.
Run the same table through the onboarding workflow for new clients before the kickoff call, and the kickoff becomes a confirmation rather than a discovery.
Disclosure is a deliverable, not a footnote
The FTC's guidance on endorsements, influencers and reviews treats a material connection between creator and brand as something the audience must be able to see. The duty runs to the advertiser and the endorser, which in practice means the agency and the talent.
Two operational consequences follow. First, disclosure language is a scope item with an owner and a due date, not a note the creator remembers.
Second, the agency's own marketing is covered: the FTC's guide on soliciting and paying for online reviews says review requests should reach genuine clients rather than a hand-picked happy few, and that incentives must not create a false picture.
If you run live events or a public-facing office, the Justice Department's ADA guide for small businesses covers barrier removal and accessible routes. Treat that as a safety line in the scope table, with a cost attached.
Worked example: pricing a bundle that holds
Suppose a retainer of R per month covers S submissions, C content reviews and one quarterly report. Your delivery cost is D per month. Margin is (R minus D) divided by R.
Now add a safety duty that costs X per quarter, and a client goal that requires a second reviewer at Y per review. New margin is (R minus D minus X/3 minus Y) divided by R.
If that number falls below the margin you need to keep the account staffed, the fix is the fee or the scope, not the effort. Underpriced bundles do not show up as losses. They show up as slow replies and quiet churn.
Common questions
What belongs in the client's goals versus the agency's service?
Client goals are outcomes the talent wants: rate floors, brand tiers, excluded categories. Service is what the agency does to pursue them. Keep them in separate columns, because a goal is not something you can be late on.
Who is responsible for disclosure on a sponsored post?
The FTC places the duty on both the advertiser and the endorser. In agency practice that means the label is a scope item with a named owner, checked before the post goes live.
How do we know a deliverable is finished?
It has an acceptance test written before the work started. If the test is a feeling rather than a check, rewrite it or drop the deliverable.
