Checklist vs. task — how to structure shift work

"Just add it to the list" is the default answer in most hospitality operations. It's a fine default. But if the list becomes the only answer, you end up with either a task mountain or a checklist so long nobody reads the last item.

Here's how we think about the difference.

A task is a piece of work

A task has an owner, a deadline, a status, and a "done" that means something. It's the unit you'd assign to a person and follow up on. Examples:

• "Fix the leak in the walk-in fridge."
• "Call supplier about Tuesday's delivery."
• "Onboard the new waiter."

Tasks are worth tracking individually because they can go wrong in ways that matter. They can be blocked, reassigned, or escalated. They have a history worth keeping.

A checklist is an atomic routine

A checklist is a sequence of small steps that all belong to the same piece of work. It's not five tasks — it's one task with five parts. Examples:

• "Opening checks" — lights, music, cash float, fridge temps, mise-en-place.
• "Closing checks" — same but in reverse.
• "Room turnaround" — strip, clean, reset, inspect.

A checklist item, on its own, isn't really a unit of work. "Check the music" doesn't need an owner — it needs the opening checklist to happen.

The test

Ask two questions:

1. Could this be "blocked"? Tasks can be blocked. Checklist items can't really — if the music is broken, that becomes a new task, but the checklist item is still just "check the music."
2. Would you follow up on just this? If the answer is yes, it's a task. If you'd only notice it as part of a larger routine, it's a checklist item.

When to convert

The most common mistake is starting with a long list of tasks for a routine and realizing later it's one task. The reverse also happens: a "single task" grows tentacles and should have been a parent task with sub-items.

Rules of thumb:

• If a routine has more than three steps and is done in one sitting, make it a task with a checklist.
• If a "task" keeps spawning clarifying questions in its comments, split it.
• If you find yourself copy-pasting the same checklist into different tasks, extract a template.

How Shifo models this

In Shifo, a task has a status, assignees, a due time, and a checklist of sub-items. Templates let you reuse common checklists. Recurring rules put them on a schedule. And tasks live alongside the shifts on your roster, so the work and the people who do it stay in the same view.

The unit you share with someone is the task. The checklist is how they work through it. Get the boundaries right, and your shift goes from "what am I supposed to do next?" to "next item."

That's the whole game.