Acquisition diligence
Public booking evidence for location-based entertainment acquisitions.
Public booking research supplements financial, operational, customer, and technology diligence. It documents checkout reachability, offered schedules, posted prices, booking horizons, platform dependencies, and observed changes.
One target · up to five agreed peers · ten business days · final scope follows cohort and source feasibility review
Role in diligence: this research provides supplementary external evidence. It does not replace management data, financial diligence, customer research, legal review, or technical diligence.
Six factual tests
Evidence reviewed in a public booking diligence engagement.
Each test is attached to a fixed cohort, observation window, provider-native identity, source pointer, and known missingness.
Can a visitor reach a public checkout?
Record whether the agreed booking paths respond, where they stop, and whether failures are isolated or repeated. A failed observation remains a failure, not proof of unavailability.
What dates and start times are publicly offered?
Preserve the schedules returned for the agreed products and service dates, including observation gaps and provider-specific semantics.
Which prices and conditions are visible?
Compare provider-returned price fields only with their product, party size, date, fees, and other visible conditions intact.
How far forward can a visitor inspect?
Document the public date horizon by location and product without treating future visibility as a completed booking or revenue signal.
Where does the public booking stack differ?
Map observed provider footprints, redirects, schema changes, and location-level inconsistencies that may shape integration planning.
Which exceptions persist or resolve?
Separate a one-time observation from repeated evidence and retain the exact observation window behind every reported change.
Ten-business-day review
Fixed scope and defined deliverables.
Fix the decision and cohort
Agree the target, up to five peers, products, service dates, questions, and prohibited interpretations.
Collect and preserve
Observe the approved public surfaces, retain timestamps and request context, and keep failures and missingness explicit.
Compare and review
Prepare factual comparisons, investigate persistent exceptions, and remove results that do not satisfy the evidence policy.
Deliver the diligence brief
Provide the written brief, comparison table, provenance index, limitations, and management follow-up questions.
Interpretation boundary
Supported uses and interpretation limits.
Supported factual language
- Observed public bookability and checkout response
- Offered product, service date, start time, or schedule span
- Posted or provider-returned price with its conditions
- Provider-returned availability state or remaining-inventory field
- Public platform footprint and observed change
Not established by this evidence alone
- Bookings, sales, tickets sold, attendance, or foot traffic
- Revenue or financial performance
- Physical capacity, occupancy, or utilization
- Customer demand or market share
- Unavailability when an observation failed or is missing
Methodology sample: the linked historical availability study states its observation basis, evidence freshness, provider-native semantics, and source traceability.
The sample does not describe current market conditions or imply endorsement by any observed provider or venue.