How SRV was tested — and where it stands
SRV is not open yet. This page says what was tested, what passed, what failed, and what is still being proven. Every figure on it is drawn from the house’s testing record, and the failures are on the page beside the passes.
Where it stands
- Opening soon. SRV opens to writers after its first outside reads. Nothing is for sale yet.
- Continuity. Continuity checking — catching a fact that changes from one page of a script to another — is still being proven on sealed tests, and it has not passed them yet.
- The final review before opening has not been passed yet. SRV opens only after it is.
- The answer keys. The sealed tests so far were prepared inside the house, kept apart from the people building the reader. That is self-testing, and we say so. An answer key written by a person outside the build is still to come, and no further paid test read runs before it exists.
- The engine on our server today carries the digest
ff74313a81b2f2d4. Its own test battery passed 367 of 367 checks on 7 October 2026.
The two release reads
Two complete reads of the founder’s own scripts ran end to end on our server: a 116-page feature screenplay of 91 scenes, and a 51-page television pilot of 34 scenes.
Both passed the read’s own 55 delivery checks before any document left the server. Every quotation was found on its own page — 35 of 35 in the feature and 14 of 14 in the pilot — and neither read invented a fact about its story.
The feature’s first read had two faults in how its documents were put together, and the house’s checks caught them. The faults were cured at their root, the feature was read again, and the second read passed. Both reads are on the record.
Passing its own checks is not the same as being right. A document can agree with itself and still miss a mistake in the script — which is what the sealed tests below are for.
What failed, stated plainly
Before a sealed test, known continuity errors — a fact that changes from one page to another — are planted in a copy of a script, and the answer key is sealed away from the people building the reader. The read is then scored against the key. The pass line was 7 of 8 planted errors caught across the two scripts.
- The release reads, 5 October. The feature caught 0 of 5 planted errors; the pilot caught 1 of 3. Both failed.
- The continuity reader rebuilt, 7 October. On a fresh sealed set: 1 of 5 in the feature and 2 of 3 in the pilot. Widened, on another fresh set: 1 of 5 and 1 of 3. Each set fell short of the pass line.
- The engine on our server today. On its sealed test the pilot caught 0 of 3. The feature’s test stopped at its own spending limit before it finished, so it has no score — and we do not count it as a pass.
A score under the pass line is a fail, and we report it as one.
Why the engine did not change
On 11 October a repair to how the reader records the facts of a script was built. Its test battery came back with 35 checks failing, so it was never sent to our server. It was set aside whole, kept, and is being rebuilt on its own, apart from the engine that is live. The engine on our server today is the one that passed its battery.
What these tests do not prove
- No outside writer has had a read yet. The first five free seats open only after the tests above are passed.
- The television lane opens soon. Until it does, no television seat is sold and no television script is read.
- Today SRV reads scripts written in English.
- Reading scanned pages is still being proven. Upload the PDF your screenwriting software exports.
- None of this is a promise that every writer will agree with the findings of a read. It is a record of what was checked, what failed, and what is being fixed before the doors open.
Writing in another language? It’s coming.
Today The Script Reader's Verdict reads scripts written in English. Native-language reads are coming soon, and each language opens only once it has been proven on real screenplays written in it. If you would like to hear the moment yours opens, write to us: support@lovingmywords.com.