Published November 19, 2026.
A shutdown routine often lives in one supervisor's head. When that person moves to another shift, the next supervisor inherits a site with no clear close-out. The result is a missed lock, an unplugged freezer, or an open request that nobody owns. A written checklist protects the site and makes the transition boring.
Start from the risks that stay the same
List the conditions that must be true at the end of every shift regardless of who is working. Locks, equipment state, safety checks, and open customer requests are common examples. These conditions do not change when a supervisor changes. They form the stable core of the checklist.
Separate a condition from a task so the list stays useful. A condition describes the end state, while a task describes how to reach it. The next supervisor may use a different task and still meet the same condition. Write conditions wherever possible so the checklist does not over-specify.
Ask two supervisors who rarely work together to compare their close-out habits. Their answers show which steps are truly shared and which are personal. Shared steps belong on the checklist and personal steps belong in a note. This comparison also reveals a step that only one person knows.
Put the checklist in the order of the shutdown
Walk the site at the end of a real shift and write down what you do in sequence. The order matters because some tasks depend on others. A freezer must be checked before the area is locked, not after. Follow the walk once and resist the urge to reorganize it on paper.
Group the steps into a small number of stages such as safety, equipment, records, and locks. Stages help a new supervisor see the shape of the shutdown. They also make it easier to pause if an emergency interrupts the routine. A four-stage list is easier to remember than twenty loose items.
Keep the checklist on one page. A long checklist gets folded into a pocket and ignored. If the list needs more space, move the detail into a reference guide. The one-page version is the working tool.
Make each step observable
Write each step as something a second person could verify. "Check the freezer" is weaker than "record the freezer temperature and confirm the door seals." The second version leaves evidence and cannot be satisfied by a glance. Observable steps reduce the chance that a rushed supervisor skips one. They also make it easier to hand the routine to someone who has never done it before.
Add a space for the time and initials beside each critical step. The time shows when the step was completed and the initials show who did it. This is not surveillance, because the record protects the person who followed the routine. If a question arises later, the record answers it.
Mark the steps that can be delegated and the steps that must stay with the supervisor. Delegation keeps the shutdown moving when one person is busy. Some steps, such as the final lock check, should remain with the person accountable for the site. A clear split prevents confusion.
Write one handover line for the next shift
End the checklist with a single line that names the state of the site and any open item. The line should say whether the site is secure, what is still running, and who owns the open item. It is the first thing the next supervisor reads. Keep it short enough to fit on the same page.
Avoid repeating the entire checklist in the handover line. The checklist is the record of what was done, and the line is the summary of what remains. A summary that repeats everything hides the one item that matters. Write the exception rather than the routine.
Ask the incoming supervisor to sign the line when the site has more than one shift. The signature confirms that the handover was received and understood. It does not confirm that every step was correct. It confirms that someone accepted responsibility for the next period.
Test the checklist during a supervisor change
Use the first week of a new supervisor as a live test of the checklist. Watch whether the steps are clear without the previous person present. Note any step that requires a call to the old supervisor. Each call is a sign that the written version is incomplete.
Ask the new supervisor which step felt ambiguous and why. Their answer is more useful than a general review because it comes from use. Update the wording rather than adding another step. A small wording fix often removes the need for a long explanation.
Have the outgoing supervisor review the changes before they leave the site. Their knowledge can catch a missing condition or a wrong sequence. Keep the review short and focused on accuracy. The goal is a checklist that the next person can trust.
Handle exceptions without rewriting the list
Some nights bring a broken freezer, a late delivery, or a safety incident. The checklist should say what to do when a normal step cannot be completed. A short exception rule keeps the shutdown honest when conditions are unusual. Without a rule, people either skip the step silently or improvise alone.
For each critical step, name the person to call and the condition for stopping work. The rule should be specific enough to use under pressure. It should also allow a supervisor to leave a step open with a note. An open step with an owner is better than a false checkmark.
Record exceptions in the same handover line as the open items. The next supervisor needs to know that the site is not in its normal state. A clear exception protects the next person from making a wrong assumption. It also creates a record if the issue repeats.
Review the checklist every quarter
Read the checklist with the supervisors who use it once a quarter. Ask whether any step has become obsolete or any risk is missing. Equipment changes and layout changes often make a step unnecessary. New work often introduces a risk that the old list does not cover.
Compare the checklist with any incident reports from the period. A repeated incident may point to a missing condition rather than a careless person. Update the list and tell every supervisor what changed. A change that is not communicated will not be used.
Keep the checklist version and the date of the last review at the top. A visible version helps a supervisor know they are using the current list. It also makes an audit straightforward. Over time, the checklist becomes part of how the site changes hands.
