No one knows how it works because no one wrote it down

Ask anyone who runs a venue how the coffee machine gets descaled, which supplier to call when the vegetable order turns up short, or why table 12 always goes to the regulars, and you will get a clear answer. Ask where that answer is written down, and the room goes quiet.

It is not written down anywhere. It lives in one person's head. The place runs fine right up until that person is on a day off, off sick, or gone for good. Then a question that used to take five seconds takes a phone call, a guess, or a mistake in front of a guest.

This is the quiet problem under almost every operational headache in hospitality. The knowledge that runs your venue is real, it is valuable, and it is invisible.

The knowledge nobody sees

Some of what a venue knows is obvious: recipes, the menu, the wine list. But most of it is the small stuff that never makes it onto a document.

• Who to call when a supplier does not turn up, and whose mobile actually gets answered.
• The agreement with the neighbour about the bins, the one nobody remembers making.
• The knack for the coffee machine, the one that only works if you do the steps in the right order.
• Where the spare key lives, and which door you have to lift before it will lock.
• That the dinner vouchers from that one campaign are still valid until the end of the year.

None of this is secret. It is just never written down, because the people who know it are too busy doing it to stop and record it.

Why it never gets written down

It is easy to say "just write it down." The reason nobody does is structural, not lazy.

• Writing it down is no one's job. During service there is no time. After service there is no energy. The knowledge stays in heads because the head is the only place it costs nothing to keep.
• A binder dies the day it is printed. The classic fix is a folder of procedures. Within a month a supplier changes, a process changes, a number changes, and the binder is quietly wrong. A wrong reference is worse than none, so people stop trusting it, and then they stop reading it.
• The group chat is not a record. Most venues actually do write things down, in WhatsApp. But a chat scrolls away. The answer to "how do we do X" is in there somewhere, under three hundred messages about shift swaps. You cannot find it, so you ask again.
• The people who know the most write the least. The head chef and the manager carry the most in their heads and have the least time to empty it onto paper. So the most valuable knowledge is the most exposed.

What it actually costs

The cost is easy to miss because it never shows up as one big bill. It arrives as a hundred small ones.

• Training takes longer than it should. Every new hire learns the unwritten rules by getting them wrong first. The same questions get answered out loud, shift after shift, because there is nowhere to point.
• A sick day becomes a scramble. When the one person who knows the supplier order is out, the order is late, wrong, or skipped. The venue absorbs the cost and calls it bad luck.
• A resignation is a leak. When someone leaves, the knowledge leaves with them. You do not find out which pieces left until you reach for one that is gone.
• The owner never switches off. This is the one that wears people down. If the knowledge only lives in your head, the phone rings on your day off. Stepping back is impossible, because the place cannot answer its own questions without you.

That last one 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.

What "written down" should actually mean

The problem is not that people refuse to record things. It is that the usual ways of recording them, the binder and the group chat, both fail at the only moment that matters: when someone needs the answer fast, mid-shift, and cannot find it.

So "written down" has to mean more than "stored." For it to actually help, the knowledge has to be:

• Searchable. The value is not in keeping it, it is in finding it back. On the floor you should reach the answer in seconds, not scroll for it.
• One version, kept current. Not "procedures_final_v3.docx" on someone's laptop. One place everyone updates, so the answer you find is the answer that is true today.
• Read at the start of the shift. Changes and agreements that the team actually sees, instead of an announcement buried in a chat that half the staff muted.
• Owned by the venue, not by a person. The knowledge stays with the place when someone is out or leaves, because it never lived in their head alone.

Get those four right and the unwritten venue becomes a written one, without anyone having to sit down and write a manual.

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. In the kitchen you find the recipe and how to plate it. On the floor you find the agreements and the changes. And the knowledge stays with the place, even when someone is out or moves on.

If the unwritten venue sounds like yours, the Memory module is where to look, and the pricing page lays out what it costs with no surprises.