Learn · Module detail
setting thresholds
Set a threshold where the desired behaviour, member effort, reward cost, and operational control meet. Start from observed behaviour and make the qualifying rule easy to explain and audit.
## The mechanism
Define the qualifying event, value change, owner, correction path, and member explanation. Keep eligibility, liability, fulfilment, consent, and reversal as separate rules. The operating control must be testable from the ledger.
## Worked example
Illustrative arithmetic: a member needs 5 visits to qualify and has completed 3 visits, leaving 2 visits. If each visit earns 4 points, the current balance is 12 points.
## Do it
State the rule in one sentence. Map the event that starts it, the event that changes value, the exception path, and the review action. Test ordinary, cancelled, duplicated, and disputed cases before release.
## Common mistakes
- Measuring activity instead of the target behaviour. Name the counterfactual. - Treating face value as operator cost. Price fulfilment and correction. - Hiding exclusions or expiry. Put the boundary beside the decision. - Automating an undefined rule. Resolve ownership before implementation.