Due Badger DB/REG/01

Four warnings, then every morning.

Every obligation on your register is watched on the same schedule. You do not set it up, and there is nothing to configure.

Six months beforeFirst email
“No rush. Just putting it in your diary.”

Easy to file and forget, and he is fine with that for now.

One month beforeSecond email
“Right. Shall we get this booked in?”

He has noticed the first email did nothing. Still polite, now holding a clipboard.

One week beforeThird email
“I am going to keep mentioning it.”

The rule is reached and unsent, never is it today. If the job misses a night he still gets you the next morning.

The day beforeFourth email
“Tomorrow. It is tomorrow.”

The last polite rung. Four emails about one date, and it still has not been booked.

OverdueEvery morning after
“969 days. I email you at six every morning. This is my whole job now.”

There is no snooze button anywhere in Due Badger. A snooze is how a date slips in the first place.

What it does, exactly.

Checked
06:00 Europe/London, every day
Sent to
The reminder address on your account, which can differ from your sign in
Warnings
Six months, one month, one week and one day before the date
Once overdue
Every morning, until the date is closed
Missed a night
The rule is reached and unsent, so you get it the next morning instead
Snooze
There is none, deliberately
Turning it off
Close the obligation, or archive it. Both are recorded

A snooze is how a date slips in the first place, so there is no button for it. The two honest ways to stop an email are to do the thing or to say the obligation no longer applies, and both of those leave a record of who decided and when.

Moving a date is the third way, and it needs a written reason at the point of moving. The original date stays on the record either way.

Start your register.

It starts emailing you six months before your first date.