Tulips in July

The story I wrote takes place in “real time” by that I mean an imagined year of the current year. I was about halfway through when I realized to interact with the world around them I needed to know exactly what day of the year it is. It would be silly to have them looking at tulips in July. It became apparent that I needed to keep track of time as well as the characters.

So I printed out a generic calendar from about ten years from now. It isn’t important that I say it’s April 17th, but it is important to stay on track.

As I went back to the beginning, I wrote down any significant plot events on the calendar. As I moved forward I discovered that by the end of the book, the story was off by two weeks. At the beginning I eluded how long they would be working for. Instead of changing the conversation that outlined the length of the summer job, I wrote the difference in. It gave me the opportunity to add a little more dynamic to the mystery that I hadn’t thought about before. Fifty  days in, someone in charge slips up and gives the protagonist has a very large clue. This is an important event. That clue leads her quickly to solve the grand mystery just in time. I actually planned it to be that day so if I refer back it’s an easy number to remember.

Having a timeline or calendar of events made things much easier. I can refer back to it or even have the characters refer back. At one point, the number of days is actually mentioned. If a reader were to follow along that carefully, they would find it accurate. Even though it is a fantasy, some reality is required.

My advice about time lines.
Use them even if it’s not important it’s a fantastic way to keep track of events or interactions that drive the story. Did Joe make the ominous phone call before or after he got the internship? If I need to check I can refer to a calendar and not have to flip back chapters to find it if I forget.

-Sheryl

Here is a link to a previous post. The first Fifty  pages. Why are they so important?

The first 50 pages.

Copyright © 2016 All rights reserved