Consequences, waivers, and resolution notes
How rule misses create consequences, who can resolve them, and when a reason is required.
Consequences let you attach a reusable or one-off follow-up action to a missed rule. They work for solo use and for shared partner dynamics.
Where consequences come from
- A rule can create no consequence, use a saved consequence template, or create a one-off consequence when missed.
- Saved templates are useful when the same missed-rule response happens repeatedly.
- One-off consequences are useful when a rule needs custom instructions that should not be reused elsewhere.
Who can resolve a consequence
- The assignee can mark a consequence complete.
- The assignee can also cancel it if the context changed.
- A partner in the same active dynamic can complete, waive, or cancel it.
When notes are optional vs required
- Complete allows an optional note when you just want to leave context in history.
- Waive requires a reason so it is clear why the consequence was excused.
- Cancel requires a reason so it is clear why the consequence was closed without completion.
Common consequence errors
- Only a partner can waive this consequence — assignees should use complete or cancel instead.
- Already resolved — refresh the page to see the latest history before trying another action.
- Not authorized — make sure you are in the correct active shared dynamic for that consequence.
If you want consequence setup to stay light, start with one saved template and attach it only to rules that genuinely need a follow-up action.
Related articles
Creating and managing rules
How to create, edit, archive, and organise your rules.
Logging your daily progress
How the Today view works, what each log status means, and how points or consequences are triggered.
Points, rewards, and reward approvals
How points are earned, how reward requests reserve points, and what each reward status means.