Choose duration and party-size rules for Experiences

Duration and party-size rules shape the availability guests see. They also help staff avoid bookings that do not fit the room, schedule, or service model.

Start simple. Add complexity only when the operation needs it.

Set The Default Duration

The default duration is the reservation length CoverCount uses when no party-size rule matches.

Common starting points:

Use the time guests actually need, including arrival, service, payment, and reset time. If the duration is too short, CoverCount may offer inventory the team cannot realistically turn.

Add Party-Size Duration Rules

Use duration rules when larger parties need more time.

Example for a restaurant:

Example for a tasting:

The matching duration feeds availability and table assignment. A slot must have enough runway for the calculated length.

Set The Public Party-Size Limit

The public party-size limit is the largest party guests can book themselves for that Experience.

Set it based on what the team can handle without manual review.

Good reasons to lower the limit:

• Large parties need specific tables or table combinations.
• Large parties require a deposit.
• Staff need to confirm menu, staffing, or timing.
• The venue wants to avoid accidental buyout-sized bookings.

Guests above the limit should be directed to contact the venue or use the appropriate inquiry flow.

Use Minimum Booking Notice

Minimum booking notice prevents guests from booking too close to the reservation time.

Examples:

• 0 minutes for ordinary same-day dining
• 60 minutes when staff need a little notice
• 24 hours for large-party tastings or special setup
• 48 hours or more for prep-heavy Experiences

Staff-created reservations can still be handled manually when the team wants to make an exception.

Use Pacing Carefully

Pacing caps the number of guests who can book the same exact offered start time for an Experience.

Use pacing when:

• Too many guests can otherwise arrive at the same time.
• A tasting bar, kitchen, or host team has a real start-time capacity.
• The Experience has limited staff coverage.

Most Experiences do not need pacing at first. Table availability and duration rules may be enough.

If you enable pacing, choose a realistic maximum guest count for each offered start time. Then test small and large parties at the same time to make sure the cap behaves the way you expect.

Test The Rules

Before publishing:

• Search as a party of 2.
• Search as a party of 4.
• Search as the largest self-service party size.
• Search above the public limit and confirm guests cannot self-book.
• Try today or tomorrow if minimum notice applies.
• Confirm the staff view shows the expected duration.

For a fuller checklist, see Test an Experience before publishing.