Runsheets are collections of jobs that you schedule at sites within a zone. With TrackTik's Mobile Suite, users can complete runsheets in the mobile application. Users can perform jobs within a runsheet and finish the runsheet even if they haven't completed all the jobs. In this case, any other guard with access will be able to pick up where the previous guard left off.
- Select the Runsheets icon from the home screen.
- Select the runsheet you would like to perform.
- Confirm that you would like to start the runsheet.
Note: The application will warn you if you are too early to begin a runsheet. If the current time of day is within the planned runsheet time, you will see a list of jobs in the runsheet. Likewise, the application will tell you if there are no runsheets available to perform.
Why this happens: Runsheets are only visible in the mobile app within a defined time window around their scheduled time. A common configuration is up to two hours before the start time and up to five hours after the end time. If it’s too early or too late relative to the schedule, runsheets will not appear.What to check:
- Confirm the scheduled start/end times of the runsheet.
- Ensure your device’s time and timezone are accurate (use automatic date/time).
- Verify you are looking within the allowed visibility window. Your organization’s window may differ; check with your administrator.
- Review filters in the mobile app list view (e.g., date, site, status) to ensure runsheets are not being hidden by a filter.
- Sync the app or refresh the runsheet list.
How to view outside the window:
- Use the Web Portal (Mobile Dispatch > Runsheets Overview) to see upcoming or recently ended runsheets regardless of the mobile visibility window.
Admin Cancel Runsheet Feature
When an admin cancels a runsheet, the user will receive a push notification.
"This runsheet was closed. Please contact your supervisor for more details."
Note: App version 5.12.3 on Android and iOS: 3.10.2 and up required
Shared Device Handover and Runsheet Troubleshooting
If a new employee signs in on a device previously used by someone else, you may see errors or unexpected runsheet states.
To prevent and resolve these issues:
- Require a full sign-out and sync before handing off a device. The current user should:
- Complete or pause runsheets as appropriate.
- Manually sync (if your app has a sync control).
- Sign out from the account.
- Update the app. Ensure the device is running the minimum versions noted above, and update via the app store.
- Clear stale data. If errors persist, uninstall/reinstall the app to clear cached sessions and tokens, then sign in fresh.
- Avoid concurrent use. Do not use the same account across multiple devices at the same time, as it can cause state conflicts.
- Verify the device date/time and time zone. Incorrect clocks can cause schedule or status errors. Set automatic date/time and the correct time zone.
- Test updates on a single device first. Confirm stability before rolling changes to all shared devices.
- If errors continue, collect diagnostics for Support: device model and OS version, app version, account/employee ID, the runsheet(s) involved, timestamps, and screenshots or screen recordings.
Best practices for shared devices:
- Where possible, assign one device per employee. If devices must be shared, implement a check-out/check-in process that includes a full sign-out and sync.
- Define a policy to prohibit app handoff mid-runsheet to reduce conflicts.