# CS-34: Field-service offline handover

Category: Work & enterprise tools
Level: Advanced
Suggested duration: 4–6 weeks

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

## Problem
A fictional field-service tool loses clarity about whether a job update is saved locally or synced. Explore a handover flow where technicians can record work and resolve conflicts without assuming constant connectivity.

## People to learn from
Technicians completing work in areas with unreliable connectivity

## Core scope
- Record a job update
- work offline
- resolve sync conflict

## Research questions
- What must remain available offline?
- How do teams handle conflicting edits?

## Edge cases
- Duplicate update
- photo upload fails

## Specific artefact
An offline state model and conflict-resolution flow

## Evaluation question
Can technicians distinguish saved, queued and synced work?

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