Work Package Template

Work Package Template

The document that hands work to a team leader and makes clear exactly what they have agreed to deliver.

A work package is where a project stops being a plan and becomes somebody's job. Done properly it states the products, the standards, the tolerances and the reporting — so the person doing the work knows when they are finished, and the project manager knows when to step in.

The eight sections

1. Work package identity — reference, owner, dates, the control account it sits under
2. Products and scope — what is to be produced, and what is explicitly not included
3. Techniques, standards and constraints — how the work must be done
4. Interfaces and dependencies — who this work depends on, and who depends on it
5. Quality arrangements — what checks apply, by whom, against what criteria
6. Tolerances and escalation — how far it can drift before it comes back to you
7. Reporting and communication — what gets reported, how often
8. Authorisation, acceptance and closure — signed at the start, signed at the end

Thirteen pre-built tables — you are recording an agreement, not designing a form.

Why it matters

Most disputes on a project are about scope that was assumed rather than written. A work package with the exclusions listed and the tolerances stated prevents the argument, because both sides signed the same page.

Who it's for

Project managers delegating to team leaders or subcontractors, and anyone who has been handed vague work and blamed for delivering the wrong thing.

How you use it

Complete it, agree it with the person doing the work, both sign, and use the same document to accept the work at the end. Editable Word document. No macros, no subscription.

Pairs with the Project Initiation Documentation (A$16), which sets the tolerances this package inherits.

Built in Australia from more than twenty years of program delivery experience. Instant download, yours to keep, use it on as many packages as you like.