← All posts

What a line producer and a 1st AD each ask their connected assistant

August 31, 2026 · updated August 31, 2026

Connect a line producer and a 1st AD to the same project through the same assistant, and they’ll ask it almost nothing in common. Same connector. Same underlying schedule, breakdown, and reports. Completely different conversation – because the two roles aren’t looking at the project for the same reason, and a connected assistant reflects that difference back almost immediately once you watch what each of them actually asks.

What a 1st AD’s questions look like

A 1st AD’s questions cluster around the next few days and whatever’s about to go wrong in them. What’s scheduled tomorrow, and is anything flagged. Has a cast availability change been reflected in the current schedule yet, or is that still pending. How close is a turnaround running on a specific day. Is the breakdown complete enough on an upcoming scene to trust the call sheet it’ll generate. These are prep-and-execution questions – close to the ground, close to the next twenty-four to seventy-two hours, aimed at catching something before it becomes a problem on set rather than after.

The first_ad persona setting, when applied to a connected assistant, tunes it toward exactly this: conflicts, immediate scheduling detail, and the practical state of the next few shoot days, rather than the wider financial or administrative picture.

What a line producer’s questions look like

A line producer’s questions cluster around cost and risk, not the next twenty-four hours specifically. Which flagged conflicts carry a real financial consequence – a meal penalty risk, an overtime pattern building across several days. How close is a child performer to their hour limit this week, not just today. How does the current day count compare with what was planned at this stage of the schedule. These are pattern questions, spanning a longer window, aimed at catching a cost before it’s locked in rather than catching a single day’s logistics.

The line_producer persona setting reflects this: it prioritises cost-relevant flags and pattern-level questions over the close-in scheduling detail a 1st AD’s persona setting would surface first.

The pattern generalises across the other roles too

A location manager’s questions cluster around a different axis again – which days involve a company move, what’s confirmed versus tentative for each set-up, whether a location’s availability window is holding. A casting director’s questions run closer to availability and booking status than to the shoot-day mechanics either an AD or a line producer cares about. A script supervisor connected to the same project asks yet another kind of question – continuity flags, scene-by-scene detail, the state of the latest revision – closer to the script and breakdown than to the schedule’s cost or logistics layer.

Five roles, five different working relationships with the same underlying data, and a persona setting exists for each because the alternative – one generic assistant answering every question the same way regardless of who’s asking – would either bury a 1st AD in cost detail they don’t need in the next hour, or leave a line producer wading through granular scheduling minutiae to find the one number that actually matters to them.

Why this matters beyond convenience

None of these roles work from a different project. They work from the same schedule, the same breakdown, the same reports – the connected workspace’s entire premise is that this data doesn’t fork into five separate versions depending on who’s looking at it. What forks is the question, not the source. A line producer catching a cost risk early and a 1st AD catching a logistics conflict early are both drawing on the same underlying accuracy, just asking for a different slice of it.

That’s arguably the more useful way to think about what a connected assistant is for in a production context. Not one tool doing one job, but one accurate source, answering genuinely different questions well, because the questions themselves – not the underlying facts – are what change from role to role.

Related: How to connect Claude to your SceneItAll project, Why line producers should look at scheduling before budgeting