Shared checklists by team: how to hand work off without dropping the ball

Plenty of small-business work passes through more than one pair of hands. The front desk checks a dog in, then the groomers take over. The counter writes up a repair, then the shop does the work, then the counter calls the customer. The opening shift starts the day's list and the closing shift finishes it.

The work itself is rarely the problem. The hand-off is. Somebody finished their part and didn't tell anyone. Somebody else ticked a box that wasn't theirs. A ticket sat in "done with my part" limbo until a customer called to ask.

Here's a simple way to fix that: one checklist, split into parts, with each part owned by the team that does it.

Why one shared list beats two separate ones

The usual workaround is two lists: the front desk has theirs, the groomers have theirs. It works until it doesn't.

• Nobody can see the whole job at a glance.
• The second team doesn't know the first team is done unless someone walks over and says so.
• When something goes wrong, there's no single record of who did what.

A single checklist with sections keeps the whole job in one place and still makes it clear whose turn it is.

Give every section an owner

Split the list where the work changes hands, and give each part an owner: a team, or a specific person when one person always does it.

A grooming visit might look like this:

• Check-in (Front desk): checked in, vaccines verified, owner's phone confirmed
• Grooming (Groomers): bath, trim, nails
• Pick-up (Front desk): photo sent, paid, picked up

Ownership does two jobs. It tells people what's theirs, so the groomers aren't left wondering whether "vaccines verified" is on them. And it protects each part: only the team that owns a section can tick it off, so nobody accidentally checks a box for work they didn't do.

Let finishing a part do the handing off

The best hand-off is the one nobody has to remember. When the last item in a section is ticked, the work should move to the next team automatically:

• It lands in that team's queue, where whoever's free can pick it up.
• Everyone on that team gets a heads-up that their part is ready.
• The history records who finished what, and when.

No walking to the back to say "she's ready for you." No sticky note on the kennel. The list itself does the telling.

Hold the finish line until every part is done

Some things shouldn't close early. A repair shouldn't be marked done until the counter has called the customer. A boarding stay shouldn't close until the kennel has been cleaned.

Add a rule that a job can't close until the last section is complete. Now "done" means done, for everyone.

Tips that make it stick

• Split where the people change, not where the steps change. Three sections owned by two teams is fine. Ten tiny sections is a chore.
• Keep items short and checkable. "Bath" beats "Give the dog a bath using the appropriate shampoo." If it needs instructions, put them in your training docs.
• Name sections after the work, not the team. "Grooming" stays true even when the team gets a new name.
• Use a person as the owner only when it's always the same person. Otherwise give it to the team, so it doesn't stall on someone's day off.
• Look at the history when something slips. A shared list makes it easy to see where a job waited, so you can fix the hand-off instead of blaming a person.

How it works in TicketStacker

In TicketStacker, any stack can have a checklist field, and a checklist can be split into sections by team. Each section has a Done by team or person; on the ticket, your part is highlighted and the other teams' parts are read-only for you. When a section is finished, the ticket goes into the next section's team's queue (it shows in their queue and in Up for grabs on Today's Stack, and each of them gets a notice), or straight to the next person. A step rule can hold a ticket until a section, or the whole list, is complete.

The step-by-step setup is in Checklists and signatures. If you're new to giving work to a team instead of a person, group and location tickets explains how teams pick work up.

Try it

Pick one job that always crosses teams and write its checklist on paper first: what each team does, in order. That's your first set of sections. If you want help setting it up, join the pilot. It's free while we build TicketStacker with a small group of businesses.