If you're the one getting the script to your cast — the director, the stage manager, or the actor who ended up coordinating — the job isn't emailing a PDF. It's making sure everyone works from one version, from table read to opening night, without drowning in resends. Do it badly and by week three you have five files circulating and no one sure which is current. Here's how to share a script with your cast cleanly: one link, one version, rights handled, and a plan for when copies have already scattered.
The One-Source Rule: One Version, Zero Version Drift
The standard approach in community theatre is simple: export the PDF, email it to the cast, done. It works exactly once. The problems start the moment anything changes.
A director cuts a scene. The stage manager fixes a blocking error. Someone misses the update email and shows up with last week's file. That version drift has a concrete cost in the room: two actors running a scene from different files aren't building the same cue lines, blocking notes reference lines that don't exist in one person's copy, and the director re-explains changes that were already written down. Every one of those is rehearsal time you don't get back.
The fix isn't a better email system. It's removing the file-sharing model entirely. Everyone accesses the same source, so when the script changes it changes for everyone at once — no resend required.
One URL. One version. No attachments.
The right tool depends on what your cast needs. A shared document can work as a baseline — everyone sees the same text. But it won't give you scene-level navigation or notes attached to specific lines, and a cast working scene by scene needs both. Whatever you land on, the test is simple: does an update reach the cast without anyone re-downloading anything? If a change still means re-sending a file, you haven't left the email model — you've just moved where the attachment lives. The usual failure mode is someone reverting to email because it's faster in the moment, and the single source collapses by week two.
What's Rights-Safe to Share
Before you upload anything, understand what you're actually allowed to distribute. This is workflow guidance, not legal advice: your license, publisher terms, or written agreement always wins.
Most published plays are licensed. Licensing a production covers performance rights — it does not automatically grant the right to digitally distribute the full script. What you can share depends on your specific license and publisher terms.
| Scenario | What to check | What you can share |
|---|---|---|
| Licensed production (Concord Theatricals, Samuel French, DPS, etc.) | Your exact license and the publisher's FAQs | Usually the authorized cast copies bought through the publisher; uploading or duplicating an acting edition often needs explicit permission |
| Original or public-domain text | That the specific edition is public domain | Freely, once PD status is confirmed — but verify; modern translations and adaptations are not themselves PD |
| New play / local playwright | Your written agreement with the playwright | Whatever the agreement explicitly allows |
Copyright duration rules shift over time, so rather than trusting a fixed cutoff date, check the U.S. Copyright Office duration guidance or your licensing house directly. Publisher FAQs are the source of truth for copies, uploads, and digital distribution. The safest rule: use the authorized cast copies your publisher provides, and don't upload a licensed acting edition to a third-party platform unless your license explicitly permits it. If in doubt, ask before uploading.
Set Up Sharing Before the First Rehearsal
Getting the system right before day one saves time every week after. The setup:
- Confirm your rights. Check whether your license permits digital distribution. For a public-domain text, verify the specific edition is PD — not a modern translation.
- Choose one platform and commit. Pick a single home for the script. Don't split it across a Drive folder, a PDF email, and a WhatsApp chat. One location, announced clearly at the table read.
- Assign characters before distributing. If your platform supports character-level access, set it up first. Cast members who can jump straight to their scenes use the system more consistently than those who scroll 90 pages every time.
- Announce the link once, as canonical. Send it at the first cast meeting and be explicit that all future updates happen there, not by email. Something like:
"The script is live at [link]. This is the only version — bookmark it. If anything changes, I'll update it there and post here. Don't work from the PDF you downloaded last week."
- Update in place, not in parallel. When the script changes, edit the original source. Never spin up a "version 2" file. When a change matters, announce the specifics — scene, line, what changed — so no one has to hunt for differences.
- Give the stage manager admin access. The SM should be able to flag lines, add scene notes, and update the script without routing everything through the director. That removes a communication bottleneck during rehearsals.
If some cast members are less comfortable with apps, a two-minute walk-through on someone's phone at the first rehearsal prevents weeks of "I can't find the link" messages. For the full arc from distribution to opening night, the community theatre rehearsal hub covers the rest of the workflow.
When Multiple Versions Are Already Circulating
Often you inherit the mess: three files are already floating around before anyone agreed on a system. Resetting to one source mid-process is messier than starting clean, but you can do it in a single rehearsal.
If you're coordinating:
- Declare the canonical source out loud and in writing. Pick the version the director is actually working from — usually the one with the latest cuts — and name it at the next rehearsal.
- List the differences yourself. Note each change between the old files and the canonical one: scene, line, what changed. Don't make thirty people diff it independently.
- Kill the old copies. Delete superseded files or relabel them "OLD — do not use," so no one drills from them by accident.
If you're an actor who's been marking up the wrong file:
- Migrate notes change by change, not blind. For each cut or rewrite, move only the annotations that still apply to lines that still exist.
- Check for orphaned cue lines. When a line you'd marked is gone, see whether your blocking or cue note attached to it should move to the neighbouring line. Cuts orphan cue lines more often than actors expect.
- Recount your scenes against the canonical version before your next off-book pass, so you're not memorizing a speech that got trimmed.
Do it in HitCue
- Share script link: invite your whole cast with one link — no attachments, no version confusion, and no re-sends when the text changes.
- Shared notes: post scene-level notes the whole cast can see, so a cut or a blocking change lives next to the line it affects instead of getting buried in a group chat.
- Cast recordings: share audio of cue lines inside the script, so every actor can run drills alone, on their own schedule, from the same source everyone else is using.
Upload your script, assign characters, and share one link with your cast. → Download HitCue
