Ticket Workflow & Status Design

Ask three technicians what In Progress means and you will get three answers and a short argument. One uses it for anything they have opened. One uses it for anything they are actually typing in. One uses it as a place to keep tickets they intend to look at, which is a fourth status wearing a disguise. Meanwhile Pending holds tickets waiting for the user, tickets waiting for a vendor, and tickets waiting for a miracle, all together, with the same icon. A status is supposed to answer one question: whose move is it? Most status lists answer a different question, which is what the tool shipped with.

This series is about making the statuses mean something, including in tools where you cannot rename them. It covers what a status is for and the whose-move test. It covers defining each status in one sentence with an entry and an exit. It covers pending-user versus pending-vendor versus on-hold, and why the three kinds of waiting need different follow-up. Then comes why fewer states win, with the lifecycle drawn out. It covers resolved versus closed and the confirmation window between them. And it covers writing the workflow down on one page so a trainee follows it on their second day. The closing conversation itself belongs to the next series. This one is the state machine behind it.

Articles in This Series

• What a Status Is For
  A status answers 'whose move is it'; the minimal set; status versus priority versus category confusion; the status nobody can explain; and a whose-move table.
• Statuses That Mean Something
  One sentence per status with an entry condition and an exit condition; why the meaning lives in your definitions when the tool fixes the labels; and a status definition card.
• Pending User vs Pending Vendor vs On Hold
  Three kinds of waiting, why separating them matters for follow-up and reports, and the nudge rule for each. Covers designing targets when the clock does not stop on hold, and the waiting-state rules.
• Workflow Simplicity: Why Fewer States Win
  The twelve-state workflow nobody follows, the lifecycle as a diagram, the test every transition must pass, removing a state, and a transition table.
• Resolved vs Closed: The Confirmation Window
  Why two end states, the confirmation window, auto-close timing and notice, the reopen path from each state, and the confirmation-window rules.
• Writing the Workflow Down (One Page)
  The one-page workflow document: states, transitions, who may make them, examples, and the training that goes with it; the page itself to copy.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.