Online venue booking system: requests look booked

A book club organizer needs a room for forty people on a Thursday next month. The venue page has a calendar with the date shown as free, a guest field, and a button that says Book this room. The form asks for an event type, but the list has no club meeting option. The next screen says thanks, we will be in touch, and the organizer closes the tab believing the room is hers. A week later she learns the venue only logged a request, and another group has the room because it was never held.

• Read the button, then the next screen. Does either say requested, held or booked?
• Enter a group size. Does the page say whether the number is seated or standing?
• Pick the event type your group would use. Is there an option for it near the top?
• Add a projector or tables. Is the extra price shown before the date step?
• Choose a date with a setup day before it. Does the form refuse it later, and why?

A venue has three states for a date: free, held and booked. A request sits between held and booked, and the venue may not have decided yet. A form may not show which state the visitor is creating, because the button label is written for the venue's own staff. A planner reads Book this room as a reservation. Read the button, then the next screen, then the confirmation email, and write down the exact word for the date state at each one. If the three words do not match, the planner cannot know which one is true.

The expiry is the hidden part. A held date can lapse after a set period if no deposit or confirmation arrives, and the form may not say so. A planner who returns after the lapse may find the room gone. A planner will not look for that date unless the page puts it in front of them, so check whether the confirmation shows the day the hold ends, and whether the email repeats it.

Checkout flow testing

A group size field that accepts forty does not tell the planner whether the room seats forty at tables or holds forty standing. A venue may list one maximum, and a planner who needs round tables for a meeting reads that number as seated capacity. Add-ons such as projectors, chairs or catering can appear after the date is chosen, with prices shown only at the summary. A planner who has already committed to a date then finds the total has moved. Check the layout question before the date, and check whether the add-on prices appear on the first screen that lists the room.

Venue calendars can show the event day as free while a setup or cleaning day before it is blocked. A planner who needs to load a stage on Wednesday night may pick Thursday with no warning, then get a refusal on the next screen. The form should explain the rule where the date is picked, in plain words, such as a setup day needed before the event. Run the test with a date you know is free and with a date just before a blocked one, and note the screen where the refusal first appears.

To find the cause, compare the screen where the date was picked with the screen where it was refused. If the refusal names the setup day, the calendar is working and the page is not explaining it. If the refusal is a generic error, the rule is hidden from the planner, and the fix belongs on the date picker. A planner who sees the reason named can try a nearby date before the room is gone.

The first run finds whether a planner stopped at the request wording, the headcount, the add-ons or the setup day. A fix changes a button, a layout question or a calendar note, and a new room, a seasonal rate or a changed hold rule can bring the same confusion back. Run a planner for a seated group after each change, then one who wants a standing event, so both layouts get checked. Repeat it before a busy season.