Read the statuses
Separate pending, handed-over and completed statements. Do not add an outcome absent from the file.
Concrete output: An annotated status list.
FICTIONAL LEARNING EXERCISE
A fictional shift-handover file
Organise eight sample requests without personal data by status and follow-up question. No real booking system is used.
Inspect the sample file
8 sample rows · 3 columns
| request_id | sample_request | status |
|---|---|---|
| H01 | Confirm whether a training event has a projector | pending |
| H02 | A sample guest asks for directions | completed |
| H03 | Clarify the time of a fictional group arrival | pending |
| H04 | Pass a sample catering question to the relevant team | handed-over |
The table shows the first four rows. The file is fictional; some exercises intentionally include missing or conflicting values. Do not interpret them as real operational outcomes.
Download fictional sample CSV ↓Write the ambiguity
Record one unclear detail as a question. Avoid unnecessary personal information.
Concrete output: Two clarification questions.
Build a handover note
Use completed, pending and response-needed headings. Do not invent real people or room details.
Concrete output: A short shift-handover note.
Review for the reader
Could someone understand the next action from this note alone? Explain assumptions made around missing information.
Concrete output: A revised handover note and one limitation.
My own project narrative
Write what you actually did and its limits in your own words rather than copying a prewritten achievement.
Ask yourself before saving
- Did I add real personal data?
- Did I separate pending from completed work?
- Can another reader understand the next action?