Skip to main content

Using a Spreadsheet to Write

Beat sheets, outlines, storyboard, and other tools help me organize my thoughts when writing. Too many writers stick with word processors as their sole "digital tools" when many other great applications exist — and "applications" for various applications, too.

How can you use a spreadsheet to write? And why might you try this?

A spreadsheet's columns and rows, a reflection of the ledger books they replaced, make an ideal way to track your pages, words, minutes, or other metrics. My writing spreadsheets range from simple checklists to complex sheets with calculations reflecting how much I need to cut or add to parts of story. (Scrivener's outline view is similar to this, so allow me to plug Scrivener yet again.)

My basic story sheet resembles the chart on our website page "Plot and Story" [http://www.tameri.com/write/plotnstory.html].

Some plot points should be reached at specific pages, especially early in a story, while others should be reached within ranges of pages, as a percentage of the overall work. Using a spreadsheet helps me track these personal ideas.

For example: I like to have the "perceived problem / challenge" and the "real problem" within the first ten pages of a 90 minute screenplay or stage script. In a book, I might want those within the first "ten percent" of the work. Express each plot point in 25 words or less.

Major Beat 3 -> Perceived / Immediate Challenge -> Bomb ticking in a subway tunnel
Minor…
Major Beat 4 -> Real Challenge -> Corrupt leaders creating the chaos to gain powers
Minor…

Using Excel or another spreadsheet, I include columns reflecting page counts, minutes, real time, literary time, and more. These metrics help me pace my stories.

Do you have a checklist? If not, create one. Every creative writer using narratives should have a beat sheet, because it forces you to recognize when things are missing from a story.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.