What this guide covers
- How to open an assigned job.
- How to use job notes, access notes, and linked site detail.
- How job actions work in complete and incomplete tracking modes.
How it works
Mobile is the execution surface for jobs. It should give staff what they need on-site without making them dig through admin screens.
The job page is where the work happens: review context, carry out the task, then use the action that matches the organisation's tracking mode.
Common workflows
Prepare before arriving
Open the job, read the access notes, and confirm the site before the team gets out of the van.
Complete or flag issues on-site
Use the right status action for your tracking mode instead of improvising a separate workflow.
Steps
Open the job sheet
Mobile app -> Schedule or Jobs -> Select job- 1Open the assigned job from the schedule or jobs list.
- 2Review the title, timing, linked site detail, and any job notes.
- 3Check `Parking, Access & Green Waste` before travelling if the job depends on gate codes, parking rules, or site-specific handling.
Use the right on-site action
Job detail -> Main action- 1If your organisation uses `complete` mode, start the job when work begins and mark it complete when finished.
- 2If your organisation uses `incomplete` mode, do not start or complete the job manually. Only flag it incomplete when something went wrong.
- 3Add the supporting note or context straight away if the team needs to explain what changed.
Capture the context around the work
Job detail -> Linked actions- 1Use related actions like gallery or timesheets when the job needs evidence or time logging.
- 2Keep the work attached to the live job where possible so admin follow-up stays easy.
- 3Return to the schedule when you are ready for the next stop.
Tips and gotchas
- If you only need one thing before arrival, make it the access notes.
- Use the main status action that matches your organisation settings. Avoid inventing a parallel process in notes or chat.
- When the job changes in the field, add the detail while you are on the page rather than trusting memory later.