Kleara

Kleara · Library

Check reminders that start at month end

A monthly task that starts on the 31st moves to the last valid day of shorter months and then stays there. See the January-to-June example and how Kleara handles it.

What clamping does to a monthly date

Monthly tasks in Kleara step by calendar month, not by 30 days. When the next month has no matching day, the date is clamped to that month's last day. A task due on 31 January therefore comes back on 28 February in a common year, because February has no 31st.

The clamp is not undone later. The next step starts from the clamped date, so the task continues on the 28th: 28 March, 28 April, 28 May and 28 June. The model does not remember that the task originally started on the 31st.

Reading the example table

The example starts on 31 January 2026 and follows the monthly steps until June. The gaps between dates are 28, 28, 31, 30 and 31 days. The first gap is short because of the clamp to February; after that the gaps simply follow the lengths of the months, while the day number stays on the 28th.

In a leap year the same start would land on 29 February instead, and then continue on the 29th. The pattern is the same: once a date has been shortened, it stays shortened.

How this plays out in the app

When to change the setup

If a job really belongs to the last day of the month, such as a check you do when the month closes, the plan cannot express that rule. Move it by hand when it comes up, or pick a day that every month has, such as the 1st or the 28th.

Weekly and every-three-days tasks are not affected. They add a fixed number of days and never need clamping.

Tools