In this, the final episode of a writing structure series, I will describe how I progress from having 15 story beats and around 40 planned chapters, to a completed, published book. I like to do things in an efficient way, which means planning and sticking to a process.
I know that I’m swimming against the ‘creative tide’ here. The conventional wisdom (or perceived or received wisdom, if you prefer) is that anything which improves the efficient process of creating a completed and published story is anathema to creative writing. I sometimes have enough trouble trying to convince other writers that having a basic plan as an underpinning structure for a story is a good idea. To have a well thought-out, tried and tested process which sees me move from story idea through to completed book in as speedy and simple as way as possible causes many writers to react in horror.
So… why? Why streamline the process? It all started at a crime writing weekend, put on by the National Centre for Writing in Norwich.
[ https://nationalcentreforwriting.org.uk/ ]
We had lots of interesting workshops and talks, all centred on crime stories. In one session, a large group of us listened to a successful crime author – for the life of me, I can’t remember who it was now. One member of the audience asked: “How many rewrites do you make from finishing the final manuscript?” At the time, I had struggled to finish even one novel. I was expecting an answer around three or four. “At least… ten to eleven times, I would say.”
WHAT????
There was a rewrite for this, a rewrite for that, a rewrite after a beta reader, a rewrite after the first reading from an editor, a rewrite on subsequent critiques, a rewrite once the publisher had seen it… and so on, and so on.
Blimey.
How can anyone spend so much time rewriting and rewriting and rewriting the same story? What was wrong with it in the first place? I turned this over and over in my head. What a waste of time! Why not get the story pretty near perfect as early as possible?
So, lots of thinking and reading and analysing later, I came up with my process:
1. Develop scene-by-scene plan for story.
I use three (four) acts, seven plot points, fifteen story beats, forty scenes (see previous posts), breaking down the story from a simple premise until I have a full story plan.
2. Write each scene in turn.
I do not edit-as-I-go (although I will fix typos, because they’re just annoying); any plot holes I discover get highlighted, and I move on – the same with questions that come to light regarding plot or characters, or I recognise the need for further research or an edit to a previous scene. The core idea is: keep crafting the manuscript until the first draft is complete.
3. First rough edit.
At the end of the first draft, immediately go back and fix the problems indicated by the highlighted text. This I call the Hammer and Chisel edit. It’s fixing the big problems so at least I have a coherent telling of the story I’ve created. I don’t do anything else – just fix the big, highlighted problems.
4. I let the manuscript settle for a while.
Just like you let pastry settle in the fridge before you shape it into a pie (or whatever), the manuscript needs to be put away for a while to give me, the author, some distance from the words I’ve just typed. This is important. As a writer, you can become word blind, unable to see the actual words in the manuscript and instead see the words you have in your head – those that you actually wrote compared to the words you think you wrote. My usual settling time is 2-4 weeks, which I spend designing the cover or writing non-fiction or something else.
5. First run-through edit.
Yes, I edit my own work. I don’t need to perform a structural or developmental edit. The structure of the story is sound, because it was designed that way from the start. I’m not saying that the overall story never needs work. Occasionally, it’s only when reading the story from start to finish that a major problem raises its head, but it is rare. So I read from start to finish, dealing with issues as they occur.
6. First proof read.
Before sharing the work (see item 7, below), I need to make sure the manuscript is in good condition. The beta reading process is intended to tell me, the author, if the story works as a completed novel, and I don’t want any high-level analysis of the completed work to be peppered with irritating minor errors. I use Pro Writing Aid to help me. A couple of points here – there are a number of writing analysis tools on the market. I just happen to get on with PWA better, especially since it has some integration with Scrivener, my writing software. The second, and important, point is that it helps me. It’s good at finding things in the writing it doesn’t understand, but sometimes so-called flaws are deliberate elements of my writing style (e.g. short sentences or irregularly-formed sentences). And sometimes it trips up over something which is perfectly all right, but the error actually resides earlier in the sentence or paragraph.
7. Beta read.
A beta reader is someone who will read my manuscript and tell me if it works as a story. Hopefully, they won’t find any typos, but they can give me clues about the pacing, the characters, the viability of the story. Will someone who buys this book enjoy reading it? And you must choose your beta readers carefully. They must be someone who reads a lot, preferably in your genre. They must understand what their job is – not to analyse sentence-by-sentence, but to go with the flow, read the story, and tell me if it works. It must be someone who you trust. It must be someone who can read the story relatively quickly, and has time to finish it. There’s no point if you have to wait for a year to get feedback.
8. Post-beta edits.
Hopefully, once the beta reader has finished, I will have a few pages of notes. Perhaps some questions, where elements of the plot aren’t clear, or the characters are quite plausible enough. I use my partner
[ http://www.anitabelli.com/ ]
as my beta reader, and I think I address about 80% of her issues with the story. It is my choice how much, or how little, to edit the story after the beta read.
9. Second proof read.
After making any edits to the manuscript, it’s important to check for any typos which may have crept in during the previous edit process. No matter how carefully you make the changes, there are always one or two small errors that can creep in, especially when you’re making a small change into an existing paragraph of text. It’s well worth performing a final proof read, before…
10. PUBLISH!
Publishing a book is a great moment. If you’re going to try to engage a publisher or agent, this is probably the point at which you send off emails and, hopefully, copies of manuscript files. The agent/publisher is your first customer. Yes, they may see ways in which the manuscript can be improved, or the story changed slightly based on their understanding of the market, but they will want a clean draft with zero errors, so they’re not being tripped up by typos and so on.
Of, if you are a self-publisher, like me, it’s the point at which you begin engaging with online publishers and real-life printers.
Well, that is my process for creating a manuscript and preparing it to be published. My time spent preparing the story before writing the manuscript pays off with fewer edits at this early stage, and a cleaner manuscript for the reader.
I hope you’ve enjoyed this insight into my writing process. I’d better get off and finish off my latest book!