What the map tells you that numbers don't. Combinable tables: the two-top and the four-top at the back count as six together, but only if the request arrives before the others — the map shows it, the count doesn't. High chairs: a “four-cover” table with a baby in a high chair sits six comfortably on some plans, impossible on others. The terrace: twenty extra covers in summer that exist only if the weather holds, and the map marks them differently because the handling is different. Whoever runs the dining room without a map answers “we'll see”; whoever has one answers “yes, at 8:45 pm” and the booking is closed.
“A table for six, Friday at 9 pm”: the request looks numeric, in truth it's geographic. Six covers are always there in the count; somewhere to sit six, that Friday at that hour, is another story — it depends on which tables are already taken, which can be pushed together, where the service walks, who has the high chair and who doesn't. The map inside the management system answers in a second, and answers right: it proposes the real six, or the four plus two nearby saying so straight away. The same logic protects you from overbooking by mistake: a table taken on the map no longer exists for any later request, whichever channel it comes from.
Frequently asked questions
- Is a table map useful without bookings?
- Yes: even those who work on a walk-in basis use the map to lay out the room, assign sections to the servers and keep a real-time cover count. With bookings, though, it becomes indispensable: it's what ties the request to a real seat.
- How long does it take to draw the room?
- With current tools, little: you drag the tables onto the grid, assign the seats and save the combinations — an hour for a normal dining room, then you forget about it. Changes, moving a table or adding the terrace, take a few minutes.