Casting and Audition Management Software: The Private System Behind the Public Marketplace

Why the marketplace is not your system of record

Casting Networks, Breakdown Services and Casting Frontier are marketplaces. They connect casting to agents and performers, distribute breakdowns, take submissions, and handle self tapes, and they are good at that. What they are not, structurally, is your internal operations system, because their job is to serve the whole industry and yours is to serve one company's projects with one company's obligations.

Look at what a casting office actually does with a project. Breakdowns go out through the marketplace. Submissions come back and get triaged. Selects move into a spreadsheet because the marketplace's list tools do not match how your team works. Self tapes get downloaded and put on a shared drive so producers can watch them without a login. Feedback arrives as email replies and text messages. Callback scheduling happens in a calendar and a group chat. Avails and holds get tracked in a second spreadsheet. Minors' paperwork sits in a folder somebody named PERMITS. And the talent history that took your casting directors fifteen years to accumulate, meaning who read well for what, who was unavailable and why, who a director liked, lives in individual memories and personal notes.

Across media and workforce projects Digital Heroes has delivered, the specific costs in this category are consistent. Somewhere between a quarter and a third of a casting associate's week goes to moving material between systems and chasing information that already exists somewhere. And the risk sits entirely on the compliance side, because a company that cannot produce a work permit, a trust account confirmation or a consent form for a recorded audition is exposed in a way that has nothing to do with how well the part was cast.

Problem 1: casting a minor turns a creative decision into a compliance event

The moment you shortlist a fourteen year old, a set of obligations attaches that has nothing to do with the reading. In California a minor needs an entertainment work permit, and earnings are subject to the Coogan law requiring a portion to be set aside in a blocked trust account with confirmation provided. Work hours are limited by age, a studio teacher is required, and school schedules constrain the day. New York and other jurisdictions have their own permits and their own trust requirements, and they do not match California's. If you shoot in more than one state, you are administering more than one rulebook.

None of this is in a casting marketplace, because a marketplace connects people and does not employ them. So it lands in a folder and an email chain, and the failure mode is not a missing permit at the point of hire. It is a permit that expired between the callback and the shoot date, discovered by a production coordinator on a Sunday.

What a custom build does: attach permit, trust account and guardian consent records to the talent, not to the project, since a working child actor carries them across your projects. Store issue and expiry dates with the document and generate escalating notices, not a single reminder. Model work hour and schedule constraints by jurisdiction and age band so scheduling a callback or a fitting outside allowed hours raises a flag before the invitation goes out. And keep guardian contact and consent distinct from agent contact, because those are different relationships with different legal weight.

Problem 2: union status is a clearance step, not a field on a record

Hiring a performer under a union agreement requires verifying that they are in good standing before the engagement, which is a clearance request to the union rather than a lookup in your database. Hiring a non union performer in a covered role means a Taft Hartley report with a justification that someone has to write and file. Both are steps with owners and dates that determine whether a shoot day is legal.

In most offices this happens by email between a casting associate and production, and the evidence that it happened lives in a sent folder. When a production accountant asks six months later whether a specific performer was cleared, the answer is a search.

What a custom build does: model clearance as a task on the engagement with a status, a requester, a date, a response and an attached document. Non union engagements generate the report requirement automatically with a template that pulls the role, the project and the audition history that supports the justification. The system will not do the union's job or yours, but it will make sure the step exists as a record rather than as a recollection, and it will stop an offer from advancing while a required clearance is outstanding.

Problem 3: you are holding thousands of people's faces and voices, permanently

A casting operation accumulates headshots, resumes, self tapes, callback recordings, chemistry reads and sometimes personal contact details for people who never worked for you and never will. Most of them are not employees, most of them never hear from you again, and the material sits on a shared drive indefinitely because deleting things takes effort and nobody owns the decision.

Two forces make that untenable. Privacy law in several jurisdictions gives individuals rights over their personal data including deletion, and a performer's headshot and self tape are unambiguously personal data. Separately, consent for the use of recorded audition material has become a live issue in the industry, with digital replica and synthetic performance provisions now part of the conversation in a way they were not five years ago. What a performer agreed to when they submitted a tape three years ago probably did not contemplate what could be done with it now.

What a custom build does: consent is a record, not a checkbox. Capture what the performer agreed to, for what purpose, on what date, under what terms, and attach it to the material rather than to the person generally. Set retention periods by material type and enforce them with an automated review rather than an intention. Restrict who can download original media, and log every download, because material walking out on a personal laptop is how these situations actually arise. Handle deletion requests as a workflow that reaches every copy the system knows about. A casting company that can answer a data request in an afternoon is in an entirely different position from one that starts by searching a shared drive.

Problem 4: avails, pins and holds across roles and projects

Casting runs its own version of the availability problem. A performer is pinned for one role, on avail for another, and has a conflicting hold from a different production entirely. Producers ask for a shortlist that is genuinely available on the shoot dates. Agents want to know whether their client is released. Directors change their mind on Friday afternoon.

What a custom build does: hold status is an object with a role, a date range, a level and an expiry, visible across every project your company is casting. A performer's record shows every current claim on their time, including the ones your other project made. Release notices go out from the system with a record that they went. And the shortlist a producer sees carries availability rather than being a list of names someone believes are free.

Problem 5: the handoff to contracting and payroll is where information dies

An offer is agreed. Then somebody retypes the performer's legal name, agent details, fee, role, dates and terms into a deal memo, and later somebody retypes it again into a payroll onboarding system. Every retype is an error opportunity, and the errors surface as a wrong name on a contract or a misrouted commission payment.

What a custom build does: the offer object carries the agreed terms and becomes the source for the deal memo, so the contract is generated rather than retyped. Where your production works with a payroll provider, the engagement data exports in their expected format rather than being keyed a third time. Signature status flows back so casting can see what is outstanding without asking. This is not glamorous and it is usually the feature that convinces a finance director to approve the budget, because it removes a recurring category of error that costs real money to fix.

What this costs and how long it takes

A first release covering projects, roles and breakdowns, submission intake from the marketplaces, media handling with self tape review and structured producer and director feedback, callback scheduling, and a real talent record with casting history runs $55,000 to $120,000 and ships in 12 to 16 weeks in our delivery experience. A full platform adding minor permits and trust tracking, union clearance workflow, consent and retention management with deletion handling, avails and holds across projects, offer and deal memo generation and payroll handoff runs $140,000 to $340,000 phased over 6 to 12 months.

What drives the price up: media at scale, because self tapes are large video files and a system storing years of them needs deliberate design around cost, transcoding and access speed rather than an afterthought. Integration with marketplace platforms, which varies by what each one exposes and should be scoped after checking rather than assumed. Multi jurisdiction minor rules, at real time per jurisdiction. And background or extras casting at volume, which is a different operational shape from principal casting and should be treated as its own phase.

Build versus buy, and when buying is the right call

Keep the marketplaces. This is the part we would push back on if a client proposed otherwise. Casting Networks and Breakdown Services are where agents and performers already are, and building a private submission channel means asking the entire representation community to change how they work for you specifically. They will not. Your system should consume submissions from those platforms and hold everything that happens afterwards.

Buy only, and build nothing, if you are a casting office running one or two projects at a time with a small team. The marketplace plus a shared drive plus a spreadsheet is proportionate, and a custom platform would consume the attention of the people who should be casting.

Build the internal layer when several of these are true. You cast four or more projects concurrently, so avails and holds collide across your own slate. You employ minors regularly, particularly across more than one state. You are a studio or broadcaster where casting feeds directly into contracting and payroll systems you already own. You have been asked a data privacy question you could not answer quickly. Or your institutional casting knowledge, meaning years of who read for what and how it went, exists only in individual memories and would leave with the people who hold it.

How to choose a developer for casting software

Ask them how they will handle a fourteen year old cast on a production shooting in two states. If the answer is a document upload field, they have not understood that permits, trust accounts, work hour limits and guardian consent are different objects with different rules and different expiries. This is the part of the domain that carries actual legal weight.

Ask how they will store and serve self tapes. Video at scale is a real engineering decision with real running costs, and a developer who has not thought about storage tiering, transcoding and access logging will build something that works in month one and becomes expensive and slow in year two.

Ask who owns the code and put it in the contract before kickoff. You should own the repository, the infrastructure accounts and the right to hire anyone else. At Digital Heroes the client owns the code from the first commit. In a business holding thousands of performers' images, recordings and personal data, a vendor with independent control over that store is a liability you would struggle to explain to anyone who asked.