Address an Expense-Policy Violation

This template covers a private manager-to-employee conversation after finance flags an expense report for review. The learner practices naming the specific concern, avoiding accusation, and keeping the discussion focused on facts, policy, and next steps. It is built around a repeat issue, so it also tests how the learner responds when the employee minimizes the problem.

Use it when an expense claim includes personal charges, unclear business purpose, duplicate submissions, or another suspected policy violation that needs a direct conversation. It fits situations where you already have enough information to discuss the issue, but you still need the employee's explanation and a correction plan. It is not for a formal investigation or disciplinary hearing.

This scenario is best run by managers, team leads, finance partners, or HR partners who may need to address reimbursement issues. It is especially useful for people who approve expenses or coach others on policy compliance. The learner should practice as the person delivering the conversation, not as the employee.

Use it during onboarding for new managers, before expense policy rollouts, or as a refresher when reimbursement errors start to repeat. It also works well as a short recurring practice scenario for leaders who want to improve consistency in difficult conversations. Because the persona is defensive but not hostile, it can be replayed to practice different tones and openings.

Yes. It supports compliance training by reinforcing respectful escalation, documentation, and policy-based correction rather than vague criticism. The conversation should stay aligned to company expense rules and any internal review process, and it should avoid making claims beyond the facts in the report. Because it is a workplace compliance scenario, it should be used as training, not as a substitute for legal or HR advice.

Learners often start with blame instead of facts, soften the message so much that the issue becomes unclear, or jump straight to punishment before hearing the employee out. Another common mistake is failing to reference the policy expectation, which makes the conversation feel personal rather than procedural. The scenario also reveals whether the learner can set a concrete correction step instead of ending with a vague warning.

Yes. You can adjust the expense type, the size of the personal charges, the employee's temperament, and the level of repeat behavior to match your workplace. You can also swap in your own policy language, approval workflow, or reimbursement correction process. Keep the situation specific so the roleplay still feels realistic and scorable.

It fits naturally alongside feedback conversations, policy enforcement, and documentation practice. Many teams pair it with other roleplays about code of conduct, attendance, or performance expectations so managers can practice consistent accountability language. It also works well as a follow-up to policy-reading modules because it tests whether the learner can apply the rule in a real conversation.