Allocate tasks

The skill and its purpose

A rollout total describes quantity but not responsibility. Each location can need its own measurement, access confirmation, content review, receipt and installation. Task allocation should show the person who can perform or decide the work at that site and the information it depends on. A central coordinator can organise the plan without holding every local authority.

Work through the decision

Create tasks linked to stable site and variant references. State the required action, accountable owner, due date, prerequisite and evidence needed to close it. Separate planning dates from accepted commitments. Identify deputies and escalation paths for overdue work. When a shared baseline changes, review which local tasks depend on it rather than changing all statuses at once.

Practical exercise — fictional

A fictional five-site programme has four confirmed measurements and one outstanding survey. Prepare a site-task list showing the remaining survey, the dependent artwork review and the owner’s next action. Keep the other sites’ actual status visible. Explain how a global production total can conceal the single site that is not ready for release.

Take it to the next job

• Link tasks to exact sites and variants.
• Name owners and required completion evidence.
• Make dependencies and escalation visible.
• Keep local statuses separate from programme totals.