Opening and Closing Checklists: Build Them With AI in an Hour

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Opening and Closing Checklists: Build Them With AI in an Hour.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Opening and Closing Checklists: Build Them With AI in an Hour.

Build opening and closing checklists with AI by walking through the real routine, recording each task, and asking the assistant to turn those notes into observable checks with owners and failure actions. Allow an hour for a first usable version, then test it on actual shifts before treating it as the approved routine.

The hour works when your operating procedures already exist and the right people are available. AI can organise instructions, but it should not invent food-safety limits, equipment shutdown steps or emergency procedures. Keep those linked to your approved documents and have the responsible person check the draft.

Follow me on Instagram@sagnikteaches

Set a sixty-minute session with something real to inspect

Bring the opening lead, the closing lead and the person who can approve the routine. In a very small business, one person may hold more than one role. Have the current checklist, equipment instructions, relevant safety procedures and recent handover notes ready. Start at the place where the shift actually begins.

Connect on LinkedInSagnik Bhattacharya

Agree the scope in one sentence: “This checklist covers preparing the food truck for service and handing it over safely after service.” Keep weekly maintenance, monthly stocktakes and unusual event setup in separate routines unless they genuinely form part of every shift. A daily list becomes hard to use when it contains everything the business might ever do.

Subscribe on YouTube@codingliquids
MinutesActivityResult to keep
0–10Walk the opening and closing route.Rough notes in the order work happens.
10–20Check procedures and recent failures.Required checks, owners and escalation rules.
20–32Ask AI to structure the notes.Separate opening and closing drafts.
32–45Walk through the draft with a colleague.Missing tasks and ambiguous wording marked.
45–55Correct the draft and test exception cases.Reviewable pilot version.
55–60Name the owner and arrange the live trial.Dated version, storage place and review date.

If the session reveals a missing safety procedure, record the gap and assign it to a competent person. Do not spend the last five minutes asking AI to invent a substitute so you can claim the list is finished. You can still publish the non-critical draft for review while keeping affected operations under the existing approved controls.

Capture actions and evidence while walking the route

Ask the person doing the job to describe what they check, what a satisfactory result looks like and what happens when the result is wrong. Record plain notes. “Check fridge” is incomplete. “Record the unit reading and compare it with the approved operating range; follow procedure F-02 if outside range” identifies the evidence and the response.

Use your actual document references instead of the illustrative F-02. Do not put door codes, alarm codes, passwords or sensitive customer details into the AI prompt. The checklist can refer authorised staff to secure instructions without reproducing those instructions in a widely shared document.

For each task capture five things: action, responsible role, completion evidence, exception route and sequence dependency. A dependency means one action must happen before another, such as confirming the service area is ready before admitting customers. Let the experienced worker identify those relationships.

Illustrative before and after: a butcher's rough note says “Fridges OK”. The improved check says, “Record each listed unit's reading, compare with the approved range and record any exception against the unit reference.” The checklist points to the existing response procedure. It does not supply a guessed universal temperature or allow a tick to replace the required record.

Keep the distinction between a checklist and a procedure. A checklist confirms that an action has been completed; a procedure explains how to perform it. Link to or name the full instruction when the task needs detail. The procedure-writing tutorial helps develop those underlying instructions separately.

Give the assistant your notes and clear boundaries

Use Claude or another approved writing assistant to organise the notes into two lists. No integration is required for the first version. Paste only the relevant operational information, ask the assistant to identify gaps and keep its suggestions visibly separate from instructions already approved by the business.

Turn these shift notes into separate opening and closing checklists.
Use columns: check, owner role, evidence, if not complete.
Write one observable action per row and follow the physical route.
Use only the supplied procedures and limits.
Mark missing safety instructions as REVIEW REQUIRED.
Do not invent temperatures, chemical quantities, shutdown steps,
passwords, alarm instructions or emergency actions.
Keep suggested improvements separate from approved instructions.
Statuses must be: Done, Issue, Not applicable, Not started.
Require a reason and approval for Not applicable on critical checks.
End with unanswered questions for the shift lead.

Illustrative prompt result: notes saying “count returned boards, usual 24, tell lead if short” become “Count returned serving boards; closing assistant; record actual count against dispatch count; report any difference to the shift lead.” This is usable after checking the role and the actual dispatch record.

An unsafe edit would be “Confirm all 24 boards returned” with a pre-filled tick. That wording encourages confirmation rather than a count and assumes every event used 24. Correct it to require the actual expected and returned quantities. AI should make the evidence easier to record, not write the desired result in advance.

Ask the assistant to list duplicated tasks and instructions that conflict. Review its suggestions with the people doing the work. A task appearing twice may be a deliberate independent check; do not remove it simply because AI calls it repetitive. Record why the second check exists.

A food truck turns eighteen vague reminders into daily checks

For this illustrative main example, a food truck has two people on a normal shift. Its old sheet contains 18 reminders, including “stock”, “clean”, “payments” and “lock up”. Staff tick most boxes, but the owner still receives questions about missing packaging and whether equipment has been left in its required overnight state.

The team walks the actual route and consolidates the reminders into eight opening checks and seven closing checks. Detailed food handling, cleaning, equipment and security procedures remain separate. Each checklist entry refers to the relevant approved procedure where needed. The examples below show the format, not a complete operating or safety specification for every truck.

The opening list follows the service setup

CheckOwnerEvidenceIf not complete
Read the previous shift's unresolved handover.Shift leadEach open issue acknowledged and assigned.Resolve or escalate issues affecting service before opening.
Complete the approved access and readiness inspection.Shift leadInspection record with time and initials.Follow the relevant exception procedure.
Record required storage checks.Preparation leadUnit references and readings in the approved log.Use the food-safety response procedure.
Confirm the day's menu information is approved.Preparation leadCurrent menu and ingredient-information version recorded.Resolve discrepancies before selling affected items.
Count service packaging against the shift plan.Service assistantActual quantities and shortages recorded.Ask the lead to adjust or replenish the plan.
Complete the approved payment-readiness check.Service assistantPass or issue recorded without customer payment data.Use the agreed payment-failure process.
Complete the service-area preparation checks.Service assistantRequired cleaning and setup records completed.Finish missing work and report any blocker.
Review critical issues before authorising service.Shift leadOpening decision and time recorded.Follow the approved rule for any unresolved critical issue.

The packaging check now has a useful number. For an illustrative forecast of 90 orders, the owner has approved a starting stock of 110 bowls for that shift. The assistant counts 84, records a shortage of 26 against the plan and alerts the lead. This is a local stocking decision, not an industry buffer recommendation.

The lead can arrange replenishment or change the service plan before customers queue. “Packaging checked” would not reveal either the quantity or the decision. Keep calculations such as 110 minus 84 visible so staff do not have to rely on an AI-generated explanation for a simple shortage.

The closing list leaves a usable handover

CheckOwnerEvidenceIf not complete
Account for outstanding customer orders.Shift leadEvery open order has a recorded outcome or owner.Resolve or hand over explicitly.
Complete the approved stock and food-handling close.Preparation leadRequired stock, waste and storage records.Follow the relevant procedure and notify the lead.
Complete required cleaning checks.Service assistantCleaning record and unresolved exceptions.Finish or escalate before sign-off.
Reconcile the shift's payment records.Shift leadExpected total, actual total and any difference.Record the difference and follow the review process.
Put each asset into its approved overnight state.Assigned authorised personAsset-specific checklist completed.Use the equipment procedure; do not improvise.
Write the next shift's exceptions and shortages.Shift leadIssue, owner, action and due time.Assign any issue without an owner.
Complete the approved security close.Authorised closerSign-off using the business's secure process.Follow the security exception procedure.

The owner deliberately rejects the AI suggestion “Switch off all equipment”. Some assets may have a required overnight operating state. The correct checklist points to the approved asset instructions and records completion without giving staff a blanket instruction that could cause damage or spoilage.

In an illustrative timing trial, these checks take 14 minutes to open and 17 minutes to close, including the routine work being checked. Those are observed example timings, not a promise. If the business previously allocated only ten minutes for each, the manager must change staffing or the process rather than encourage premature ticking.

Adapt the evidence to five different businesses

Delicatessen: “Update the board” becomes “Compare today's display labels with the approved product-information sheet, record its version and report mismatches before selling the affected item.” The check points to the business's established ingredient and dietary-information process. Staff should not ask AI to infer information from a product photograph.

Furniture maker: “Machines ready” becomes “Confirm the required pre-use inspection for each scheduled machine is complete and check for unresolved maintenance restrictions.” An inspection record is evidence; a photograph of a clean machine is not proof that it passed. Equipment instructions and authorised maintenance decisions govern whether it can be used.

E-commerce homeware brand: the closing team has 112 orders showing as ready to dispatch, but only 109 appear in the approved dispatch record. The check requires the three unmatched order references and an owner for each. It does not allow “dispatch complete” because the warehouse looks empty.

Catering company: an event dispatch record lists 24 serving boards, while the return count is 23. Record the difference of one and assign a follow-up before the next event. Do not let AI mark the kit complete because the usual stock level is 24. The relevant evidence is the actual count against that event's dispatch record.

Butcher: an opening delivery check identifies one item whose label does not match the order reference. The checklist records the item reference and follows the approved goods-in exception process. It should not offer “accept likely substitute” as an AI-generated shortcut. A named person resolves the discrepancy using supplier information.

These examples need different evidence, even though the checklist columns are similar. Use the process-mapping tutorial if staff disagree about where a check belongs. Resolve who does the work and when before building reminders around it.

Make an unresolved item impossible to mistake for completion

Use four clear states: Done, Issue, Not applicable and Not started. For Done, capture the evidence the task requires. For Issue, require a description, owner and next action. For Not applicable, require a reason and any approval your critical-check policy calls for. A blank field means the task is not yet recorded as complete.

Illustrative handover: “Packaging low” becomes “Only 84 bowls counted against tomorrow's approved plan of 110. Shift lead to arrange 26 more before setup; incoming lead to acknowledge.” This separates observation, action and responsibility. Do not automatically copy yesterday's completed status into today's checklist.

Define which issues block opening or closing sign-off using the business's approved safety and operating procedures. Other issues may allow work to continue with a named follow-up. AI can format that distinction once supplied; it should not decide that a safety-related item is minor because resolving it would delay service.

If one person performs and signs the whole routine, be honest about that arrangement. Do not create a fictional second check in the record. Where an independent check is required, organise real cover. Elsewhere, a later manager review of exceptions may be more practical than an unused approval box.

Keep the first version simple enough to use at the door

A printed sheet or shared spreadsheet is sufficient for the pilot. Give it a title, operating area, shift date, version, responsible roles and a place for exceptions. Keep the current approved version in one known location and remove obsolete copies from use once the replacement is approved.

Excel can use data validation to offer a list of allowed status values. That can reduce spelling variations such as “finished”, “yes” and “all good”. It does not prove the physical task happened. Choose the format that staff can actually reach during the shift, including an agreed fallback if their normal device or connection fails.

Allow an illustrative hour of owner time and half an hour of colleague time for the drafting session. At an internal value of $30 an hour for both, that represents $45 of staff time. An optional Claude Pro subscription has a list price of $20 a month. You can also organise the same notes manually without a new tool purchase.

Test the draft through one real opening and one real closing before approval, and continue reviewing the first week's records. Watch where staff pause, skip a row or ask what a word means. Replace vague verbs such as “ensure” with an action that someone can demonstrate or record.

Review exceptions before adding reminders or automation

During the first week, count missed checks, unresolved issues carried into the next shift and tasks that staff say cannot fit the allotted time. Read the comments, not just the completion percentage. A list can show 100% completion while staff tick items before doing them because the sequence is wrong.

Use AI to group redacted exception notes into recurring themes, then check each theme against the original entries. Three packaging shortages suggest a purchasing or forecasting issue. Three forgotten signatures may suggest the sheet is stored in the wrong place. Those problems need different fixes.

Only add automatic reminders after the routine works. If an exception should create a task or require approval, follow the approval-step tutorial and keep a named person responsible for the result. A notification sent is not the same as a problem resolved.

The checklist is ready for normal use when staff can follow the route, understand the evidence required, identify issues and hand them over without relying on the owner's memory. Give the document a review owner so changes in equipment, menu, staffing or workflow lead to a checked revision, not a growing collection of handwritten exceptions.

Further reads

Sources: Microsoft Support, Apply data validation to cells. Anthropic, Claude pricing page (Pro list price, checked September 2026). Checklist examples are illustrative and require the business's approved operating and safety procedures.

Want checklists staff will use on a busy shift?

On a 1:1 call, we can map your opening and closing routines, define the checks that need evidence, and plan a simple handover for unresolved items.

Book a 1:1 call with me