Wedding venue booking form: the guest minimum

A couple planning a small wedding types a guest count of thirty and submits. The form turns red at the guest field and says only 'Please enter a valid number.' The number is valid. The real rule is a minimum the venue sets for weekend dates, written in a paragraph on another page the couple has not opened. Some couples retype the number, then a bigger one, then leave. The owner knows the minimum well, so the rule feels obvious from inside, while a stranger reads the error as a broken form.

• Enter a guest count below your minimum. Does the error name the minimum, or only say 'invalid'?
• Pick a Friday and then a Sunday. Does the date picker accept both, or only the days your calendar uses?
• Is the guest minimum shown above the guest field, before a couple types a number?
• After a tour request, does the confirmation give a tour time and a way to change it?

Venues set rules that change with the day, the season or the room: a minimum guest count for a Saturday, a weekday rate, a cap for the garden. These rules often live in a terms page or a note under a pricing table, and the booking form enforces them without repeating them. A couple who meets the rule in the form has no context for it, so the error reads as a fault. The couple cannot tell whether to change the date or the number.

Find the rule by reading every error the form gives you. Enter a guest count below the minimum, then above the room's limit, then pick a weekday, and write down each message. If a message names the rule, the page and the form agree. If it says only 'invalid', the rule exists and the form hides it. The run records the error text a simulated visitor saw, with the field and a screenshot, so the vague message is written down the way a couple sees it.

A date picker built for the most common booking can refuse a day a couple needs. If it allows only Saturdays, a couple who wants a Sunday brunch or a Friday ceremony cannot pick their date, and may not know why. The picker shows the calendar dimmed, with no line saying which days are open. From the couple's side, the venue is either fully booked or it does not know its own weekdays.

Test the picker with a date you know the venue offers and one it does not. Read the text beside the picker: does it say which days are bookable? Then test a tour request, not only the booking, since a tour can be requested on a day the booking form refuses. A tour request that works on a day the booking form rejects shows the mismatch in one step.

A tour request on a weekend often gets a confirmation at once, and a reply from a coordinator later. The gap between the two is where a couple decides whether the venue answered at all. A confirmation that says 'We will be in touch' without a tour time gives the couple nothing to act on, and a couple with a busy week may book another venue before the reply arrives.

Submit a tour request with a test address, then read the confirmation page and the email in full. Check whether a time, a meeting place and a way to change the time are all there. A simulated visitor has a working inbox, so it can read that email and report what is missing. It cannot judge how fast your team replies, which you measure from your own inbox.

A new room, a holiday rate or a calendar sync can change the minimum or the bookable days, and the form can keep the old rule until someone tests it. Rerun the guest count and date path after every rule change. Use a guest count just under the minimum, and a day that is bookable only in certain weeks, because those are the cases where an old rule hides longest.