Empty states: what a new user sees before there is any data
Short answer: An empty state is any screen or panel with nothing to show yet: a new account, a search with no results, a list that's been cleared, or data that failed to load. Left blank, it confuses people about whether the app works. Designed well, it tells users what's going on, what will appear here, and the one action that gets them started. Treat each kind of empty state separately, because "you haven't added anything yet" and "something went wrong" need very different messages.
Business apps are full of empty screens on day one. A new client portal has no projects, a CRM has no contacts, a booking system has no appointments. Those first blank screens decide whether a new user explores or gives up. Nielsen Norman Group's guidance on empty states puts it well: intentionally designed empty states communicate system status, help users discover features and provide direct pathways to key tasks. The checklist below turns that into something you can run through screen by screen.
Step 0: List your empty states
Go through the app as a brand-new user, and then as an existing user applying odd filters. Note every place that can be empty:
- ☐ dashboards and home screens before any data exists;
- ☐ lists and tables (clients, jobs, invoices, files);
- ☐ search results and filtered views;
- ☐ notifications, alerts, favourites and "recent" panels;
- ☐ reports for periods with no activity;
- ☐ anything that can fail to load.
For each, decide which type it is. The four types below cover almost everything.
Type 1: First use ("nothing here yet")
The user hasn't created anything. This is an onboarding moment.
- ☐ Say what will appear here in plain words: "Your jobs will show up here once you create one."
- ☐ Offer the one main action as a clear button: "Create your first job".
- ☐ Add a secondary option where useful: "Import from a spreadsheet" or "See an example".
- ☐ Keep it short. One or two sentences, not a manual.
- ☐ Consider sample data, clearly labelled and easy to delete, for complex screens like dashboards, so users can see what a filled screen looks like.
- ☐ Explain value, not mechanics: "Track which quotes are waiting on clients" beats "This is the quotes module".
NN/g describes empty states as learning cues: a moment to show users features they haven't discovered yet. A short tip tied to the screen does this better than a generic tour.
Type 2: No results (search or filters)
Something should exist in general, but the current query matches nothing.
- ☐ State it clearly: "No invoices match 'Smith' in October."
- ☐ Show the active filters and offer a one-click way to clear them.
- ☐ Suggest alternatives: check the spelling, widen the date range, search all statuses.
- ☐ Don't show the first-use message here. Telling an experienced user to "create your first invoice" because their filter excluded everything is confusing.
NN/g's example is a log viewer that shows an empty table for a date range with no logs. Without feedback, users can't tell whether there's truly nothing, an error occurred or the system is still processing. A simple message removes that doubt.
Type 3: Cleared or completed ("all done")
The user has dealt with everything: all tasks complete, inbox cleared, no pending approvals.
- ☐ Confirm the good news: "No approvals waiting. Nice work."
- ☐ Point to what's next, if anything: "Next scheduled job: Thursday 9 a.m."
- ☐ Keep it calm. No need for big illustrations on a screen people see every day.
Type 4: Error or unavailable
Data should be here but couldn't be loaded, or the user lacks permission.
- ☐ Say something went wrong, without blaming the user.
- ☐ Offer a retry and, if it keeps failing, a way to get help.
- ☐ Distinguish permissions from errors: "You don't have access to Finance reports. Ask an admin," not a generic failure.
- ☐ Never show an empty table that looks like "no data" when the truth is "failed to load". That's the most misleading empty state of all.
Loading is not empty
- ☐ Show a loading indicator or skeleton while data is fetched, and only show an empty state once you know there's nothing.
- ☐ Avoid a brief flash of "No clients yet" before the list appears. Users notice and lose confidence.
Accessibility
- ☐ Empty-state messages are real text, not only an illustration.
- ☐ Buttons in empty states are proper, keyboard-reachable buttons with clear labels.
- ☐ When a search or filter returns no results without a page reload, announce it to screen reader users. MDN describes the ARIA
statusrole as a live region for advisory information that isn't important enough to be an alert; a "No results found" message is a typical use. - ☐ Decorative illustrations have empty alt text, so screen readers skip them.
Writing the words
- ☐ Use the names your users use ("jobs", not "work orders", if that's what they say).
- ☐ Lead with what matters: what's happening, then what to do.
- ☐ Keep the tone consistent with the rest of the app; avoid jokes on error screens.
- ☐ Make every button say what it does: "Add a client", not "Get started".
A quick example (hypothetical)
A Wellington cleaning company's new staff portal opens on a blank "Today" page for new hires. After a review, the first-use state says: "Your shifts will appear here once a manager assigns them. Check your availability so you're first in line," with a button "Set my availability". The no-results state on the shift search reads: "No shifts on Sunday 12 November. Try another day or clear the location filter," with a clear-filter button. Same screen, two very different messages.
FAQ
Do empty states really matter if users only see them once?
First-use states are seen once, but at the moment users decide whether the app is worth learning. No-results and error states are seen repeatedly.
Should we use illustrations?
They can help on first-use screens, but the text and the action matter more. Keep them light on screens people see daily.
Is sample data a good idea?
For complex dashboards, often yes, as long as it's clearly labelled and easy to remove.
Who should write empty-state copy?
Whoever knows the users best, reviewed by someone who uses the app daily. Short, specific copy beats clever copy.
If new users of your app keep landing on blank screens, send us screenshots of the first few pages and we'll suggest what each empty state should say and do.