Another Check-In · R03
Monthly register
30 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.
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 separates register data, exported output and governed snapshot state.
Read the full explanation
Before we begin, check these prerequisites: R01; prepared month; reports.shift_view; extra approval/lock permissions for relevant actions. The intended outcome is: Learner separates register data, exported output and governed snapshot state. 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.
Register selection
- Open Work > Monthly Register and set month/range, staff/unit, location/shift and weekend options
In this step
Choose the month or range and inspect the available staff, location, shift and weekend options. These selections define the report you are about to review. Record them when a register supports a formal decision.
Read the full explanation
Open Work > Monthly Register and set month/range, staff/unit, location/shift and weekend options. Choose the month or range and inspect the available staff, location, shift and weekend options. These selections define the report you are about to review. Record them when a register supports a formal decision. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Daily codes and totals
- Read the daily codes and totals, then verify a known event/exception
In this step
Read the daily codes before relying on the totals. Trace one known exception back to its event and decision history. A total is easier to explain when you can show the daily evidence that contributes to it.
Read the full explanation
Read the daily codes and totals, then verify a known event/exception. Read the daily codes before relying on the totals. Trace one known exception back to its event and decision history. A total is easier to explain when you can show the daily evidence that contributes to it. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Live register exports
- Export CSV or XLSX and compare selected period/staff to the displayed register
In this step
CSV and XLSX exports represent the live register. Compare the selected period and staff with the screen. An approved snapshot has a separate evidence purpose and should not be replaced by a later live export.
Read the full explanation
Export CSV or XLSX and compare selected period/staff to the displayed register. CSV and XLSX exports represent the live register. Compare the selected period and staff with the screen. An approved snapshot has a separate evidence purpose and should not be replaced by a later live export. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Snapshot approval
- With reports.approve create a snapshot, submit draft for review and approve under agreed governance
In this step
An authorized approver creates the snapshot and sends the draft for review before approval. Follow the organization’s sign-off responsibilities. The software’s state transitions do not by themselves establish an independent reviewer policy.
Read the full explanation
With reports.approve create a snapshot, submit draft for review and approve under agreed governance. An authorized approver creates the snapshot and sends the draft for review before approval. Follow the organization’s sign-off responsibilities. The software’s state transitions do not by themselves establish an independent reviewer policy. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Lock and reopen
- With reports.lock lock approved state
- demonstrate reopening/resubmitting only on a disposable training period
In this step
Locking and reopening require the corresponding authority. Changed report data can invalidate a transition and require a new snapshot. Follow the displayed state and preserve the history instead of treating approval as a permanent description of changing data.
Read the full explanation
With reports.lock lock approved state; demonstrate reopening/resubmitting only on a disposable training period. If report data changed, create a new snapshot. Locking and reopening require the corresponding authority. Changed report data can invalidate a transition and require a new snapshot. Follow the displayed state and preserve the history instead of treating approval as a permanent description of changing data. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Approved snapshot evidence
- Live CSV and XLSX can change
- An approved snapshot records a specific version
- Use the authorized snapshot download
Check the snapshot
Approved or locked state
Valid stored hash
Your current reporting scope
Read the full explanation
A live export and an approved snapshot answer different questions. The live CSV or XLSX reflects current report data. The dedicated snapshot download returns the stored evidence for an approved or locked version, subject to a valid stored hash and your current reporting scope. Older approvals may lack the stored snapshot needed for this download. Ask the authorized report owner for the verified link and identify the approval before using it. Keep that evidence with its version rather than replacing it with a fresh export when the underlying records change.
Common problems
- Assuming current export is the approved snapshot
- approving the wrong filters
- expecting supervisor to approve or manager to lock by default
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 current export is the approved snapshot; approving the wrong filters; expecting supervisor to approve or manager to lock by default. 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
- Reader exports a prepared month; authorized approver identifies snapshot version/state; lock authority explains the changed-data and reopen path
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. Reader exports a prepared month; authorized approver identifies snapshot version/state; lock authority explains the changed-data and reopen path. 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 separates register data, exported output and governed snapshot state.
Read the full explanation
The expected outcome is: Learner separates register data, exported output and governed snapshot state. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Work > Monthly Register and set month/range, staff/unit, location/shift and weekend options. Read the daily codes and totals, then verify a known event/exception. Export CSV or XLSX and compare selected period/staff to the displayed register. With reports.approve create a snapshot, submit draft for review and approve under agreed governance. With reports.lock lock approved state; demonstrate reopening/resubmitting only on a disposable training period. If report data changed, create a new snapshot. For an exception, name the evidence you would preserve and the person with authority to take the next action.