Useful error messages, empty states, and loading screens explain what is happening, what it means for the user’s work, and what they can do next. Plan these situations alongside the normal success screen, with clear wording and behaviour that matches the actual system state.
A customer who sees a blank appointment list may wonder whether no times are available or the page failed to load. Someone submitting an enquiry may be unsure whether to wait, retry, or contact the business.
These moments belong in your UI/UX design process. The message, available action, and underlying workflow need to support the same explanation.
Start with the tasks that matter most to your customers. Then identify the states they can encounter before, during, and after completion.
Start With the State the System Actually Knows
Different situations need different explanations.
A successful search with no matches is different from a search that failed. A request being processed is different from a completed booking.
| State | What the system knows | What the user needs |
|---|---|---|
| Loading | The result is still being retrieved | An understandable waiting state |
| Input error | Information needs correcting | A clear explanation and correction route |
| Empty result | The request succeeded but returned no matching items | The reason and a relevant next step |
| Service failure | The system could not complete an operation | A truthful explanation and recovery option |
| Access restriction | The user cannot perform the action with their current access | An appropriate access or support route |
| Confirmed completion | The stated operation successfully completed | A clear outcome and relevant next action |
Define these distinctions before selecting a visual component.
Avoid showing “No results” while the system is still waiting for a response. If previously loaded information remains visible during an update, make its status understandable where that affects a decision.
Accurate states give the team a foundation for writing accurate messages.
Write Error Messages That Help People Recover
An error message should identify the relevant problem and help the user continue.
Use familiar language and refer to the field or task the person is working on. Keep the explanation calm and specific.
The following examples are illustrative. Match formats, limits, and recovery options to the product’s actual rules.
| Unhelpful message | More useful alternative |
|---|---|
| Invalid input | Use an email address such as name@example.com |
| Upload rejected | Choose a PDF smaller than 10 MB |
| Error loading data | We could not load your appointments. Try loading this section again |
| Access denied | Your role does not include report access. Ask your workspace administrator |
A field-level message is appropriate when a user can correct the information. A service failure needs an explanation about the operation that failed.
GOV.UK’s error-message guidance makes this distinction: validation messages address input problems, while service problems and access issues need their own explanation and next steps. GOV.UK Design System
Show input feedback near the relevant field. For a longer form, provide a useful way to find and reach the fields needing attention.
Review timing too. Displaying an error while someone is still entering a valid answer can interrupt their work.
Keep detailed diagnostics available to the support or development team through an appropriate process. The user-facing explanation should help the person complete their task.
Preserve the Work Behind the Error
A useful message loses value if the interface clears the entire form afterwards.
Keep appropriate entries available so people can inspect and correct them. Retain valid selections when an upload or another step needs attention.
Decide how this should work for the information involved. Sensitive fields and session boundaries require deliberate handling.
For a multi-step form, show which stage needs correction and provide a sensible return route. If a selected appointment becomes unavailable, preserve other relevant choices while offering valid alternatives.
Include recovery behaviour in the design specification. “Show an error” leaves important questions unanswered:
- Which information remains available?
- Where does the message appear?
- How does the user reach the affected field?
- What happens after correction?
- How can the person get help if they remain blocked?
These decisions affect the effort required to finish the task.
Give Each Empty State the Right Explanation
An empty screen can represent several normal situations.
A new account may have no records yet. A search may return no matches. A user may have completed every item in a queue.
| Situation | Useful explanation | Suitable next step |
|---|---|---|
| New workspace | Explain what belongs in this area | Create or import the first item |
| No search matches | Explain that the current search has no matches | Change the search or remove a filter |
| Work completed | Confirm that the current queue is clear | Continue elsewhere if relevant |
| No availability in the selected range | Explain the scope of the result | Try another range or an appropriate contact route |
Atlassian’s empty-state writing guidance recommends an informative heading, a concise explanation, and a next action that fits the situation. Adapt those principles to the user’s task. Atlassian Design
For example:
No appointments match these filters
Choose another date range or remove a filter to see more options.
Action: Change Filters
A completed queue may need no primary action. “Your inbox is clear” can be sufficient when there is nothing the user needs to do.
Keep illustrations supportive and restrained. The explanation should remain useful without the artwork.
Make Loading Explain What the System Is Doing
Loading feedback should make the current operation understandable.
“Preparing your report” gives someone more context than an unexplained spinning shape. The wording should reflect the real operation.
Choose the pattern according to what the system can reliably communicate.
| Loading situation | Pattern to consider |
|---|---|
| A local action is processing | Feedback beside the action or within its control |
| A predictable page structure is loading | Stable content placeholders with an appropriate status message |
| A longer operation has measurable progress | A progress indicator based on actual completion |
| A background job can continue independently | A clear job status and a way to find the result later |
Atlassian’s progress-bar guidance recommends measurable progress for suitable longer processes and clear labels describing the current state. Use a percentage only when the system can support it accurately. Atlassian Design
Avoid allowing an indicator to imply completion while essential work remains unfinished.
A loading state also needs an exit path. Decide what happens when the operation completes, fails, or takes longer than expected.
Base delay handling on the actual process. If a job continues in the background, explain whether the user can leave and how to return to its status.
Make Retry Actions Match the Operation
“Try again” can be appropriate, but its behaviour needs to fit the task.
For a failed attempt to retrieve a list, retrying can request the information again.
For an order, booking, or message submission, a connection problem may leave the outcome uncertain. The interface should check or expose the status before encouraging another attempt that could repeat the action.
Distinguish what is known:
- Not submitted: the request did not reach the processing step.
- Processing: the request was accepted and is still being handled.
- Completed: the system has confirmed the outcome.
- Uncertain: the interface cannot yet establish the result.
Use these explanations only when they match reliable system information.
Where a task cannot continue online, provide a relevant support route and explain what information will help staff investigate.
This is part of the product workflow and belongs in the web application development scope.
Make Feedback Available to More Users
Messages need to work for people using different devices and assistive technologies.
Use text to explain meaning alongside colours and icons. A red border alone does not tell someone what to correct.
Connect field messages to the relevant controls, keep headings logical, and make recovery actions operable with a keyboard.
For relevant messages that update in place, W3C’s Status Messages guidance explains how assistive technology can notify users without moving focus to the message. Apply this to appropriate loading, result, and completion updates. W3C
Review focus behaviour according to the interaction. A form error summary, a modal task, and a background status update do not all need the same treatment.
Check whether important feedback remains available long enough to understand. Put essential confirmation details somewhere users can revisit.
On mobile, test with the keyboard open and larger text enabled. Messages and recovery actions should remain reachable without being covered by sticky elements.
Plan the States Before Development Begins
Include these situations in your website design reviews and product specifications.
For each important task, agree on:
- The possible states and what triggers them.
- The information the system can confirm.
- The message and where it appears.
- The available actions and their destinations.
- The information retained during recovery.
- The conditions for returning to normal use.
Review the plan with designers, developers, content owners, and the people handling support.
Reusable components can keep presentation consistent. The wording still needs to reflect each task’s actual cause and recovery options.
Assign ownership to changes. If an upload limit or booking process changes, update the related instructions and messages as part of the same work.
Test Failure, Waiting, and Recovery
A review should go beyond the successful journey.
Use a prototype or test environment to check situations such as:
- Missing or incorrectly formatted input.
- Unsupported or oversized uploads.
- A successful search with no matches.
- An empty new account.
- A slow or interrupted request.
- Missing permissions.
- A submission whose outcome is temporarily uncertain.
- Successful completion after correction or retry.
Ask participants what they believe has happened and what they would do next.
Observe whether they can recover without losing work, repeatedly tapping, or contacting support unnecessarily.
Include mobile use, keyboard navigation, and assistive technology where relevant. Check that the final message matches the resulting record or operation.
Use a focused redesign and optimization review to prioritise the points where people become blocked or misunderstand the outcome.
Measure Recovery Alongside Error Frequency
Track how often important states occur and what happens afterwards.
Useful measures include:
- The proportion of users who complete a task after an input error.
- Repeated errors at the same field or step.
- Successful recovery after a failed request.
- Abandonment during extended loading.
- Support requests caused by unclear status.
- Duplicate requests associated with uncertain outcomes.
Interpret the numbers with care. Fewer displayed errors may mean the form improved, or it may mean validation stopped detecting a problem.
Separate input issues from service failures so the team investigates the right cause.
Keep personal answers, uploaded documents, credentials, and other sensitive content out of general-purpose analytics. Use suitable error categories and appropriately restricted diagnostic information.
M4YOURS IT Recommendations
| What you observe | Recommended starting point |
|---|---|
| Users cannot explain an error | Rewrite the message around the relevant problem and correction |
| Forms restart after a mistake | Improve appropriate data retention and the correction route |
| Failed searches appear empty | Separate successful empty results from request failures |
| Users repeatedly submit while waiting | Clarify processing status and review duplicate prevention |
| Loading appears endless | Add a defined completion, failure, or status-check path |
| Users miss important feedback | Review placement, persistence, focus, and assistive-technology support |
Start with the states that block important tasks or create uncertainty about completion.
Then improve recurring sources of effort, such as repeated field corrections or lost selections.
Your next project
Let’s make your brand recognizable.
Have a business in mind? Tell us about your ideas, your audience, and the identity you want to create.
Prefer a direct conversation?
FAQ
Choose the presentation according to the problem. A field correction usually belongs near the field, while a broader service problem may need a section or page-level explanation. Use a dialog when the interaction genuinely requires a separate task or decision.
It may be sufficient for a simple local wait when the operation is clear. More complex tasks often need explanatory text, meaningful progress, or a way to check status later. The loading state should lead to a defined outcome.
No. A new workspace or unsuccessful search often benefits from an action. A cleared inbox may only need confirmation that the work is complete. Include a button when it supports a useful next step.
Choose one important form, search, or transaction. List its loading, empty, error, access, and completion states. Check the wording and recovery behaviour for each one, then test the complete journey with someone outside the project team.
Review one important customer task this week. Check what users see when they wait, make a mistake, find nothing, encounter a failure, and complete the task.
M4YOURS IT can help connect interface feedback with the product behaviour behind it. Request a consultation to discuss clearer states and more reliable recovery for your website or application.
























