A fictional room-by-night availability grid and request-by-request feasible-room list with arrival/departure boundary and hold explanations. This is a written practice result, not a recorded AI run.
Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides
Saving needs JavaScript. Reading and downloading this guide does not save it.
Make a start
One step at a time.
3 steps
Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.
Start with the synthetic example, then adapt each prompt to your task.
01
Try the complete example
Open a text AI chat you already have permission to use. Paste the whole prompt below, from TASK through END INPUT, and send it. The input is source material; do not paste the illustrative Output as an answer to imitate. Expect A fictional room-by-night availability grid and request-by-request feasible-room list with arrival/departure boundary and hold explanations. If you receive advice instead of the result, ask for the complete requested result from the supplied input.
Your starting prompt
TASK
Validate the complete fictional interval snapshot first, holding affected rooms for unknown or conflicting source intervals. Expand occupied and maintenance nights under the exact arrival/departure rule. Return the complete room-by-night grid and each request’s candidate rooms/exclusion reasons, independently. Distinguish snapshot fit from housekeeping release and any booking.
INPUT
Complete fictional snapshot only, using room and request tokens. Review nights 2026-10-14 through 2026-10-20 inclusive. Arrival date is occupied; departure date is not occupied. Rooms T1 and T2 are twins; D1 and D2 are doubles. No other stays or blocks exist in this synthetic snapshot.
S1: T1 arrives 2026-10-14, departs 2026-10-17.
S2: T2 arrives 2026-10-18, departs 2026-10-20.
S3: D1 arrives 2026-10-15, departs 2026-10-18.
M1: D2 maintenance blocks the nights of 2026-10-16 and 2026-10-17.
Q1: needs one twin, arrives 2026-10-17, departs 2026-10-19.
Q2: needs one double, arrives 2026-10-16, departs 2026-10-18.
No split-room stays. Check requests independently, not as accepted bookings. Missing departure dates, overlapping existing stays on a room, or occupancy conflicting with a block put the whole affected room on hold until the source owner resolves it. Do not silently prioritize one record. Housekeeping release, real availability and booking authority are not supplied.
END INPUT
02
Check and correct
Mark S1 nights 14/15/16 and S2 nights 18/19; checkout nights 17 and 20 are excluded. Q1 covers 17/18 and has only T1 as a snapshot candidate. Q2 covers 16/17 and has no eligible uninterrupted double. A dot is only a snapshot cell. No real release, cleanliness, booking or current-availability claim should appear. Compare with the unchanged source yourself. If anything differs, use the correction prompt, then recheck the complete replacement before saving.
Your starting prompt
Check the answer in this sample chat against the complete INPUT above. Mark S1 nights 14/15/16 and S2 nights 18/19; checkout nights 17 and 20 are excluded. Q1 covers 17/18 and has only T1 as a snapshot candidate. Q2 covers 16/17 and has no eligible uninterrupted double. A dot is only a snapshot cell. No real release, cleanliness, booking or current-availability claim should appear. Quote each mismatch and its source, then return a complete corrected replacement. If source or answer is missing, ask for it. Do not describe a suggested human trial as completed.
03
Use your own source instead
Open a new chat and copy the prompt below. Replace every bracketed field with your own permitted non-sensitive material, or write unknown. Change the source names, counts, dates and rules together wherever they occur. Expect a complete result using those new values. Compare each source link and calculation with your new input, using the review instructions in this prompt. If a fact or rule is wrong, quote the mismatch and source and ask for a complete corrected replacement; keep essential unknowns held rather than borrowing the practice values.
Your starting prompt
Check my complete synthetic room snapshot and proposed stays. Validate room IDs/types, dates and intervals first; hold each affected room for missing essential endpoints, overlapping existing stays or occupancy/block conflicts until the owner resolves the source. Apply my stated arrival/departure boundary, expand every room-night across my horizon, then list each request’s uninterrupted candidate rooms and exclusion reasons. Check requests independently unless my rules explicitly define an allocation problem. Derive requested nights, types and counts from MY INPUT; never use practice dates. Independently mark every interval on a calendar and compare each requested night. Keep release status and live availability unverified and do not allocate, release or book rooms.
MY INPUT
Fictional room IDs/types: [replace with your source or rule]
Complete dated existing occupancy intervals: [replace with your source or rule]
Maintenance blocks and their dates: [replace with your source or rule]
Arrival/departure boundary rule: [replace with your source or rule]
Proposed stay requirements: [replace with your source or rule]
Snapshot scope and unknown/conflict policy: [replace with your source or rule]
Use only MY INPUT for facts, quantities, names, dates and permissions. Ask for missing essential facts or conflicting rules instead of guessing. Creative invention is allowed only where this task and my boundaries permit it. Return the actual complete requested result, a separate unknown/hold list and the source-specific review described above. Do not reuse practice-example facts. Keep this a draft; do not publish, contact people, book, buy or change another service.
Optional: improve the result
Test an unknown departure
Optional, sample-only extension. Return to the practice chat, or paste this guide’s complete practice input and your checked answer into a new chat. Check that one missing boundary blocks an otherwise attractive candidate. This does not apply unchanged to your own source.
Advanced prompt
In a separate copy of this sample, replace S1’s departure date with unknown. Rebuild the hold list and Q1 candidate result without guessing a date. Explain why T1 can no longer be called a candidate and T2 still fails on night 18. If the complete sample input or answer is missing, ask me to paste it. Keep new variants separate from the original result.
Show, then try
See the shape of the result.
This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.
01 / The starting point
Synthetic input
COMPLETE SYNTHETIC PRACTICE INPUT
Complete fictional snapshot only, using room and request tokens. Review nights 2026-10-14 through 2026-10-20 inclusive. Arrival date is occupied; departure date is not occupied. Rooms T1 and T2 are twins; D1 and D2 are doubles. No other stays or blocks exist in this synthetic snapshot.
S1: T1 arrives 2026-10-14, departs 2026-10-17.
S2: T2 arrives 2026-10-18, departs 2026-10-20.
S3: D1 arrives 2026-10-15, departs 2026-10-18.
M1: D2 maintenance blocks the nights of 2026-10-16 and 2026-10-17.
Q1: needs one twin, arrives 2026-10-17, departs 2026-10-19.
Q2: needs one double, arrives 2026-10-16, departs 2026-10-18.
No split-room stays. Check requests independently, not as accepted bookings. Missing departure dates, overlapping existing stays on a room, or occupancy conflicting with a block put the whole affected room on hold until the source owner resolves it. Do not silently prioritize one record. Housekeeping release, real availability and booking authority are not supplied.
Copies text only. For image or file tasks, use the source files named in the steps too.
ILLUSTRATIVE AUTHORED OUTPUT
Written for this guide; no consumer AI execution or real-world trial is claimed.
NIGHT GRID — FICTIONAL SNAPSHOT
O = existing occupied night; M = maintenance block; . = no listed occupancy/block in this complete snapshot. A dot does not mean released or bookable.
Night in October 2026: 14 15 16 17 18 19 20
T1, twin: O O O . . . .
T2, twin: . . . . O O .
D1, double: . O O O . . .
D2, double: . . M M . . .
Source expansion: S1 = 14/15/16; S2 = 18/19; S3 = 15/16/17; M1 = 16/17. No missing or conflicting intervals occur in this fixture.
REQUEST CHECK
Q1 needs nights 17 and 18. T1 is a snapshot candidate for both nights. T2 is excluded because night 18 is occupied by S2. D1/D2 have the wrong room type. Candidate set: T1 only.
Q2 needs nights 16 and 17. D1 is occupied by S3 both nights; D2 is blocked by M1 both nights. T1/T2 have the wrong type. Candidate set: none. Do not split the stay.
BOUNDARY AND HOLD NOTES
T1’s departure on 17 makes night 17 unoccupied under this fixture’s rule; it does not establish cleaning completion or room release. T2’s night 20 is not occupied by S2. The request departure dates are excluded too.
Ask the responsible owner to check a current authorized snapshot and actual room-release status before any real action. This result is neither live availability nor a reservation; no room is allocated, released or booked.
These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.
Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.
!
A few things to watch for.
An unknown departure is not a one-night stay. Hold the affected room rather than guessing.
A checkout-exclusive interval can fit on paper while housekeeping release remains unknown. Keep these decisions separate.