Visa Application Document Checklist
Design a country-specific checklist that helps an applicant prepare, validate, and track documents without implying legal approval.
The brief
Understand the problem
Background
Visa requirements change by destination, applicant nationality, purpose, duration, and family situation. Generic checklists create false confidence, while official language can be difficult to interpret.
User context
Hana is applying for a six-month student visa and includes her child as a dependent. She needs translations for two civil documents and has an appointment in five weeks.
Product problem
Hana needs a checklist tied to her circumstances, with source dates, accepted formats, dependencies, and clear routes to official guidance.
Objective
Create eligibility context, personalized checklist, document review, and readiness states for application preparation.
What to design
Define the experience
Required experience
- Confirm route, nationality, purpose, duration, and dependents
- Review a sourced checklist grouped by preparation effort
- Upload a document and resolve a quality issue
- Assess readiness and export an appointment pack
Screens and states
- Application context
- Personalized checklist
- Document requirement detail
- Readiness review
Core user flow
Follow the critical path
- 01
Hana selects the student route and adds one dependent
- 02
The checklist identifies translation and consent requirements
- 03
Her child's birth certificate scan fails the full-page check
- 04
She replaces it and exports a dated pack with links to official requirements
Product rules
Requirements and constraints
Requirements
- Tie every requirement to applicant context and an official source
- Show publication or verification date for changing guidance
- Explain original, copy, translation, certification, and expiry rules
- Track documents separately for each applicant
- Make incomplete or uncertain readiness explicit
Constraints
- The product cannot determine legal eligibility or guarantee approval
- Official requirements take precedence over saved checklist data
- Identity documents need clear retention and deletion controls
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens covering a dependent document issue
- A checklist model with required, conditional, complete, rejected, and changed states
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
