First Shared, recurring with no due date "Bonus Point Chores"

[Ehill05]

It would be useful to have the option to have a type of First Shared chore that could be set to recur after certain intervals but doesn't have a due date. Right now, if you set up a "bigger" chore that either kid can complete it looks like it shows up in the Today section when the due date matches. "Bonus" chores that stay in the pending section and once completed only reappear in that section after the reset interval would be very handy.

Example:

Clean Fridge Doors, monthly
First kid to do it gets the points, doesn't show up for another month (the front of the fridge doesn't get that fast), but stays in pending until someone claims it again. It doesn't need a due date, but it also doesn't need to clog up the Due Today section.

[ccpk1]

If I’m understanding you correctly, one option could be removing the due date and recurrence set to none. Then make a small automation on, for instance, the 14th of every month setting the due date to the 15th. That will make the chore due showing in the correct sections. Upon completion and reset, the system will remove the due date automatically because there is no recurrence. The chore stays pending until next month when the due date is again set on the 14th.

Let me know if that’s on the right track or not.

[ccpk1]

Another alternative might be to to set it as a monthly chore and set the “Due Time” to something like 3 days, then set the chore to be locked until those 3 days before it is due. This would put the chore in waiting state most of the time which you could exclude from the dashboard views.

[muzikfreec]

Here's an idea for you. Most of this works today with stock settings, so posting the config in case it's useful, noting that it's not everything you asked for.

Setup:

• completion_criteria: shared_first — first kid to claim it gets the points
• recurring_frequency: none, due date left empty
• approval_reset_type: manual, auto-approve off
• A Home Assistant label on the chore (mine is currently Bonus Chore, but I'm planning to split it a few ways to better reflect the difficulty of the task).

With no due date, the chore sits permanently claimable and never appears in Due Today. Exactly the stays in pending until someone claims it behavior.

Keeping it out of the way (this is also #269 and #154): add pref_exclude_label_list: ['bonus chore'] to the main chore card, then add a second card with pref_include_label_list: ['bonus chore'] and pref_use_label_grouping: true. Labeled chores get routed to a label group before any time bucket, so they leave the LATER bucket entirely, and empty groups don't render. The bonus chores end up on their own card under their own heading.

Re-arming after completion: with manual reset it stays completed until you act. choreops.set_chore_due_date with just chore_name and no date resets every assignee to pending. One action, no global reset, points kept.

I plan to use this for bigger chores like Clean out the van, and place them into a separate card called Side Quests. Since there's no obvious set interval, manual reset makes sense. If we go camping and track a bunch of leaves and dirt into the car, we'll reset it to be claimable. If we're relatively clean for three months before we need another cleaning, no problem. The chore doesn't need to show at all until we reset it.

One gap: the recurs after an interval half isn't reachable without a due date. Reset types are tied to midnight or the due date, so you can get daily ('at_midnight_once`) or manual, but not reappears monthly, no due date. That's the piece still worth building, and it's the part your fridge-doors example actually needs.

Two caveats if anyone copies this: the card title and the label group icon are both hardcoded in the templates, so renaming the section or theming the icon means hand-editing the generated card, which the dashboard generator overwrites on regeneration.

Note that Claude Code helped me with some of these details, but I have built what is described here.