Onetrace allows you to run reports for any custom timeframe, providing valuable insights into specific periods. The Timesheets report enables you to access consolidated information in table form regarding members, teams, and projects within your selected timeframe.
Generating this report allows you to view all the relevant data together in one place. This guide will walk you through the steps necessary to generate a Timesheets report.
Generate a timesheets report
How to generate a timesheets report:
Navigate to timesheets in the left-hand sidebar.
Select your date range by clicking the date in the top left corner or using the calendar.
Run the report from the overview page, or select a specific member. Use the filters at the top to view by date range, team, client, and projects.
Click Get report to download the data as an Excel file.
Access your report via email or the reports hub by clicking the report icon in the top right.
đĄ The Excel report includes:
Operative details - name, employee number, rates, and teams.
Time details - start and end stamps, duration, clock skew and total hours.
Location details - start and end distances with coordinates to identify clocking in and out discrepancies.
Time breakdown
Onetrace checks for clock skew by comparing device time against the server whenever someone clocks in or out. The clock skew columns show the time differenceâpositive numbers mean the device was ahead of the Onetrace server, and negative numbers mean it was behind. Time zones donât affect clock skew.
Clock Skew FAQs
What are the "clock-in skew" and "clock-out skew" fields in the Timesheets report?
They show the difference in seconds between the operative's device time and server (UTC) time at clock-in/out.
Where can I see this?
Clock-in and clock-out skew are fields in the timesheets report (given in seconds), and also appear as in-app indicators.
What does âclock mismatchâ mean?
It means thereâs a difference of more than 5 minutes between the operative's device time and server (UTC) time.
What does ânot confirmedâ mean?
It means there wasnât enough data to validate the device time (e.g. offline usage).
What does a large skew mean? Does it mean manipulation?
Not necessarilyâoffline work or delayed sync can cause this. Itâs a signal, not proof.
Does this prevent inaccurate timesheets from being submitted?
It doesnât block operatives from submitting their timesheetsâit surfaces issues so you can review them with context.
Can operatives bypass this using timezones?
Noâthis flag ignores timezones. Only actual differences between the device clock and server time affect it.
How should I use this in practice?
Use this as part of your timesheets review, alongside job context and activity history.
Location breakdown
Distances are measured based on the end location of the operative's device. The exact location of a device can be affected by various factors, including device hardware and battery, signal strength, user location permissions, surrounding structures, being below ground, etc.
These start and end distances will be empty if:
The timesheet was created pre-6th February 2026.
If the site lacks an exact address or a what3words location, find out how to add a site address here.
Timesheet was added manually.
Device location permissions are not enabled.