Another Check-In · C05

Personal attendance

20 minutes. · 11 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)11 pages · 5.1 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 locates the correct event and explains scope/filter effects.

Read the full explanation

Before we begin, check these prerequisites: C03; saved fictional records; relevant export/map grants. The intended outcome is: Learner locates the correct event and explains scope/filter effects. 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.

My Check-ins

  • Open Work > My Check-ins

In this step
This page shows the records your account can access. Begin with your own expected event so that you know which identity, date and action you are trying to find. Broader access depends on permissions and organizational scope.

Read the full explanation

Open Work > My Check-ins. This page shows the records your account can access. Begin with your own expected event so that you know which identity, date and action you are trying to find. Broader access depends on permissions and organizational scope. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Useful filters

  • Set a narrow date range and staff/action filters that are available to your role

In this step
A narrow date range makes a missing record easier to investigate. Check the selected action and staff identity before concluding that attendance is absent. An empty result can simply mean that the filters exclude the event.

Read the full explanation

Set a narrow date range and staff/action filters that are available to your role. A narrow date range makes a missing record easier to investigate. Check the selected action and staff identity before concluding that attendance is absent. An empty result can simply mean that the filters exclude the event. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Record evidence

  • Locate the arrival/departure and inspect attendance, location and sync indicators

In this step
Read the event kind, time and available review or synchronization indicators together. An absent device identifier alone does not establish tampering. Ask what evidence this particular workflow was expected to record.

Read the full explanation

Locate the arrival/departure and inspect attendance, location and sync indicators. Read the event kind, time and available review or synchronization indicators together. An absent device identifier alone does not establish tampering. Ask what evidence this particular workflow was expected to record. I will pause here so you can identify the control or result that tells us where we are in the workflow.

The record map

  • Open the record map where GPS and permissions allow, then return with filters preserved

In this step
Use the map as supporting location evidence. If map tiles fail to load, the recorded coordinates and accuracy may still be available. A visual map problem should not become a claim that the attendance record disappeared.

Read the full explanation

Open the record map where GPS and permissions allow, then return with filters preserved. Use the map as supporting location evidence. If map tiles fail to load, the recorded coordinates and accuracy may still be available. A visual map problem should not become a claim that the attendance record disappeared. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Filtered export

  • Export filtered check-ins when permitted and compare record identities/date range to the displayed result

In this step
Compare the exported date range and staff identities with the screen. Share only the authorized result. Reporting CSV serves reporting needs and must not be substituted for the signed session evidence required by the signature verifier.

Read the full explanation

Export filtered check-ins when permitted and compare record identities/date range to the displayed result. Compare the exported date range and staff identities with the screen. Share only the authorized result. Reporting CSV serves reporting needs and must not be substituted for the signed session evidence required by the signature verifier. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Map viewer

  • Optional Map extension: open Work > Map (/viewer), set dates and Load Server Data
  • alternatively Load CSV from an authorized sample

In this step
Load the authorized server range or a permitted CSV sample. Jitter separates overlapping points visually. It does not correct the original coordinates or improve the accuracy of the observation.

Read the full explanation

Optional Map extension: open Work > Map (/viewer), set dates and Load Server Data; alternatively Load CSV from an authorized sample. Explain that Jitter is visual separation and does not correct recorded coordinates. Load the authorized server range or a permitted CSV sample. Jitter separates overlapping points visually. It does not correct the original coordinates or improve the accuracy of the observation. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Common problems

  • Searching the wrong date range or staff link
  • interpreting Not recorded device ID as proof of tampering
  • mistaking report CSV for signed session CSV

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. Searching the wrong date range or staff link; interpreting Not recorded device ID as proof of tampering; mistaking report CSV for signed session CSV. 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

  • Find one training record by date/action, explain GPS evidence, and export the permitted result
  • Explain an empty filter result before escalating

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. Find one training record by date/action, explain GPS evidence, and export the permitted result. Explain an empty filter result before escalating. 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 locates the correct event and explains scope/filter effects.

Read the full explanation

The expected outcome is: Learner locates the correct event and explains scope/filter effects. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Work > My Check-ins. Set a narrow date range and staff/action filters that are available to your role. Locate the arrival/departure and inspect attendance, location and sync indicators. Open the record map where GPS and permissions allow, then return with filters preserved. Export filtered check-ins when permitted and compare record identities/date range to the displayed result. Optional Map extension: open Work > Map (/viewer), set dates and Load Server Data; alternatively Load CSV from an authorized sample. Explain that Jitter is visual separation and does not correct recorded coordinates. For an exception, name the evidence you would preserve and the person with authority to take the next action.