Use this when
The commercial relationship is agreed but the project needs a precise delivery plan that can be referenced by the proposal, contract, and invoices.
Objective and success
Describe why the work exists and how both sides will recognise a complete outcome.
- Project objective and intended users
- Success indicators under the freelancer’s control
- Constraints, assumptions, and required standards
Deliverables
List concrete outputs with formats, quantities, environments, or boundaries.
- Deliverable name and description
- Included versions, pages, channels, integrations, or file formats
- Owner, target date, and acceptance criteria
Dependencies and review
Make client inputs and review windows visible so schedule changes can be explained factually.
- Access, content, data, decisions, and approvals required
- Review participants and feedback format
- Included revision rounds and consolidation rules
Change control
Define how a request becomes approved additional work instead of an informal expectation.
- Request description and business reason
- Effect on scope, fee, schedule, and dependencies
- Named approver and written acceptance before work begins
Adaptable sample language
Deliverable: responsive implementation of six approved page templates.
Acceptance: matches approved designs at the defined breakpoints and passes the agreed browser review.
Dependency: final copy and image assets supplied by the client five business days before implementation.
Change requests begin only after written approval of the revised fee and schedule.
Check before using
- Avoid vague verbs such as improve or optimise unless the measurable boundary is defined.
- Record assumptions that affect effort, not only the deliverables.
- Update connected milestones and invoices when a change is approved.
Continue the workflow