What is Empty State Copy?
Empty state copy is the interface text shown when a screen, list, search, filter, dashboard, or account has no content to display yet or no results for the current conditions.
What good empty state copy looks like
Strong empty states explain why nothing is shown, distinguish a new account from a no-results condition, and suggest a useful next step without pretending the absence is an error.
- Name the empty condition accurately.
- Explain the reason when it is not obvious.
- Offer one relevant next action when the user can change the state.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Name the empty condition accurately.
- Explain the reason when it is not obvious.
- Offer one relevant next action when the user can change the state.
How to write empty state copy step by step
- 1Determine whether the state means new, cleared, filtered, unavailable, or no results.
- 2Write a specific heading for that state.
- 3Add one sentence of context only if needed.
- 4Offer a primary action that can genuinely change the state.
- 5Avoid celebratory or apologetic tone unless appropriate.
8 Empty State Copy examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
No projects yet. Create a project to group tasks, files, and decisions.
No invoices match these filters. Clear the date range or choose another status.
Your reading list is empty. Save an article to find it here later.
No comments yet. Start the discussion with a specific question.
Nothing is scheduled for today. View this week or add an event.
No search results for “metonymy.” Check the spelling or browse literary devices.
Empty State Copy templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Heading: No [items] yet. Body: [what appears here]. CTA: [create/add action].
Heading: No results. Body: Try [specific filter/search adjustment].
Heading: All caught up. Body: There are no [pending items].
Common mistakes to avoid
- Using the same empty message for a new account and a failed search.
- Adding a generic Start now button without saying what will happen.
- Treating expected emptiness as an error.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about Empty State Copy
What is Empty State Copy?
Empty state copy is the interface text shown when a screen, list, search, filter, dashboard, or account has no content to display yet or no results for the current conditions.
What makes Empty State Copy effective?
Strong empty states explain why nothing is shown, distinguish a new account from a no-results condition, and suggest a useful next step without pretending the absence is an error.
How do I write Empty State Copy?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing Empty State Copy?
Using the same empty message for a new account and a failed search. Adding a generic Start now button without saying what will happen. Treating expected emptiness as an error.
How do I know whether a claim or source on a Empty State Copy guide is stale, corrected, or still active?
Do not infer status from the page-wide update date. Check the controlling source or project record, the exact version/date last verified, and the trigger that could make the item changeable. Keep it active when the source still controls the exact claim; mark review due when a trigger has fired but the conclusion is not yet disproved; mark stale when the old version no longer controls; and use corrected, retracted, withdrawn, or superseded when the editorial history requires it. The correction level should match reader impact: cosmetic edits are not the same as a material factual correction or a critical source failure.
If a source behind Empty State Copy changes, how do I know which other claims or guides need review?
Use the dependency map rather than reviewing the entire site blindly. Identify the exact claim or example that depends on the source, classify the dependency as direct, shared, advisory, or independent, and record why the source changed. Direct dependents should be reviewed immediately when a controlling source is corrected, retracted, superseded, or no longer supports the claim. Shared dependents can be queued by source/claim ID and scope. Replace the source only when the replacement performs the same evidentiary job—or change the claim. Keep the old source/status in the ledger, then propagate the review to templates, examples, and related guides only where that dependency actually exists.
How can editors track a source change for Empty State Copy without reviewing the entire site?
Use persistent claim, source, and dependency records. Link only the claims that truly depend on a source, then change that source record’s status in the Writing Authority admin when it is corrected, superseded, stale, withdrawn, or retracted. The registry queues the linked claims with a reason code and priority. Reviewers can see the affected guide, inspect the source/dependency IDs, revise or replace the evidence where necessary, and close the queue item after verification. Original site-created examples and templates remain independent unless they contain a real external factual dependency.