Learn · Module detail
spreadsheet to platform
Move from a spreadsheet to a platform when manual reconciliation, identity matching, or reward fulfilment creates a control problem. Preserve the rules and audit trail before migrating the data.
## 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 sheet records 90 earn events and 30 redemption events, with 12 corrections. A migration must preserve all 132 ledger events, including the correction trail.
## 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.