Skip to content

Insights

Jump to bottom
tempus2016 edited this page Jul 22, 2026 · 3 revisions

TaskMate panel → Insights. Four reports that answer the questions the raw numbers don't.

Report Question it answers
Fairness Am I dumping everything on the eldest?
Friction Which chores are quietly never getting done?
Week ahead What points are actually available in the next seven days?
Health Is anything misconfigured?

All four are computed on demand and never cached. A stale report is worse than a slow one.

Fairness — who is actually doing the work

For a chosen window (7, 14 or 30 days) it shows each child's completed chores, points earned, share of the family total, and how many distinct days they were active — with a marker showing where an even split would sit.

Judged on chore count, not points. A pricier chore shouldn't be able to hide an uneven split. Points are shown alongside because the two can genuinely disagree: three quick jobs versus one hard one is balanced by points and lopsided by count, and only you can say which you meant.

A child is flagged as doing more or doing less when they are more than 15 percentage points off an even share — wide enough that normal week-to-week variation doesn't nag, narrow enough to catch a real imbalance.

Only approved, non-bonus completions count. Unapproved work isn't yet work you've agreed happened, and bonus sub-tasks hang off a chore that is already counted.

Friction — what isn't working

The second view judges each chore rather than each child: how often it actually gets done versus how often it came up, over 14, 30 or 90 days.

Verdict Meaning Suggestion
Never done No completion on record, ever Retire it
Stalling Done under 20% of the time it came up Retire if long dead, otherwise raise the points or reassign
Patchy Done 20–60% of the time Raise the points
Fine Done 60%+ of the time Leave it alone

Chores with outstanding mandatory misses show a ⚠ count. The report leads with a suggestion rather than just a diagnosis — a stalling chore that already pays well doesn't need more points, it needs a different child.

What it can't tell you. TaskMate deletes a completion when you reject it, and removes a mandatory miss once you resolve it, so neither rejection counts nor historical miss counts exist to be reported. The report says so rather than quietly omitting them. Expected counts are approximate — they don't replay rotation, dependencies, weather or vacations.

Week ahead — what's coming up

The third view projects the next 7, 14 or 28 days from each chore's schedule: how many chores and points are heading each child's way, what balance they'd reach, and a day-by-day grid.

Rotation is projected using the same daily-assignment computation the integration itself uses, so alternating, random and balanced picks match what will really happen rather than an independent guess that could drift.

It's a ceiling, not a forecast. A chore open to everyone is counted for each eligible child, because the schedule cannot know who will get there first. Weather, dependencies and availability aren't projected either — they depend on the day. Points that aren't assigned to anyone are called out separately.

Health — is anything broken?

The fourth view checks the setup itself and reports storage size and entity counts.

Check Severity
A chore depends on a chore that no longer exists, so it can never unlock Error
A chore or reward is assigned to a deleted child Warning
A chore references a visibility or weather entity that doesn't exist Warning
A reward unlocks an entity no longer on the allowlist, so nothing will happen Warning
A child has no chores; completion records for deleted chores; a very large history Note

Every issue carries a plain sentence and a Show me button that jumps to where it lives — a diagnostic that only says "3 problems" isn't one you can act on.

Notes alone still count as healthy.

Related

Clone this wiki locally