# Checklists vs Workflows: When Each One Works

- URL: https://www.herarx.com/blog/checklists-vs-workflows
- Published: 2025-09-02
- Topics: Productivity
- Publisher: Herarx

> A checklist makes sure nothing is forgotten; a workflow makes sure things happen in order, by the right person. How to tell which a process needs, and when to combine them.

Teams often argue about whether a process needs "a checklist" or "a proper workflow" as if one were a cheap version of the other. They solve different problems. **A checklist protects against forgetting. A workflow controls order, ownership and hand-offs.** Pick by asking which failure you are trying to prevent.

## What a checklist is good at

A checklist is a list of things that must be true or done, usually by one person, in roughly any order. It works when:

- The person doing the work knows how to do each step; the risk is skipping one.
- The steps are independent, or their order is obvious.
- One person, or one small team, owns the whole thing.
- The process is short: minutes to days.

Opening a new client file, closing a tenancy, preparing for a hearing, a pre-publication check: these are checklist jobs. The value is almost entirely in the discipline of ticking, which is why checklists work best short and specific. Twenty items that someone actually ticks beat a hundred that everyone skims.

## What a workflow is good at

A workflow is a sequence of states with rules about who moves the work from one to the next and when. It is needed when:

- **Work passes between people.** The hand-off is where things get lost.
- **Order matters.** Approval must come before payment; consent before data collection.
- **Something must wait.** For a signature, a reply, a deadline, a decision.
- **You need to see where everything stands** across many items at once.
- **Some steps need authority**, such as sign-off by a manager, not just completion by anyone.

Expense approval, a complaint that escalates, a job application moving through stages: workflow jobs. The risk is not forgetting a step; it is work sitting in someone's queue with nobody noticing.

## A quick test

Question | If yes

Does more than one person touch it? | Workflow, or a checklist with named owners per item

Does any step have to wait for another? | Workflow

Do you need a status report across many at once? | Workflow

Is the main risk skipping a step? | Checklist

Is it done start to finish by one person in one sitting? | Checklist

## Most real processes need both

The usual answer is a workflow whose stages each carry a checklist. A matter moves from intake to active to closing; each stage has its own short list of things that must be done before it can move on. The workflow gives you the overview and the hand-offs; the checklists make sure each stage is complete. Client onboarding is a good example: [the client onboarding checklist](https://www.herarx.com/blog/client-onboarding-checklist-professional-services) works much better when it sits inside the life of the matter rather than on a separate sheet.

## Common mistakes

- **Workflow for everything.** Six approval states for a task one person does in ten minutes. People route around it.
- **Checklist for a hand-off.** A shared list where "someone" ticks items and nobody knows who is next.
- **Checklists that never change.** Review them when something goes wrong; add the step that was missed and remove the ones nobody needs.
- **No due dates.** A checklist item without an owner and a date is a wish.

## Keep it visible

Either one only works if it is seen. Review open workflows weekly (see [how to run a weekly case review meeting](https://www.herarx.com/blog/how-to-run-a-weekly-case-review-meeting)), and make sure both survive absence; [holiday cover](https://www.herarx.com/blog/holiday-cover-keeping-matters-moving) is where undocumented processes fall over first.
