Use the original TQ01 fixture below to reconcile anonymous travelers, rooms, nights, and supplied prices. Use this fixture to prepare a native Excel or DOCX quote; the HTML companion is a comparison copy with known-component calculations and unresolved items, not a supplier offer, invoice, or confirmed booking.
Record the price basis before calculating
Keep a row for each component with its ID, description, currency, rate, rate basis, quantity, source/version reference, and confirmation state. Separately list required items that have not been quoted.
The CTP group-travel guide hosted by Lehigh University asks for arrival, nights, rooms, occupancy, and a room-night budget, and distinguishes quote review from booking confirmation. This template adopts those record distinctions. Its prices and capacity are fictional supplied assumptions; the guide's provider policies and timelines are not general rules for this example.
Use only anonymous traveler IDs T1, T2, T3, and T4. Assign room R01 to T1/T2 and R02 to T3/T4, with a supplied maximum of two people per room. The roster has four unique travelers and the two rooms have four places.
Check that every traveler appears once in the occupancy ledger and no room exceeds its supplied capacity. Do not infer bedding, accessibility, age suitability, or actual availability from a valid arithmetic allocation; those fields remain TO CONFIRM.
Count occupied nights with checkout excluded
The fictional check-in date is October 20, 2026, and checkout is October 22. The occupied night labels are October 20 and October 21: two nights, not three calendar dates.
| Room | Traveler IDs | Night Oct 20 | Night Oct 21 | Room-nights |
|---|---|---|---|---|
| R01 | T1, T2 | Included | Included | 2 |
| R02 | T3, T4 | Included | Included | 2 |
There are four room-nights in total. At the supplied fictional rate of USD 100 per room-night, the room component is 2 rooms × 2 nights × USD 100 = USD 400.
Use valid date-only check-in and checkout fields with checkout later than check-in. Count nights by calendar dates rather than local-clock elapsed hours, so daylight-saving behavior does not silently alter the quantity.
Show a known-component subtotal
| Component | Supplied price basis | Calculation | Known amount |
|---|---|---|---|
| Rooms | USD 100 per room-night | 2 × 2 × 100 | USD 400 |
| Activity | USD 30 per traveler | 4 × 30 | USD 120 |
| Group transfer | USD 80 once per group | 1 × 80 | USD 80 |
| Required train travel | TO CONFIRM | Not calculated | Unknown |
The three known components sum to USD 600. Keep that label: known-component subtotal. The required train item is unknown, not USD 0, so the register cannot provide a complete trip total.
An illustrative equal allocation of USD 600 ÷ 4 = USD 150 per traveler is a separate planning calculation. It is not the supplier's per-person rate, an amount actually owed, or a final invoice. It also omits the unresolved train cost.
Keep inclusions, exclusions, taxes or fees, source validity, acceptance, payment, refunds, and booking confirmation TO CONFIRM unless the relevant source supplies them. The fixture's USD rates do not establish any of those terms.
Compare a withdrawal without canceling a room
For revision TQ01-B, T4 withdraws. Retain R01 with T1/T2 and R02 with T3. The three remaining travelers fit within the four supplied places, but both room units remain in this scenario.
Assuming the same fictional rates, two nights, and unchanged services, rooms stay USD 400; activity becomes 3 × USD 30 = USD 90; the group transfer stays USD 80. The known-component subtotal becomes USD 570.
The reduction is USD 30, not one quarter of USD 600. An illustrative equal allocation is USD 570 ÷ 3 = USD 190 per remaining traveler. A lower group subtotal can therefore produce a higher equal allocation when fixed components are spread across fewer people.
Neither the template nor a roster edit cancels R02. Any real supplier revision, charge change, or cancellation must be separately confirmed and entered as a new sourced record.
Keep the extra-night scenario independent
TQ01-C starts from the original four travelers and changes checkout to October 23. Its night labels are October 20, 21, and 22.
Two rooms × three nights × USD 100 = USD 600 for rooms. The activity remains USD 120 and group transfer USD 80, giving a known subtotal of USD 800. This is a separate scenario from T4's withdrawal; combining the scenarios would require its own explicitly supplied quantities and confirmation.
| Scenario | Travelers | Rooms | Nights | Known subtotal |
|---|---|---|---|---|
| TQ01-A, baseline | 4 | 2 | 2 | USD 600 |
| TQ01-B, T4 withdraws | 3 | 2 | 2 | USD 570 |
| TQ01-C, original roster plus one night | 4 | 2 | 3 | USD 800 |
All three still have the required train item unresolved.
Keep unresolved capacity and currency out of a false total
A fifth traveler cannot be assigned to the existing four supplied places without a revised room plan. Mark allocation unresolved; do not overfill a room or automatically add an unquoted room.
All calculated fixture components use USD. If a new quote arrives in another currency, keep it separate until an explicit conversion basis is supplied. Do not add its bare number to the USD subtotal.
Retain source versions and scenario assumptions in the native register. An optional read-only HTML copy can compare the fictional scenarios, but it needs no Book, Pay, Cancel, or Send control.
Copyable quote prompt
Create one complete, self-contained US-English HTML companion for “Travel quote · TQ01”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for A · Four travelers; B · T4 withdraws; C · One extra night. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Create a complete native Excel or DOCX draft travel quote, anonymous occupancy/night ledgers and a scenario comparison. Label all prices fictional and status unconfirmed booking; preserve required unknown items rather than generate a full trip total.
Baseline TQ01-A: traveler IDs T1,T2,T3,T4; R01=T1/T2, R02=T3/T4; supplied capacity 2 per room. Check-in 2026-10-20, checkout 2026-10-22: night labels Oct 20/21 only, two nights. USD 100 per room-night -> 2*2*100=400; activity USD 30 per traveler -> 4*30=120; group transfer USD 80 once -> 80. Known-component subtotal USD 600, required train TO CONFIRM, never zero. Illustrative equal allocation 600/4=150, not supplier rate/invoice/amount owed.
Revision TQ01-B removes T4 but retains both rooms, two nights and the same rates/services: R01=T1/T2, R02=T3; rooms USD 400, activity 90, transfer 80, known subtotal 570. Equal allocation 570/3=190 illustrative only. Do not calculate 600*.75 or cancel a room without sourced supplier revision.
Independent TQ01-C keeps the original 4 travelers; checkout Oct 23 adds the Oct 22 night: rooms 2*3*100=600, activity 120, transfer 80, known subtotal USD 800. Train unresolved in every scenario. A fifth traveler against the existing 4 places means unresolved room allocation, not automatic additions or overoccupancy.
Fields: componentID/description/currency/rate basis/quantity/source-version/confirmation; unique travelerID-room occupancy; calendar-night ledger; source validity/inclusions/exclusions/acceptance/payment/refund/booking confirmation TO CONFIRM. Actual supplier confirmations blank. Valid date-only checkout later than check-in, checkout excluded; avoid timezone-hour nightcounts. Mixed currency unconverted stays separate,no implicitFXsum.
Optional read-only HTML comparison specification only, native files/source records primary; no Book/Pay/Cancel/Send, passport/payment details, destination recommendations, real rates or provider policies. Provide arithmetic/capacity/date/unknown/currency test matrix; check native print, article width and 360 px. Mark unexecuted formulas/runtime/render checks not_tested; no actual booking or payment claim.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Travel Quote Template: Keep Room, Traveler, and Group Prices Separate
One traveler withdraws from a four-person trip, so someone reduces the entire estimate by 25%. That removes part of a group transfer and part of a room charge even though neither service has changed. A travel quote template should preserve the price basis of each component when the roster changes.
Use the original TQ01 fixture below to reconcile anonymous travelers, rooms, nights, and supplied prices. Use this fixture to prepare a native Excel or DOCX quote; the HTML companion is a comparison copy with known-component calculations and unresolved items, not a supplier offer, invoice, or confirmed booking.
## Record the price basis before calculating
Keep a row for each component with its ID, description, currency, rate, rate basis, quantity, source/version reference, and confirmation state. Separately list required items that have not been quoted.
The [CTP group-travel guide hosted by Lehigh University](https://financeadmin.lehigh.edu/sites/financeadmin.lehigh.edu/files/Purchasing/documents/CTP_Group%20booking%20guidelines%20and%20processes-General.pdf) asks for arrival, nights, rooms, occupancy, and a room-night budget, and distinguishes quote review from booking confirmation. This template adopts those record distinctions. Its prices and capacity are fictional supplied assumptions; the guide's provider policies and timelines are not general rules for this example.
Use only anonymous traveler IDs T1, T2, T3, and T4. Assign room R01 to T1/T2 and R02 to T3/T4, with a supplied maximum of two people per room. The roster has four unique travelers and the two rooms have four places.
Check that every traveler appears once in the occupancy ledger and no room exceeds its supplied capacity. Do not infer bedding, accessibility, age suitability, or actual availability from a valid arithmetic allocation; those fields remain TO CONFIRM.
## Count occupied nights with checkout excluded
The fictional check-in date is October 20, 2026, and checkout is October 22. The occupied night labels are October 20 and October 21: two nights, not three calendar dates.
| Room | Traveler IDs | Night Oct 20 | Night Oct 21 | Room-nights |
|---|---|---|---|---:|
| R01 | T1, T2 | Included | Included | 2 |
| R02 | T3, T4 | Included | Included | 2 |
There are four room-nights in total. At the supplied fictional rate of USD 100 per room-night, the room component is 2 rooms × 2 nights × USD 100 = USD 400.
Use valid date-only check-in and checkout fields with checkout later than check-in. Count nights by calendar dates rather than local-clock elapsed hours, so daylight-saving behavior does not silently alter the quantity.
## Show a known-component subtotal
| Component | Supplied price basis | Calculation | Known amount |
|---|---|---|---:|
| Rooms | USD 100 per room-night | 2 × 2 × 100 | USD 400 |
| Activity | USD 30 per traveler | 4 × 30 | USD 120 |
| Group transfer | USD 80 once per group | 1 × 80 | USD 80 |
| Required train travel | TO CONFIRM | Not calculated | Unknown |
The three known components sum to USD 600. Keep that label: known-component subtotal. The required train item is unknown, not USD 0, so the register cannot provide a complete trip total.
An illustrative equal allocation of USD 600 ÷ 4 = USD 150 per traveler is a separate planning calculation. It is not the supplier's per-person rate, an amount actually owed, or a final invoice. It also omits the unresolved train cost.
Keep inclusions, exclusions, taxes or fees, source validity, acceptance, payment, refunds, and booking confirmation TO CONFIRM unless the relevant source supplies them. The fixture's USD rates do not establish any of those terms.
## Compare a withdrawal without canceling a room
For revision TQ01-B, T4 withdraws. Retain R01 with T1/T2 and R02 with T3. The three remaining travelers fit within the four supplied places, but both room units remain in this scenario.
Assuming the same fictional rates, two nights, and unchanged services, rooms stay USD 400; activity becomes 3 × USD 30 = USD 90; the group transfer stays USD 80. The known-component subtotal becomes USD 570.
The reduction is USD 30, not one quarter of USD 600. An illustrative equal allocation is USD 570 ÷ 3 = USD 190 per remaining traveler. A lower group subtotal can therefore produce a higher equal allocation when fixed components are spread across fewer people.
Neither the template nor a roster edit cancels R02. Any real supplier revision, charge change, or cancellation must be separately confirmed and entered as a new sourced record.
## Keep the extra-night scenario independent
TQ01-C starts from the original four travelers and changes checkout to October 23. Its night labels are October 20, 21, and 22.
Two rooms × three nights × USD 100 = USD 600 for rooms. The activity remains USD 120 and group transfer USD 80, giving a known subtotal of USD 800. This is a separate scenario from T4's withdrawal; combining the scenarios would require its own explicitly supplied quantities and confirmation.
| Scenario | Travelers | Rooms | Nights | Known subtotal |
|---|---:|---:|---:|---:|
| TQ01-A, baseline | 4 | 2 | 2 | USD 600 |
| TQ01-B, T4 withdraws | 3 | 2 | 2 | USD 570 |
| TQ01-C, original roster plus one night | 4 | 2 | 3 | USD 800 |
All three still have the required train item unresolved.
## Keep unresolved capacity and currency out of a false total
A fifth traveler cannot be assigned to the existing four supplied places without a revised room plan. Mark allocation unresolved; do not overfill a room or automatically add an unquoted room.
All calculated fixture components use USD. If a new quote arrives in another currency, keep it separate until an explicit conversion basis is supplied. Do not add its bare number to the USD subtotal.
Retain source versions and scenario assumptions in the native register. An optional read-only HTML copy can compare the fictional scenarios, but it needs no Book, Pay, Cancel, or Send control.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Optional use for a prepared quote-review copy
Keep the native quote, supplier source records, and authorized booking process as the primary materials. The HTML companion is available above for comparison with the original records. Verify its displayed amounts and assumptions in the actual workspace; that view does not confirm availability, acceptance, or a booking.