inknix

Clear production for screen and stage

← Journal
Workflow Planning

Before You Commit: A Workflow Planning Checklist for Crews and Networks

A checklist for producers and venue managers to work through before signing off a production workflow: schedules, signal flow diagrams, handover documents and the questions that settle them.

Daniel Whitcombe

7 minutes to read

Before You Commit: A Workflow Planning Checklist for Crews and Networks

Start with who has to read the plan

Before anything is drawn or scheduled, decide who will actually use the finished documents. A plan written for the producer who commissioned it is often useless to the vision mixer, the sound crew or the network engineer who inherits it on the day. I have seen very tidy schedules that nobody on the floor could follow, because they were built around the commissioning team's vocabulary rather than the crew's.

List every reader and what each needs to find within a minute of picking the document up. A camera operator wants call times, positions and comms channels. A network engineer wants feed formats, return paths and who to ring when a feed drops. If your readers are not named at the start, the plan will quietly favour whoever wrote it, and that is where handovers begin to fail.

This checklist is for the decision stage, the weeks before a studio day or an event load-in when a workflow is still cheap to change. Treat each section as a question you should be able to answer in writing before you agree the plan with your partners.

  • Name every role that will read the schedule, the diagram and the handover notes
  • Note what each role needs to find first
  • Agree one person who owns the final version

Check the schedule against the real working day

A schedule is only as good as the assumptions underneath it. Walk through it hour by hour and ask whether each block allows for what actually happens: crews arriving at different times, a rig that needs a second pass, a rehearsal that overruns because the talent has not seen the set. Optimistic schedules usually fail at the joins between departments rather than inside any one of them.

Look at the order of work. Lighting often needs to be focused before cameras can be shaded, and sound lines cannot be checked until cabling is finished and power is stable. If the schedule puts these in the wrong order, someone will stand idle while another team works, or worse, redo their work after a change.

Ask where the slack sits. A plan with no spare time before transmission or doors is a plan that will cut corners under pressure. Mark the points where a delay would push everything else and decide in advance what you would drop, so the decision is not made in a rush.

  • Does the order of work match the dependencies between departments?
  • Is there spare time before transmission or doors, and is it marked?
  • Who decides what is dropped if the day runs late?

Read the signal flow diagram as a stranger would

A signal flow diagram should let someone who was not in the planning meetings trace a picture or a sound from source to destination. Test that by handing it to a colleague outside the project and asking them to follow one camera feed to the programme output and the recording. Where they hesitate, your crew will hesitate too, usually at a bad moment.

Check that every connection is labelled consistently, that formats and sample rates are stated where they matter, and that the diagram shows what happens when something fails. A diagram that only shows the working state is half a document. Include the backup route, the spare return and the point at which a person has to switch something by hand.

Make sure the diagram matches the equipment list and the cabling plan. Small mismatches, such as a converter shown on the page but missing from the kit, are exactly the faults that surface during setup, when time is shortest and everyone is watching the clock.

  • Can a newcomer trace one feed from source to output unaided?
  • Are formats, labels and backup routes shown?
  • Do the diagram, kit list and cabling plan agree?

Test the handover documents before you need them

Handover documents are the part of workflow planning most often left until the last evening, and they are the part a network team relies on when the original crew has gone home. They should say what was built, how it is meant to be operated, what was changed from the plan and what remains unresolved. Honest notes about open problems are worth more than a polished summary.

Ask whether someone could run the next session using only these pages. Include contact details for the people who built each system, the order in which things are powered up and down, and the settings that were deliberately chosen rather than left at default. Anything held only in someone's memory should be written down.

Decide where the documents live and who may edit them. A handover pack that exists in three versions on three laptops is worse than none, because each crew will trust the one they happened to receive.

  • Could the next crew run a session from these pages alone?
  • Are power-up order and deliberate settings recorded?
  • Is there one agreed home for the current version?

Settle responsibilities and the points of contact

Most workflow failures are not technical. They come from two teams each assuming the other would handle a feed, a booking or a sign-off. Before agreeing a plan, go through it line by line and attach a name to every task, including the dull ones such as confirming network access, arranging power and checking the return feed with the receiving centre.

Agree how decisions are made during the day. Who can authorise a change to the running order or the rig, and how is that change recorded so the documents stay true? A short written rule, shared with everyone, saves arguments at the worst possible moment.

Finally, confirm how partners will reach each other. A phone number that rings in a quiet office is no use to a crew in a loud venue. Settle the channel, the backup channel and the person who answers them.

  • Every task has a named owner
  • Changes are authorised by one person and logged
  • Primary and backup contact channels are agreed

Decide what you will review afterwards

A good workflow improves with use, so decide now how you will learn from the first run. Agree a short review once the session or event has finished, while memories are fresh, and decide who will update the schedule, diagram and handover pack as a result. Without that step the same small faults return every time.

Keep the review practical. Note what took longer than planned, which documents were consulted most and which were never opened, and where a person had to improvise. These observations tell you what to simplify and what to explain better next time.

Set aside a little time for this in the schedule rather than hoping it will happen. A review that is only an intention tends to vanish the moment the next job begins.

  • Schedule a short review soon after the session
  • Record overruns, improvisations and unused documents
  • Assign who updates the pack afterwards

Deciding on a workflow plan is easier when you can answer a short list of plain questions: who reads each document, whether the schedule fits the real day, whether a stranger can follow the diagram, whether the handover notes stand alone, who owns each task and how you will learn afterwards. If any answer is vague, that is where to spend the next hour, before the crew arrives and changes become expensive.