Decide where the work belongs
Name the decision at risk
Record whether users must wait, retry, replace, edit, download, or submit, and what processing result makes that action safe. Note the cost of a wrong choice and whether the document can remain open while work continues.
Assess action clarity
List visible controls and status text for pending, slow, failed, and partial-capability states. Mark whether a person can tell what happened, what to expect next, and which action will preserve the current document.
Choose the queue
Queue state-action design when controls contradict capability, failure investigation when the next action depends on an unexplained stage, or copy repair when behavior is safe but wording is thin. Attach the observed state and intended decision.
What to carry forward
Prioritize the case when unclear stage guidance can cause a destructive replacement, repeated retry, premature submission, or lost review time. A pending state that clearly permits waiting or safe continuation can rank below a failure with no recovery path.
Technical background: W3C guidance.
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