Aglet

Prioritize document status gaps by blocked processing decisions

A missing status matters when readers must decide whether to wait, retry, edit, download, or submit a document. Prioritization should focus on the decision and the derivative it relies on, separating a vague but safe pending state from a label that hides failure or premature readiness.

Decide where the work belongs

  1. Name the blocked decision

    Record the action users attempt after transfer and the processing result it requires. Note whether a document can be reviewed while another derivative waits, and distinguish a delayed optional feature from a blocked core workflow.

  2. Map dependent surfaces

    List document rows, detail pages, previews, text views, download controls, and downstream submissions that reuse status. Mark which surfaces collapse pending, failed, and ready states, and which preserve a specific stage.

  3. Choose the queue

    Queue status-model work when a required transition is absent, action gating when a ready label permits premature use, or copy repair when state is correct but vague. Attach the status sequence and derivative dependency.

What to carry forward

Prioritize the gap when a skipped state can hide failure or invite use before a required document result exists. A safe pending state with a clear wait action can rank below a final label that masks an incomplete or failed stage.

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