Decide where the work belongs
Rank the blocked task
Describe whether users need to review, create, connect, wait, recover, or understand that nothing exists. Give higher priority to states that conceal a required setup or an active filter.
Rank ambiguity reach
Compare roles, projects, filters, and lifecycle states that produce the same empty copy. Record observed paths and unknown reach instead of assuming every empty page has the same consequence.
Set a copy checkpoint
Choose a review after copy, empty-state branch, filter, or setup changes. State which cause labels and next actions must appear for the page to support the user decision.
What to carry forward
The queue result should name the empty cause, blocked decision, affected contexts, owner, and checkpoint. Keep priority high when the page conceals setup or active filtering; lower it when users already have a clear truthful next step. Prioritize confusion that blocks a clear next action or causes users to believe work disappeared, especially when filters, setup, or access produce the same visual state.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow