# CS-32: Expense approval exceptions

Category: Work & enterprise tools
Level: Intermediate
Suggested duration: 3–4 weeks

Original UXCharan practice scenario. Validate assumptions; do not present it as a commissioned client project.

## Problem
A hypothetical expense tool rejects claims with a generic policy message. Explore how submitters and approvers can clarify missing evidence and explain exceptions without repeatedly recreating a claim.

## People to learn from
Employees submitting expenses and managers reviewing them

## Core scope
- Submit a claim
- request clarification
- revise and decide

## Research questions
- Which details cause back-and-forth?
- How are exceptions explained?

## Edge cases
- Missing receipt
- partial approval

## Specific artefact
A two-role review flow and audit history

## Evaluation question
Can each role understand what changed and why a decision was made?

## Work to share
Problem and role; anonymised evidence; alternatives and rationale; task flow; prototype; accessibility considerations; testing findings; revisions and honest limitations.

## Request feedback
Share a viewable Figma, document or portfolio link with Saicharan on WhatsApp: https://wa.me/917093809350
Include CS-32, your name, project stage and your main feedback question. Confirm review scope, timing and any fee directly.

## Methods
- Research planning: https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service
- Research consent: https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research
- Design exploration: https://www.designcouncil.org.uk/resources/the-double-diamond/
- Usability testing: https://www.nngroup.com/articles/usability-testing-101/
- Accessible forms: https://www.w3.org/WAI/tutorials/forms/
- Portfolio storytelling: https://www.nngroup.com/articles/ux-design-portfolios/