From 708e26b8ef7cd578aeb4eb92c5afe1e3dfef66e0 Mon Sep 17 00:00:00 2001
From: George Karr <georgekarrv@users.noreply.github.com>
Date: Fri, 19 Jun 2026 09:37:28 -0500
Subject: [PATCH] Update design QA considerations for empty states

Add a note about defining empty states for views that load data.
---
 docs/Contributing/guides/ui/design-qa-considerations.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/Contributing/guides/ui/design-qa-considerations.md b/docs/Contributing/guides/ui/design-qa-considerations.md
index 9dfd708b56e..8227ef0b641 100644
--- a/docs/Contributing/guides/ui/design-qa-considerations.md
+++ b/docs/Contributing/guides/ui/design-qa-considerations.md
@@ -146,6 +146,7 @@ This is meant to be a helpful checklist of 'events' or 'transactions' to help ca
 - Error states (conditions, clientside vs. server side, location of error message, trigger onBlur/onChange/onSubmit)
 - Disabled states (conditions, on button, on form fields)
 - Dynamic views (show/hide buttons, dynamic help text, edge case views)
+- Views that load data have an empty state defined.
 
 ## Responsiveness and low-width browsers
 - Long database names rendered in the UI e.g. fleet names, scripts, software titles...