The short answer
Build the smallest fantasy calendar your scenes already need: a year count, the seasons or months that change what people can do, and any named day a chapter will mention. Store a plain number beside the words characters say, so you can sort dates and subtract them. Decide who may declare a new year or a festival, and recheck ages, travel and harvests on that one calendar whenever you move a scene. A timeline can store the labels you write. It will not count days, ages or leap days unless the tool is built to calculate your calendar.
A wedding cannot sit both before and after the grain tax. A traveler cannot cross a pass that the same week is still shut. A fantasy calendar your story can actually use is the smallest set of dates that keeps those facts from drifting. It is not a model of the sky.
The orchard town of Pell, the dates and the people below are invented. This is a planning method.
Start from the dates the draft already needs#
List the moments the current draft cannot drop. Pell’s story already implies four:
- The night the guild declares First Blossom, when the gates stay open late.
- A wedding three days after that declaration.
- A grain tax due before the wedding.
- Col, who left the hills while snow still held the pass, and who arrives the morning of the wedding.
You do not need month names to put these in order. You need to know which comes first. The guide to building a fictional timeline is where you track each event, its consequences and who knows about it. This article is the calendar those events share.
Relative labels are enough while the story is short: “blossom night”, “three days later”. The moment a chapter states an age, a journey or a festival by name, give the calendar a count.
Keep a number beside the name people say#
“First Blossom” is what a character says. “Year 40, day 88” is what you sort and subtract. Store both. A spoken name alone cannot tell you, after a revision, whether the tax still falls before the wedding.
| What a character says | What you store | What the number is for |
|---|---|---|
| First Blossom, year 40 | Year 40, day 88 | Sort it against the tax |
| Three days after the blossom | Year 40, day 91 | The wedding has a fixed gap |
| While snow still held the pass | Before day 80, same year | The journey has a latest start |
| The tax, before the wedding | Year 40, day 90 | One day of slack |
Give the year a public name only if people in the story use one. “The 40th year of the Orchard Compact” is a cultural fact. “Year 40” is your index. Dialogue can use the long form. The notes keep the index.
Add a leap day only when a scene crosses it#
If no chapter lands on a leap day, write “leap rule: not decided” and stop. A rule you have never applied cannot contradict itself.
If the story does cross one, write the rule in a single sentence and use it every time. An invented rule for Pell: a spare day is inserted after day 87 in every year divisible by 4. Year 40 is one of those years. First Blossom was day 88, so it becomes day 89, and a wedding three days later becomes day 92. Leave the wedding labeled day 91 and the gap is two days, not three. Updating those numbers is the whole job of the rule.
Decide which pieces the story actually spends#
A calendar has layers. Add the next layer only when a scene names it.
| A scene needs | Add this | Leave out for now |
|---|---|---|
| An age, a reign, a “last year” | A year count, and whose count it is | Month names |
| A harvest, a closed pass, a monsoon | Seasons, each with a length in days | Weeks and weekdays |
| “The third of Rainmonth” | Months, their lengths, and where the year starts | A second moon |
| “Market day” | A week length, and which day the market falls on | Holy days you never show |
| A night that depends on darkness or a tide | One moon, its period in days, and what people do about it | A full model of the sky |
Twelve renamed months from Earth are a costume. They help when you want readers to feel a familiar year, and they are honest only if you are actually using Earth’s year, including its length. If the pass, the harvest or the festival would not change after you deleted six of those months, you do not need them.
Let the culture and the faith decide what a date costs#
A month name does not make a culture. Someone declares First Blossom, and someone else loses sleep because the gates stay open. The guide to creating a fictional culture is where a shared pressure becomes everyday practice, with a cost and an exception. If the declaration is a duty, with a keeper and a disagreement about what the duty requires, design that with the guide to a fictional religion, rather than listing festivals here.
Three decisions are enough for Pell:
- The orchard guild declares First Blossom. A late declaration pushes the wedding and the tax into the same week.
- The town collects the grain tax on the day before any wedding held in blossom season. Families who marry then pay while they are also feeding guests.
- The hills count the year from the first snow, not from First Blossom. Col’s “this year” and the guild’s “this year” differ by a season.
That third count is worth keeping because a scene uses the difference. A second count that never changes a line of dialogue is a second place for an age to go wrong.
Check ages, travel and the harvest when a date moves#
Put every birth, wedding, tax and journey on the same count. When you move Nessa’s wedding from day 91 to day 70, walk these checks before you polish the prose.
- The blossom declaration is day 88. A wedding on day 70 now falls before it. Move the declaration, or give the early wedding a reason the guild will argue about.
- Col needed snow on the pass, stored as “before day 80”. Day 70 still allows that. Day 100 would not, unless the pass is closed for another reason you also write down.
- The tax was day 90, the day before a blossom wedding. It no longer sits the day before this wedding. Decide whether the rule follows the wedding or the season.
- Nessa was born on day 88 of year 21. On day 91 of year 40 she has turned 19. On day 70 she is still 18. Change the age in the dialogue, or move the birth.
Do the same for any scene that names weather, a crop or a festival. The timeline guide still covers what each person knows. The calendar adds the single count those facts have to share.
How much calendar each story needs#
| Story shape | Put on the calendar | Keep as a rough season |
|---|---|---|
| Short story | The days the scenes span | Years, moons, leap rules |
| Novel, one viewpoint | Ages, journeys, and the festivals that person attends | Calendars used in places they never visit |
| Novel, several viewpoints | One shared count, plus any date two viewpoints would name differently | A full conversion table |
| A series | The count an earlier book has already put on the page | Rules you have not stated |
Mistakes that break a calendar in revision#
- Pretty months with no length. Renaming a month does not tell you whether the pass is open. Give each season a length in days, or decide that you are using Earth’s year and keep Earth’s length.
- A festival that slides to fit the plot. If First Blossom can fall on any day you need, it cannot also be three days before the wedding. Write the gap as a rule, or stop mentioning it.
- Ages on a different year length. A year of 400 days and an age counted in 365-day years will drift. Use one length for births and for reigns.
- A second moon that never touches a scene. If nobody sails, plants or prays by it, cut it. You can add it when a chapter needs the dark.
- A speech that explains the calendar. A guild clerk can correct one wrong date. The clerk should not recite the leap rule. Show the tax arriving on the wrong morning instead.
Put the dates where the events already live#
The calendar is a set of labels and one rule for counting. The events stay on the timeline you already keep. A sheet with one column for the day number and one for the spoken date is enough to run the Pell checks: subtract the birth from the wedding and divide by the length of your year.
Yazar.io can store those labels next to the people they belong to. Its timeline, which the product page calls Event Flow, is a single list. Each event has a short title, a date label you type as ordinary text, and an optional note. The label does not have to be a real date. The page’s own example is “Year 3, Harvest Month”, so “Year 40, First Blossom” fits the same kind of field. Event Flow is not a calendar. It will not give you the weekday, Nessa’s age, or the number of days between the tax and the wedding. You still do that arithmetic. You drag an event when the order changes. You can attach the characters who take part and the location, and their pages then list those events in timeline order (timeline, updates). The timeline is unlimited on the free plan for ordinary individual writing. The pricing page says automated or unusually heavy use may be restricted (pricing).
Two counts at once, such as the guild year and the hill year, are not shown as separate tracks. The product page says the list is single. If you need both, mark which count a date uses in the event title.
When the plot needs ages and leap days calculated for you, that is a different tool. The timeline tools shortlist compares tools that do that arithmetic with tools that only keep the label you type. This guide does not rank them.
Sources
- Yazar.io: Timeline software · October 17, 2026
- Yazar.io: Product updates · October 17, 2026
- Yazar.io: Pricing · October 17, 2026
