Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.

Open video on YouTube ↗

Download slide guide (PDF)10 pages · 3.9 MB

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
Staff can distinguish location identity from their own linked identity and verify a saved location check-in.

Read the full explanation

Before we begin, check these prerequisites: C01; linked staff ID; current approved label; C02 where enrolled-device proof is required. The intended outcome is: Staff can distinguish location identity from their own linked identity and verify a saved location check-in. 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.

The location label

• Open Scan QR or the authorized label link while online and confirm the resolved location

In this step
Check the resolved location name before entering attendance. Labels can be replaced or become invalid. A successful scan only opens the workflow; it does not itself record your arrival.

Read the full explanation

Open Scan QR or the authorized label link while online and confirm the resolved location. Check the resolved location name before entering attendance. Labels can be replaced or become invalid. A successful scan only opens the workflow; it does not itself record your arrival. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Staff identity

• Sign in as staff when prompted
• return to the location page and select your linked staff ID

In this step
Sign in with your own account if the page requests it. Then select the staff identity linked to you. A guest entry and a staff attendance event follow different workflows even when they use the same location.

Read the full explanation

Sign in as staff when prompted; return to the location page and select your linked staff ID. Sign in with your own account if the page requests it. Then select the staff identity linked to you. A guest entry and a staff attendance event follow different workflows even when they use the same location. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Location requirements

• Check location/device requirement, allow fresh GPS and enter optional notes

In this step
Read the site’s device and location requirements. Fresh GPS and enrolled-device proof may be required. If your browser lacks the required proof, contact the issuer rather than trying another person’s identity.

Read the full explanation

Check location/device requirement, allow fresh GPS and enter optional notes. Read the site’s device and location requirements. Fresh GPS and enrolled-device proof may be required. If your browser lacks the required proof, contact the issuer rather than trying another person’s identity. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Arrival and departure

• Choose the Check In event and submit once
• later repeat with Check Out and inspect both saved event kinds in personal history

In this step
The staff QR screen offers check-in and check-out. The standard attendance screen has the separate lunch actions. After submission, verify the site and event kind so that a scan at departure has not become another arrival.

Read the full explanation

Choose the Check In event and submit once; later repeat with Check Out and inspect both saved event kinds in personal history. The staff QR screen offers check-in and check-out. The standard attendance screen has the separate lunch actions. After submission, verify the site and event kind so that a scan at departure has not become another arrival. I will pause here so you can identify the control or result that tells us where we are in the workflow.

A rejected scan

• For expired label, unlinked identity, GPS rejection or missing device proof, preserve the error and ask the authorized host/issuer for recovery

In this step
Preserve the displayed reason and the intended location. An expired label belongs with the host, while missing enrollment belongs with the issuer. Prepared offline staff capture still needs later server acceptance.

Read the full explanation

For expired label, unlinked identity, GPS rejection or missing device proof, preserve the error and ask the authorized host/issuer for recovery. Preserve the displayed reason and the intended location. An expired label belongs with the host, while missing enrollment belongs with the issuer. Prepared offline staff capture still needs later server acceptance. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Common problems

• Assuming the QR identifies the employee
• entering guest details instead of staff login
• choosing the wrong event kind
• attempting first-time offline lookup

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. Assuming the QR identifies the employee; entering guest details instead of staff login; choosing the wrong event kind; attempting first-time offline lookup. 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

• Use the training site QR, sign in and record the authorized check-in/check-out sequence; verify both event kinds and site/mode in history
• Explain a prepared expired-code or enrolled-device-required message

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. Use the training site QR, sign in and record the authorized check-in/check-out sequence; verify both event kinds and site/mode in history. Explain a prepared expired-code or enrolled-device-required message. 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
Staff can distinguish location identity from their own linked identity and verify a saved location check-in.

Read the full explanation

The expected outcome is: Staff can distinguish location identity from their own linked identity and verify a saved location check-in. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Scan QR or the authorized label link while online and confirm the resolved location. Sign in as staff when prompted; return to the location page and select your linked staff ID. Check location/device requirement, allow fresh GPS and enter optional notes. Choose the Check In event and submit once; later repeat with Check Out and inspect both saved event kinds in personal history. For expired label, unlinked identity, GPS rejection or missing device proof, preserve the error and ask the authorized host/issuer for recovery. For an exception, name the evidence you would preserve and the person with authority to take the next action.