← Blog

Strategy & Results · 10 min read

Process Teardown, Part 3: The Handoff, from Signed Yes to Kickoff

Part 3 of a weekly series: map the handoff from signed yes to kickoff, find six leaks and fix them with a nine-field sheet, a kickoff and four numbers.

A smooth metal relay baton resting across a red running track lane in low morning light
In a relay race the baton is dropped in the handoff, not on the straight. A signed yes is the same: the risky part is the next ten feet.

A landscaping company I will call Greenfield (an invented name, a composite of a few businesses I have seen) won a nice job on a Friday. The owner shook hands, said "we will start Monday" and went to dinner. On Monday a crew of four arrived with a truck of the wrong mulch, found the gate locked, discovered that the customer had been told "no more than two days" while the schedule said four, and spent the morning learning that the customer's husband had a dog. A large dog. Which nobody had mentioned, because nobody had asked, because the person who sold the job had the whole conversation in her head and her head was in a different truck.

Nothing in that story is a catastrophe. It is a small, expensive, embarrassing Monday. The strange thing is how normal it is. Every one of those problems was knowable on Friday.

This is the third part of Process teardown, the weekly series in which I take one common business process apart, step by step. In part 1 we looked at the new inquiry. In part 2 we followed the quote to a signed yes. Today we pick up the baton at the most dangerous place in the race: the handoff.

Why a handoff is an operations process

Let me say again who is talking. I am not here to teach selling, and I would not trust a stranger who promises to teach it in a blog post. What I know is that a sale, once made, is a promise that a team has to keep. The promise travels from one person to another, and that travel is a process with a start, an end, an owner and a queue.

The start is the signed yes. The end is a kickoff that the customer and the team both understand. What happens in between is rarely designed. It is a text message, a hallway comment and "I put it in the folder." The folder is not a process. It is an optimistic place.

There is a reason this matters more as a business grows. When the same person sells and does the job, the handoff happens inside one head and costs nothing. The day you add a second person, the head splits in two, and the information has to cross the gap. Most businesses add the second person long before they add the process for crossing the gap.

The map of a typical handoff

When I map this with a small business, the picture on the wall usually looks like the one below. Count the steps, the people and the waits.

1The customer says yesEmail, text or a handshake
2The seller celebratesReasonably
3A message to the team"We got the Miller job!"
4The team asks questionsWait for the answers
5The seller answers from memoryIn pieces, between calls
6Someone schedules the startWhere there is a hole
7The customer is told a dateNot always the scheduled one
8The first visitThe first surprise appears
9A fix on the spotA morning and some trust
10The first invoiceMaybe another surprise
The map of a typical handoff, from yes to the first surprise.
  1. The customer says yes, by email, text or a handshake.
  2. The seller celebrates (reasonably).
  3. A message goes to the team: "We got the Miller job!" with a link or nothing.
  4. The team asks questions. Wait for the answers.
  5. The seller answers from memory, in pieces, between other calls.
  6. Someone schedules the start, usually where there is a hole in the calendar.
  7. The customer is told a date, not always the date that was scheduled.
  8. The first visit begins. The first surprise appears.
  9. A fix on the spot, which costs a morning and a little trust.
  10. The first invoice, which may contain another surprise.

Ten steps, one handoff that happens by memory, two waits and a surprise that is built in. Nobody designed this. It is the sum of good intentions and a very full Friday.

Where it leaks

I use a short list. Each of the six leaks has a symptom you can spot and a fix that does not need software.

1. The promise lives in one head. The seller knows what was promised: the date, the extras, the "we'll see what we can do." Nobody else does. Symptom: the team asks the seller the same questions every time. Fix: the seller writes the promise on one sheet before the celebration, not after.

2. The yes arrives without the details. "They accepted the quote" is not information. The team needs the scope, the exclusions, the address, the access, the contact and the dates. Symptom: the first week starts with phone calls. Fix: a handoff sheet with fixed fields, described below.

3. The kickoff is late. The first conversation with the customer happens after the first problem. Symptom: the first message from the team is an apology. Fix: a short kickoff call or message that happens before the work starts, with a date in the sheet.

4. The customer does not know what you need. Access, decisions, payments, the person who signs off. Customers are not mind readers. Symptom: "we are waiting on the customer" shows up in week two. Fix: a customer list of what you need and by when, sent with the kickoff message.

5. The team learns the scope by surprise. The crew finds out what is included when they find out what is not. Symptom: extras done for free "to be nice," then expected forever. Fix: the sheet states what is excluded, in the customer's words, and the kickoff repeats it.

6. Nobody confirms the first step. The job starts, or does not, and nobody checks. Symptom: a customer calling to ask where the crew is. Fix: a confirmation after the first day, with one question: "Is this what you expected?"

A plain brown cardboard box with a tape dispenser and a few blank white sticky labels on a worktable
A handoff is a package: you pack it, label it and check that it arrived. If any of the three is missing, you have sent a rumor.

I have never met a business that was careless on purpose. They were busy, and busy people hand off by memory.

The handoff sheet: nine fields, one page

The best fix I know is also the plainest. One page, the same every time, filled in by the person who sold the job, before it is passed on. Nine fields:

  1. Customer and contact. Name, phone, the best time to call and who decides.
  2. Address and access. Where, gates, codes, parking, pets, hours when the place is open.
  3. What was sold, in plain words. Copy it from the quote.
  4. What is not included. Copy that too. This line prevents more arguments than any other.
  5. What was promised outside the quote. The "we'll try to" and the "I'll look into it." If it is not written, it was not promised.
  6. Dates. Requested start, agreed start, and any date the customer cannot move.
  7. What we need from the customer, and by when. Access, choices, payments, approvals.
  8. Owner of the job. One name, plus a backup.
  9. Kickoff. Date, how (call, visit, message) and who is on it.

That is the whole tool. If your business is bigger, add a field. If it is smaller, you can still use the nine; the habit matters more than the fields. The rule is that a job does not go on the team calendar until the sheet is complete, and a sheet is complete when none of the nine is empty. "Not applicable" is a valid answer. Blank is not.

1Customer and contactAnd who decides
2Address and accessGates, codes, pets, hours
3What was soldCopied from the quote
4What is not includedThe line that prevents arguments
5Promised outside the quoteIf not written, not promised
6DatesRequested, agreed, immovable
7Needed from the customerAnd by when
8Owner of the jobOne name, plus a backup
9KickoffDate, how and who
The nine fields of the handoff sheet.

The kickoff: five minutes that save a morning

A kickoff does not have to be a meeting with a projector. For a small job it is a ten-minute call or a clear message, and it has five parts: who is who, what will happen and when, what is not included, what we need from you and how we will confirm. If you want a fuller agenda for bigger work, my project kickoff meeting agenda has one, and the RACI chart guide helps when several people share the job.

The effect is bigger than it looks. The customer hears the exclusions from you, in a friendly tone, before the work starts, and not in the middle of it as bad news. The team hears the plan from the same voice. Everyone leaves with the same picture, and that picture is, by an unusually large margin, the cheapest insurance in the business.

Four numbers to watch

You do not need a dashboard. Four numbers, counted by hand for a month, will show you whether your handoff works.

  1. Days from signed yes to kickoff. The median. If the answer is "it depends," start counting.
  2. Jobs started with a complete sheet. Out of the jobs started this month, how many had all nine fields filled in before day one?
  3. Customer items missing at kickoff. Access, decisions, payments. How many were still open when the crew arrived?
  4. Surprises in the first two weeks. Anything that made someone say "nobody told me." Count them, write a line for each and sort by cause.
1Days from yes to kickoffThe median
2Jobs with a complete sheetAll nine fields before day one
3Customer items missingStill open when the crew arrives
4Surprises in two weeksAnything "nobody told me"
The four numbers for the handoff.

The fourth number is my favorite, because the list of surprises is the next improvement, written by the business itself. After a month you will see that three or four causes repeat, and each of them is a new field or a new line in the kickoff.

An open empty manila folder with three metal paper clips lined up beside it on a tidy desk
The folder is not the handoff. The sheet inside it is, and a folder without the sheet is only optimism.

The fix ladder: in order

As in the other parts of this series, I fix in a fixed order: eliminate, simplify, standardize, reorder and only then automate.

Eliminate. Stop the handoff by memory. The seller does not message the team until the sheet exists. This is not a technology change. It is a rule.

Simplify. Nine fields. Not nineteen. If a field is never used, remove it, and if a surprise repeats, add one.

Standardize. The same sheet for every job, in the same place, with the same name format, so that anyone can find it. A folder with a good naming habit is a decent database for a small business.

Reorder. Move the kickoff to before the first day of work, not after the first problem. Move the question "what do you need from the customer?" to the quote stage if you can; it makes the handoff nearly empty.

Automate. Once the steps are stable, a form can fill the sheet, a template can create the folder, a reminder can book the kickoff, and a message can ask the customer for their items. This is where tools such as business process automation pay off. An AI helper can summarize an email thread into the draft of the sheet for the seller to correct. It must not guess the missing fields or schedule the work on its own, and the one-page AI policy is a good place to write that rule down.

1EliminateStop the handoff by memory
2SimplifyNine fields
3StandardizeThe same sheet every time
4ReorderKickoff before the work
5AutomateForms, templates, reminders
The fix ladder for the handoff, in the order I use it.

If you recognize a bottleneck behind all this, the cause is often that one person is the only one who knows. The capacity planning and bottlenecks guide explains how to spot that person before they take a holiday, and the process improvement guide shows how to map and measure any process like this one.

Try the handoff sheet

The tool below builds the handoff sheet, a kickoff message to the customer and a list of what you need from them. Fill in your business, the job, what is included and excluded, the dates and who owns the job. The tool tells you which fields are empty or too vague. Everything is invented in the starting values, so replace them with yours.

Interactive tool

The handoff kit

Loading the tool…

A note for very small teams

If you are a team of two, this can sound like a lot of paper for a Monday. It is not. The sheet takes about ten minutes the first time and five minutes after that, and the saving is one wrong-truck morning. Also, notice that a handoff does not need two people. When you sell a job on Friday and do it on Monday, you hand it to your own tired Monday self, who has forgotten the gate code, the dog and the thing you promised. Write the sheet for that person. They are the most forgetful colleague you will ever have.

What to do this week

Take your last three jobs and write down, for each, what the team did not know on day one. That is your baseline, and it is usually a bigger list than you expect. Then do three things: write the nine-field sheet, require it before any job goes on the calendar and put the kickoff on the calendar the day you sign.

Next week, in part 4, we tear down the delivery: how to keep the work and the customer moving after the kickoff. If you want help mapping your own lead-to-cash flow, look at my services, the free templates and the two-minute diagnostic, or tell me about your business.

What is the last thing your team found out about a job on the first day, and who knew it a week before? Tell me in the comments. I will not tell the dog.

General information, not legal, financial or tax advice. Examples are illustrative and the numbers are invented. Contracts, scope and what you promise customers are your business decisions; ask your lawyer to review your agreements before you rely on them.

Frequently asked questions

What is a project handoff?

A handoff is the moment a job passes from the person who sold or planned it to the people who will do it. It includes what was promised, what is excluded, the dates, the access and the customer's needs. Most delivery problems start here because the information lives in one person's head.

What should a handoff sheet include?

At minimum: the customer and contact, address and access, what was sold, what is not included, anything promised outside the quote, the dates, what you need from the customer and by when, the owner of the job and the kickoff date. Keep it to one page and use the same sheet every time.

How soon should the kickoff happen after the customer says yes?

There is no universal number, and I would not trust one given without a source. Measure your own median time from signed yes to kickoff, set a promise you can keep and put the kickoff on the calendar the day the yes arrives. The kickoff should happen before the work starts, not after the first problem.

Can AI do the handoff for me?

A tool can summarize an email thread or a quote into a draft of the handoff sheet, for a person to read and correct. It should not guess missing details, schedule work or promise dates on its own. Fix the process first, because automation makes a confused process faster, not better.

Monthly newsletterNext issue · Dec 1

Everything new, once a month.

One email on the 1st of every month with everything new: articles, series parts, news, website updates, project results, where I am working and the business opportunities I am looking at. No spam.

  • Fresh on the site right now
  • ArticleProcess Teardown, Part 3: The Handoff, from Signed Yes to Kickoff
  • NewsSalt Lake City pauses new data centers for up to 180 days: what a project manager sees in a hold
  • SeriesThe handoff: from signed yes to kickoff

One email a month, on the 1st. Leave any time.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Be the first to react.

Comments

Loading comments…

Leave a comment

No email and no sign-up. Every comment is reviewed before it appears. Please keep it respectful and leave links out.

Keep reading

More ideas you may like.

Keep exploring

Related projects and services.

Next step

Let's find the project that moves your business.

Tell me where things are stuck. I will tell you which project I would start with.