Aglet

Triage a document stage with no useful next action

A status can be technically accurate yet leave a person unsure whether to wait, retry, replace, download, or contact an owner. Triage should record the stage, current capability, controls, and expected outcome. The goal is to distinguish missing action guidance from a processing defect.

Establish what is happening

  1. Capture the user decision

    Record the document stage and the action the reader needs to choose. Note the visible status, elapsed context, controls, and document identity, including whether a page revisit changed what the interface offered.

  2. Compare action with capability

    For each available control, state the processing prerequisite and resulting transition. Identify controls that are missing, premature, duplicated, or labeled too broadly, and record whether waiting has any visible evidence of progress.

  3. Classify the guidance gap

    Classify the case as wait-versus-retry ambiguity, hidden replacement path, unavailable derivative, unclear failure, or owner decision. Preserve the state evidence so a label correction is not confused with a stage repair.

What to carry forward

Triage is complete when the current stage, needed capability, available controls, and intended next action are recorded. If the process has no defined safe action for a state, treat that missing decision as the primary workflow gap.

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