Advanced: Badges Periodic

This guide details the Periodic Badge engine (Daily, Weekly, Periodic). In kid-facing dashboard language, this same family may be shown as Quest Badges or Quests. Unlike Ranks, these are parallel missions used to enforce habits ("Clean Room").

The Core Concept: The Scope

While Ranks look at all points, Missions can be surgical. You define exactly what counts using Target Types and Tracked Chores.

1. Advanced Scope & Filtering

By default, a badge tracks "All Chores." You can narrow this focus to create "Specialist" badges.

• Scenario: "The Dishwasher King."
• Configuration:
  • Target: 10 Count.
  • Frequency: Weekly.
  • Tracked Chores: Select only "Load Dishwasher" and "Unload Dishwasher."
• Result: The assignee can clean their room 50 times, but the badge progress will sit at 0%. Only dishwasher activities move the needle.

2. Strict Mode (No Overdue)

If you select a Target Type ending in (No Overdue), the logic changes from "Accumulation" to "Survival."

• The Logic: The system checks the last_overdue timestamp of every Tracked Chore.
• The Fail State: If any tracked chore goes overdue even once during the badge cycle, the badge status calculates as 0%.
• Recovery: The badge cannot be earned until the cycle resets (e.g., next Monday).
• Use Case: "Perfect Week." Use this to reward punctuality rather than just completion.

3. The Contract (Auto-Penalties)

Periodic Badges are the only place where Penalties are automated based on time.

• The Logic: If Date > End_Date AND Progress < 100% -> Apply Penalty.
• The Setup:
  1. Create a Penalty Entity (e.g., "Missed Quota: -50 Points").
  2. Create a Weekly Badge (e.g., "Clean Room").
  3. Set Awards -> Penalty -> "Missed Quota".
• The Outcome: This creates a binding contract. If the assignee fails to clean their room by Sunday night, the system automatically deducts 50 points on Monday morning.

4. Logic Trap: Single-Claimer chores

Be careful when combining single-claimer chore criteria with Periodic Badges.

Single-claimer criteria:

• Shared First (shared_first)
• Rotation Simple (rotation_simple)
• Rotation Smart (rotation_smart)

Why this can fail:

• Badge Requirement: "Complete 100% of Assigned Chores."
• Chore: "Feed Dog" assigned to Assignee A and Assignee B.
• If A is the winner/turn-holder, B may still have the chore in scope but no completion credit.
• Result: B can fail completionist badge targets even when chores were done in the household.

Practical guidance:

• For single-claimer chores, prefer points/count targets over strict completionist targets.
• Use Tracked Chores to scope badges to chores each profile can realistically complete in-cycle.
• If you keep completionist targets, treat the badge as intentionally competitive.

Quick compatibility guide:

• shared_all: usually safe for completionist targets
• shared_first: high trap risk
• rotation_simple / rotation_smart: high trap risk unless turn cadence fits the badge window

5. Special occasions

Special Occasion badges are simply Periodic badges with a duration of exactly 24 hours.

• Hidden Default: The target defaults to 1 Chore Count.
• Behavior: The badge is "In Effect" only on that specific date. The moment the assignee completes any single chore on that day, the badge is awarded (along with any Birthday/Holiday loot).

---

Related docs

• Configuration: Periodic Badges (Quest badges)
• Configuration: Badges overview
• Technical: Badges

---

Last Updated: March 2026 (dashboard terminology bridge for Quest badge wording)