Fictional completed intake → real delivery format

What comes back after a free three-observation mini-review.

This example turns a fictional Asia ground-transport coverage ledger request into three bounded, founder-readable observations—without live inventory, operator accounts, private API assumptions or a booking-platform build.

Read the three observations Open the prefilled public-source lane

Disclosure: “RouteReach Asia”, all operator/route rows, URLs, statuses and dates below are fictional/composite. They demonstrate the request and review format only. No real operator coverage, booking availability, payment acceptance or commercial relationship is claimed.

1. The completed fictional request

A useful free request names one lane, one flow and one decision question. It does not ask for a general strategy review.

Public-source data product Product

RouteReach Asia — corridor coverage-gap ledger

Stage

Five-row fictional fixture; no live inventory or operator integration

Evidence

One public sample page plus a redacted/fictional CSV schema

Boundary

No ticket sales, refunds, routing advice or real-time availability claims

One flow to review

Choose a corridor → inspect an operator/route card → understand whether it is merely discoverable, publicly bookable, payment-ready or still unknown → export a buyer-readable gap note.

One concern

Does the schema accidentally turn “a page was found” into “this route can be booked or integrated”?

Evidence contents

Five fictional rows with route, language, public booking path, payment observation, OTA observation, source date and unknown fields. No customer, traveller or account data.

Desired outcome

Three concrete changes that make the first public sample credible enough to test as a fixed-price corridor brief.

2. The fictional evidence excerpt

The five fictional/composite ledger rows deliberately contain gaps. A readiness review checks whether the product preserves those gaps instead of filling them with optimistic labels.

Card	Corridor	Public page	Booking observation	Payment observation	OTA status	Observed
FX-01	Regional rail placeholder	Local-language timetable	Link found; checkout not evidenced	Unknown	Not checked	2026-07-20
FX-02	Intercity coach placeholder	Bilingual operator page	Reservation form described	Card icons shown; acceptance not tested	Unknown	2026-07-20
FX-03	Island ferry placeholder	PDF timetable	No public booking evidence saved	Unknown	Unknown	2026-07-21
FX-04	Mountain bus placeholder	Tourism-board listing	Operator source missing	Unknown	Aggregator listing observed; relationship unknown	2026-07-21
FX-05	Cross-border coach placeholder	Operator route page	Public checkout path described	Local wallet named; foreign-card support unknown	Not checked	2026-07-21

3. The delivered three-observation mini-review

Split discovery, booking and integration into separate statuses

The current card can show a timetable, form or aggregator listing, but those observations do not prove a working checkout, real-time inventory or a commercial operator relationship. Use independent fields such as public_source_found, booking_path_observed, checkout_tested and integration_status; default the last two to unknown.

Immediate change: replace one broad “available” badge with four evidence-specific statuses and show the source date beside each.

Make language and payment claims route-specific and observable

A bilingual homepage does not prove the booking flow is bilingual. Payment logos do not prove foreign cards, wallets or refunds work. Record where each observation was made, what step was reached, who observed it and what remains untested; never ask the free sample to transact.

Immediate change: add evidence_url, evidence_location, observed_at, test_level and unknown_reason to every friction claim.

Sell a bounded corridor evidence brief before building coverage software

The buyer-readable outcome is not “Asia transport in one app.” It is a small, auditable answer to: which operators/routes are absent or hard to distribute, what public evidence supports that, and what question should a partnerships team verify next?

Immediate change: publish ten real source-backed gap cards across three corridors, cluster three repeated frictions, then test a fixed-scope brief. Kill the lane if useful fields require private inventory/API access or the only repeatable gap is translation.

4. What the paid scope would add

A$149–299 Public-source Data Product Readiness Review
One landing page plus one sample ledger/brief, returned in 48–72 hours with a source schema, raw/derived/unknown-field policy, evidence-status copy, one buyer-readable card template, pricing/CTA teardown and an approval-gated distribution queue.

Build a free three-observation request See a deeper five-bullet data sample

Boundary: public or explicitly supplied redacted evidence only. No live booking, ticketing, payments, refunds, operator contact, account access, route advice, inventory/API availability claim, market-coverage guarantee or commercial-outcome promise.