A compliance training presentation should help people recognize a situation, choose the approved route and know where to ask for help. It is not a substitute for the policy or legal advice. Use an education presentation workflow to structure practice, then have the policy owner review every scenario and answer key before release.
Set the rule boundary
Name the policy, version, effective date and audience. State the behavior the session covers and the cases it does not cover. This prevents a training deck from turning a narrow internal rule into a universal claim.
Distinguish required action from recommended good practice. Use the exact approved wording for a must-do step, and plain language for the explanation around it. If the rule is being updated, mark the draft status and keep it out of a production session.
A narrow rule for the example
This exercise uses a fictional organization, Alder Services, and an invented Expense Claim Rule v1. It teaches employees how to handle missing evidence and possible duplicate reimbursement. The rule is teaching material, not tax advice, a Presenti policy or an instruction for your organization.
A claim requires an itemized receipt, a business purpose, a cost center and recorded manager approval. The same expense must not be reimbursed twice. If the employee cannot confirm whether it was already claimed, hold the new claim and ask the expenses team to check. If an itemized receipt is missing, use the approved missing-receipt route. Manager approval does not replace either evidence requirement.
The learning objective is: “Given an expense record, select the normal, missing-receipt or possible-duplicate route and explain the evidence needed.” The example deliberately sets no monetary threshold, tax treatment or retention period. Those details belong to the organization’s actual policy.
The CDC Quality Training Standards, developed for public-health training, offer a useful design principle: connect assessments directly to their learning objectives. Here, that means practicing expense decisions rather than memorizing the title of a policy.
Turn clauses into decisions
For each important clause, write one decision question: Is approval required? Can this file be shared? Which record must be kept? Then give the minimum facts needed to answer it. This produces a teachable scenario instead of a slide full of policy text.
Use one correct route and explain why the tempting alternative is wrong. When multiple interpretations are possible, show the escalation route. Do not invent a penalty or promise that a single quiz proves compliance.
Scenario: one receipt appears in two claims
Sam prepares a claim for a taxi trip to a client meeting. The itemized receipt, business purpose and manager approval are present. While checking the records, Sam finds the same receipt number attached to an earlier claim under a different project. That claim’s payment status is unclear, and the monthly submission deadline is approaching.
- Submit the new claim because the project code is different.
- Remove the receipt number from the new claim to avoid a duplicate warning.
- Hold the new claim and ask the expenses team to resolve the earlier claim’s status.
Answer: C. A different project code does not make the same taxi trip a second expense. Removing the receipt number conceals the mismatch instead of resolving it. The expenses team must establish whether the earlier claim was paid, rejected or withdrawn before Sam chooses the next route.
Ask participants which fact controls the decision. It is the matching receipt and unresolved earlier claim, not the deadline. Also ask what they still do not know: a possible duplicate is not proof of misconduct. The next action is to resolve the record, not accuse a colleague or guess that payment never happened.
Show evidence and escalation
Add the record that proves the action happened: an approval, an access log, a report or a completed checklist. Explain who owns the record and how long it is retained only when the policy confirms it. Otherwise label the point for confirmation.
Give participants a safe way to pause. A named owner, channel and expected response time make escalation practical. Avoid putting personal contacts in a public training copy; use the approved internal route instead.
A complete escalation record
| Field | Completed fictional example |
|---|---|
| Expense | Taxi trip for the client meeting; receipt T-204. |
| Records involved | New draft claim C-52 and earlier claim C-41 contain receipt T-204. |
| Known facts | The manager approved the business purpose; C-41 has a different project code. |
| Question to resolve | Was C-41 paid, rejected or withdrawn? Which claim, if any, should proceed? |
| Action already taken | C-52 is held; no second claim has been submitted. |
| Owner and response | The expenses team checks C-41 and records its decision against both claim references. |
This record separates what Sam knows from what the expenses team must establish. If C-41 was paid, do not submit the expense again. If it was rejected or withdrawn, follow the team’s documented route for the valid claim, with the references linked. If its status remains unclear, keep C-52 on hold.
Use the approved internal channel for receipt details, which may contain personal information. A public training deck needs only fictional IDs and facts; it does not need an employee’s actual travel history or payment information.
Build a fair knowledge check
Use short scenarios with one learning objective each. Explain the answer after the choice and point back to the source rule. A question should test the behavior the session teaches, not a trick in wording or a detail that never affects the decision.
Record completion separately from demonstrated understanding. If the organization requires a pass threshold, use the approved threshold and explain what happens after an incorrect answer. Do not present an illustrative score as a compliance certification.
Three questions that test different decisions
| Question | Expected action | Why |
|---|---|---|
| The receipt, purpose, cost center and approval are complete, and the expense has not been claimed before. | Submit through the normal route. | The facts meet the fictional rule; “always hold” misses the distinction. |
| The manager approved the trip, but the employee has only a card-payment total, not an itemized receipt. | Use the approved missing-receipt route. | Manager approval does not replace the required evidence. |
| A receipt matches a paid earlier claim, but the employee wants to charge a different project. | Do not submit another reimbursement; ask the expenses team about correcting the allocation. | Changing a project code does not create a second expense. |
Ask learners to name the condition and the next action. If someone chooses correctly for the wrong reason, give a variant: what if the matching earlier claim was withdrawn rather than paid? The answer now needs a record check and the documented resubmission route. It is not enough to memorize that every matching receipt must be rejected.
Do not set a universal pass mark from this exercise. If the organization requires one, its policy should also define remediation and completion records. A three-question result provides evidence about these decisions only, not proof of compliant behavior across someone’s work.
Plan refresh and review
Close with the source, owner, escalation path and review trigger. Policies change after incidents, regulations, product launches or process changes; tie the deck to those triggers instead of a vague annual promise.
Ask a reviewer who did not write the deck to run the scenarios. Capture ambiguous wording, missing evidence and any step that depends on a local process. Fix those points before publishing and record the next review date so the presentation does not outlive the rule.
Review the decision path, not only the wording
Before a real session, give the policy owner the rule excerpt, scenarios, answer reasons and escalation record together. Ask whether the evidence requirements and missing-receipt route match actual practice, whether the support channel exists and who can resolve a duplicate. A grammar check cannot resolve a mismatch between slides and the operating process.
If expense rules change, revise the affected scenarios and retire the superseded handout. Keep completion records separate from the latest teaching materials so they do not imply someone completed a version they never saw. The result should be a usable decision path: recognize the issue, preserve the relevant record and reach the person authorized to resolve it.
