What Check Please The Play Script Actually Is
It’s a script verification and formatting tool designed for theater production teams. You upload a play script, and it checks for consistency issues — character name variations, scene numbering errors, dialogue formatting problems, and royalty attribution mistakes. Think of it as a spell-checker specifically built for dramatic works rather than generic prose. I’ve been using this in our regional theater workflow for about two years now. The basic process is straightforward: you create an account, upload your script file (supports .txt, .docx, and .rtf), and run the scan. The scan itself takes roughly 30 seconds for a standard one-act and maybe 2-3 minutes for a full-length play. Results come back as a color-coded report showing flagged issues with line numbers and suggested fixes. The free tier lets you run about five scans per month on scripts up to 50 pages. The paid plan at $12/month removes those limits and adds collaboration features so your director, stage manager, and dramaturg can all see the same flagged issues. For most small-to-medium theaters, the free tier covers your needs if you’re not in active rehearsal right now.
How It Actually Works In Practice
Here’s where it gets useful — and where it gets annoying. The tool catches things human eyes miss because we’re reading for meaning rather than format. When I ran our production of a lesser-known 1980s play through it, the script caught that one character was listed as "MARGIE" in act one, "marge" in act two, and "Margaret" in the stage directions. The actor reading the prompt book wouldn’t have noticed that until opening night. The tool also flags copyright and licensing issues. If your script includes quoted material — a poem, a song lyric, a passage from another work — it’ll highlight those sections and ask whether you’ve secured the proper performance rights. This saved us from mounting a production with an uncleared musical excerpt. That would have been a lawsuit waiting to happen. One specific edge case I ran into: the tool misidentified stage directions that contained dialogue-like text. In one play, a character reads a letter aloud during a monologue, and the script flagged it as "unattributed dialogue" because it wasn’t formatted with a character name followed by a colon. My workaround was to manually add character attribution to those sections before running the scan. Takes about five minutes and prevents false positives from cluttering your report.
Things Beginners Get Wrong
Most people assume the tool will fix formatting problems for them. It doesn’t. It flags issues and sometimes suggests corrections, but you still have to apply them. I watched a new production assistant try to treat the output as a final document and nearly sent a prompt book with inconsistent character names because the tool had suggested changes that weren’t actually implemented. Another misconception: the royalty check feature isn’t a legal guarantee. It cross-references a database of known playwrights and licensing organizations, but it’s not comprehensive. If you’re dealing with an obscure work or a play that’s been adapted multiple times, the tool might come back clean when you actually need a license. Always verify through the official licensing agent — Samuel French, Concord Theatricals, or the playwright’s estate — regardless of what the scan says.
Get the Full Details
When It Falls Apart
The tool struggles with experimental or non-standard scripts. We tried running a postmodern piece with fragmented dialogue, minimal stage directions, and intentional formatting anomalies. About 40% of its flags were false positives — it couldn’t distinguish between deliberate artistic choices and actual errors. If you’re working with a conventional script, it’s solid. If you’re dealing with something that intentionally breaks formatting rules, you’re better off doing a manual read-through or hiring a dramaturg. There’s also a file size limitation on the free tier. Scripts longer than 50 pages get cut off mid-scan, and you won’t know which portion was missed until you upgrade or split the document. I once had a two-act play where the second act’s entire third scene went unscanned because of an invisible formatting break. Splitting the script into separate act files before uploading solves this.
Should You Use It
If you’re running a production and still catching script inconsistencies by hand, yes. The time savings are real — what used to take our team about three hours of manual proofreading now takes maybe twenty minutes of review after a scan. But treat it as a first-pass tool, not a replacement for human judgment. Run the scan, review the flagged items carefully, verify any royalty concerns through official channels, and then do one final read-through with the actual cast and crew before tech week.
