12 / 12 Approval gates

Your production. Your approval at every turn.

Know who approved what, and what that approval releases.

Approval gates are first-class production objects, not comments buried in a chat thread. Each records the approver, their role, the version they saw, the decision, the comments, the time and the downstream scope it released.

Free planning. Scoped, paid rendering after approval.

Illustrative production view
Choose an illustrative production scenario

Your decisions move the production.

  1. Brief
  2. Rights
  3. Canon
  4. Script
  5. 05Storyboard + cost
  6. 06Master
  7. 07Languages
  8. 08Delivery
Storyboard + cost
Awaiting authorization
Master + tracks + delivery
Not released

Gate 5 holds full-quality rendering.

Fictional example. Explore the workflow; these controls do not render media, approve work or authorize spend.

01

Creative and financial decisions separated

02

Version-specific approval records

03

Only affected gates reopened after a change

One core. Two launch solutions.

Built around the work you need to deliver.

Approval gates

Human control is not a compliance tax. It is the feature.

Approval gates reduce expensive mistakes and establish accountability. A production where nobody can say who approved the thing that went wrong is a production that will make the same mistake again.

01 / Inside the workflow

The eight blocking gates

  1. Greenlight brief and intended useCustomer decision-makerBlocks: All generation spend on the production
  2. Rights and source-asset clearanceCustomer, with a Tosheo rights reviewerBlocks: Work depending on the unresolved asset
  3. Creative canon or brand systemCreative approver; brand approver for campaignsBlocks: Planning that would inherit unapproved canon
  4. Script or production planWriter or creative approverBlocks: Boarding and rendering of the affected scenes
  5. Storyboard, animatic and cost authorizationCreative approver and budget holderBlocks: Full-quality rendering
  6. Primary master reviewCreative approverBlocks: Derivation of platform versions and cutdowns
  7. Language and market reviewNative reviewer for that trackBlocks: That track only
  8. Final delivery acceptanceDelivery approver, plus legal where requiredBlocks: Handover of the delivery package

02 / Inside the workflow

What reopens after a change

The failure mode of a gated process is that every change restarts everything, so people stop making changes or stop using the process. Tosheo scopes reopening to the gates a change actually reaches.

Common changes and the gates they reopen
ChangeReopensLeaves alone
Add a language trackLocalization and deliveryCanon, script, boards, accepted master
Revise a costumeCanon, and the shots that inherit it from that pointEarlier accepted episodes
Change episode lengthPlan, storyboard, cost authorizationCanon, rights positions
New substantiated claimScript, brand and legal, affected tracksUnaffected episodes and tracks
Swap a music cueRights clearance, delivery acceptancePicture, canon, other tracks

03 / Inside the workflow

The human-control rule

Automation can propose, generate, check, route, and assemble. It cannot silently greenlight spend, approve rights, accept a final cut, publish externally, or represent a person or brand.

Brief v5, section 8

Read as a product decision rather than a safety statement, this is what makes the rest of the system sellable. A brand will not hand its claims and packaging to a pipeline that can approve itself. A creator will not hand over a season to a system that can regenerate accepted work.

Tosheo is not a replacement for writers, directors, producers, editors, rights owners or brand reviewers, and it is not an autonomous publisher. Buyers demanding fully autonomous publishing without approval are explicitly outside the customers we take.

  • Automation cannot approve a budget.
  • Automation cannot clear a right.
  • Automation cannot accept a final cut.
  • Automation cannot publish to a platform.
  • Automation cannot speak for a person or a brand.

Questions

Before you bring it into production

Is this not a lot of approvals for a 90-second episode?

Most gates are fast, and several are approved once per production rather than per episode. The brief, canon and rights gates close early and stay closed unless something material changes. Per-episode, the reviews that recur are the plan, the board with its cost authorization, and the master.

Can one person hold several roles?

On a small serialized production, usually yes - a solo creator may be the customer, the creative approver and the budget holder. The roles stay distinct in the record even when the person does not, because the decisions are different decisions.

What stops a gate from becoming a rubber stamp?

Nothing in software can, and we would rather say so. What the system does is make the stamp attributable: the approver, the version, the time and the scope it released are all recorded. Accountability is not the same as diligence, but it is what makes diligence possible to check.

Do gates slow a campaign deadline down?

They move the slow part earlier. The gates cluster before rendering, which is where changes are cheap. Time from approved brief to delivery is one of the metrics we hold ourselves to, and it is measured from the approval, not from the first conversation.

What happens if an approver goes silent?

The gate stays closed and the production stops at that point. That is the intended behaviour. A production that proceeds past an unclosed blocking gate has no accountable owner for whatever it produces.

Connected by design

The next decision has context.

Explore all 12 features

YOUR NEXT PRODUCTION

Bring the ambition.
Keep control of the work.

Start planning for free through the brief, canon, storyboard and animatic. Full-quality rendering is a paid, scoped engagement with explicit cost authorization.