Checklist: things to think about
Design prompts for file upload components
This checklist is here to help. It isn’t a rulebook, it’s a set of prompts to help you think through the design, spot potential issues, and shape a smoother experience for users.
If you can’t tick everything off, that’s OK. Not every point will be relevant, but it might spark areas to explore further. And if you’ve solved something differently, please share it.
Design prompts for file uploads
Setting clear expectations
Users feel more confident when they know what's expected of them before they start. If file rules are hidden or unclear, uploads can fail and trust in the service can drop.
- Do users know, before they start, what file types, sizes, and number of files they can upload?
- Is this information always visible, not hidden in tooltips or expandable sections?
- If there are file naming rules, are they genuinely needed and explained in plain language?
- Are restrictions shown before a user chooses a file?
- Do users understand what happens after they upload, when files are submitted, and who will see them?
Starting the upload journey
Users don’t always struggle with what they’re being asked to do; they struggle to see how to do it. These prompts focus on making the start of the upload process obvious and confidence-boosting.
- Is it clear where users begin the upload process?
- Can users upload files using both a button and drag-and-drop?
- Is drag-and-drop offered as an extra, not the only option?
- Is the drop zone clearly marked and visible when needed?
- Do upload controls look active and prominent, not passive or greyed out?
Uploading files
Adding files should be flexible enough to match real situations. If limits are too tight or too rigid, users end up blocked or forced into workarounds.
- Can users upload multiple files at once?
- Can users add files in stages without starting over?
- Are supported file formats broad enough to cover common needs?
- Are file size limits realistic for the task?
- Can large image files be compressed before upload?
Reviewing and managing files
Uploading is rarely the final step. Users need space to check, adjust, and stay in control of what they’ve added before they commit.
- Is there a clear list of uploaded files with filenames?
- Can users remove or replace files before submission?
- If files need labelling or sorting, is it clear what’s required?
- Is it obvious when files are uploaded but not yet submitted?
- Can users review all files before final submission?
- Are destructive actions confirmable or reversible?
- For large sets of files, can users sort, search, or review in batches?
Upload vs submit
Uploading a file can feel like the task is done, but if “upload” and “send” aren’t separated, users risk leaving too early or resending unnecessarily.
- Is the difference between “upload” and “submit” clear?
- Are upload and submit buttons labelled differently?
- Is the process broken into clear steps: select, upload, review, submit?
- Are there separate confirmations for upload and submission?
- If files are auto-submitted on upload, is that explained before users start?
Feedback and validation
Without timely, clear feedback, users can feel uncertain or stuck. Strong signals help them trust what’s happening and recover quickly if things go wrong.
- Does feedback appear immediately when a file is selected, uploading, or finished?
- Is feedback placed inline, near the action, not just at the top of the page?
- Are error messages clear, supportive, and actionable?
- Do error messages avoid technical jargon?
- Can users recover from an error without starting over?
- Is there a confirmation step before final submission?
- Does the confirmation clearly show what happened and what’s next?
Accessibility, mobile, and edge cases
For many users, mobile is the only device they’ll use, and not everyone has fast, reliable internet. Design uploads to be forgiving of real-world conditions.
- Is the upload process usable with a keyboard and screen reader?
- Is the flow designed mobile-first, not adapted from desktop?
- Does the flow work in low-connectivity environments?
- Can uploads resume if the connection drops?
- Are users warned about high data use before a large upload?
- Is there a valid non-digital alternative (post, in-person) and is it clearly presented?
Familiarity and consistency
Consistency helps users feel at home. Aligning with GOV.UK patterns makes uploads predictable and reduces the learning curve.
- Does the experience align with other DWP or GOV.UK services?
- Are shared patterns used where possible?
- If diverging from a pattern, is the reason documented?
Could we improve this page?
Send questions, comments or suggestions to the DWP Design System team.
Last updated: