INDUSTRY FIELD GUIDE
Bed-and-breakfast guest preparation records for AI
An innkeeper can prepare an amenity for a booking that later changes rooms or dates.
NAICS 721191 · Bed-and-Breakfast Inns
An innkeeper can prepare an amenity for a booking that later changes rooms or dates. FTC short-term lodging materials provide business context. A small inn can show a reviewer an invented handoff that separates the requested setup and the setup actually confirmed. FTC short-term lodging context
Create two practice room aliases and an original reservation note with no guest name. Move an amenity request to a revised date and supply a verified setup check for only one version. Ask which record supports each statement and what needs confirmation. Use a neutral prop photo only if it helps.
Do not include real guests, room access, dietary or disability information, interiors you lack rights to, payment details or reservations. Use original or approved practice material.
Describe an inn handoff example
Original Fiund exercise
Follow an amenity after a practice booking change
Two invented room aliases and dates describe an administrative handoff. No guest, actual reservation or private accommodation details appear.
| Record | Source | What it records |
|---|---|---|
| REQUEST-B1 | Original preparation note | A neutral practice welcome card is requested for room Birch on day 4. |
| REVISION-B2 | Confirmed amendment | The B1 request moves to room Cedar on day 5 and supersedes the earlier room and date. |
| CHECK-B3 | Setup verification | A verified card placement names Birch on day 4. No Cedar day-5 check is supplied. |
Question for the model
Does the supplied setup verification establish completion of the amended request?
Show the reference answer and checks
No. CHECK-B3 supports the original Birch day-4 setup. REVISION-B2 changes the target to Cedar on day 5, and the package has no matching verification for that amended target. State that the request changed and that the later setup remains unconfirmed. Do not move the earlier check to another room or date simply because it shares the request's history.
- Reusing an old-room setup check as proof of the amended-room setup.
- Dropping the date when matching the verification to the request.
Fields to preserve
- Request lineage
- Connect the amendment to B1 without erasing its prior target.
- Room alias and date
- Match both parts of the setup scope.
- Verification event
- Keep actual confirmation distinct from the requested arrangement.
Test another case
Add a Cedar day-5 check with the correct request reference. The model should now identify the amended setup as documented.
Use invented room aliases and a neutral prop only. Exclude real guests, room access, preferences, dietary information, bookings and payment data.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.