Purpose
The task list description is what a planner reads on screen when picking a job. A consistent description means the right list is picked every time, and grouping in reports (compliance, backlog, workload) actually makes sense.
Scope
- All task list header descriptions
- All task list step descriptions
- Applies to newly created and legacy task lists as they are revised
Key Terms
| Term | Meaning |
|---|---|
| Header description | The single-line description of the whole task list. |
| Step description | The one-line description of each numbered step inside the task list. |
Sections
- 01
Header description pattern
IntentForce a consistent word order so lists group and sort predictably.
Actions- Pattern: OBJECT TYPE — TASK — INTERVAL (e.g. PUMP CENTRIFUGAL — INSPECT — 500 H).
- Object Type mirrors the Object Type Component Naming standard.
- Task verb from the approved list: INSPECT, LUBRICATE, REPLACE, CALIBRATE, CLEAN, TEST, OVERHAUL.
- Interval in units (H = hours, M = months, K = cycles) — never spelt out.
What Good Looks Like- Publish sample task lists that show the standard done well.
What Bad Looks Like- Free-text descriptions with abbreviations only the original author understands.
- Bundling multiple intervals into one header ('inspect / lubricate 500 H / 2000 H') — reporting can't split them.
- 02
Step description pattern
IntentMake each step scannable and unambiguous on the printed work pack.
Actions- Pattern: ACTION — TARGET — REFERENCE (e.g. CHECK — DRIVE END BEARING TEMP — ≤ 65 °C).
- Action verb from the approved list.
- Target names the component using the Object Type Component Naming standard.
- Reference gives the acceptance criterion or standard (limit, torque, procedure code).
What Good Looks Like- Print a laminated cheat-sheet of allowed verbs and units for planners.
- Publish sample task lists that show the standard done well.
What Bad Looks Like- Free-text descriptions with abbreviations only the original author understands.
- 03
Language & symbols
IntentRemove ambiguity from search, print and translation.
Actions- UK English spelling.
- Units always SI (mm, °C, Nm, kPa).
- No embedded free notes — put those in the long-text field, not the description.
What Good Looks Like- Print a laminated cheat-sheet of allowed verbs and units for planners.
What Bad Looks Like- Free-text descriptions with abbreviations only the original author understands.
- Bundling multiple intervals into one header ('inspect / lubricate 500 H / 2000 H') — reporting can't split them.
- 04
Approvals
IntentPrevent silent drift from the standard.
Actions- Data Steward reviews new task list descriptions during the master data sign-off step.
- Legacy descriptions are updated when the task list is next revised — not in bulk.
What Good Looks Like- Print a laminated cheat-sheet of allowed verbs and units for planners.
- Publish sample task lists that show the standard done well.
What Bad Looks Like- Free-text descriptions with abbreviations only the original author understands.
- Bundling multiple intervals into one header ('inspect / lubricate 500 H / 2000 H') — reporting can't split them.
Best Practices
- Print a laminated cheat-sheet of allowed verbs and units for planners.
- Publish sample task lists that show the standard done well.
Common Pitfalls
- Free-text descriptions with abbreviations only the original author understands.
- Bundling multiple intervals into one header ('inspect / lubricate 500 H / 2000 H') — reporting can't split them.
- Mixing units within one task list — planners misread limits.