Standard item
Also known as Standard class of service, Regular work item
Definition
A standard item is work that follows the ordinary pull order, WIP policy, and service expectation of a workflow. It is distinguished from urgent, fixed-date, or other special classes of service.
The default path
A standard item uses the workflow's normal policies. It is not unimportant; it simply does not have a special date or urgency rule that changes its sequencing. Keeping this class clear provides a baseline for understanding the impact of expedite and fixed-date work.
A concrete example
An illustrative product improvement has no external deadline and is ready for delivery. It enters the normal queue and is pulled according to the team's ordinary policy. If it later becomes date-constrained, the classification changes with an explicit reason.
Use the class as a baseline
Compare standard item age, cycle time, and throughput with other classes. If ordinary work is repeatedly interrupted, the service policy may be overloaded or urgent work may be over-classified.
Limitations
“Standard” does not mean identical size or risk. Segment when a meaningful difference affects flow. Avoid using the label to dismiss work that has a legitimate but non-urgent priority.
How this relates to Weave
Weave can help teams compare delivery patterns for ordinary changes with other service classes. It does not assign priority or determine whether an item is standard, so the classification should remain explicit in the team's workflow.
Explore Engineering intelligence