Another Check-In · G01
Guest check-in
20 minutes. · 10 slides
Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.
Work through the lesson
Use these explanations alongside the slide guide. Expand any section to read its full explanation.
Before the demonstration
- Your assigned responsibility
- The correct training record
- Evidence of the result
Today’s outcome
Guest sees a valid receipt and host can locate the correct entry.
Read the full explanation
Before we begin, check these prerequisites: A03 configured active guest/mixed location, license, online GPS; fictional guest identity. The intended outcome is: Guest sees a valid receipt and host can locate the correct entry. Keep a note of the training identity and date so that you can recognize the result. We will pause before any action that your role or the exercise does not authorize.
Host preparation
- Host verifies location label, mode and event availability
In this step
The host checks the location mode, active period and guest availability. Guests use the public workflow and do not need an application role. The location and license still need to support guest entry.
Read the full explanation
Host verifies location label, mode and event availability. The host checks the location mode, active period and guest availability. Guests use the public workflow and do not need an application role. The location and license still need to support guest entry. I will pause here so you can identify the control or result that tells us where we are in the workflow.
The guest destination
- Guest opens Scan QR or approved code link and confirms the location name
In this step
The guest scans the current label or uses the approved code link. Confirm the displayed location before collecting details. An old or invalid code should return to the host for resolution.
Read the full explanation
Guest opens Scan QR or approved code link and confirms the location name. The guest scans the current label or uses the approved code link. Confirm the displayed location before collecting details. An old or invalid code should return to the host for resolution. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Details and consent
- Enter required name and approved optional details
- accept required consent and allow GPS
In this step
Collect the required fictional name and only the optional details approved for the exercise. Explain the consent wording before submission. GPS permission supports the location check and should not be bypassed if it fails.
Read the full explanation
Enter required name and approved optional details; accept required consent and allow GPS. Collect the required fictional name and only the optional details approved for the exercise. Explain the consent wording before submission. GPS permission supports the location check and should not be bypassed if it fails. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Guest receipt
- Submit Guest Check In and inspect saved confirmation
- handle invalid code/GPS/consent failures without bypassing checks
In this step
Read the saved confirmation. Guest entry requires server access and does not use the staff offline queue. If the code, consent or GPS check fails, correct the cause through the proper host process.
Read the full explanation
Submit Guest Check In and inspect saved confirmation; handle invalid code/GPS/consent failures without bypassing checks. Read the saved confirmation. Guest entry requires server access and does not use the staff offline queue. If the code, consent or GPS check fails, correct the cause through the proper host process. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Host review
- Host with locations.guests.view verifies the entry in Guest Check-ins for that location/date
In this step
The authorized host finds the entry for the same location and date. Guest visibility has its own permission and scope. Confirm the fictional entry without exposing unrelated participants in the screenshot or lesson.
Read the full explanation
Host with locations.guests.view verifies the entry in Guest Check-ins for that location/date. The authorized host finds the entry for the same location and date. Guest visibility has its own permission and scope. Confirm the fictional entry without exposing unrelated participants in the screenshot or lesson. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Common problems
- Guest trying staff login/enrollment
- using old code
- entering unnecessary personal details
- assuming online guest workflow can queue offline
A useful support report
The task and record
The expected result
The actual message
The authorized next step
Read the full explanation
Let us consider the mistakes that can disrupt this workflow. Guest trying staff login/enrollment; using old code; entering unnecessary personal details; assuming online guest workflow can queue offline. Describe what you expected and what the application actually showed before choosing a remedy. Preserve the relevant record and error. The role responsible for a review or configuration change should make that decision. Do not borrow broader access simply to finish the exercise.
Guided practice
- Submit one fictional guest check-in at the approved test venue and let the host confirm it; demonstrate a prepared invalid/expired code error
Evidence to show
The correct training case
The result or permitted decision
Your explanation of the next step
Read the full explanation
Now it is your turn. Submit one fictional guest check-in at the approved test venue and let the host confirm it; demonstrate a prepared invalid/expired code error. Work within the assigned training role. When you finish, show the result and explain which identity and date it belongs to. If the exercise includes a restricted action, explain the decision and its authorized owner rather than carrying it out without approval.
Practice debrief
- Correct context and permitted action
- A result you can trace
- A clear next step if blocked
Expected result
Guest sees a valid receipt and host can locate the correct entry.
Read the full explanation
The expected outcome is: Guest sees a valid receipt and host can locate the correct entry. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Host verifies location label, mode and event availability. Guest opens Scan QR or approved code link and confirms the location name. Enter required name and approved optional details; accept required consent and allow GPS. Submit Guest Check In and inspect saved confirmation; handle invalid code/GPS/consent failures without bypassing checks. Host with locations.guests.view verifies the entry in Guest Check-ins for that location/date. For an exception, name the evidence you would preserve and the person with authority to take the next action.