From South Beach to Soundstage: How Fluid On-Set Coordination Compares to Studio Division-of-Labor Models

Every production set—whether a Miami beach shoot or a controlled soundstage—runs on coordination. But the way that coordination happens can look radically different depending on the environment. On a fluid on-set location, roles often overlap, decisions happen in real time, and the chain of command is flat. In a studio with strict division-of-labor, everyone has a defined job title, handoffs are formal, and hierarchy is clear. Both models have strengths, and both can fail when pushed too far. This guide breaks down the two approaches, compares their trade-offs, and offers practical steps for blending them to match your project's real constraints.

Why Coordination Models Matter and What Breaks Without Them

When a production lacks a clear coordination model, the default is chaos. On a location shoot, this might mean two people calling “cut” at the same time, or a lighting team setting up without telling the camera department, forcing a 20-minute re-rig. In a studio, the same problem shows up as bottlenecks—the gaffer waits for a sign-off from a producer who is in another meeting, while the crew stands idle. Without an explicit model, teams default to whatever feels familiar, which often mismatches the actual demands of the shoot.

The consequences are measurable: lost time, duplicated effort, and frayed trust. A 2019 survey by the Production Managers Association found that over 60% of delays on set trace back to miscommunication or unclear handoffs. While we don't have a precise number for every shoot, the pattern is consistent across both location and studio work. The difference is that location shoots absorb some chaos through flexibility—people just figure it out—while studio environments punish ambiguity because the division-of-labor is designed to prevent it.

This article is for anyone who has ever been on a set where the workflow felt off: producers who watch the schedule slip, directors who can't get a clear answer, or crew leads who spend more time negotiating than working. After reading, you'll be able to diagnose your current coordination model, decide when to shift toward fluid or structured approaches, and implement small changes that reduce friction without requiring a full overhaul.

Prerequisites: Understanding Your Production's Baseline

Assess Your Team Size and Experience Level

Before choosing a coordination model, know your crew. A team of six on a documentary shoot can operate with near-total fluidity—everyone hears every decision, and roles shift as needed. A crew of forty on a commercial soundstage needs more structure. The key variable is not just headcount but how many people need to act on the same information at the same time. Small, experienced teams thrive on fluid coordination because they have shared mental models. Large teams or those with many junior members benefit from clear role definitions because they reduce the cognitive load of deciding who does what.

Map Your Communication Channels

Every production has formal channels (walkie-talkie calls, daily emails) and informal ones (side conversations, text groups). In a fluid on-set model, informal channels often carry the most important information—the DP whispers to the gaffer about a last-minute light change. In a studio model, formal channels are supposed to be the only ones, but that rarely holds. The problem is when the informal channel becomes the only way to get things done, and the formal channel becomes a paperwork ghost town. Map both before you design your workflow. If your team already relies on a WhatsApp group for critical timing calls, you are operating in a fluid model whether you planned it or not.

Identify Your Bottleneck Roles

Every set has at least one role that, if delayed, stalls everything. On a location shoot, it is often the location manager or the AD. In a studio, it might be the gaffer or the key grip. Knowing which roles are bottlenecks helps you decide where to add structure (like a backup contact) or where to allow fluidity (like letting the DP bypass the AD for a quick lighting change). A common mistake is to treat all roles as equally critical; they are not. Focus your coordination design on the top two or three bottlenecks.

Core Workflow: Sequential Steps for Choosing and Implementing a Model

Step 1: Define Your Coordination Style for Each Phase

Break the production into phases: pre-production, setup, shooting, wrap. For each phase, decide whether you will use a fluid or structured model. For example, pre-production often benefits from structure (clear deadlines, assigned tasks), while the shooting phase on a location may need fluidity to adapt to changing light or weather. Do not assume one model fits the entire project. Write a one-page coordination plan that lists each phase with the model you will use and the key people responsible.

Step 2: Set Up Communication Protocols

For a fluid model, the protocol is “escalate quickly, decide locally.” That means the grip can adjust a flag without asking, as long as they tell the DP within 30 seconds. For a structured model, the protocol is “escalate formally, decide at the right level.” That means the grip flags a change to the key grip, who tells the gaffer, who confirms with the DP. Write these protocols down. The simplest way is a one-page matrix: “If you see X, do Y, and tell Z.”

Step 3: Run a Mini-Table Read of the Workflow

Before the shoot, gather key leads and walk through a 15-minute scenario: a light breaks, a talent is late, a location falls through. Ask each person what they would do under your chosen model. This exposes gaps. Often, the AD assumes they will be told, but the DP assumes they can decide independently. Fix these mismatches before they happen on set.

Step 4: Build in Checkpoints

Even in a fluid model, you need checkpoints—moments when everyone syncs. A common checkpoint is the 10-minute huddle before each scene change. In a structured model, checkpoints are more formal: a daily morning meeting and a midday check-in. The content is the same: what has changed, what is next, who needs what. The difference is who runs the meeting and how decisions get recorded.

Tools, Setup, and Environmental Realities

Physical Tools: The Communication Backbone

Walkie-talkies are still the default on most sets, but they work differently in each model. In a fluid model, keep all channels open so anyone can speak—but that creates noise. Many teams use a “priority channel” for the AD and a secondary channel for department heads. In a studio model, you might use a closed channel for each department, with a separate channel for cross-department communication. The choice of tool matters less than the rule for when to switch channels. Write that rule on a laminated card and attach it to each walkie.

Digital Tools: Shared Boards and Status Tracking

Apps like StudioBinder, SetKeeper, or even a shared Google Doc can support both models. For fluid coordination, use a real-time board where anyone can update their status (e.g., “Camera ready,” “Lighting 5 more minutes”). For structured coordination, use a board with permissions—only the AD can mark a department as “ready.” The risk with digital tools is that they become a second system of record that no one trusts. Pick one tool and enforce its use for at least the first two days of the shoot. If it fails, drop it and go back to paper or verbal handoffs.

Environmental Factors: Location vs. Studio

Location shoots introduce unpredictability: weather, noise, public interference. These favor fluid coordination because you cannot plan for every variable. Studio shoots offer controlled conditions, so structured models are easier to maintain. But even on a soundstage, things go wrong—a light blows, a set piece shifts. The best approach is to default to structure for routine tasks and allow fluid override for emergencies, with a clear signal (like “red flag” on the walkie) that indicates the model has temporarily switched.

Variations for Different Constraints

Small Crews (Under 10 People)

With a small crew, fluid coordination is almost always better. Formal division-of-labor creates overhead that outweighs the benefit. The variation to watch for is when a small crew includes inexperienced members—they may need more structure. In that case, assign one experienced person as a “shadow AD” who keeps the workflow moving without formal titles. That person can fluidly take on coordination tasks while others focus on their craft.

Large Crews (Over 30 People)

Large crews need structure, but pure division-of-labor can lead to silos where departments don't talk. The variation is a “hybrid hub” model: each department has a clear lead, but those leads meet every 30 minutes for a quick stand-up. This keeps the structure while adding a fluid layer for cross-department coordination. The AD runs the stand-up, but decisions can be made on the spot if all leads agree.

Tight Budgets and Fast Turnarounds

When money is tight and the schedule is compressed, fluid coordination is tempting because it seems faster. But it often backfires because people skip communication. The variation is to use structure only for the critical path—the sequence of tasks that determines the overall timeline. Everything else can be fluid. For example, on a fast commercial shoot, the setup of the hero shot is structured (each department has a time slot), but the B-roll shoot is fluid (whoever is free grabs it).

Multi-Camera or Complex Setups

Complex shoots with multiple cameras, VFX, or stunts require more structure, not less. The variation is to assign a dedicated “flow coordinator” who does nothing but track handoffs and flag delays. This role is separate from the AD and the DP. The flow coordinator uses a simple checklist and a timer. When a handoff is due, they call it out. This adds a layer of structure without making everyone follow a rigid script.

Pitfalls, Debugging, and What to Check When It Fails

The “Too Many Cooks” Trap

In a fluid model, the most common failure is that too many people make decisions, leading to conflicting instructions. The fix is to designate a single “tiebreaker” for each phase—usually the AD or the DP. That person does not need to make every decision, but they must be the final word when two people disagree. If you see the same argument happening twice, it means the tiebreaker is not clear or not respected. Reaffirm their authority in the next huddle.

The “Bottleneck Bypass” in Structured Models

In a structured model, the failure is that people bypass the chain because it is too slow. The gaffer talks directly to the producer instead of going through the key grip, and the key grip feels undermined. The fix is not to enforce the chain rigidly—that slows things down—but to create a fast lane for urgent issues. Define what counts as urgent (e.g., safety hazard, equipment failure, talent issue) and allow direct communication for those cases. For everything else, stick to the chain.

Checking When the Schedule Slips

If the schedule is falling behind, check your coordination model first. Are people waiting for decisions? That is a structured model problem—too many layers. Are people stepping on each other's tasks? That is a fluid model problem—too little role clarity. The quick fix is to adjust the model for the next scene: if you are behind, add a 5-minute huddle before each setup (adds structure) or let the DP decide lighting without waiting for the AD (adds fluidity). Do not switch models mid-scene; wait for a natural break.

When the Team Is Exhausted

Fatigue makes both models worse. In a fluid model, tired people forget to communicate. In a structured model, tired people follow rules blindly and miss obvious adjustments. The debugging step is to check if the model is still appropriate for the team's energy level. If the crew is running on four hours of sleep, simplify: reduce the number of handoffs, increase the frequency of check-ins, and lower the threshold for what counts as urgent. Sometimes the best fix is to call a 10-minute break and let everyone reset.

Frequently Asked Questions and Practical Checklist

Can I switch models mid-production?

Yes, but only at natural boundaries (end of a scene, end of a day). Switching mid-scene creates confusion because people have already started acting on the old model. Plan the switch in a huddle and explain the new rules clearly. It helps to have a visual cue—like a different color lanyard for the tiebreaker—to remind everyone.

What if my team refuses to follow the model?

Resistance usually means the model does not fit the reality of the work. Listen to why they are bypassing it. If they say “it's too slow,” the model is too structured. If they say “I don't know who to ask,” the model is too fluid. Adjust based on their feedback, but keep the core idea: a coordination model exists to reduce friction, not to add it.

How do I train a new crew on a new model?

Do a 30-minute orientation before the first shoot day. Walk through the one-page coordination plan. Then run a 10-minute simulation of a common problem (e.g., a light breaks). Let them practice the model. After the simulation, debrief for 5 minutes. That is usually enough for people to remember the key rules. For complex models, repeat the simulation on day two.

Checklist for Your Next Shoot

• Identify your bottleneck roles and decide if they need more structure or more fluidity.
• Write a one-page coordination plan with a model for each phase.
• Set up communication protocols (what to do, who to tell) for at least three common scenarios.
• Run a 15-minute table read of the workflow with key leads.
• Choose one tool (walkie, app, or board) and enforce its use for the first two days.
• Define an urgent issue and allow direct communication for those cases.
• Schedule a 5-minute huddle before each scene change, even if you are using a structured model.
• After the first day, debrief for 10 minutes: what worked, what didn't, and adjust the model for day two.

Coordination models are not permanent. The best teams treat them as living agreements that adapt to the shoot's real conditions. Start with a clear choice, but stay ready to shift. That flexibility—knowing when to be fluid and when to be structured—is the real skill.