Skip to Content
Services

Agree scope, reviews, and handover

Clarify what is included, how it will be checked, and who handles what follows.

A service description is a starting point. The agreed scope needs to say what will actually be delivered for your project.

Before work starts

  • Define deliverables, priorities, dependencies, and what counts as complete.
  • Clarify the information, decisions, and access each side needs to provide.
  • Discuss cost, timing, review points, and any third-party services or subscriptions.
  • If delivery is phased, agree what the first phase achieves and what waits.
A service page introduces the work and links to an enquiry. The project scope still needs to be agreed.
A service page introduces the work and links to an enquiry. The project scope still needs to be agreed.

During review

Check working features and outputs against the agreed requirements. Use specific examples when reporting a problem. New requirements can affect cost or timing, so discuss the change before assuming it is included.

After delivery

Confirm handover, documentation, deployment, and ongoing responsibilities. Maintenance and support arrangements depend on the agreed scope; do not assume every service includes indefinite changes or monitoring.

See How We Work for the wider process, or contact us about your project’s arrangements.