How to Manage Time in a Novel: Pacing, Time Jumps and a Calendar That Holds
Managing time in a novel is two jobs: knowing how long the story lasts, and deciding how to spend that span on the page. Slow down for the moments that matter with scenes, compress or skip the weeks in between, and tell readers how much time has passed after every jump. Behind the scenes, keep a calendar for yourself: who is where, how long the road takes, how old everyone is, what season it is. Readers never see that calendar, but they notice when you haven't kept one.
A novel runs on two clocks
Every novel keeps two clocks. One is story time: do the events take a day, a year, a century? The other is page time: how many pages do you give that span? Virginia Woolf's Mrs Dalloway fits inside a single day; Gabriel García Márquez's One Hundred Years of Solitude follows seven generations of the Buendía family. Both are novel length, because one unfolds minutes and the other folds up years.
Before you draft, decide how long the whole story lasts and write it down in a sentence: 'The story opens one autumn and ends in the spring two years later.' Every pacing decision you make sits inside that frame. Putting events in order is covered in our guide to building a timeline for your novel; this guide is about how time moves once that order exists.
Set the pace with scene, summary and skips
There are three basic ways to put time on the page. In a scene, time moves at roughly reading speed: dialogue, action, moment-by-moment detail. In summary, time is compressed: 'All winter she walked down to the harbor every morning' covers three months in a line. In a skip, time isn't narrated at all; one chapter ends and the next opens a year later.
Readers take the number of pages you spend on something as a measure of how much it matters. Ten pages for a ten-minute argument that changes a character, and a paragraph for two months in which nothing changes, is a natural ratio. When a chapter drags, the cause is often time that should have been summarized and was written as scenes; when a turning point feels rushed, it's the reverse.
Make every time jump visible
If readers miss a jump, they spend the next pages lost. In the first paragraph after one, give a concrete marker: a new season, a child who has grown, a shop that has closed, a plain 'Three winters later', or a chapter heading with a date. Whichever you pick, use the same method through the whole book so readers learn to spot it.
Once the jump is written, ask what must have changed in the meantime: ages, hair and scars, the height of the children, pregnancies, who holds power, who isn't speaking to whom, prices. If you skip five years and the side characters' lives are exactly where you left them, the world looks frozen. A short 'meanwhile' list for each long jump also hands you material for the chapters that follow.
Tie parallel storylines to the same clock
Follow two characters in different places and you're keeping two clocks, and they have to show the same day when the characters meet. If one has spent three weeks on the road while the other has lived through two days, the logic of the story gives way even if readers can't say why. In the appendices to The Lord of the Rings, J.R.R. Tolkien gives a dated chronology, 'The Tale of Years', where you can follow which day each of the separated characters was where.
The easiest way to tie storylines together is shared anchors: a storm both sides see, a full moon, a feast day, a piece of news that reaches everyone. Remember that news has a speed. In a world without telephones, word of a death spreads only as fast as a messenger can ride, and a character can't know what happened in the other storyline before that word arrives. If switching storylines takes you back in time, say so clearly.
Travel times: make the map and the calendar agree
Journeys are where timing mistakes hide most often. If the road takes ten days in chapter three and two in chapter twenty for no reason, attentive readers catch it. Decide once how long it takes to get between your important places and write it down: on foot, on horseback, by ship, and what changes in winter or when the pass is closed. You don't need exact miles, only numbers that agree with each other.
Travel time matters to more than the traveler. It decides whether an army arrives in time, when the answer to a letter can come, and how much of a head start a fugitive has. If you want tension out of a journey, fix the duration first and then race your character against it; stretch or shrink it to suit each scene and the race stops meaning anything.
Ages, seasons and the body's clock
When time passes, bodies and the natural world change first, and how fast they change is set by your world. Geography, climate, season and the body's healing have to agree with each other inside that world. If your story starts at harvest in a cold northern valley, four months later it should still be winter there; on a mild coast the same four months may bring nothing but rain. Which crop comes in during which month depends on the place and the crop, so decide once and stick to it. The same goes for bodies: how long a break takes to heal depends on the break and on the person's age, but if a character who breaks an arm is swinging a sword the following week, readers will want a reason. Seasons are the cheapest way to tell readers time has passed, and the place where an inconsistency shows most easily.
For ages, the safest method is to fix a character's birth date, not their age; their age at any point in the story follows from it. When the draft is done, check the gaps between siblings, how old each parent was when a child was born, and how old a character was during the old event they describe so vividly. Small details hang on the same calendar too: the day of the week, the phase of the moon, whether school is out.
When exact dates matter and when they don't
Some stories need a calendar kept day by day: historical novels that lean on real events, mysteries built on where each suspect was at a given hour, novels told in letters or diary entries, books that run many points of view at once, and series that return to the same past from book to book. In these, being off by a single day can become a contradiction.
In others, exact dates are dead weight. A story that follows one character over a short stretch, or one told in a fairy-tale voice, gets by on 'the next morning', 'that winter' and 'years later'; it's enough that the order and the gaps are clear. Either way, you don't owe readers the dates. The calendar is your working tool, and only as much of it as the scene needs goes into the text.
Where should you keep this calendar?
A notebook or a spreadsheet will do; what matters is that it lives in one place and is at hand while you write. In yazar.io that place is the Event Flow, free on every plan. Each event takes a free-text date note such as 'Day 3, evening' or a calendar date: a full day, a year and month, or a year alone, BC dates included. Link the characters who take part and the place where it happens, and the same event appears in order on that character's page and that location's page. Travel times can live in a custom field on your location records, such as 'Distance to the Capital'.
If you'd like to see dated events on a calendar or along a single axis, the Calendar and Timeline on Yazar Pro do that; in the Parallel view each character gets their own lane, so you can see whether two storylines land on the same day. The details are on the timeline software page, and age math is covered on the character age tracker page. You keep writing the novel itself in Word or Google Docs.
Do I have to give readers explicit dates?
No. In most novels readers only want the order of events and how much time lies between them; 'two weeks later' is often more useful than a date. Keep the dates in your own calendar and put only the necessary ones on the page. Historical novels and diary-style narratives are the exception, where a visible date helps.
How long can a time jump be?
There's no limit; it can be a night or twenty years. What matters is that nothing that changes the story is hidden inside the gap, and that the world looks older by that much on the other side. After a long jump, one or two concrete details in the first scene are enough to show what has changed.
How do I keep time in a world with its own calendar?
Decide first how many months and days a year has and which months each season falls in, and put that on a single page. Note events with your own month names, but know the number of days between them too. In yazar.io you can keep your own month names in the free-text date note; the calendar views work with the standard calendar and don't recognize invented months.
How do I check the timing once the draft is finished?
Read through and write the day of the story next to every scene. Then check three things: are characters who meet on the same day, does every journey take as long as you decided, and do the seasons and ages match the time that has passed. Most slips can be fixed by changing a sentence or adding a few days between two scenes.
Related Content
Start building your world on yazar.io
Bring your characters, locations, and every thread of your world together in one place; no credit card required.