What goes on a daily ops checklist?

A daily ops checklist is the set of recurring tasks tied to a shift, opening, mid-shift, and closing, that a store completes the same way every day. Each item has an owner, a time window, and a proof requirement. That proof can be a checkbox, a temp reading, a photo, or a signature. What changes by vertical is the content of the items, not the structure.

Every daily ops checklist shares four building blocks, no matter the format:

1. Opening tasks establish that the location is safe and ready to operate. Equipment on, temps in range, cash counted, signage correct.
2. Mid-shift or line-check tasks catch drift before it becomes a failure. Re-check temps, restock, walk the floor.
3. Closing tasks secure the location and set up the next open. Clean-down, reconcile, lock-up, certification.
4. Shift handoff transfers accountability from one team to the next. What got done, what is pending, what is broken.

The proof layer is where a digital checklist beats paper. A clipboard captures a checkmark. A tablet captures the checkmark, the timestamp, and the person who did it. That is the difference between a task list and a standard operating procedure with real compliance evidence.

The stakes differ by vertical, but the mechanic does not. The National Restaurant Association ties food safety standards to documented daily procedures, and a checklist is the first layer of proof. The NRF reports retail shrink is nearly a $100 billion problem, and structured open and close routines are a frontline defense. Different stakes, same checklist habit.

Sample daily ops checklist by vertical

Each vertical runs a different list, in its own native vocabulary, on the same engine. Below are four sample checklists. They map directly to the deeper cluster guides for each format.

Restaurant and QSR opening checklist

A restaurant open is built around food safety and line readiness. The temp spine drives the list.

1. Unlock, disarm the alarm, turn on lights and hood vents.
2. Power on the line, fryers, grills, and hot-hold wells.
3. Log the walk-in cooler temp (must read 41°F or below per the FDA Food Code).
4. Log freezer and reach-in temps.
5. Run the opening line check, verify prep levels and FIFO rotation.
6. Calibrate and verify thermometers.
7. Confirm hot-hold units reach 135°F or above before service.
8. Count the opening drawer and verify the safe.
9. Walk the dining room and patio, check cleanliness and table setup.
10. Confirm restrooms are stocked and clean.
11. Verify drive-thru equipment (headsets, timers, menu board lit).
12. Review reservations, catering, and LTO prep for the day.

The FDA Food Code sets the danger zone at 41°F to 135°F, with cold TCS food held at 41°F or below and hot TCS food at 135°F or above. The USDA FSIS danger-zone guidance frames the same range. For the full open, see the restaurant opening checklist guide, and for the mid-shift re-check the restaurant line check for mid-shift.

C-store opening and shift-handover checklist

A c-store open adds the forecourt. The pumps, the reader board, and the fuel price are the items a restaurant never sees.

1. Disarm, lights on, sign in.
2. Walk the forecourt. Check pumps, pick up litter, refill squeegee buckets, check air, vacuum, and car wash.
3. Verify fuel pricing on the reader board matches the POS and the corporate price.
4. Log cooler and walk-in temps. Check roller grill and hot-hold food safety and labeling.
5. Stock coffee, fountain, and never-out items.
6. Count and verify the drawer. Check the safe.
7. Confirm age-restricted sales prompts are active for tobacco and alcohol.
8. Check restrooms, floors, and mats.
9. Review surveillance and the communication log from the prior shift.
10. Complete shift handoff: what is stocked, what is low, what is broken, any overnight incident.

The forecourt walk (pumps, squeegees, air and vacuum, reader board) is the documented c-store daily standard per NACS Store Operations. For the handoff mechanic, see the c-store shift handover guide, and for the QSR forecourt-adjacent variant, the QSR drive-thru opening checklist.

Retail closing checklist

A retail close leans on loss prevention and cash discipline. The drawer and the fitting room are the high-risk items.

1. Announce closing, clear and lock fitting rooms.
2. Empty, count, and sign off on items left in fitting rooms.
3. Reset the floor to the planogram standard. Refold, re-face, re-size.
4. Run end-of-day cash reconciliation. Recount any over or short past the threshold and have a second party sign the discrepancy report.
5. Process returns and hold items.
6. Run a cycle count on flagged SKUs.
7. Power down non-essential displays and equipment.
8. Verify the alarm, security cameras, and back-door lock.
9. Set the floor for tomorrow's open.
10. Complete the closing sign-off and handoff note.

Cash-handling discipline with dual sign-off is a standard retail closing control. The NRF found shrink accounted for over $112 billion in industry losses in 2022, so these controls are not optional. For the full close, see the retail closing checklist guide.

Hotel housekeeping room-turnover checklist

A hotel runs room turnover as its daily ops loop. Turn time is the KPI. Inspection is the proof gate.

1. Pull room status from the PMS. Prioritize checkouts and pre-arrivals.
2. Strip and replace all linens.
3. Deep-clean the bathroom and sanitize high-touch points (door handles, remotes, switches).
4. Dust, vacuum, and restock amenities to par.
5. Make the bed to brand standard.
6. Inspect for damage, left-behind items, and maintenance needs. Log any guest or maintenance request.
7. Set climate and lighting to arrival standard.
8. Mark room status (clean, inspected, ready) and log turn time.
9. Run the supervisor pre-arrival inspection on flagged rooms.
10. Hand off open requests and DND rooms to the next shift.

AHLA Safe Stay guidance emphasizes structured sanitization and high-touch disinfection on each turnover. For the supervisor proof gate, see the hotel housekeeping pre-arrival checklist.

How does Xenia track checklist completion?

Xenia tracks completion as a live percentage per location and per shift. Every item is checked off with a timestamp, and items can require a photo or a temp reading as proof. By a set hour, the area manager sees who is at 100% and who is not, across every location, with the missing items flagged. The completion percentage becomes the store's pulse.

Here is the concrete mechanic. Opening, mid-shift, and closing checklists are configurable templates, built once and scoped by role and location. They are not AI-prioritized. A manager builds the list, sets the proof requirement on each item, and assigns it to the right shift. Each item supports photo proof and a timestamp. Conditional visibility means a store only sees the items it actually has. A fuel-only c-store does not see the tap-system temp questions. A hotel without a pool does not get pool items. Nullify scoring means the items a location does not have do not count against it, so N/A items never tank a store's score.

A worked example. A store manager opens at 6am. The tablet shows 22 opening items. Each is photographed and timestamped. By 7am the DM can see across 12 stores: 11 at 100%, one at 73% with the missing items flagged. The DM calls that store first, not all twelve.

| Attribute | Manual paper checklist | Xenia tablet-based |
|---|---|---|
| Completion proof | Checkmark only, no time or person | Timestamp, photo, and the person who did it |
| Real-time DM visibility | None until the binder is reviewed | Live completion percentage by set hour |
| Multi-vertical reuse | Re-printed per format, no link | One engine, items configured per location |
| Offline mode | Always works, never syncs | Works offline, syncs when connectivity returns |

The same completion screen works whether the items are walk-in temps, a forecourt walk, a planogram reset, or a room turnover. The engine does not change. The configured items do. The daily completion habit also creates the on-ramp to audits. A common adoption pattern is that teams start with daily ops, get the completion-rate habit, then graduate to weighted audit scoring with critical-item thresholds once the daily habit is the foundation. When a closing checklist surfaces a broken pump or a dead cooler, the same app routes it as a QR-code work request with no login required.

How to roll out a daily ops checklist in Xenia

Roll out a daily ops checklist in five steps: build the template once, configure per-location visibility, assign by role and shift, set the proof requirements, then watch completion percentage and tighten from there. Most operators start with one shift, usually opening, at a pilot group of stores before pushing to the full fleet.

1. Build the template once. List the items for opening, mid-shift, and closing. If the SOP already exists as a PDF, the AI Template Agent converts it to a digital form with required fields in minutes. It transforms an existing SOP. It does not invent one.
2. Configure conditional visibility per location. Tag which formats see which items: tap-system versus fuel-only, patio versus no-patio, pool versus no-pool. Stores only see what they have, and nullify scoring keeps N/A items from counting against them.
3. Assign by role and shift. The opening team sees opening items. The closing team sees closing items. Location hierarchy means a DM sees their district and a regional sees all regions.
4. Set proof requirements. Decide which items need a photo, a temp reading, or a signature. A temp out of range can trigger a follow-up question and a required photo, then auto-create a corrective task.
5. Pilot, then scale. Start opening checklists at a handful of stores. Confirm the completion habit sticks. Then roll to the full fleet and add mid-shift and closing.

Sign-offs every shift keep standards consistent across the fleet. That is the discipline that turns a one-time rollout into a daily habit your teams actually run.

Where do operators see results?

Operators see daily-ops results in three places. Completion percentage climbs and stays high. Manager phone calls drop because the DM can see status without calling. And the paper clipboard disappears. The daily habit then becomes the foundation for audits and food-safety compliance.

The numbers come from real multi-location rollouts:

• Power Market went live across 360 c-store locations with bilingual checklists and QR deployment, and saw 40% faster task resolution. See the Power Market c-store daily ops rollout.
• Mezeh cut manager phone calls by 60% after moving daily ops into the app.
• Tempstop went paperless in 14 days. See the Tempstop paperless migration story.
• Cook Out runs a weekly price-change process plus line-check temperature capture across 335 locations.
• Newk's Eatery automated 100-plus franchises in one rollout. See the Newk's Eatery restaurant automation story.
• H&S Energy runs a fuel price form with 4,000-plus submissions across 360-plus stores.
• Refuel runs offline mode for rural fuel stops and a DM-to-Regional escalation flow on incident reports. Refuel kept Service Channel for asset depth and added Xenia for frontline ops, a complementary buy, not a migration.

The thesis is the same across every format. The daily-ops habit is the foundation. Operators adopt daily ops first, get the completion-rate habit, then graduate to audits. The same checklist engine that runs a restaurant open also runs a c-store forecourt walk, a retail close, and a hotel room turnover. One platform, configured per location. For the c-store seat specifically, see how convenience store operations software handles the forecourt-to-audit path. Daily ops is not a single-vertical tool. The items differ by format. The engine does not.