Skip to main content
GullySystem
Other industries

Work Order Management for Animation studios

Track a production job from material issue to completed output.

Manufacturing

Does this function belong in your operation?

Use when physical production needs a job-level record of materials and output.

A production plan releases a specific job.

A shot becomes a work order when it is handed to layout, animation or lighting. Orders carry the shot code. Every order names the artist, the scene and the delivery slot.

Bring the records the workflow depends on.

  • Required output
  • Approved material list
  • Process steps and due dates

Outputs to check

  • Released production-job record
  • Material and output reconciliation
  • Work-in-progress and variance list

Follow the work order management workflow.

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

  1. 1. Release the job

    Record output quantity, instructions and the approved material version.

  2. 2. Issue resources

    Link materials and assigned production stages to the work order.

  3. 3. Record progress

    Capture completed operations, interruptions and additional material requests.

  4. 4. Inspect output

    Pass the produced quantity to the agreed quality or acceptance check.

  5. 5. Close the job

    Reconcile accepted output, scrap, unused material and unfinished quantities.

Who uses the module, and who approves?

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

Production in-charge

Releases jobs, moves them between stages, and holds the ones waiting on material with a reason typed in.

Supervisor

Marks the stage done from a tablet near the machine.

Storekeeper

Issues material against the job number and sees what is still due to it.

Owner

Looks at what is late, and at what is late for the same reason every week.

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.

Material issued beyond plan

Record the reason and obtain the required approval.

Output below target

Keep the uncompleted balance or close it with an authorised shortfall reason.

Job paused mid-process

Retain work-in-progress quantities and the stage from which work will resume.

Can this work independently?

A work order needs an output definition and process instructions. It can use entered materials and progress, but bill-of-materials, stock and quality links make execution traceable. Sales orders provide demand; closing production is not the same as dispatching or invoicing the finished goods.

Systems and records it connects with

  • Bill of materials: Approved component quantities and production-definition versions.
  • Production planning: Demand, planned quantities and resource or material constraints.
  • Stock: Item-location quantities and authorised stock movements.
  • Job work delivery notes: Material dispatch and return references for outside processing.

Configure, test and introduce the workflow.

  • Tell us the stages a job passes through, in your words. A stage list comes back to confirm.
  • Sales orders are connected, and so is the bill of materials. A sample work order draws on each. A screen shows jobs by stage. The supervisor tries it beside the whiteboard.
  • Supervisors and the store use live work orders. The whiteboard is retired after a trial period.

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.

  • Output links to its work order.
  • Material usage is traceable.
  • Unfinished quantities remain visible.
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 work order management?

Use when physical production needs a job-level record of materials and output. A production plan releases a specific job.

What should we bring to the requirements discussion?

Bring anonymised examples of Required output; Approved material list; Process steps and due dates. 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. Track a production job from material issue to completed output. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

This is a production work order; field repairs and customer visits belong in job cards.

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. Output links to its work order. Use this check when reviewing the first working version.

Talk to us

Discuss work order management 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