Remember my
'10 Steps to Become a Professional Screenwriter' series? Well, I've put them altogether so it reads like a quick booklet. You can download it directly from
this link (automatically opens as a Word doc). Feel free to share. I've been getting a few enquiries lately about how to be a script reader, so I've rounded up the relevant posts towards the bottom of this piece. All the good jelly is there, and you can download a couple of sample reports
from my website.
It's been a few years since I was a full-time script reader. I still read scripts but not for any of the production companies that used to give me regular work (in my heyday, I was doing coverage on about 10 scripts a week, plus 2 or 3 books). My reading nowadays is more to do with script editing or consultancy rather than the sometimes curt and superior air of a studio reader's notes. I do offer a basic script reading service. ** UPDATE, if you'd like me to read your script, please check my
consultancy page ** UPDATE
It's interesting flicking through some of the script reading blogs now. There are a couple of good ones around but some adopt the tone and attitude of the 'I Know Better Syndrome' (prevalent from readers to execs, to producers and directors). A lazy habit we're all guilty of is that it's too easy to be critical of something that's in front of us: a script, a TV show, a film, book, whatever. Pick up a script and, like, meh. It's much, much harder to create something from nothing; to put something out there. Wannabe writers really get my goat when they criticise everything. If you're so clever, then write something better. I'll wait. Still waiting. Not so clever now, are you? Directors really piss me off when they express disappointment with a script, especially after their energetic input and use of their ideas. If you're such a visionary storyteller Mr Director, why don't you write the script yourself?
I don't mind 'I Know Better' from general audiences but aspiring writers or people in the biz should really know better not to think they're above the material in front of them. Unfortunately, it's a natural position to assume, especially with some key development personnel. I was certainly scathing as a reader when I first started but I quickly mellowed because it was too depressing otherwise. You do get brow beaten by bad scripts, so it's impossible not to develop shorthand quips and 'clever me' rejection notes, slipping you further into 'I Know Better' territory. To combat this, you have to give a script a break, even if you hate it. Find something positive to say. There's always something.
Script reading is a hard job, especially when you do it day in, day out. It doesn't pay well, even when you read flat out. It's good for basic experience and vital for any development work you might fancy, or to prove your chops as a script editor. Development and script editing gigs are hard to come by though so sometimes reading will feel like a never-ending and thankless task. When this happens, you'll want to say 'no more' but in reality, it's not something you can move on from at the drop of a hat. The turn will happen slowly as you pick up other gigs, and then you look around and realise you're no longer a full-time reader (but hopefully on to bigger and better things).
This blog started as a rundown of my experience as a script reader, and what the whole process is like. You can download a couple of my sample reports at my
website. Here's a list of the relevant script reading posts in one handy section so you don't have to go trawling through the site to find them:
Logline (August 2005): "On the first page of a reader’s report, there’s a section called the “logline” where the reader sums up the story in one or two sentences (preferably one). This is an essential part of the report, and indeed, a screenplay’s development." Read the full post
here.
First Ten Pages (August 2005): "A reader/exec will automatically know from the script’s first 10 pages if it’s good or bad, regardless of what happens. But this will be evident from the first page, never mind trawling through ten of them." Read the full post
here.
Script Reports (September 2005): The basic structure and approach to a script report. Read the full post
here.
Script Reader UK (October 2005): "The role of a script reader is a thankless and anonymous task but every production company will tell you that they are vital to the submission pile and to some extent, the development process. Producers and development executives simply don’t have the time to read every script that comes in the door and they rely squarely on the reader’s report and recommendation." Read the full post
here.
Script Reading Tips (October 2006): "Once you start reading for a few different companies, they sometimes give you their own criteria on how they like their reports, and what they expect to read. It’s all variations of the main topics, of course, but they’re usually good script reading tips nonetheless." Read the full post
here.
Script Reading Commandments (December 2006): "1. Thou Shalt Read The Script in Its Entirety - When you’re reading a poor script, your mind will naturally wander and your attention will stray so try to stay focused as you don’t want to miss any important plot detail that will impede your ability to write up a good synopsis later." Read the full post
here.
Script Reading Realities (May 2007): "f you really want to know what it’s like, or simply want to improve your level of writing, then here’s what you do..." Read the full post
here.
Sample Script Reports: Available to download
at my website.
