Works is HEPO's module for tasks, deliverables, issues, and other units of work. Teams maintain the work's type, responsibility, state, and relevant connections. Those records give Process Orchestration something concrete to coordinate and examine, and can supply permitted evidence for a defined P&C question.

The key object is the work item with its lifecycle. Its current status is useful, but the context of a change often explains more than the status alone.

Four classifications describe the item: type identifies the kind of work, status describes its current state, priority expresses urgency, and resolution records how it ended. Categories group work by function or programme; supported features can add characteristics such as effort, complexity, or required skills. These definitions make comparisons meaningful only when the organisation applies them consistently.

Follow work through a difficult delivery

A deliverable is created and assigned. It progresses until a required input is missing. Recording the blockage and dependency helps the team distinguish waiting from active work. If the deliverable is returned for correction, recording rework against the same effort makes the return visible. Completion identifies the result and the relevant follow-up.

The organisation defines the types and transitions it needs. Any required approvals, reasons, or handoff rules belong in that working model. Keeping blockage and rework visible helps reviewers understand how delivery actually unfolded.

Keep the connections beside the task

These connections help a reviewer ask why a task waited or returned. They also make the result available to a project review without treating each status update as an isolated event.

Use lifecycle evidence carefully

Process Evidence can draw on work records and transitions to examine delivery patterns. A measure such as blocked duration needs a defined start, end, and treatment of incomplete records. Rework needs a clear definition of what counts as a return.

A slow item may reflect an unresolved dependency or a changing requirement. The record supports investigation; it does not automatically identify a person's performance or the cause of a delay. P&C interpretation retains the same distinction.

Configure the work the organisation actually does

Process owners and consultants identify useful types, states, reasons, and responsibilities. Implementers configure the supported lifecycle and connect it to projects, communication, and execution. Review a normal completion, a blocked item, and a return for rework. Check both the operational handoff and what the later reading can substantiate.

The result is a connected account of delivery that people can act on and review.

Operational Core | Platform overview