Fixed-date item
Also known as Date-constrained work, Deadline-driven item
Definition
A fixed-date item is a work item with a meaningful deadline or time window. It is a class of service that may justify different sequencing and forecasting, while still consuming the same constrained capacity.
A different service need
Fixed-date work has a deadline that changes the cost of waiting. It should not automatically bypass every other item. Instead, the team makes the date, scope, dependencies, and tradeoffs visible and selects a service policy that fits the risk.
A concrete example
An illustrative team must support a regulatory change on October 1. It breaks the work into a testable slice, identifies an external approval, and forecasts the path using available capacity. If the date cannot be met, the risk is raised early rather than hidden behind a late expedite request.
Protect the system
Limit the number of fixed-date items and review their age and dependency waits. Splitting scope can reduce risk, but only if each slice contributes to the deadline outcome. Compare date performance with ordinary flow so urgency does not quietly starve routine work.
Limitations
Not every desired date is truly fixed. Treating all requests as deadlines destroys the meaning of the class and creates chronic priority churn. A date policy should state who can declare the constraint and what happens when it changes.
How this relates to Weave
Weave can help teams examine historical delivery timing and change activity for work with a known date constraint. It cannot validate the business reason for the date or guarantee completion, so the commitment and risk should be managed in the team's planning system.
Explore Engineering intelligence