Schedule and field operations
Clock in and out, choose the right work, and recover from a missed punch
Record field time against the right project/item/cost code and know what to do when a punch is missing or blocked. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.
Before you begin
- Audience: Standard user, field user.
- Job Clock module and per-user flag enabled
- accessible work target
- required location/cost code
- device permission and connectivity when applicable.
Job Clock controls in portal/mobile; mobile web entry under #/m; corrections reviewed in Time Entries (#/time-entries)
Clock in and out, choose the right work, and recover from a missed punch
-
Open the workspace
In JobBuddy, go to Job Clock controls in portal/mobile; mobile web entry under #/m; corrections reviewed in Time Entries (#/time-entries).
-
Confirm access and starting state
Job Clock module and per-user flag enabled; accessible work target; required location/cost code; device permission and connectivity when applicable.
-
Complete the main setup
Review selecting target/cost code, starting/stopping, active-clock visibility, web/mobile sync expectations, offline/missed punch recovery, error messages, and when to request an edit instead of creating overlapping time.
-
Verify the result
Record field time against the right project/item/cost code and know what to do when a punch is missing or blocked.
Expected result: Record field time against the right project/item/cost code and know what to do when a punch is missing or blocked.
Troubleshooting
The page, control, or action is unavailable.
Confirm the required access and starting state: Job Clock module and per-user flag enabled; accessible work target; required location/cost code; device permission and connectivity when applicable.
The result is incomplete or unexpected.
Job Clock enablement, work hours, geofence/location, project/item access, cost-code requirements, parallel-clock policy, network sync, and maximum duration can all block or alter a punch.
The issue remains after checking the record.
Capture the exact visible error, record status, approximate time, and intended result. Give support only the minimum customer-safe evidence needed to trace the problem.
What happens next
- Record field time against the right project/item/cost code and know what to do when a punch is missing or blocked.
- Review the resulting record, status, notifications, and related history before continuing downstream work.
- Use the related guide when the next action belongs to another JobBuddy workflow.