Aglet

Verify a blocked team handoff is ready to proceed

Verification must test the handoff as the receiver experiences it. Confirm that the unblock artifact, decision, access, or dependency is usable, then run the next action and ensure no hidden blocker was simply moved downstream. Record who owns the first successful receiver action.

Check whether the outcome improved

  1. Check the unblocking condition

    Confirm the missing decision, context, access, or artifact is present, current, and within the receiver’s authority. Recheck that it applies to the stated work item rather than a similarly named request.

  2. Run the receiver’s next action

    Have the receiving role perform the previously blocked step and record the result, remaining inputs, and any expected failure path. Do not infer readiness from a sender message alone. Use the receiver’s real next step to expose any blocker that moved downstream.

  3. Close the loop

    Assign ownership for the next work step, preserve the blocker history, and set a new review point if another dependency remains. If the action still fails, return to blocked with the new evidence.

What to carry forward

Verification passes when the receiving role can complete the blocked step, context and dependencies are usable, and the next action has an owner. If the blocker moved downstream or remains ambiguous, keep it blocked and record the new boundary rather than closing it.

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