Though I had heard it mentioned before, I really didn’t know what the beat sheet was until I happened on Larry Brooks’s lucid explanation of it in Story Engineering. It sounded so good I decided to try it.
The beat sheet isn’t a complex thing. It’s just a list of your scenes with the minimal information necessary—a scene name and maybe a nutshell description. Having assembled your list, you start fooling with their order, adding some, subtracting others, until you have a satisfactory skeleton on which to hang the flesh of your tale. You can use whatever you like to make your beat sheet: a word processor, post-its, index cards, scraps of tanned cowhide. The main thing is that you can rearrange, add and subtract scenes with ease.
The beauty of the beat sheet is that it removes detail. If you’re trying to sort paragraphs describing each scene, or scene-construction forms of some kind, it’s too easy to get lost in the information about each scene, rather than simply concentrating on where it should go in the story. With the beat sheet, you get a couple of crystalline drops of data for each scene. These info-chicklets are easy to hold in your short-term memory, so you can juggle several at once and better determine how they affect each other, which insight goes into your scene arrangement. (FYI, the average short-term memory holds about seven items at once.)
I was stunned by my results with the beat sheet. I had a big sub-plot and realized it wasn’t working at all, so I cut it to the bone. I figured out how to tighten up the first three sections and began forming an idea of how the concluding section would go. Most valuable of all, I found that events in need of foreshadowing and questions in need of answering jumped out at me like clowns popping out of a miniature Volkswagen.
Valuable as it was, the beat sheet still left me feeling a little short in the coherence department. I didn’t have a good sense of whether all the beats made sense or not. Now it was time to bring back some detail. The next step, writing a descriptive paragraph for each beat, helped me take care of that. Writing a paragraph about each beat helped me analyze it to be sure it held up as a worthwhile part of the story and also fit well with the other beats. I discovered more plot gaps, more foreshadowing needs and even a few more scenes that needed adding.
I’m still working on the descriptive paragraphs, but they’ll be wrapped up soon and when they are I’ll be in great shape to plan each scene to the point where I can write it easily. Then – joy of joys! – I’ll actually write those puppies!
Bonus! Here’s a beat with a descriptive paragraph to give you a concrete idea of the process.
1. Colin gets killed. The Dough(boy) is Flat Colin gets hit by a truck while delivering pizzas.
Colin is toodling along on his scooter with the music turned up. [Look up some real scooter/motorcycle fatal wrecks and base the scene on them.] A truck runs a light; Colin doesn’t hear it coming and gets hit. He sees the famous bright, white light beckoning him forward. [What about other people who are in comas? Why don’t they get the same reaction as Colin? And if there are more like him, why don’t they recognize the smell of someone still connected to a body? Maybe de Retz, in his eagerness to make good, broke the rules and snatched a soul (Colin’s) meant for Limbo, Heaven or some other area; that hasn’t happened before. Also, Colin is the only person ever to find out he is in a coma someplace and that affects his behavior.] [If Colin is meant for Heaven, why is his body still alive? Maybe Colin’s angel is the one to escort him to Limbo or coma holding area.]