Kleara

Kleara · Library

Change one recurrence without changing every matching label

Changing the kitchen floor from weekly to monthly leaves the bathroom floor untouched. See the before-and-after example and how the app and web planner differ.

Every task line has its own identity

Kleara stores each task as a separate line tied to one room. The kitchen and the bathroom both have a task called mop the floor, but they are two lines with their own frequency and date. Changing one does not change the other, even though the names are identical.

The web planner shows the same idea in its identifiers: the kitchen floor is kitchen.taskMop.1 and the bathroom floor is bathroom.taskMop.4, and a frequency override is stored for one identifier only.

The example before and after

The page compares two runs that contain only these two floor lines. In the first run both are weekly: the kitchen floor starts on 26 October 2026 and the bathroom floor on 31 October, four times each, eight occurrences in 28 days.

In the second run the kitchen floor is set to monthly. It then appears once, on 31 October, and the bathroom floor stays weekly but starts on 30 October. The total drops to five occurrences. The bathroom start date moved because the web planner rebalances the whole draft each time you calculate; its frequency did not change.

Change one frequency in the app

Pitfalls when changing a frequency

Expecting the app to rebalance after a change. Unlike the web planner, the app does not redistribute other tasks when you change one frequency; it simply changes that line.

Changing the wrong line. The task names are shared across rooms, so check the room heading in the Plan tab before you change anything.

Comparing the two web runs date by date. Because the planner recalculates start offsets, a few dates move even for tasks you did not touch; compare frequencies and counts instead.

Tools