Time Clock Downtime Procedure Template: A 6-Step Continuity Kit

What is a time clock downtime procedure?

A time clock downtime procedure is the approved backup process for recording hourly work when the normal clock is unavailable or producing suspect records. It states who declares the outage, how employees capture time, where records go, who reviews them, when normal clocking resumes, and how payroll reconciles each manual entry. Datapath’s EHR downtime checklist and Accountable HQ’s step-by-step downtime guide support the same transferable operating pattern: clear command, manual documentation, controlled recovery, and final reconciliation.

1. Declare downtime. The authorized incident lead confirms that the clock is unavailable or unreliable, records the affected scope, and opens an incident record. Employees should follow the activation decision defined in the approved procedure.
2. Notify staff. Send the activation message through approved channels. Name the affected locations or teams, the manual method to use, where to obtain it, and the role handling questions.
3. Switch to the approved manual record. Employees capture every required entry on the paper or offline form approved by payroll, HR, counsel, and the system owner. Supervisors distribute blank forms and state where completed records must go.
4. Secure and review entries. Supervisors check for missing fields, unreadable details, overlaps, and obvious omissions. Completed records move to the designated controlled location. Unresolved entries follow the documented correction route.
5. Restore normal clocking. The system contact tests the service, and the incident lead decides whether the clock is reliable enough to use. Employees resume normal punches only after the restoration notice arrives.
6. Reconcile all records. The assigned payroll or HR owner enters or imports manual records, checks for duplicates and omissions, documents corrections, and gives every outage record a final disposition.

When should the time clock outage procedure be activated?

Activate the procedure when the authorized incident lead determines that the time clock is inaccessible or its records cannot be trusted. Accountable HQ’s downtime guide identifies planned maintenance, network or power loss, interface failure, cyber incidents, and service-provider outages as possible triggers for an inaccessible or unreliable system. Accountable HQ also emphasizes unit-level triggers, while Datapath calls for a defined communication plan. Once downtime is declared, communicate the exact scope through approved channels.

• The clock, kiosk, mobile interface, or required network connection is inaccessible.
• Employees can submit punches, but records are missing, delayed, duplicated, or otherwise unreliable.
• A planned maintenance window requires the approved backup process.
• The system owner or security lead directs teams to stop using the normal clock.
• A local site trigger is met, even though other locations remain operational.

Use prepared communication scripts

Activation: “The time clock is unavailable or unreliable for [scope]. Effective [time], use [manual method]. Obtain the form from [location] and submit it to [role or location]. Do not resume normal clocking until an authorized restoration notice is issued.”

Restoration: “Normal clocking resumes at [time]. Submit any remaining manual records by the deadline established in our policy. Report a missing, duplicate, or incorrect entry through the missed-punch correction process.”

Who has authority and responsibility during downtime?

Use a written chain of command. One incident lead declares and ends downtime. Supervisors direct local work, a communications owner issues updates, the system contact investigates, and payroll or HR validates records after restoration. Accountable HQ’s downtime guide calls for explicit decision authority, escalation paths, unit-level triggers, and a clear map of who decides, documents, and verifies checks.

The escalation path should identify who takes control across multiple locations, who can contact the system provider, and who receives unresolved pay-period issues. Keep the operating rule blunt: map who decides, documents, communicates, and verifies.

What should employees record during manual timekeeping?

The approved manual record needs enough detail for payroll and HR to identify the employee, work period, required punches or elapsed time, location or assignment, reason for manual entry, and attestations. Use the list below as a working field set until payroll, HR, counsel, and the system owner approve it. Accountable HQ’s downtime guide supports preparing paper forms and other manual supplies before an outage, but employment and payroll reviewers must decide which fields are legally sufficient.

Do not assume this field list is legally sufficient. The final form must match authoritative federal, state, and local requirements, applicable agreements, payroll rules, record-retention requirements, and the organization’s approved attendance policy. The supplied continuity sources provide an operating framework but do not establish wage-and-hour requirements for a specific employer or jurisdiction.

One-page employee instruction sheet

How should supervisors review and secure manual records?

Supervisors should review manual records, send missing or unreadable entries through the documented correction path, and transfer completed forms to the approved secure location. Datapath’s downtime checklist includes secure record access, while the adapted procedure described in the evidence calls for deciding in advance how completed records will be secured and corrected. Keep the authoritative copy in the designated controlled system or location and limit handling to assigned roles.

Use a separate exception path whenever an entry requires judgment. For example, an outage record that includes extra time should enter the organization’s overtime approval process for review instead of being changed outside the documented correction route. Keep the submitted record associated with the resulting decision.

How should restoration and reconciliation work?

Restoration has two gates. First, the system contact confirms that the clock is reliable again. Second, the operational owner confirms that manual records can be entered or imported without loss, duplication, or overlap. Normal clocking resumes after the authorized announcement, but reconciliation stays open until every outage record has a documented disposition. Datapath’s EHR downtime checklist treats recovery sequencing and post-event reconciliation as planned parts of the response rather than an after-the-fact cleanup task.

Restoration checklist

Reconciliation log

Set submission, correction, payroll handoff, and closure deadlines with payroll, HR, counsel, and contractual stakeholders. Publish those deadlines in the policy rather than inventing them during an outage. A consistent reconciliation log also helps teams reduce timesheet errors before payroll by keeping omissions, duplicates, and unresolved corrections visible.

How should staff training and downtime drills be run?

Train each role on its assigned actions during orientation and scheduled refreshers. Then test the entire chain with tabletop scenarios and timed functional drills. Collect sign-offs, record gaps, assign each fix to an owner, and revise the kit after the exercise. Accountable HQ recommends role-based orientation, refreshers, tabletop walkthroughs, timed functional drills, scenarios, and sign-offs. ASPR TRACIE’s electronic records downtime collection also summarizes recommendations for plans, drills, staff training, and communication triage.

Accountable HQ’s training guidance supports role-based orientation, refreshers, tabletop walkthroughs, timed drills, realistic scenarios, and participant sign-offs as a model that can be adapted for hourly workplaces. These exercises can expose unclear authority, slow communication, missing forms, and weak reconciliation before a real outage. They do not establish employment-law rules, so keep legal and payroll review as a separate approval gate.

What belongs in the complete downtime procedure kit?

A complete kit includes the policy, employee instruction sheet, supervisor checklist, manual record form, reconciliation log, message scripts, downtime supplies, and drill worksheet. This package adapts the planning, documentation, communication, training, recovery, and reconciliation practices described by Datapath, Accountable HQ, and ASPR TRACIE. Store the operating documents together, assign one owner to keep them current, and route the final version through employment-law, payroll, HR, contractual, and system review. The result should be usable at 2 a.m. by a supervisor who did not write it.

• Policy: purpose, scope, activation criteria, authority, escalation, restoration, and review cycle.
• Employee sheet: where to get the form, what to record, where to submit it, and when to stop.
• Supervisor checklist: distribution, review, correction, security, and escalation duties.
• Downtime kit: current blank forms, instructions, approved contact list, collection materials, and access to offline tools.
• Reconciliation log: receipt, entry, duplicate checks, discrepancies, approval, and final disposition.
• Incident record: activation, communications, affected scope, restoration, unresolved issues, and post-event actions.

How Cogniver helps manage timekeeping exceptions after downtime

Cogniver turns post-outage attendance exceptions into a defined approval flow instead of an email chase. Its visual builder supports branching, merging, and multi-step approval chains. Teams can require a supporting document before an exception proceeds, so payroll does not receive an unsupported correction at the end of the pay period.

An AI Router sends each exception down exactly one branch using exact values or the organization’s plain-words policy. Every routing point has a mandatory default branch. When the request is uncertain, it takes that branch instead of stalling or guessing which reviewer should decide.

Each workflow gets an isolated AI agent trained by org admins on that workflow’s rules and configuration. The agent answers questions, routes requests, and follows up with approvers. During normal operations, Cogniver’s geofenced check-in validates that an employee is physically on site. The attendance policy keeps working hours, holidays, leave types, and balances in one place.