Skip to main content
GullySystem
Other industries

Workflow and Approvals for Film production houses

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 set build request, an extra day of hire or a script change goes through the producer and the line producer. Approvals are dated. Costs show before being committed.

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.
Film production houses

How the business operates.

A production house makes a film, series, advert or branded video one project at a time, and each project means hiring a crew, renting kit and booking locations. Each project is a temporary organisation. Cameras roll across a fixed block of shooting days. After that the finished material goes to a buyer, a broadcaster or a streaming platform, each with its own delivery specification.

Script breakdown and scene list

Split the script into scenes, each with its cast, props, wardrobe, locations and kit, so every department reads from one list.

Shooting schedule and call sheets

Order scenes into shooting days, then produce the call sheet with unit call, pickups and contacts, and send it to everyone listed.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Script breakdown and scene list. Split the script into scenes. Each is tagged with cast, props, wardrobe, vehicles, locations and kit, so the art department, costume, transport and the storyboard artist all read from one list.
  • Shoot calendar and call sheets. Order scenes on a stripboard into shooting days. Issue the call sheet with unit call, cast pickups, sunrise time, the nearest hospital and the ambulance route, and send it to everyone listed.
  • Cast and crew bookings. Hold each person’s role, day rate, deal memo terms, start date and wrap date, together with the signed agreement and any work permit for a foreign hire.
  • Equipment hire and returns. Book camera, lens, lighting and grip packages by day. Record the check-out and return of each serial number, list the carnet for kit crossing a border, and flag a scratched filter before the vendor invoices for it.

Operational bottlenecks to check

The schedule and the breakdown drift apart

A scene moves to a different day and the props, cast and location sheets are not updated. The wrong items arrive on set.

Call sheets are rebuilt every night

Each call sheet is typed from the schedule, the cast list and the weather note. A late change reaches only the people who were phoned.

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. Development and budget

    The script is loaded. The budget is built line by line, from above-the-line fees down to fringes and contingency, and the producer locks a version that every later cost is compared with.

  2. 2. Breakdown and schedule

    Scenes are tagged. Each carries cast, props, vehicles, wardrobe and locations, and the assistant director orders the strips into shooting days, balancing night shoots and turnaround against the cast’s availability.

  3. 3. Booking and clearances

    Each booking holds its paper. The signed deal memo, permit or release is attached to the booking of the cast member, crew head, camera kit or location, with its days marked on the roster.

  4. 4. Shoot

    The call sheet goes out each evening. The script supervisor logs takes against timecode during the day, and the production office files the shoot report after wrap, with pages and camera rolls counted.

  5. 5. Cost control

    Purchase orders, petty cash and crew payments are posted against budget lines as they happen, and cost to finish is read each week ahead of the next cash call.

  6. 6. Post and delivery

    Camera cards reach the editor first. Then comes the grade and sound mix, and each item on the buyer’s delivery list is ticked off while the final paperwork is gathered into one folder.

Industry reports to connect with

  • Budget against actuals and cost to finish by line
  • Daily production report with pages and scenes shot
  • Stripboard schedule and scenes remaining
  • Cast and crew days worked, overtime and meal penalties

Questions before implementation.

When should film production houses 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