Decide where the work belongs
Rank the waiting cost
Describe what changes if a person sees the event later and whether a recovery path exists. Compare security, workflow, review, and informational examples. Keep “important” separate from “must interrupt now.”
Compare interruption choices
Set passive, active, scheduled, urgent, and in-app-only treatments beside one another. Consider user settings and alert fatigue. Prefer the least disruptive path that preserves the decision, and record when a platform may delay presentation.
Choose a bounded move
Set event class, owner, scope, and revisit evidence. Decide whether to change urgency, add context, or improve durable history. Preserve the current path and one routine control so the queue decision can be checked after the change.
What to carry forward
Prioritize urgency changes only where delay materially changes the user’s decision and the evidence supports that claim. The decision should name event class, interruption level, and recovery. If the event remains available and waiting is safe, prioritize clarity over escalation.
Technical background: Apple developer documentation.
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