Another Check-In · C03

Daily attendance

25 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.

Open video on YouTube ↗

Download slide guide (PDF)10 pages · 4.7 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
Learner distinguishes successful server receipt, failed GPS and local pending evidence.

Read the full explanation

Before we begin, check these prerequisites: C02; valid staff identity; actual GPS permission and venue; approved training attendance. The intended outcome is: Learner distinguishes successful server receipt, failed GPS and local pending evidence. 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.

Attendance readiness

  • Open Check In (/)
  • inspect connection, security, pending and storage indicators

In this step
Read the status indicators before entering an event. An available page does not prove that the server is reachable or that local storage can keep a pending event. These indicators help you decide what confirmation to expect.

Read the full explanation

Open Check In (/); inspect connection, security, pending and storage indicators. Read the status indicators before entering an event. An available page does not prove that the server is reachable or that local storage can keep a pending event. These indicators help you decide what confirmation to expect. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Identity and action

  • Confirm Staff ID/name and choose Check In
  • position/work detail is optional and not unit assignment

In this step
Check the Staff ID and name every time. Choose the action that actually occurred. Optional work detail describes the activity and does not change your organizational unit or permissions.

Read the full explanation

Confirm Staff ID/name and choose Check In; position/work detail is optional and not unit assignment. Check the Staff ID and name every time. Choose the action that actually occurred. Optional work detail describes the activity and does not change your organizational unit or permissions. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Location evidence

  • Allow GPS, inspect accuracy and use Retry GPS when necessary

In this step
A GPS reading includes an accuracy estimate. Give the device a chance to obtain a fresh reading and use the retry control when needed. If location fails, explain the failure to support instead of inventing coordinates.

Read the full explanation

Allow GPS, inspect accuracy and use Retry GPS when necessary. A GPS reading includes an accuracy estimate. Give the device a chance to obtain a fresh reading and use the retry control when needed. If location fails, explain the failure to support instead of inventing coordinates. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Submission result

  • Submit once and wait for server confirmation or clearly identified local pending state

In this step
Submit once and read the full result. Distinguish a server receipt from an event retained locally for synchronization. Repeated clicks can make the situation harder to understand without solving the original problem.

Read the full explanation

Submit once and wait for server confirmation or clearly identified local pending state. Submit once and read the full result. Distinguish a server receipt from an event retained locally for synchronization. Repeated clicks can make the situation harder to understand without solving the original problem. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Lunch and departure

  • For an approved training day, record Start Lunch, Return from Lunch and later Check Out when each occurs
  • inspect all event kinds and timestamps in history

In this step
The standard screen records four event kinds: check-in, lunch start, lunch return and check-out. Check the saved kind and timestamp in history. These events record what happened; payroll treatment depends on separate organizational policy.

Read the full explanation

For an approved training day, record Start Lunch, Return from Lunch and later Check Out when each occurs; inspect all event kinds and timestamps in history. The standard screen records four event kinds: check-in, lunch start, lunch return and check-out. Check the saved kind and timestamp in history. These events record what happened; payroll treatment depends on separate organizational policy. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Common problems

  • Double-clicking submit
  • leaving Check In selected at departure
  • typing unit changes into position detail
  • equating GPS acquisition with server acceptance

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. Double-clicking submit; leaving Check In selected at departure; typing unit changes into position detail; equating GPS acquisition with server acceptance. 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

  • Perform the approved training arrival, lunch-start, lunch-return and departure sequence, then locate all four saved event kinds
  • For exception practice deny GPS in the disposable browser, explain the message and restore permission

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. Perform the approved training arrival, lunch-start, lunch-return and departure sequence, then locate all four saved event kinds. For exception practice deny GPS in the disposable browser, explain the message and restore permission. 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
Learner distinguishes successful server receipt, failed GPS and local pending evidence.

Read the full explanation

The expected outcome is: Learner distinguishes successful server receipt, failed GPS and local pending evidence. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Check In (/); inspect connection, security, pending and storage indicators. Confirm Staff ID/name and choose Check In; position/work detail is optional and not unit assignment. Allow GPS, inspect accuracy and use Retry GPS when necessary. Submit once and wait for server confirmation or clearly identified local pending state. For an approved training day, record Start Lunch, Return from Lunch and later Check Out when each occurs; inspect all event kinds and timestamps in history. For an exception, name the evidence you would preserve and the person with authority to take the next action.