Knowledge & data
Knowledge catalog for offer, rooms and FAQs
How many people fit in the vaulted room? The website says one thing, the quote PDF another – and on the phone the owner gives a third number. What your venue knows is spread across five places.
You'll get …
- 1
Everything about your venue in one place
Rooms, capacities, packages, processes and FAQs sit in one place as clear building blocks – instead of spread across the website, PDFs and people's heads.
- 2
The same answer everywhere
Website, assistant, quote and the team on the phone all give the same numbers, dated and with someone responsible.
- 3
Gaps and outdated content come to light
Building it shows what's missing or contradictory – clear responsibilities keep the catalog up to date.
01Intro
The knowledge catalog brings that knowledge together in one place, in clear building blocks: rooms with capacities and equipment, offers and packages with price ranges, processes from inquiry to teardown, and the FAQs that would otherwise come in by phone three times a day. Every building block has a date and someone responsible for it – change the room hire and it changes everywhere it appears. Website, team, Google and AI systems all draw on the same source.
Worth knowing: this is structural work – first the knowledge is put in order, then a tool is added. A catalog is only as good as it is current: if you don't plan who looks after it, in a year you'll have five versions of the truth again. That's why responsibilities and a regular review are part of the project.
02How it works
- 01
Gather the knowledge
Website, quote PDFs, menus, standard email replies, what the owner knows: everything about rooms, offers and house rules goes on the table – contradictions included. Finding those is part of the job.
- 02
Structure the building blocks
Rooms, offers, prices and price ranges, processes, FAQs: each area gets clear fields (seated/standing capacity, equipment, valid from, terms) instead of running text with the number buried somewhere in it.
- 03
Flag gaps and dead wood
What's missing, what's out of date, what contradicts itself? The catalog shows you – the 2024 price list goes, and the missing answer to the most common wedding question goes in.
- 04
Put it to use
The building blocks feed their channels: website pages and structured data for search and AI, an internal overview for the team, a basis for the assistant and event inquiries. One source, many outputs.
- 05
Make upkeep a routine
An owner and a schedule for each area: prices with each seasonal menu, rooms after a refurbishment, FAQs on an ongoing basis from real guest questions.
03Stages
The starting point is deliberately small: one area of knowledge, properly structured – usually the one causing the most trouble right now.
Starter: one area, done properly
Rooms and capacities, or offers and prices, as a structured model – one single source of truth for the area people ask about most.
Next step: all the important topics
Rooms, offers, prices, processes and FAQs are in the catalog. Website, FAQ assistant, event inquiries and the team on the phone all read from it and give the same answer.
Full build: a living source
The catalog is kept up to date on an ongoing basis, with owners and a date for each building block, so it stays the single source of truth. New channels plug in: the screen at the entrance, notices and table cards, booking portals, AI search engines.
04Try it yourself
The catalogue of the fictional “Alte Mühle” event venue. Right now every place answers differently. Connect them to the catalogue, then change a value in the block and save – website, companion, quote and phone all update at once.
Every place keeps its own version of the answer.
This is how the catalogue is built: building blocks with fixed fields – each with an update date and an owner – and output places that draw from them. No place keeps its own copy: when a value changes, everything that uses it follows. AI search engines get the same facts as structured data.
Pick a building block in the “try it out” tab – it lights up here along with the places that use it.
05Technical implementation
- Storage to suit your venue: the website's CMS collections, Airtable/Notion or a Markdown structure – what counts is the field model, not the tool.
- Structure: clear content types (rooms, offers, prices and price ranges, processes, FAQs) with fields for status and owner.
- Output: website pages, JSON-LD/Schema.org (LocalBusiness, FAQ, event markup), an internal overview, and later context for the assistant.
- Optional AI during the build: a language model helps sort existing material and track down contradictions – people do the curating.
- No RAG project: at the usual size of a venue, structured context is enough – cheaper and easier to maintain.
- Maintenance: a review date for each area, upkeep as part of everyday work (a new guest question → a new FAQ building block).
for context · This shows how something like this usually gets built – not how it has to be built for you. What actually fits is worked out in the project: around your existing setup, your team, and what stays easy to maintain.