Compare one punch terminal or workstation with a trusted reference twice. The worksheet shows how far ahead or behind the clock was at each observation and whether the change exceeds your measurement uncertainty. Use device readings only. Keep employee names, punches and payroll records out of the worksheet.
Use the worked example and method below if the interactive worksheet is unavailable.
At 16:00:00 UTC the terminal reads 16:00:05, so it is 5 seconds ahead. Exactly 24 hours later it reads 16:00:12 at the same reference time, so it is 12 seconds ahead. The offset increased by 7 seconds, or 7.00 seconds per 24 hours over this interval. With a 2-second uncertainty per capture, the change exceeds the 4-second combined bound. Review sync history and repeat the observation before attributing the change to drift.
A positive offset means the device read ahead. A negative offset means it read behind. A steady offset can still warrant checking the display time zone, reference or clock setting. A changing offset warrants checking sync events, connection and capture consistency. If the readings cannot resolve the change, capture again over a longer unchanged interval or use a more precise comparison.
Compare a synthetic punch to its raw event timestamp and export if the issue affects timecards. Follow your organization's review process for affected records. Use the time clock pilot checklist for broader punch-to-payroll testing.
Offset is device time minus its paired reference time. Change is follow-up offset minus first offset. The reference timestamps define the elapsed interval, which must be positive. Observed change per 24 hours is change × 86,400 ÷ elapsed reference seconds, rounded to two decimals for display and CSV. Integer seconds are used throughout the timestamp subtraction.
The change exceeds the measurement bound only when its absolute value is greater than twice the entered uncertainty. This is a conservative sum of two capture bounds, with equality treated as unresolved. It is a measurement check. The worksheet provides no acceptable payroll tolerance, trend forecast or device certification. A clock change makes the two offsets useful as separate observations and suppresses the normalized rate.
Disclaimer: This worksheet compares whole-second clock readings for operational troubleshooting. It does not verify the timestamp used for payroll, determine a clock's accuracy beyond the entered uncertainty, or provide payroll, legal or calibration advice. Verify all inputs, results and assumptions against appropriate records and obtain qualified advice before relying on them. To the fullest extent permitted by applicable law, this resource is provided "as is" without warranties of accuracy, completeness or fitness for a particular purpose, and TimeTrex and its affiliates disclaim liability for losses, damages, costs or claims arising from its use, inability to use, or reliance on it, including errors or omissions. Nothing in this disclaimer excludes or limits liability or rights that cannot lawfully be excluded or limited.
Trusted By
Join our ever-growing community of satisfied customers today and experience the unparalleled benefits of TimeTrex.
Strength In Numbers
Time To Clock-In
Experience the Ultimate Workforce Solution and Revolutionize Your Business Today
Saving businesses time and money through better workforce management since 2003.
Copyright © 2026 TimeTrex. All Rights Reserved.