The hand-off problem: why detail dies between sales and delivery

What the hand-off actually is

The hand-off is the moment a piece of work changes owners. The people who understood the scope best, because they built the quote and talked to the client, pass it to the people who now have to deliver it, who often weren't in any of those conversations. Everything the sellers knew but didn't record has to survive that gap. Usually, it doesn't.

The four things that break

1. The reasoning behind the price

A line says "Custom checkout, £4,200". Delivery has no idea that figure assumed the client's current payment provider, a single currency, and no address-validation service. So they either gold-plate it or hit a surprise mid-build. The number survived the hand-off; the thinking behind it didn't.

2. The assumptions and exclusions

What was deliberately excluded, content population, data migration, third-party licence costs, lived in the salesperson's head or in a caveats paragraph nobody re-reads. It comes back as a scope dispute exactly when it's most expensive to resolve. This is one of the most common causes of scope creep.

3. The estimated effort

The hours that justified the price rarely travel with the document. Delivery re-estimates from scratch, arrives at a different number, and the project is behind before the first sprint. The estimate was real work, see estimating hours at quote time, and it should not be thrown away at the hand-off.

4. The structure

A proposal is organised to read well for a buyer: outcomes, narrative, a clean price. A build needs to be organised by component and sequence. So someone re-shapes and re-types it into a project tool, slow, and lossy, because re-typing is where decisions quietly change.

Why the usual fixes don't hold

Teams try to patch the hand-off with a kickoff meeting, a briefing doc, or a stricter template. These help at the margin, but they don't touch the root cause: the quote, the spec and the task list are three separate documents in three separate tools. As long as that's true, someone is always transcribing, and transcription is where detail dies.

A better template just produces a tidier document to transcribe. The durable fix is to stop transcribing altogether.

The structural fix

The hand-off stops leaking when the client-facing quote, the technical specification and the delivery task list are the same structured scope, viewed at different stages, not three files you keep in sync by hand.

When that's true:

• The price's reasoning sits in a note against the section it belongs to.
• Exclusions are written where the work is, not in a caveats block.
• The estimated hours stay attached and carry into delivery.
• Nobody re-shapes anything, because the structure never changed.

That's the model behind ScopeDeck's quote → specification → tasks: one section tree, three stages, so delivery inherits context instead of reverse-engineering a PDF. The next step after naming the problem is turning your quote into a buildable spec.