# CS-26: Neighbourhood issue reporting

Category: Public & community services
Level: Beginner
Suggested duration: 2–3 weeks

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

## Problem
A fictional local service collects reports but gives little indication of ownership or progress. Explore a flow that helps residents submit useful information, spot duplicates and understand updates without exposing their exact home address.

## People to learn from
Residents reporting a non-emergency street issue

## Core scope
- Report an issue
- check duplicates
- follow progress

## Research questions
- What makes reporting worth the effort?
- Which updates are meaningful?

## Edge cases
- Duplicate report
- wrong service area

## Specific artefact
A report lifecycle and public/private information split

## Evaluation question
Can people submit a useful report and understand who is handling it?

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