Opening a restaurant is a long list in one person's head: the alarm, the lights, the tables, the till, the specials. On a busy morning something slips. I would give the manager one short form to run through, then read it later.
Before service
The manager enters a name and the date, then picks opening. The opening jobs are the alarm and lights, the dining room set, restrooms stocked, the till float counted, specials agreed with the kitchen, fridge temperatures logged and the team briefed.
While the shift ends
For closing, the manager picks closing instead. The jobs are the till counted and takings secured, doors and windows locked and the alarm set. A box catches anything that needs attention.
A manager's AI might ask "Are you opening or closing?" Then "Is the alarm off and the dining room set?" Then "Is anything broken or missing?" It shows every answer and sends only after a yes. See agent-fillable forms.
After the shift
Download the CSV and sort by date and check type. Look for days with no closing entry, and compare the staff count with your rota. The back of house has its own kitchen cleaning checklist. Guests who want a table can use a restaurant reservation form. Afterwards, diners can reply on a restaurant feedback form. Browse forms for restaurants and food businesses and forms for IT and operations.
Questions
Can one form cover both opening and closing?
Yes. The first question asks whether this is an opening or a closing check. Filter the CSV on check_type to read each one separately.
Who should fill it in?
The manager on duty, or whoever opens or locks up. The name question shows who logged each check, so you can compare it with the rota.
How do I make sure nothing is skipped?
Leave the task boxes optional so the log stays honest. An unticked box shows as a gap in the CSV, and the issues box explains it. The form sends no reminders.