All rules

A time out of order in a day's schedule

time-orderon by defaultJapanese / English

One time out of order in an itinerary or a day's programme

Example

Flagged
- 9:00 AM Tour of the plant - 12:00 PM Lunch - 11:00 AM Report meeting - 6:30 PM Dinner
What chaff prints
3:3 11:00 AM breaks the order of the times around it (after 12:00 PM)
Fixed
- 9:00 AM Tour of the plant - 12:00 PM Lunch - 2:00 PM Report meeting - 6:30 PM Dinner
What chaff prints
no finding

How to fix

Check the time. Correct it if it is a typo, or move the item if the order is wrong.

Why it matters

In a list or a table whose items start with a time, such as an itinerary or a programme, one time earlier than the item before it makes the reader check whether it is a typo or a swapped row, and someone turns up at the wrong time. A day's schedule runs from the earliest time, so a time against that order is pointed out. A day ends where a date heading or the date at the start of a row changes. A time past midnight, such as 0:15 after 23:30, is read as the next day's when it is marked so (+1, "next day"). Two times whose labels fix their order, such as doors open and the show's start, or meeting time and departure, are compared too, since doors that open after the start leave the audience outside when the show begins.

What it does not flag

A run of only two times, a list where no more than half of the times are in order (not a schedule), and times written inside a sentence rather than at the start of an item are not compared. A time more than half a day earlier than the one before it (0:15 after 23:30) is read as past midnight even without a mark. A "local time" mark, or a change of time zone, starts a new day. Two labelled times are not compared when they fall on different dates (a date heading between them), when their time-zone marks differ, when the later one is more than half a day back (past midnight), or when a line holds two times (a range). With two shows, each start is compared with the doors written nearest to it.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: time-order — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax time-order --why "reason"
Turn it off for the team (chaff.yaml)
rules: time-order: off
Technical details
Layer
L3
Status
stable
Severity
warning
Languages
Japanese and English
Suited to
business, technical, blog, legal, docs, academic, literature, speech
Reads from the document
dates

Levels

Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).

stricterror
normalwarning
relaxedinfo

This rule has no limit to count to. A level sets how a finding is marked: relaxed keeps the finding and marks it a step lower.

By genre

Runs by default in
technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes, legal/contract, legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, speech/address, speech/transcript
Turned off by the genre in
literature/fiction, literature/essay, literature/poetry, literature/play

Genres

Message

{time} breaks the order of the times around it (after {previous})

{time} breaks the order of the times after it (before {next})

{earlier_label} at {time} is later than {later_label} at {later}, which should come after it

This page is built from the rule's definition file:packages/chaff/rules/time-order.yaml