Sometimes a worker may change the time on their device so that it no longer reflects the real time. The Flag time discrepancies setting helps you spot when a recorded time may not be reliable, so you can review it before you trust it. It’s best for forms where accurate timestamps are required, like sign in and sign out.
This feature is in beta. While it’s in beta, some forms may be flagged for ordinary reasons, most often offline submissions. Treat a flag as a prompt to review, rather than proof of tampering.
Prerequisites
Before you begin make sure you have the following:
Plan: All plan types
Permission: Org Controller
Required Platform: Dashpivot
Device Type: Computer (web only)
What is time tampering?
Most phones and tablets set their time automatically from the mobile network. A worker can turn that setting off and set the clock manually, forward or back. If they fill in a sign in or sign out form while the clock is changed, the form records the altered time instead of the real one.
For example, a worker who signs in at 9:00 am could set their device clock to 7:00 am first, so the form records a 7:00 am start. The same could be done at sign out to record a later finish. Because the recorded time comes from the device, the form can’t tell on its own that it’s wrong.
How do I enable the time tampering warning?
In your template settings, toggle on Flag time discrepancies.
Where does the warning appear?
The warning shows on Signature and Location fields, which are typically used to record when a worker signed in or out. The warning appears in Dashpivot on web only (in the form itself and the Register view). The warning does not show in any CSV or PDF exports.
How it works
The flag compares two times:
The device time taken from the phone or tablet's clock when the worker captures their location or adds a signature. This is the time that can be changed on the device.
The server time recorded by our servers the moment the form reaches them. This can't be changed from a device.
If the two times are more than 30 minutes apart, the Location and/or Signature fields in the form are flagged for review, so you can see exactly which entry to check.
Why 30 minutes? Device and server times are always slightly different by a few seconds or minutes, due to short delays when a form syncs. The 30-minute threshold sits clear of that minor difference, so a form is only flagged when the gap is large enough to be worth a look.
Why might a field be flagged for an ordinary reason?
A flag is a prompt to check, not proof the time was changed. There are two common innocent causes:
Offline work. A form filled with no signal only reaches Dashpivot once the device is back online, and that delay can trigger a flag.
A form left in draft. A worker might start their sign in and sign out forms at the start of the day and submit the sign out form at the end. Because the Location or Signature was captured hours before it was submitted, the gap gets flagged, even though device time wasn’t changed.
What should I do when I see a flag?
Review the flagged field and the time it recorded. If it looks off, follow up with the worker to confirm what happened.
Frequently Asked Questions (FAQ)
Q: Does the flag appear in CSV or PDF exports?
No. The flag is only visible in Dashpivot on web — in the form itself and the Register view. It does not appear in any exports.
Q: Does the flag appear on mobile?
No. The warning is currently available on Dashpivot Web only.
Q: Can I turn this off for a specific form?
Yes. The Flag time discrepancies setting is configured per template. Toggle it off in the template settings if you don't need it for a particular form.
Q: What should I do if offline workers are regularly getting flagged?
A flag from an offline submission is not a sign of tampering. If your team frequently works offline, treat flags on those forms as expected and review the submission context before following up with the worker.