# CS-28: Public-service application progress

Category: Public & community services
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 service uses unclear status labels after submission. Explore how an applicant can understand whether action is needed, provide a missing document and see what happens next without inventing official eligibility rules.

## People to learn from
Adults completing a fictional municipal application

## Core scope
- Review status
- respond to a request
- track next steps

## Research questions
- What do current status terms imply to people?
- What causes repeat enquiries?

## Edge cases
- Document rejected
- conflicting update

## Specific artefact
A status vocabulary and evidence-resubmission flow

## Evaluation question
Can users distinguish waiting from an action they must take?

## 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-28, 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/