The Decision-Rights Map

Production teams often struggle with two opposite but equally damaging problems: the bottleneck and the thread. A bottleneck happens when the director becomes a single point of failure for every minor detail. For example, a producer might wait three days for the director to approve a simple prop change—like the color of a telephone—stalling the art department's progress over a decision that doesn't affect the story's intent.

Conversely, the thread occurs when major creative shifts happen haphazardly. This happens in long email chains where people are CC'd but not clearly authorized to decide. Imagine a script change that alters the entire ending of a scene; instead of a formal review, it is decided by two people on a thread who happened to reply first. The result is a production where small, safe tasks stall, while risky, expensive shifts happen without oversight.

To fix this, you need a decision-rights map. This is a formal document that defines exactly who has the authority to say 'yes' to specific types of changes, ensuring the director is only bothered by decisions that actually require their vision.

Creative authority is the specific power to change a scene's intent, performance, or story beats. While many people contribute to a film, only a few hold the right to alter the "soul" of a sequence. This authority ensures that the creative vision remains coherent and doesn't drift based on who is available to answer an email. If a change affects how the audience perceives a character's emotion or the plot's direction, it falls under creative authority.

Consider scene 42, where Nora tells her brother she is selling the house. A decision to have Nora set the house keys on the porch rail is not a simple prop addition; it is a creative choice. This action creates a new emotional beat—a physical signal of her departure—that changes the subtext of the conversation. Because this alters the story's intent, the decision cannot be made by the art lead or a producer alone; it requires the person with creative authority, typically the director.

When building your map, you must isolate these "intent-shifting" changes from technical ones. Your goal is to identify every point where a decision could accidentally change the story, and assign that right exclusively to the creative lead.

While creative authority protects the story, budget and schedule authority protects the production's viability. Financial authority is the power to approve cost increases, while temporal authority is the power to shift shooting dates. These rights are usually held by the producer or a line producer, rather than the director. If a decision requires spending money not already in the approved budget or requires moving the company to a different day, it must be routed to the person with this authority.

For example, imagine the director wants to add a practical rain effect to the farmhouse porch in scene 42. This isn't just a creative choice; it requires renting rain machines, hiring additional grip crew, and adding waterproof protection for the gear. Because this increases the line-item cost, the producer must sign off on the expense. Similarly, if the farmhouse owners suddenly become unavailable for the scheduled Tuesday, shifting the shoot to Wednesday affects every other department's call sheet. This is a schedule change that requires the producer's authority to authorize the move and manage the resulting ripple effects.

In your decision-rights map, you will list every trigger—such as "over-budget spend" or "date shift"—and assign it to the producer to prevent accidental overspending.

Department authority allows leads to make technical decisions within their specific domain without escalating to the director or producer. A remit is the defined boundary of what a lead can decide on their own. By granting these rights, you remove the director from the bottleneck of minor technicalities, allowing them to focus on the overall vision while the experts handle the execution.

For example, consider the porch light in scene 42. The director has already established that the scene takes place at night and needs a specific mood. The Art Department lead has the authority to choose the exact style of porch light—whether it is a modern LED fixture or a rusted vintage lantern—as long as the choice fits the established budget and does not contradict the script. The lead doesn't need to send an email or wait for a meeting to pick the lamp; they simply execute the technical detail within their remit.

When you add department remits to your map, you are defining the 'safe zone' for your leads. You must explicitly state the constraints of these remits, such as "Budget neutral" or "No script changes," so the lead knows exactly when their authority ends and escalation begins.

An escalation path is the predefined route a decision takes when it exceeds a department lead's remit. Without a clear path, leads either guess—risking expensive mistakes—or stop working entirely to avoid blame, creating new bottlenecks. The goal of the escalation path is to define the exact trigger that shifts authority from a technical expert to a production or creative lead.

Take a lighting change for scene 42. If the Gaffer wants to swap one light fixture for another to better mimic moonlight, and the cost is covered by the existing lighting budget, this is a department call. The Gaffer simply executes the change. However, if the Gaffer realizes the current location cannot support the power draw required for the moonlight effect and suggests renting a portable generator or moving to a different farmhouse porch, the decision is no longer technical. It now involves additional costs and a location change. This triggers an escalation: the Gaffer must route the request to the Producer for budget approval and the Director for creative sign-off on the new space.

When you build these paths into your map, you create a "if-this-then-that" logic that removes ambiguity from the production flow.

A decision-rights map consolidates creative, budget, schedule, and department authorities into a single source of truth. Instead of digging through email threads or guessing who can sign off on a change, the team refers to one table that maps the 'trigger' to the 'authority.' This removes the social friction of asking for permission and ensures that the right person is notified the moment a change occurs.

To build this, you list every recurring type of production change in one column and the authorized decision-maker in the next. For example, 'Script Changes'—anything affecting dialogue or story beats—are mapped as Director-only. 'Prop Sourcing'—choosing the specific furniture or accessories for a set—is mapped to the Art Lead, provided it is budget-neutral. Finally, 'Overtime Spend'—any cost increase resulting from hours worked beyond the schedule—is mapped as Producer-only.

You will use this map to configure your AI triage system. By defining these rules now, you can tell an AI agent exactly when to route a request to the producer's inbox and when to let a department head proceed without interruption.

Once your decision-rights map is drafted, you must validate it through simulation. A map that looks clean on paper often reveals gaps or overlaps when faced with a 'multi-trigger' event—a change that hits creative, department, and budget boundaries simultaneously. Testing ensures that no one is accidentally bypassed and that no two people are fighting for the same final word.

Take a scenario in scene 42: the director decides Nora should now hold a specific antique letter while speaking. This is a script change (Creative), which requires a new prop (Department), and the specific antique required costs $500 extra (Budget). If your map is flawed, the Art Lead might buy the letter based on the director's verbal note, bypassing the producer and creating a budget conflict. In a validated map, the routing is clear: first, the Director authorizes the creative shift; second, the Art Lead identifies the specific prop; third, the Producer approves the $500 spend. Only after these three sign-offs is the change finalized. By running these 'stress tests,' you identify where the logic breaks before you automate it with AI.