Skip to main content
GullySystem
Other industries

Workflow and Approvals for Animation studios

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A finished shot moves from artist to lead, then to director, then to the client. Each step needs a named approver. Rejected shots return to the artist carrying the director’s note.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
Animation studios

How the business operates.

An animated production is a pipeline. A storyboard becomes an animatic, the animatic becomes a list of shots, and every shot needs characters, backgrounds and props that must be built first. Each stage belongs to a different artist, who may be a freelancer on a short contract joining in the middle of the production and leaving before the final render.

Bid and budget by shot

Price the job by minute, episode or shot, and compare artist hours and render charges with that bid as work proceeds.

Script, storyboard and animatic

Hold each sequence from script breakdown to board and animatic, with the approved version and its running time.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Bids and budgets by shot. Price a production by minute, episode or shot, and compare artist hours and render charges with the bid as work proceeds.
  • Script breakdown and boards. Break the script into sequences and shots, and keep storyboard and animatic versions with their running time and approval.
  • Shot list and status grid. List every shot with stage, artist, frame count, due date, retake count and the assets it needs.
  • Asset library and versions. Track characters, rigs, props, backgrounds and textures with version history and the shots that use each one.

Operational bottlenecks to check

Shot status lives in a spreadsheet

A coordinator updates the sheet each evening, after a shot has already moved a stage, so the supervisors plan the next morning from rows that are no longer true.

Assets are used in the wrong version

A rig is fixed after the character’s costume changes. Two animators work on shots with different versions, and the difference surfaces in review.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Bid and set-up

    The producer prices the job by minute, episode or shot, and the production is opened with its pipeline stages and a rate card.

  2. 2. Script and boards

    The script is broken into sequences and shots. Storyboards and the animatic are saved as versions with the director’s approval.

  3. 3. Asset build

    Characters, props and backgrounds are assigned to modellers, riggers and painters, then published as versions that shots can use.

  4. 4. Shot production

    Each shot is assigned to an artist and moves through layout, animation, effects, lighting and compositing, with hours logged at each stage.

  5. 5. Review and retakes

    Notes from the director and the client are recorded against the shot and frame, and the retake returns to the artist.

  6. 6. Delivery

    Renders, audio, subtitles and metadata are checked against the client’s specification, and final cost is compared with the bid.

Industry reports to connect with

  • Bid against actual cost by sequence
  • Shots by stage and past due
  • Retakes per sequence and artist
  • Artist bookings and free capacity

Questions before implementation.

When should animation studios consider workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements