Operating casting workflow

The system prepares the field. The casting director makes the call.

Aran connects brief parsing, database search, gap research, enrichment, deduplication, and outreach preparation around one casting workflow. Selection, approval, relationships, and the final recommendation remain human.

Scope a paid pilot Trace the workflow

Operating system · explicit owners · human approval before consequential action

Status
Operating casting workflow
Agent responsibility
Research and preparation
Human responsibility
Judgment and approval

Responsibility trace

Every handoff has a named owner.

The workflow is useful because it does not blur preparation and judgment. Agents carry structured, repeatable work; people retain the decisions that depend on context, taste, permission, and trust.

workflow operating Aran human judgment
01 Interpret the brief Read the client context, cultural cues, constraints, and unstated edge. human
02 Extract requirements Turn the brief into explicit attributes, geographies, references, and constraints. Aran
03 Scan existing records Find relevant people already known to the practice before looking elsewhere. Aran
04 Research the gaps Use approved sources to expand the field where the existing records are incomplete. Aran
05 Enrich and deduplicate Structure evidence, attach source links, tag relevance, and resolve duplicate records. Aran
06 Curate the shortlist Apply taste, relationships, risk, and the eye the client hired. human
07 Prepare outreach Compile approved segments and draft contact preparation for review. Aran
08 Approve contact Review who should be contacted, why, and what should be sent. human
09 Make the final call Own the recommendation, exceptions, client conversation, and relationships. human

Evidence ledger

A record is useful when its source and decision boundary stay visible.

The operating system keeps the input, transformation, supporting evidence, and decision owner distinct. That makes a prepared candidate record inspectable rather than presenting an unqualified answer.

The system does not decide who should be cast. It prepares a better field for the person accountable for that decision.

Example record path · source retained through review
Record stage Input Evidence retained Decision owner
Requirement Approved project brief brief reference human
Candidate profile Existing record or approved source Source link, context, and relevance tags Aran prepares
Shortlist Enriched candidate field Profile evidence remains attached for review human selects
Outreach Approved shortlist Recipient, segment, and draft are reviewable human approves

System boundary

Preparation can scale. Accountability does not disappear.

The workflow documents permissions, retains provenance, and places human approval before contact or recommendation.

What the operating workflow demonstrates

  • A free-text brief can be translated into structured research requirements.
  • Existing records can be checked before approved gap research begins.
  • Candidate evidence can be enriched, tagged, and deduplicated for review.
  • Outreach preparation can sit behind an explicit approval checkpoint.

What the system does not claim

  • That available source information is exhaustive or automatically correct.
  • That finding contact information creates permission to use it.
  • That a relevance signal can replace a casting director's cultural reading.
  • That an agent should own outreach, selection, or the final recommendation.

Continue

Industry

Operational agents for casting

Where casting work repeats, where judgment stays human, and what makes a useful starting workflow.

Explore casting ↗ Use case

Research enrichment

How approved sources become structured, provenance-linked records for human review.

See the capability ↗ Paid pilot

Start with one workflow

Map the work, define its checkpoints, and deploy a deliberately scoped first system.

See the pilot ↗

Keep the preparation moving and the judgment human.

Apply for a paid pilot