Coordination starts with people
A film Production is a temporary organization. Development brings producers, writers, directors and financing into focus. Pre-production adds hiring, casting, availability, locations, scheduling, department preparation, equipment and approvals. Shooting coordinates Production Days, call sheets, specialized departments, presence and changing plans. Post brings editorial, sound, music, VFX, color and review forward. Delivery connects masters, marketing, distribution and archival.
These stages overlap. Different people become relevant at different times. Crew size depends on production type, budget, geography, schedule and creative requirements. The interactive examples use illustrative small, medium and large structures; they are not industry averages or staffing standards. There is no universal crew hierarchy.
Two graphs and a fragmented toolchain
Organizational structure describes who belongs where: Production, Department, Department Head and Department Crew. Communication structure describes who needs to exchange information for work to happen. A DP belongs to Camera but also coordinates with Directing, ADs, Grip, Electric, Art, Sound, Production, Script Supervision and Post. A pure org chart cannot capture all those relationships.
Coordination is often spread across phone contacts, text messages, email, social media, PDF call sheets, spreadsheets, calendars, cloud storage, messaging apps, job boards, paperwork services, specialized tools and word of mouth. Get hired, join, prep, shoot, wrap, then repeat the handoffs on the next job. Professional identity is repeatedly re-entered even when two people already share a known Production context.
The production explainer makes these structures interactive. Its role perspectives and information matrix show why a PA’s operational needs, an AD’s broad coordination and a client’s review access are different. Those examples are educational, not rigid permission policies.
Context does not erase consent
Same Production means relevance within authorized context. It can support discovery, in-app communication where permitted and contact fields the Person allows to be visible. It does not imply access to every private contact field. Contact requests and a deliberate Save to My Roster action support persistent professional relationships separately from temporary membership.
Production work moves through temporary teams, dates, creative artifacts and changing obligations. A contact list answers who someone is; a work assignment answers what they do in a particular production. Neither alone answers who should receive tomorrow’s update, who is called for a day, or which version a reviewer approved.
A feature-by-feature model can accidentally create several representations of the same person. Staffing has a candidate, a call sheet has a recipient, a conversation has a participant, and a resource has a reviewer. These representations have legitimate local responsibilities, but they need explicit connections to persistent identity and current production participation.
The architectural thesis
Filmclusive keeps identity, participation, descriptive work, time and authority distinct. A Production supplies operational context. Membership connects a person to that context. Assignments describe one or more jobs. Groups organize work. Production Days tie intended work to operational time. Resources connect the people and context to what they are working on.
The conceptual vocabulary also includes Space, Workflow, Audience and Relationship. It is a vocabulary for explanation, not a claim that every concept is implemented as one universal database object. In particular, a shared Space concept does not erase differences between Production, Team and Community ownership.
A coordination path
Consider issuing tomorrow’s call sheet. The production and day provide context. Assignments describe the intended work. The schedule describes timing. An issued sheet freezes relevant content and recipients. Acknowledgement records an explicit response; presence records participation. Each stage contributes a different fact.
This separation costs more than a single spreadsheet-shaped record. Queries need deliberate joins and projections, and users need clear navigation between related records. The benefit is that replacing a work assignment does not recreate the person, viewing a sheet does not record arrival, and communicating with a group does not silently grant authority.