Preparing exports for a referral assessment

Assessments stall when exports use different date ranges or rename the same event three ways. Before a kickoff, decide one timezone (Asia/Bangkok is our default), one window, and a glossary for invite sent, invite accepted, reward pending, and reward paid.

Useful packages usually include: a referral event log with anonymized user IDs, a reward ledger, a simple description of current rules, and a note on which channels carry most invites. Screenshots of the in-app invite screen help us see friction that spreadsheets hide.

You do not need a perfect warehouse. Spreadsheets are fine if columns are consistent. What we cannot use are screenshots of dashboards without the underlying rows — they look polished and answer almost nothing.

Assign one internal contact who can clarify rule changes during the review window. Programs that “quietly” altered reward amounts mid-month need that context or findings will blame the wrong stage.

Back to field notes · Ask about an assessment