top of page
Randy

Keep a Change Log

Updated: Jun 1, 2020


Do you know which way you're going?

You’ve likely used the Track Changes function of your preferred word processing software at some point in your writing. This allows you to keep track of edits large and small and to revert them if you change your mind later on. It’s also helpful for collaboration with an editor or coauthor.

But beyond editing grammar, punctuation and style, if you’re writing a longer piece of fiction, it can get confusing to keep track of all your characters and storylines, especially if you decide to make a change partway through your draft. One of the first stories I ever read as a freelance editor was a time-travel story. You better believe the author kept meticulous notes of the various timelines going on—to do otherwise would be to risk the whole thing becoming an unfollowable mess.

When I’m working on longer projects, I’ve found it helpful to use a tool I’ve picked up from my day job: a change log.

The premise is simple and the effect can save a lot of headaches for both you as a writer and for your editor and/or reader once your manuscript is complete.

Creating a Change Log

There’s no specific format you need to use, but a few options are:


  • A physical, paper notebook with changes listed in order and any other detail you choose to include.

  • A Word or other digital document used the same way as the physical version. This can even be included as part of your manuscript document.

  • An Excel or Google Sheets or other digital spreadsheet, which provides a bit more versatility in use and is my preferred format.


Using Your Change Log


  • Decide what details your log should include

  • Any time you make a change to a character (name, description, background, personality, etc.) or story (location, theme, order of events, characters present for events, etc.), note it in the log.

  • When writing and rewriting, refer back to your log often.

  • Use the Find function to replace updated character or place names throughout your manuscript to keep things consistent.


Example of Change Log

My own change log spreadsheet generally includes two tabs, one for the “current” characters/story and the other for the past changes made.

The columns for the changes tab tend to be:


  • Change made

  • Date of change

  • Reason for change

  • Effects of change


So my change log for Phoenix looks something like this:

I always include the reason for the change because if I’m thinking of changing it again down the road, I want to be able to remember why I made the initial change. I’ve “talked” myself out of several changes by including that column with my original thought process.

Comments


The

Chimera

Blog

bottom of page