A Clearer Shift Handover
The product, document or result is one part of the story. Inspect the source record and the decision behind a specific revision.
Amira Dorsey
Third-year BS student
HOS 220 · Service Handover
Adviser: Dr. Yasmin Farrow
Original simulated teaching case

The question and the learner
Amira Dorsey noticed that the word waiting did very little work in an instructional handover. It could mean that a simulated room needed confirmation, that a learner had not checked the next step, or that a request had been passed to someone else. In each case the next desk learner had to ask another question before replying. The Hospitality Operations task was to make that uncertainty visible in the document rather than hide it behind a short status label.
Dr. Yasmin Farrow supplied twelve original fictional arrival records for a classroom walkthrough. The exercise used no real hotel, guest name, reservation or customer contact. A first version of the handover listed an arrival identifier and a broad status. Amira's revision added an owner, the next action and a confirmation boundary. A reader could then distinguish a known state from a state that still required the role-play lead's decision.
Original records and the comparison
The source table preserves both sets of invented walkthrough durations. The first sequence is nine, twelve, eight, fifteen, eleven, ten, fourteen, nine, thirteen, seven, twelve and ten minutes. The revised sequence is eight, nine, eight, ten, nine, eight, eleven, nine, ten, seven, nine and eight minutes. Their totals are 130 and 106 minutes. Dividing by twelve gives means of about 10.83 and 8.83 minutes. The arithmetic difference between the means is two minutes.
These figures are authored scenario values, not observations from a functioning hotel and not evidence that a form caused an improvement. The scenario keeps the same twelve identifiers so a learner can compare the two columns, but that pairing does not create a controlled trial. Workload, staff experience, room availability and actual guest needs are not represented. The table is useful for explaining a comparison and its limits, rather than predicting a commercial service outcome.
Amira's revised status language includes awaiting instructor confirmation when the next reply cannot be made within the learner's role. It names the studio desk learner as the current owner and identifies the role-play lead as the confirmation route. The wording avoids a promised room-ready time. In this teaching setting, a learner may acknowledge uncertainty and explain a next check, but cannot authorize compensation, a room assignment or an operational promise outside the supplied brief.
Complete original simulated source records · Scroll within the table on a narrow screen.
| Arrival Id | Original Walkthrough Wait Minutes | Revised Walkthrough Wait Minutes | Status | Owner | Next Action |
|---|---|---|---|---|---|
| A01 | 9 | 8 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A02 | 12 | 9 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A03 | 8 | 8 | Awaiting instructor confirmation | Studio desk learner | Confirm status with the role-play lead before responding |
| A04 | 15 | 10 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A05 | 11 | 9 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A06 | 10 | 8 | Awaiting instructor confirmation | Studio desk learner | Confirm status with the role-play lead before responding |
| A07 | 14 | 11 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A08 | 9 | 9 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A09 | 13 | 10 | Awaiting instructor confirmation | Studio desk learner | Confirm status with the role-play lead before responding |
| A10 | 7 | 7 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A11 | 12 | 9 | Ready for the next role-play step | Studio desk learner | Confirm status with the role-play lead before responding |
| A12 | 10 | 8 | Awaiting instructor confirmation | Studio desk learner | Confirm status with the role-play lead before responding |
Revision, limits and the next question
The important document change is the relationship between status and action. A status says what the current record supports. An owner says who is carrying the request. A next action says what should happen before a further reply. Amira places the three together so that the handover does not require a reader to search several disconnected notes. The two source versions remain available, with the revision reason beside each changed field.
The comparison keeps both twelve-entry sequences aligned with their source identifiers. Its figures describe authored walkthrough values, not a customer-satisfaction score. The two illustrative scenes show Amira discussing a record and reviewing a revised handover in the same guest studio. They help a reader follow the learning stages, but cannot validate a duration. Exact minute values remain in the readable table and complete source file, where the original and revised columns can be compared directly.
Yasmin asks Amira to check whether another learner can identify an unresolved request without help from the original author. A useful review question is not simply whether the form looks cleaner. It is whether the reader can state what is known, who owns the request and what must happen next. If the reader cannot do that, reducing the form's visual density has not solved the operational communication problem.
The next iteration would introduce an unfamiliar role-play record and ask a different learner to explain the next step. Amira would preserve any misunderstanding as feedback on the form. She would keep the numeric example separate from that reader exercise and avoid converting either into a promise of shorter real-world waits. The completed case demonstrates an explicit handover, a reproducible comparison and a clear boundary around its conclusion. It is a learning portfolio, not a claim about hotel performance.
Amira also preserves the distinction between elapsed waiting in the scenario and the time a learner spends checking a note. They are different measures, and the source table provides only the former. She cannot relabel its values as staff time saved. The explanatory caption states the unit and the scenario basis. This additional wording prevents an apparently minor chart edit from turning a classroom comparison into an unsupported claim about labor productivity or service cost.

Complete source package
The downloadable text contains the full case, every original source row and the expected reconciliation. CSV contains the same complete table. These files are learning materials, not business records.