Design / 01
Choose a manufacturing or service pilot
Program context. Add your business model, participant group and the behavior you want to change.
Start with one cycle and one clear goal.
- Open the Excel workbook and save a working copy. Review the fictional examples before clearing them.
- Fill the amber inputs in Setup. Agree the earning rules, then replace the sample Team, Events and Payments inputs. Formula cells are pale green.
- Use the rule-design and test prompts before announcing the program. The included rates are fictional starting examples, not compensation benchmarks.
- Review the Earnings exceptions and payment records. Approvals and payments are human steps recorded in the workbook.
- Copy the value of Setup B29 into the context field below. Open a prompt, add its inputs, and copy the full prompt to your AI assistant.
Your program context
Program policy means your rules for who earns a reward, what qualifies, how it is calculated and when it is paid. A plain-language draft is enough to start.
Paste the generated context from Setup B29, or replace the placeholders below. Add an appeal contact if you want participant communications.
This local file has no network calls or tracking. Inputs stay in the open page and are not saved after closing it. Only copy anonymized data to your chosen AI tool.
Choose the job you need to do.
Each prompt includes the shared context, your extra inputs, the requested output and checks for missing information. AI output is a draft to review against your policy and source records.
Design / 02
Turn your reward policy into rules
Program context and draft or approved reward terms. A plain-language description is sufficient.
Customize and copy this prompt
Design / 03
Check reward cost and margin exposure
Program context, candidate Rules and representative product invoice or accepted-work rows.
Customize and copy this prompt
Prepare / 04
Map ERP and field-service exports
Program context, export headers and anonymized invoice, credit, participant and job examples.
Customize and copy this prompt
Prepare / 05
Test returns, units and earning gates
Program context, fully specified Rules and sample Events.
Customize and copy this prompt
Launch / 06
Write participant terms and launch messages
Program context, approved rules, exclusions, payment timing and appeal contact.
Customize and copy this prompt
Operate / 07
Review the weekly reward batch
Program context and Rules, Team, Events, Earnings and Payments exports with headers.
Customize and copy this prompt
Operate / 08
Explain a participant's earnings
Program context and Rules, Events, Earnings and Payments for one participant.
Customize and copy this prompt
Operate / 09
Handle a return, cancellation or appeal
Program context, disputed event, original source evidence, rule version and payment history.
Customize and copy this prompt
Improve / 10
Review the pilot and commercial results
Program context, results and a comparable baseline with definitions and dates.
Customize and copy this prompt
Improve / 11
Reward verified product and service skills
Program context, learning milestones, verification sources and a budget.
Customize and copy this prompt
Improve / 12
Plan the move beyond spreadsheets
Program context, volumes, manual effort, exception counts and integration needs.
Customize and copy this prompt
What the workbook calculates
| Reward basis | Calculation | Use |
|---|---|---|
| Gross profit | (Invoiced revenue - returns/credits) x net-sale gross margin x rate | Focus products, accepted maintenance or projects |
| Net sales | (Invoiced revenue - returns/credits) x rate | Product sales or invoiced service renewals |
| Units | Net eligible units after returns x currency per unit | A defined item promotion in one unit of measure |
| Fixed | Flat award | Verified training or recognition |
For manufacturing, start with an eligible invoiced product line after returns. For industrial services, start with accepted and billed work or a renewal invoice. Booking a whole contract does not automatically earn on its unbilled future value.
A per-event cap applies after calculation. Zero cap means uncapped. Date, eligibility, category, event type, margin, minimum net-sales, unit-of-measure and collection gates must pass. Fixed awards still require evidence and approval.
Use one currency and one cycle per copy. Capacity is 100 events, 100 payment records, 20 rules and 30 participants. Choose one rule for each event. The workbook does not automatically detect the same deal under different Event IDs, enforce approval authority, freeze rule history, enforce the total budget, or send payments.
Tier accelerators, pooled rewards, points, automated split attribution, negative earnings and clawbacks need an additional operating design. For a split, agree credit first and use separate unique events with the split amounts. Resolve reversals with finance and preserve the original cycle.
Category lists can be adapted, but keep rule and event labels identical. Unit rules must use a matching unit of measure. A decimal rate of 0.05 means 5%; a unit rate of 2 means 2 currency units per eligible unit. The minimum net-sales gate is inclusive and the rate applies to the whole qualifying event basis. To use a new cycle, update Setup and the rule dates, assign new rule versions and clear the previous cycle's event and payment inputs. Recalculate in Excel and test your own examples before launch.
When the program needs a stronger foundation
If manual rule changes, return adjustments, disputes or payment reconciliation are slowing your team down, use prompt 12 to describe the actual workload and requirements.
Bring your program to Sepals with one audience, one sales behavior and one commercial measure.