Skip to content
Templates

Support-to-delivery handoff checklist (agencies)

A checklist for moving a support ticket into delivery work: scope, estimate, ownership, and client expectation, without losing context.

Templates Service desk Workflow
Copy/paste template. This is guidance you can copy into your docs or intake forms. Timelint doesn’t currently generate custom templates for you.

Agencies lose time when support and delivery use different languages. This checklist keeps the handoff clean.

Board view
Handoffs work when the ticket stays the unit of work.

The checklist

1) Confirm scope

  • What is the outcome (in one sentence)?
  • What’s explicitly not included?
  • What does “done” look like?

2) Decide: retainer vs project

  • Is this in contract hours?
  • Should it become scoped project work?
  • If out of contract, flag it early.

3) Add acceptance criteria

  • 3–5 bullets max.
  • Include edge cases and permissions if relevant.

4) Estimate and plan

  • Rough estimate: S/M/L or hours
  • Dependencies: …
  • Target release/window: …

5) Assign ownership

  • Who owns delivery?
  • Who owns client comms?

6) Communicate on the ticket thread

Post a short update:

  • what you’re doing next,
  • when you’ll reply,
  • and what you need from the client (if anything).

If you want support and delivery to stay in one workflow (same tickets, same statuses), see: Service desk inside projects.

Related

Want the calmer workflow?

Start with a familiar Jira-style system that’s dramatically easier to navigate.