Practical guide · Missing EVV punches
Find the visit behind the missing punch.
Published 2026-10-18 · Updated 2026-10-21
Open the specific visit, check the recorded events and clarify what happened with the responsible staff member. Keep the explanation and authorized decision with the record your next reviewer will need.
People verify the facts, review AI drafts and approve consequential actions.
Read the guide ↓30 days free · Then $20 USD per person supported per month.
$0 setup for system initialization · Month-to-month · No long-term contract
Migration scope and costs are separately agreed.
The work behind the review
A missing clock-in is a question about the record.
The alert alone does not establish whether support occurred. Begin with the correct visit and its available evidence, then follow the authorized review process for the service.
1 · Identify the visit
Check the person, service and full time range.
Confirm the assigned staff member, scheduled start and end, recorded events and current visit status. Include the full range for an overnight visit rather than relying on a single calendar-day view.
- Check whether the visit is open, completed or already decided.
- Review the available recorded times and context.
- Keep the missing event distinct from a conclusion that care was missed.
2 · Establish the facts
Ask what happened before changing the record.
Clarify the missing event with the responsible person and available source information. Preserve uncertainty until the facts support an authorized action.
- Do not invent a time to clear an alert.
- Follow the applicable correction and review process.
- Keep the explanation and reason for the decision available to the reviewer.
3 · Inspect the saved result
Check that the recorded action is the one intended.
In the synthetic LunahUP example, an administrator documented a test cancellation reason, cancelled the test visit and reopened the same record. The saved status and explanation remained after reload.
- Use the example to inspect retention of a test disposition.
- Evaluate real-care correction and approval separately for your supported workflow.
- Treat a reminder as a prompt to review; it does not create or verify a punch.
4 · Confirm the next handoff
Keep local review and external acceptance separate.
Where a configured connection is required, confirm its specification, setup, supported actions and response-review responsibilities. A saved local decision does not establish transmission, payer acceptance or payment.
- Confirm the state, payer and service requirements with the responsible team.
- Inspect the applicable receipt or error response in the agreed testing process.
- Revisit unresolved information in the source workflow.
Questions before the next step
Know what this guide establishes.
Does a missing punch prove that staff did not attend?
No. The visit record, source information and responsible staff explanation need investigation. An alert alone does not establish what happened.
Can a call or text fix a visit automatically?
A reminder is a prompt. It does not create a punch, establish service delivery or approve a visit. Confirm current channel availability before relying on it.
Does the saved cancellation example prove external acceptance?
No. It proves the saved synthetic test disposition after reload. It does not establish corrected care time, transmission, acceptance or payment.
Keep exploring
Find the next question your team needs to answer.
A focused demonstration
Bring the missing-punch question that keeps returning.
Inspect one sample visit, its source details, staff decision and the available saved result.
Book a 30-minute compliance demoUse sample data. No patient records needed for the demo.