Logbook user guide

The Logbook is a free feature that comes with Tenzo’s Sales Module. It gives anyone with a Tenzo login, front of house or back of house, a simple way to write up the day and share it with the rest of the business.

Instead of the handover living in a WhatsApp group or a notebook behind the pass, it sits next to your sales figures, where anyone who needs it can search it months later.

You can open the Logbook from any page of the web app, or from the mobile app, to write a new entry or read back through old ones.

Two words worth knowing #

A logbook is the template: the headings your team fills in, and the sites that use it. “End of day report”, “Pre-shift briefing” and “Maintenance” would each be a logbook.

A log is one entry: one site, one day, one person. Monday night’s end of day report from Air Street is a log. So is Tuesday’s.

You set up a logbook once. Your team writes a log against it every day.

---

Writing a log #

Go to Logs in the left-hand menu and choose Submit a log. The form opens down the right-hand side of whatever page you were on, so you can write up the night while you are still looking at the numbers.

1. Check the date, the logbook and the site #

   These three boxes sit across the top. The date fills itself in with your operating day, not the calendar day, so a log written at 1am still counts as the night before. Change it if you are catching up on a day you missed.

   You will only see logbooks and sites you have access to.

2. Fill in what matters #

   The headings come from your template, with any guidance your team added underneath them. Nothing is compulsory, so a quiet Tuesday can be three lines. Each box holds about 3,000 characters, which is roughly a page of typing, and a counter appears if you get near it.

3. Submit #

   You will see a short confirmation and the form clears, ready for the next one. If you close the panel with something half-written, Tenzo checks before throwing it away.

On mobile, the same menu gives you Submit a log and View all logs, with the filters in a drawer that slides up.

---

Reading logs back #

Logs › View logs shows every log from the sites you have access to, newest first. You can narrow it down by:

• Date, as a range of operating days
• Logbook, if you run more than one
• Site
• Author, to see everything one manager has written
• Keyword, using the search box. Matches are highlighted for you

Use Compact to scan a week at a glance, or Expanded to read the entries in full without opening each one. Click any log to open it, where you can edit or delete it.

If you want to go further, for example every mention of “walk-in” across six months and all of your sites, use the Go to card creator link beside the search box. That builds it into a card you can save.

---

Setting up a logbook #

This part is for admins. If you can see Manage logbooks under the Logs menu, you have what you need. If you cannot, ask whoever looks after your Tenzo account.

Go to Logs › Manage logbooks and choose + Create logbook.

1. Pick a starting point #

   Choose one of the ready-made templates, or start from scratch. A template is only a head start. You can rename, reorder and remove anything in it afterwards.

2. Name it and choose the sites #

   Give it a name your team will recognise, then tick the sites that should use it. Only people with access to those sites will see it. You need at least one.

3. Build the headings #

   + Add section creates a heading like Team or Food. + Add sub-section creates the question underneath it that people actually type into.

   • Drag anything to reorder it, including moving a question from one heading to another.
   • The ⋮ menu on any row lets you add guidance, duplicate it or delete it.
   • Guidance shows up underneath the heading when your team fills the log in. It is the place to say “any discount over 0.5%, and why”.
   • Names are capped at 50 characters, so keep headings short.

4. Check the preview, then create #

   The right-hand panel shows how the log will look once it is on a dashboard, updating as you type. When you are happy, choose Create.

Changing a logbook later #

Editing a live logbook is safe. Logs already written keep the words they were written with, so a report from March still reads exactly as it did in March.

• Adding a heading changes nothing that came before it.
• Renaming one means older logs keep the old name and newer ones use the new name. Worth doing when the meaning has genuinely changed, less worth it for tidying up wording.
• Removing one stops people being asked, but the answers already given are still there when you open those logs.

Deleting a whole logbook stops new entries. The logs written against it are kept, and you can still find them by switching on Show deleted and legacy in the Logbook filter.

---

Template examples #

Here are four our customers use. Start with whichever is closest and change it to suit you. Keep them text only.

Those descriptions underneath each heading are exactly what the guidance field is for. Add them when you build the logbook and your team gets the prompt in front of them every night.

---

Getting logs into your daily email #

Logs read best next to the numbers they explain. An 8% beat on forecast means a lot more when the note beside it says the terrace was full all afternoon.

Add a log card to your Email Report Dashboard the same way you add any other card. From Manage logbooks, open Log cards and choose one of two starting points:

• Full logs gives you the whole entry, laid out as it was written. Best for a daily read.
• Entry by sections gives you one row per heading, as a table you can filter. Best for following one heading over time, or comparing sites.

Add it to a dashboard and it arrives with tomorrow morning’s email, alongside your revenue and your KPIs.

---

Five ways to get more out of it #

These come from customers who have had the Logbook running for years.

1. Start with a template, and keep improving it #

   Structure is what gets logs filled in properly. Begin with something basic, Team, Food, Maintenance, AOB, then work with your team to sharpen it over the following weeks.

2. Make it part of the routine #

   Talk to your team about why it is worth having in one place rather than spread across WhatsApp, then agree when it gets done: after every service, or once at close.

3. Encourage extra entries #

   A problem with delivery orders, or a brilliant piece of guest feedback, is worth logging even when it is not end of day. Anything captured is something you can find again later.

4. Put them in the daily report #

   Reading the write-up next to the revenue gives you the full picture of yesterday instead of half of it.

5. Review them together, regularly #

   Bring the logs to your team meetings. Share good examples, look for the problems that keep coming back, and change the template when it is not asking the right questions.

---

Questions we get asked #