All rules

A registration deadline after the event

deadline-after-eventon by defaultJapanese / English

A sign-up or RSVP deadline that falls after the event itself

Example

Flagged
# Invitation Date: Friday, November 20, 2026, 2:00 PM Please register by Friday, November 27, 2026.
What chaff prints
5:28 The registration deadline November 27, 2026 is after the event on November 20, 2026
Fixed
# Invitation Date: Friday, November 20, 2026, 2:00 PM Please register by Friday, November 13, 2026.
What chaff prints
no finding

How to fix

Check which is right, the event date or the deadline, and correct the other.

Why it matters

When the registration deadline or the RSVP date of an invitation is after the event itself, a reader who signs up in time arrives after it is over. It happens when last year's invitation is reused and only one of the dates is changed. The date on a line starting with an event-date word (Date, When) and holding a time of day is read as the event's date, and a date in a sentence with a registration word and a deadline word (register by, Booking deadline) after it is pointed out. In a trip notice, the first day on a Departure or Dates line is read as the departure even without a time, and a payment deadline after it (Payment due, a Due by column) is pointed out too.

What it does not flag

A Date line without a time of day, a date without its year, and a sentence with two dates are not compared. With several event-date lines, the latest event is used. Only a sentence with both a registration word (register, RSVP, booking) and a deadline word (by, deadline, closes) is read, so a survey deadline or the date the slides go up is not compared, and a sentence that also names a survey, a payment or the slides is left alone. A payment deadline is read only in a ticket order, whose title names a ticket and which never mentions an invoice, since an invoice is paid after the event. A trip's payment deadline is read only in a notice whose title names a trip (trip, camp) and which never mentions an invoice, and is compared with the departure; a billing period or a delivery date is never the event. It is off in the legal, docs, academic, literature and speech genres.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: deadline-after-event — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax deadline-after-event --why "reason"
Turn it off for the team (chaff.yaml)
rules: deadline-after-event: off
Technical details
Layer
L3
Status
stable
Severity
error
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).

normalerror
relaxedwarning

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
Turned off by the genre in
legal/contract, legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, literature/fiction, literature/essay, literature/poetry, literature/play, speech/address, speech/transcript

Genres

Message

The registration deadline {deadline} is after the event on {event}

The payment deadline {deadline} is after the event on {event}

This page is built from the rule's definition file:packages/chaff/rules/deadline-after-event.yaml