The direct answer
List every story event with the story day it happens on, and the check sorts the list into day order, measures each gap, and names each problem. Backward steps fail the check. Same-day piles and wide jumps warn. A short transition passage repairs a wide jump, and clock order inside the day repairs a pile. Rerun the list after each repair until every gap flag reads OK.
That is the whole method on this page. You supply dated points such as Arrival on day 1 and Trial on day 9. The tool returns a sorted event map, four summary numbers, a gap table with one flag per gap, and repair steps shaped by your genre. Nothing here judges prose quality. It only tests whether the stated days form one forward chain the reader can follow.
How the check reads your list
The input box takes one line of text: event names paired with whole story days, separated by commas. A valid item has three parts in this order: a name, a colon, and a day number. Arrival:1 is valid. Market fire:2 is valid. Arrest:3 is valid. Anything that lacks a colon, lacks a name, or lacks a numeric day gets skipped, and the Events metric tells you how many items were skipped so nothing vanishes silently.
Parsing follows four fixed rules. The line splits on commas, so keep commas out of event names. Each item splits on its last colon, and extra spaces are trimmed, so Arrival : 1 parses as Arrival:1. Day values round to whole numbers, so 2.6 becomes 3. Days start at day 1; any event dated day 0 or below counts as an ordering fault.
The genre menu changes only the repair advice. It never changes the sorting, the span, the threshold, or any flag. A 6-day gap is a jump in every genre. What differs is the kind of transition passage recommended: clue logs for mystery, travel passages for fantasy, and so on. Choose the closest match. General fiction gives neutral transition advice that fits any story.
Sorting, span, and the 30 percent limit
After parsing, the tool sorts all events by day from earliest to latest. Events sharing a day keep their entered order, which matters later when you sequence same-day piles. The sorted order is the true story order regardless of the order you typed. If the typed order runs backward anywhere, the verdict fails and instructs you to copy the sorted order back into your draft notes.
Span is the last day minus the first day. A story running from day 1 to day 14 has a span of 13 days. A single event has no span, and the tool says so instead of inventing one. Density is the event count divided by the span, stated as events per day. Six events over 13 days gives 0.46 events per day, which tells you at a glance whether the story packs scenes tightly or spreads them thin.
The jump limit is 30 percent of the span. This is a craft convention used by this tool, not a rule from any publisher or study. It scales with story length so short stories and long novels each get a fair limit. Any gap wider than the limit earns the Jump flag and needs a transition passage. Any gap at or below the limit passes with OK.
Worked numbers on the default list
The default input holds six events: Arrival on day 1, Market fire on day 2, Arrest on day 3, Trial on day 9, Escape on day 10, and Return on day 14. Follow the arithmetic once and every later result will make sense.
Sorted order matches entered order here: 1, 2, 3, 9, 10, 14. Span is 14 minus 1, which is 13 days. The jump limit is 13 times 0.3, which is 3.9 days. Consecutive gaps are 1, 1, 6, 1, and 4. Compare each gap against 3.9. The gap of 6 between Arrest and Trial exceeds the limit, so it flags as a jump. The gap of 4 between Escape and Return exceeds the limit, so it flags as a jump. The remaining gaps of 1 pass as OK. Density is 6 divided by 13, which is 0.46 events per day.
The final tally for the default list: 6 events, 13-day span, 0.46 events per day, 2 jumps, zero same-day clusters, zero skipped items. Because the order runs forward but two jumps need bridges, the verdict is a warning, not a failure. The repair is two transition passages: one covering the six days between Arrest and Trial, one covering the four days between Escape and Return.
The limit follows length: the same events across days 1 to 40 set a 39-day span with an 11.7 limit and no flags, while days 1 to 6 set a 5-day span with a 1.5 limit and flags nearly everywhere.
What each result panel tells you
The verdict panel gives the headline judgment plus a plain explanation of the trigger. Pass means forward order with no jumps, piles, or skipped items. Warning means forward order with repairs waiting. Fail means broken order: backward steps or days before day 1. Info means too little to judge: an empty list or one event.
The metrics panel shows four numbers: parsed event count, day span, events per day, and jump count. Hints beneath add the day range and skipped-entry count.
The event map draws one segment per event on its story day. Neutral opens the chain, good follows a normal gap, warn opens after a jump or shares a day, and bad marks a day below 1. Read left to right: warn segments are the repair list.
The gap table lists each consecutive pair with its measured gap and one flag. Same day needs clock order, Jump needs a transition passage, Conflict needs reordering or renumbering, OK needs nothing.
Recommendations convert flags into ordered repairs naming exact days, events, and the genre-specific bridge form.
Illustrative hypothetical example: the backward confession
Illustrative hypothetical example. Suppose a mystery writer enters four events: Arrival on day 1, Trial on day 9, Arrest on day 3, Escape on day 10. The typed sequence runs 1, 9, 3, 10. Between Trial and Arrest the days drop from 9 to 3, which is a backward step of 6 days. The verdict fails.
The sorted order tells the true story: Arrival day 1, Arrest day 3, Trial day 9, Escape day 10. Span is 9 days. The jump limit is 2.7 days. Sorted gaps are 2, 6, and 1. The 6-day gap between Arrest and Trial flags as a jump. Density is 4 divided by 9, which is 0.44 events per day.
Two repairs follow. First, move Arrest before Trial in the notes so the entered order matches the sorted order, and correct any scene placing the Trial first. Second, bridge the 6-day gap with a dated evidence log of the investigator's work, so the Trial arrives as the result of stated effort. Rerun as Arrival:1, Arrest:3, Trial:9, Escape:10: the fail clears, leaving one jump warning for the new passage to resolve.
The lesson generalizes. Whenever the verdict fails on order, trust the sorted map over the typed list. The typed list records what you assumed. The sorted map records what your own day numbers actually say. Rewriting the weaker one to match the stronger one is the entire repair.
Illustrative hypothetical example: the crowded festival day
Illustrative hypothetical example. Suppose a fantasy writer enters five events: Arrival on day 1, Market fire on day 2, Interrogation on day 2, Arrest on day 3, Coronation on day 12. The typed order runs forward, so no fail. Two warnings appear instead.
Sorted days are 1, 2, 2, 3, 12. Span is 11 days. The jump limit is 3.3 days. Gaps are 1, 0, 1, and 9. The zero gap between Market fire and Interrogation flags as a same-day pile on day 2. The 9-day gap between Arrest and Coronation flags as a jump. Density is 5 divided by 11, which is 0.45 events per day.
The day-2 pile needs clock order. Decide which scene happens first and state the time of day in each: Market fire in the morning with smoke still in the air, Interrogation at night with the smell lingering on clothes. Add one handoff line showing how the viewpoint character moves from the market to the interrogation room, and neither scene will feel as if it erased the other. The map marks the second day-2 segment as warn until this sequencing exists in the draft.
The 9-day gap needs a travel and council passage: the march to the capital, the counted nights on the road, the session setting the coronation date. One passage of a few hundred words with dated anchors closes it. After both repairs, rerunning the list returns a pass.
Building a bridge passage that holds
A bridge passage answers four questions in as few words as possible: who is moving through the gap, where they are, what changes during the missing days, and which dated anchor proves time passed. A dated anchor can be a counted night, a market day, a letter date, a healing wound, or any stated marker the reader can check. One anchor per passage is the minimum. Two anchors are stronger for gaps above six days.
Keep bridge length proportional to the gap. A 4-day gap usually needs 100 to 200 words: travel, waiting, one anchor. A 6 to 9-day gap usually needs 200 to 350 words across two or three beats. Beyond ten days, promote the bridge to a full scene with a small decision in it, since long summaries of important days can feel like skipped story.
Place the bridge at the start of the later scene, not the end of the earlier one. Open the Trial scene with two sentences of elapsed time and the evidence gathered since the Arrest, then proceed into the room. The gap closes before the new tension starts.
Three habits cause more trouble than they solve. A flashback replaying the missing days in full belongs as its own scene; compress it to its outcome plus one anchor. A montage naming many events without dates leaves the timeline vaguer; attach at least one stated day count. A bridge contradicting an established anchor, such as a wound healed in two days that earlier needed two weeks, trades one fault for another; reread the earlier anchor first.
Sequencing a same-day cluster
A same-day cluster means two or more events share one story day. The flag is not saying the day is overcrowded. It is saying the order within the day is unstated. Two scenes can share a day without any contradiction, provided the reader learns which comes first and what fills the hours between them.
Sequence a cluster in three moves. Assign each scene a time of day and name it through light, meals, bells, shifts, or stated hours. Write one handoff per boundary: a sentence showing the character traveling, waiting, or receiving the next scene. Check durations: two scenes cannot both fill the same afternoon, so trim or shift one of them.
Two scenes per day works in almost any genre, and three works when at least one is short. Four or more scenes on one day usually means the day wants to split: move the last scene to the next morning and rerun, since the tool recomputes every gap and shows any new jump at once.
Point-of-view rotation complicates clusters, because two viewpoints can each fill the same hours without either narrator noticing. When viewpoints share a day, give each scene one time marker the other scene can confirm: a bell heard in both, a meal eaten together, a message sent in one and received in the other. Shared markers let readers merge the two timelines instead of choosing between them.
Repairing an order conflict
An order conflict means your day numbers disagree with your scene sequence. Find it by reading the sorted map against your chapter order. The map shows where each event belongs by day. Your chapters show where you placed them. Every mismatch is one repair: either the day number is wrong or the chapter position is wrong.
Renumber when the content fits its neighbors but the stated day is off: a celebration referencing yesterday's arrest belongs the day after the arrest. Reorder when the day numbers form a sensible chain but a chapter sits in the wrong place: a trial dated day 9 should not appear chapters before the arrest dated day 3.
Repairs ripple: shifting the Trial from day 9 to day 6 can turn an OK gap into a jump or strand a bridge already written. Rerun after each single change during conflict repair, not after batches, so each ripple stays visible and small.
Keep a one-line change log during repairs: event name, old day, new day, reason. When a later chapter contradicts an earlier one about when the arrest happened, the log shows which decision was deliberate.
Edge cases and failure modes
An empty list returns an info verdict with formatting instructions. It does not guess. If several entries were skipped, the verdict names the count so you can compare it against what you typed. A skipped count that equals your full list means the format broke everywhere, usually because semicolons or line breaks replaced the commas.
A single event returns info because one point cannot contradict anything. Add the nearest scenes on either side; three dated events are the practical minimum for a useful check.
An all-same-day list has a span of zero, so every gap flags as same-day and the jump limit does not apply. That is correct for a single-day story: clock order is the only repair. If the verdict surprises you, check for mistyped days.
Days dated zero or negative fail the check, since story time starts at day 1. Shift the whole chain forward so the earliest event lands on day 1, preserving every gap, or renumber deliberately.
Decimal days round to whole numbers, so two decimals can land on the same day and create an unintended cluster. Enter whole days and keep dawn-or-dusk timing inside the prose.
Duplicate names stay separate: Escape:4 and Escape:10 are distinct events sharing a label. Rename repeats, such as First escape and Second escape, when the table grows hard to read.
Very long spans mute the jump flag by design: a 200-day saga sets a 60-day limit. Split sagas into acts and check each part separately; a 40-day leg gets a strict 12-day limit that catches the gaps readers feel.
Very dense lists invert the problem: thirty events in five days produce piles, not jumps. The repair is clock discipline, not bridges, and days carrying six full scenes may want merging even when the hours fit.
Commas inside names split items, since the comma is the separator: Farewell, my love:5 breaks, so write Farewell my love:5. A trailing comma is harmless. A missing colon, as in Arrival 1, skips that item and raises the skipped count.
Genre-specific guidance
General fiction uses the neutral bridge: state where each character spent the missing days and what changed. Name the place, the elapsed days, and one consequence. Readers test bridges against ordinary life, so keep travel times, work schedules, and healing periods plausible.
Mystery and thriller timelines must keep the investigation order provable: every deduction comes after its clues. Bridge gaps with dated evidence logs stating what was found, on which day, by whom. When a suspect acts during a gap, state the act and its day instead of revealing it later as surprise, since surprise alibis read as cheating when the days do not support them.
Fantasy and science fiction gaps usually involve distance, and distance plus speed equals elapsed days whether stated or not. Bridge with travel accounting: route, pace, nights, supplies. Magic or technology that shortens travel must be established before the gap it explains, not introduced inside the bridge. Rituals with preparation days and voyages with stated durations also anchor well.
Romance continuity lives in the relationship state between meetings: a gap with no contact changes it, and the next scene must show the result. Bridge with check-in contact or state the silence deliberately and show its effect. Never place an emotional turning point inside an unbridged gap; readers need to witness the shift on a stated day.
Historical stories answer to a real calendar. Anchor gaps to documented dates, feast days, tides, musters, or dated correspondence; one dated letter carrying sender, date, place, and a plot fact can bridge a whole gap. Check travel against the period's road, ship, and seasonal speeds before finalizing any gap above a week.
Questions writers ask next
Does scene order have to match day order in the final book. No, but every deviation should be deliberate and marked. A prologue from day 40 before a chapter 1 on day 1 reads as framing; an undated day-5 chapter between day-9 and day-12 chapters reads as a slip. Add orientation in the first lines of moved scenes, then verify here that the underlying day chain still runs forward.
Can two viewpoints share one day without sharing scenes. Yes. Date each viewpoint thread as its own list, check each separately, then merge and check the combination. Shared anchors, such as a storm, a bell, or a message crossing between threads, prove both occupy the same hours. Schedule at least one shared marker per shared day so untouched threads cannot drift apart.
How wide is too wide for a gap in practice. The tool flags anything over 30 percent of the span, but genre sets the felt limit: a 3-day gap during a chase feels enormous while a 30-day voyage passes quietly. Treat flags as the repair queue and tension as the priority order, bridging flagged gaps across active tension first. Location changes may still earn one orientation sentence, and montage gaps may need only a date line.
Must every scene carry a stated day. The input needs days, but the book need not print them. Many novels date a fraction of scenes and orient the rest through intervals like three days later or after the funeral. Know every scene's day privately and check it here; publish only the anchors readers need.
What about months, years, or named dates instead of day counts. Convert to day counts: opening day is day 1, three weeks later is day 22, two months later is near day 61. Keep the conversion table with your notes. For multi-year sagas, check each volume as its own chain rather than numbering thousands of days in one line.
How should flashbacks be entered. Enter each flashback at the day it happened in story time, not the chapter where it appears: a day-3 arrest replayed in chapter 11 still enters once as Arrest:3. When flashbacks dominate a section, verify their chain as its own dated list first, since nested timelines contradict most often at the joint where memory returns to the present.
Drafting the repaired passages
Draft each bridge passage and each re-sequenced cluster in Co-Writer at /write, where the reconstructed day order can sit beside the manuscript while the new lines are written. Paste the flagged gap pairs in first, draft one transition per pair with its dated anchor stated, then return here and rerun the check until every flag reads OK. That loop turns the timeline from a private worry into a verified chain.
Keeping the timeline true while the draft grows
New scenes stretch the span, and a stretched span resets every limit. A gap of 5 days inside a 13-day span flags at a 3.9 limit; the same 5-day gap inside a 30-day span passes under a 9-day limit. Neither verdict is wrong. Each describes the story at its current length. Recheck the full list after adding any scene that extends the first or last day, and after cutting any scene that shortens the span, since cuts tighten the limit and can flag gaps that previously passed.
Run the check at three points: when the outline first holds a full dated set, at the draft midpoint, and during the final continuity pass. Each run takes minutes and prevents week-long chapter moves. Between runs, record each new scene's day the moment it is drafted, while the date is certain.