Reference · built on requestOperator by FibricWorkforce & scheduling

Missed Punch

Flags missing or out-of-window clock punches each day and proposes a correction with the schedule and badge evidence attached.

Request accessPricing ↗

About

Missed Punch is an operator job that runs at the close of each business day. It reads the day's punches from your time and attendance system and sets them against the shifts that were scheduled. A shift with no punch, a punch with no clock-out, and a punch outside the window your time system allows are each listed. For each one it gathers what a manager would look for: the scheduled start and end, and the badge reads at the site's doors around those times.

It then proposes the correction: the clock-in or clock-out time it believes is right, with the evidence beside it. The manager confirms or edits the time, and the correction is written to the time system once, as a manager edit, with the evidence kept on the record.

This is a reference listing. It documents what Fibric would read from Missed Punch and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Punches the time system has flagged: 7shifts time_punches with flags late, auto_clocked_out, and missed_break; When I Work times with alert_type
  • Open punches with no clock-out: When I Work times with only_open, Homebase timecards without clock_out, Deputy timesheets with IsInProgress
  • Scheduled shifts for the day: 7shifts shifts, When I Work shifts, Homebase shifts with start_at and end_at, Dayforce EmployeeSchedules
  • Punch windows and lateness settings: Homebase timeclock status with early_in_min, tardy_in_min, and auto_clock_out_minutes
  • Badge reads at the site's doors: Brivo access events by site and occurred time, Verkada access events such as door_keycard_entered_accepted, Kisi reader.access events
  • Shifts a manager has already approved without a time entry: When I Work shifts with is_approved_without_time

Proposed actions

  • Target capability: propose a punch correction with the evidence attached: 7shifts Update Time Punch, When I Work Update Time, or Deputy Update a Timesheet
  • Target capability: propose a new punch for a shift that has none: Dayforce POST /EmployeePunches checked with isValidateOnly, or a Deputy timesheet
  • Target capability: propose approving a missing time entry for a scheduled shift through When I Work approve-missing
  • Target capability: propose a message to the employee's manager listing the day's exceptions, each with its evidence

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Correct a 7shifts punch with Brivo evidence

    Time punches flagged auto_clocked_out are matched to the scheduled shift and to Brivo access events at the site around the scheduled end. The operator proposes the clock-out time for the manager to confirm.

    With 7shifts, Brivo Access

  • Close open When I Work times

    Times with only_open at the end of the day are set against shifts and Verkada door events. The operator proposes an Update Time with the end time and evidence, or approve-missing for a shift with no time at all.

    With When I Work, Verkada

  • List Homebase exceptions for a manager

    Timecards without clock_out and shifts with no timecard are listed per location, with tardy_in_min from the timeclock status applied. Because the Homebase key is read-only, the list goes to the manager to enter.

    With Homebase, Slack

  • Add a missing Dayforce punch

    EmployeeSchedules for the day are compared with EmployeePunches. For a shift with no punch, the operator proposes a POST to EmployeePunches, checked with isValidateOnly, with Kisi reader.access events as evidence.

    With Dayforce, Kisi

Requirements

  • A time and attendance connector with punches: 7shifts, When I Work, Deputy, Homebase, or Dayforce
  • Scheduled shifts for the same employees, from the time system or a scheduling connector
  • Optional: an access control connector for badge evidence: Brivo, Verkada, Kisi, Genea, or Avigilon Alta
  • A mapping from employee to badge holder, kept by the operator, since the two systems name people differently
Authentication
Punches, schedules, and door events are read, and corrections written, through the connectors you bind and the access you gave each; it carries no credentials itself.

Limits

  • Badge evidence is a hint, not proof. A badge read shows a door was opened with a credential, not who worked; the manager still decides
  • Brivo access events are read one 24 hour window at a time, so evidence for a day is gathered after the day closes
  • Where the time system is read-only, as with a Homebase public key, the correction is proposed for a manager to enter
  • It does not decide pay. A corrected punch reaches payroll through the time system's own approval and export

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Missed Punch ↗

Questions and answers

What does the manager confirm?
One correction at a time: the employee, the shift, the punch as it stands, the time proposed, and the evidence, which is the scheduled time and any badge read near it. The manager confirms, edits the time, or dismisses it.
What is recorded for each correction?
The exception as detected, the evidence gathered, the time proposed, the manager's decision with a timestamp, the write to the time system and its response, and the original punch so the edit can be undone.
Does it ever edit a punch without a person?
No. Every correction waits for a manager. It also does not clock anyone in or out in real time; it works from the day's record after the fact.
Ask about Missed Punch

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy