Overview
Work item templates improve consistency across teams by combining planning and execution.
Use this as a baseline for engineering, customer, and support workflows.
Adapt a complete operational work queue
Search and filter the queue, switch layout, create work, inspect durable context, and update ownership or status without losing the selected item.
Work items
Classify, assign, and move cross-functional work from one durable queue.
Anatomy
Use each piece in this order to keep interpretation and automation consistent.
- 1Header metrics
Current queue and health indicators.
- 2Filter workspace
Team, owner, and status selection.
- 3Item list
Row cards showing due dates and state.
- 4Quick actions
Most common actions at each row or bulk level.
- 5Drill-down
Open full detail without losing list context.
The ordering here is not visual-only; it reflects interaction priority and expected user cognition. Keep this order unless policy demands a specific domain exception.
When to use
Use this pattern when the user needs guided consistency, state, and reuse at scale.
Recommended
- Cross-functional workflows
When teams need one consistent work intake surface.
- Project tracking
When status and ownership need frequent updates.
- Ops triage
When items arrive continuously and require classification.
When not to use
Avoid forcing this pattern where simpler, direct interactions are sufficient.
Avoid
- Passive dashboards
Use dashboard template for monitoring-only views.
- Single-purpose forms
Use form-driven templates for one-off actions.
- Financial reporting
Use list-report for heavy data analysis.
Variants
A small number of variants helps teams choose correctly without adding complexity.
Kanban
Board-style swimlanes for visual tracking.
List
Linear list for high row counts.
Compact
High-density cards for fast triage.
States
States communicate readiness, risk, and expected user behavior.
| State | Trigger | Visual response | Interaction |
|---|---|---|---|
| Ready | Unassigned items | Unclaimed list and quick assign action | Enable assignment workflows. |
| In progress | Active work selected | Progress indicators and blockers | Use update actions in place. |
| Done | Completed | Archived visibility and close summary | Optional reopen action available. |
Behavior
Behavior should remain predictable across devices, permissions, and async edges.
Consistent routing
Maintain one action vocabulary across item sources.
Rapid updates
Quick inline edits for status and assignee.
History capture
Log assignment and status changes.
Accessibility
Keep interaction clarity high and ensure assistive technologies get the same meaning.
| Key | Action |
|---|---|
| N | Create new work item quickly. |
| A | Open assignment controls for focused item. |
| Esc | Discard inline edit and return to list. |
- Ensure each item state is visible in text and icon.
- Preserve tab order when drag-and-drop is optional but available.
- Use consistent live feedback for state transitions.
Content guidelines
Consistency is achieved by language standards, not by design only.
Item titles
Keep titles action-oriented.
Resolve billing exception
Priority labels
Avoid too many categories.
High
Due date copy
Use clear date language.
Due Friday 5:00 PM
Examples
Reference implementation style, payloads, and practical behavior.
Production use
- Expose default quick status actions aligned with team rituals.
- Surface blockers and assignee on the same row for faster triage.
- Keep completed items searchable for audit and review.
Props / API
Use these API entries as a baseline contract and validate them against your domain layer.
These names are implementation-oriented and should map to your local contracts.
Props