Document Creator Reward Rules Before You Automate
Before you automate creator rewards, write the rules down in plain language and test them against a real month. Automation should follow a documented rule set, not replace it.
Start with a written rule sheet
A rule sheet is a single document that states who qualifies, what counts, when it counts, and how it is calculated. Keep it short enough that a creator can read it in a few minutes. If a rule cannot be explained without a spreadsheet, it is not ready for automation.
Write each rule as a sentence with a clear subject. For example: A creator is eligible for the monthly reward if they were on the roster for the full period and met the activity threshold. Avoid vague words like active or good performance unless you define them.
Define eligibility and the reward period
Eligibility should answer three questions: who is included, when they must join, and what minimum activity is required. State whether new creators are prorated, excluded, or treated the same as everyone else. State whether leaving and rejoining resets anything.
The reward period must have a clear start and end, and a clear cutoff for data. For example, a monthly period might run from the first to the last day of the calendar month, with figures locked a few days later. Say what happens to late or corrected data.
Choose units and a simple formula
Pick the units that the platform already reports, such as hours, diamonds, or streaks. Do not mix units in one formula unless you explain the conversion. A hypothetical formula might be: base reward plus a percentage of a defined unit above a threshold. Use percentages only as examples, not as promises.
Keep the formula to a few steps. If it has more than three conditions, split it into a base rule and a bonus rule. Write the formula in words and in a simple table so both staff and creators can follow it.
Plan revisions and approvals
Rules will change. Decide who can propose a change, who approves it, and when it takes effect. A common approach is to publish changes before the next period starts and never apply them retroactively. Keep a version number and a short note explaining each change.
Approvals should be recorded, not just discussed in chat. A simple approval log with date, approver, and version is enough. This protects staff and creators when questions arise later.
Give creators an explainable view
Creators should see their own figures, the rule version that applies, and a step by step explanation of how their reward was calculated. They should not see other creators' data. If a creator cannot trace the number, the rule is not explainable.
A hypothetical example: a creator sees that they met the activity threshold for the month, that their unit total was above the base level, and that a bonus tier applied. The view shows the inputs and the formula, not just a final number.
Acceptance checklist and a pass or fail test
Before automating, check the written eligibility, period, units, formula and approval owner. Can a creator trace a sample result from its inputs? Is the applicable rule version recorded? Agree when future changes take effect, and distinguish your agency's own rules from verified platform requirements. Do not promise income from a hypothetical formula.
A concrete pass or fail test: take one real or realistic month of data and calculate the reward by hand using only the written rule sheet. Then calculate it again using the proposed automation logic. If the two results match for every creator in the test, the rule is ready to automate. If they differ, the rule sheet or the logic must be corrected before launch. This test does not guarantee any outcome; it only checks consistency.
A practical next step
Explore the related Devign work, then discuss your requirements before committing to a project scope.