Capturing your venue's knowledge as staff come and go

Capturing knowledge in hospitality means putting the way your venue actually works in one place your team can reach, so that knowledge stays with the venue instead of living in one person's head. Not a manual nobody reads, but the recipes, ways of working, agreements, and changes that otherwise only pass on by word of mouth. Why it matters most when staff keep changing, and how to do it in practice, is below.

Why turnover makes the problem visible

Hospitality is a high-turnover industry. According to ABN AMRO (2019), annual staff turnover in Dutch hospitality runs around 40 percent. That means a large share of your team a year from now will be different people.

Every time someone leaves, knowledge leaves with them. Not the recipes on the menu, but the small stuff that was never written down: who to call when a supplier does not show, how that one machine really works, the agreement with the neighbours about the bins. As long as the person who knows it is around, nobody notices. The day they are gone, you find out which piece of knowledge is missing.

The cost is not small. ABN AMRO (2019) calculated that turnover costs a hospitality business more than 42,000 euros a year, roughly 6 percent of revenue. Replacing one full-time cook costs almost 30,000 euros, someone on the floor around 15,000 euros. Part of that is hiring and training. But a quiet part is simply the knowledge that has to be rebuilt, because it never lived anywhere.

What you should capture

Not everything needs recording. The menu and the standard recipes are usually findable already. What matters is the knowledge that only lives in heads right now, the knowledge you lose to turnover:

• Ways of working that are not obvious. How the coffee machine gets descaled, the order the opening routine goes in, how the till is closed out. Everything a new colleague currently has to tap someone on the shoulder to learn.
• Agreements that are not on paper. The deal with the neighbours, the supplier you have to call on a specific number, the campaign whose vouchers are still valid until year end.
• Phone numbers for when something goes wrong. The plumber, the refrigeration engineer, the landlord's emergency line, the owner, the alarm company. The numbers you need at exactly the worst moment, that today live on a note by the till or in one person's phone.
• What you want on hand during an inspection. Who is named on the licence, where the hygiene code and HACCP plan live, who the manager with the food-safety certificate is, and where the allergen information sits. So that whoever is on when the inspector walks in knows where everything is.
• Where the switches are. The main gas and water shut-off, the fuse box, the alarm code, and which door sticks. The practical stuff you only miss the moment something breaks.
• The questions you get called about on your day off. Where the dinner vouchers are, whether the order already went out, who has the spare key. The things that live only in your head right now, and that the team settles itself once the answer is written down.
• Recipes and how to serve them. Not just the ingredients, but what a dish is meant to look like on the plate and what to watch for.
• The handover per shift. What the previous shift ran into, what broke, what the next shift needs to know. This is the knowledge with the shortest shelf life and the highest risk of vanishing.

The common thread: it is knowledge that keeps your venue running, that is valuable, and that currently sits invisibly in someone's head.

How to capture it so it stays with the venue

"Just write it down" is easy to say. The reason it usually does not happen is not laziness, it is how the usual fixes fail. A binder of procedures is dead the day it is printed: within a month something is out of date, and the moment it is wrong once, nobody trusts it. The group chat is not a record: the answer is in there somewhere, but under three hundred messages about shift swaps you cannot find it, so you ask again.

Capturing that stays with the venue meets four conditions:

• Searchable. The value is not in keeping it, it is in finding it back. Mid-shift you should reach the answer in seconds, not scroll for it.
• One version, kept current. Not five documents on five laptops, but one place everyone updates. Then the answer you find is the answer that is true today.
• Read at the start of the shift. Changes and agreements the team actually sees, not an announcement buried in a chat half the staff muted.
• Owned by the venue, not by a person. This is the heart of it under turnover. If the knowledge belongs to the venue and not to the departing colleague, it stays when that colleague leaves.

Get those four right and the dynamic of turnover changes. Someone still leaves, but what they knew stays. A new colleague gets up to speed faster, because the answers are written somewhere instead of repeated out loud shift after shift.

This is personal for us. moonies exists because our co-founder Sanne spent almost twenty years in hospitality, on the floor and as a manager, fielding calls on days off about dinner vouchers and bins that never got emptied. You cannot stop every question. You can catch most of them by simply having the answer somewhere the team can reach, even when you are not there.

Frequently asked questions

What does capturing knowledge in hospitality actually mean? It means putting the way your venue works in one searchable place your team can reach: ways of working, agreements, recipes, and the handover per shift. That keeps the knowledge with the venue instead of in one colleague's head.

Why does it matter most when staff keep changing? Because every departing colleague takes away knowledge that is written down nowhere. With annual turnover around 40 percent (ABN AMRO, 2019), you lose that knowledge again and again, unless you separate it from the person and keep it with the venue.

Isn't a binder of procedures or the group chat enough? Usually not. A binder ages and stops being trusted the moment it is wrong once. A group chat stores everything but lets you find nothing back. Both fail at the moment that counts: when someone needs the answer fast, mid-shift.

What does it cost when knowledge is not captured? ABN AMRO (2019) put the cost of turnover at more than 42,000 euros per hospitality business a year, roughly 6 percent of revenue. Part of that is the knowledge that has to be rebuilt because it never lived anywhere.

Where moonies fits

This is exactly the gap the Memory module is built for: the knowledge of your place in one searchable spot, with updates your team reads at the start of the shift. Recipes, ways of working, agreements, suppliers, changes, and the end-of-shift handover, instead of scattered across heads, notebooks, loose documents, and the group chat.

The point is not storage, it is recall. And the knowledge stays with the place, even when someone is out or moves on. That is exactly what makes turnover less painful.

More on this: why knowledge never gets written down, and how AI can only do something with that knowledge once it sits in one place and the guest never notices.

Does this sound like your own venue? Then the Memory module is where to look, and the pricing page lays out what it costs with no surprises.