Reminders for the things you check on a rhythm

There is a category of small recurring obligation that no tool handles well, and everyone handles by remembering. It goes like this:

Check whether the invoice was paid
Look at the analytics on the first of the month
Rotate the API key every ninety days
Renew the domain before it auto-charges
Check the status page after the maintenance window
Do the timesheet on the last working day
Look at the shared doc again after the review deadline

Each is two minutes of work. Each happens in a browser, on a specific page. And each one is a small ongoing tax on your memory, which is exactly the thing you are worst at.

Why calendars are the wrong shape for these

You can put them in a calendar and people do. Three problems show up within a month.

Your calendar becomes noise. Fifteen recurring two-minute chores sitting alongside actual meetings devalues everything in the view. Then you start ignoring calendar alerts generally, which costs you the meeting you were actually meant to attend.

No page comes with it. “Rotate the API key” arrives at 9am and you go and find the console, log in, navigate to the right project. The two-minute task is now six minutes, four of which are navigation.

Recurring rules in calendars are weak where these need them to be strong. The last working day of the month — which is what invoicing and timesheets actually run on — is not a thing most calendars can express. You end up with the 30th, which is wrong in February and wrong whenever the 30th is a Sunday.

What these actually need

A repeat rule that matches the real cadence, attached to the page where the work happens.

That is the whole requirement, and it is unglamorous, which is probably why it is underserved. In Latr it looks like: open the page, save a reminder, set a repeat. When it fires, clicking the notification puts you on the page. Two minutes later you are done and it comes back next month on its own.

The repeat rules cover the ones these tasks actually use:

Every weekday — the daily check that should not nag you on Saturday
The same weekday each month — “the third Thursday”, how recurring meetings are really described
The last working day of the month — invoicing, timesheets, month-end. It steps back off a weekend on its own
Every 90 days — key rotation, quarterly reviews, the filter in the extractor fan
Every N days — anything with an interval rather than a calendar shape

The repeat does not drift, which matters more than it sounds

A detail that sounds pedantic until it has bitten you: when a repeating reminder fires late — because the browser was closed — the next occurrence is worked out from the original schedule, not from when the delivery actually happened.

Without that, a daily 9am reminder you keep opening at 11 slides to 11, then to noon, then to some hour that has nothing to do with what you set. Over a month of a slightly irregular schedule it wanders somewhere useless.

Same for quiet hours. A 2am reminder held until 7am is delivered at 7am and is still a 2am reminder tomorrow. The hold moves one delivery, never the series.

A worked example: the invoice chase

The one I actually run:

On the invoicing page, save a reminder set to the last working day of the month.
Tag it money, so the whole set is one click in the queue.
When it fires, click through — I am on the invoicing page, not looking for it.
Send the invoice.
Mark it done, which is not the same as deleting: the record stays in history, and a follow-up fires a fortnight later asking whether it was paid.

That last step is the part I would not have thought to build if I had not needed it. “Did they pay?” has no natural moment to be written down — you would have to remember, two weeks after the thing you were already trying not to have to remember. So it is declared on the first reminder and created when you finish it.

Setting up a batch

If you have a dozen of these, do them in one sitting. It takes about ten minutes and it is the highest-return ten minutes I have spent on any of this.

Open each page, save the reminder, set the repeat. One at a time, no planning phase.
Give the lot a shared tag so you can see the whole rhythm in one filtered view.
For the ones with money attached — renewals, anything that auto-charges — also send them to your calendar, so a shut laptop cannot cost you.
Set an early warning on the ones that need preparation rather than just attention.

Then leave it alone. The point of this category is that it should stop being something you think about, and the measure of success is that in six months you cannot remember what is in it.

The one that surprised me

Status pages after a maintenance window. Every provider tells you maintenance completes at 04:00 UTC, and every one of them occasionally does not complete. A reminder for 09:00 the next morning, on the status page, has caught two things I would otherwise have found out about from a customer.

It costs nothing to set and it is the sort of thing nobody puts in a calendar because it feels too small. Small and recurring is exactly the shape this handles.