Mechanic
Start, pause, resume and finish tracked work
Start, pause, resume and finish mechanic work sessions while keeping job status and recorded labour consistent.
Work sessions record active mechanic time against an assigned job. They distinguish a temporary pause from completed mechanic work and provide saved history that contributes to the job's labour view.
The timer uses the server's time rather than relying only on the phone clock. Only one active session can exist for a mechanic at a time, which prevents overlapping labour across jobs.
Timer actions
| Action | Use it when | Result |
|---|---|---|
| Start | No earlier session exists and the in-progress job is beginning | Opens an active work session |
| Pause | Work stops temporarily, for example for parts or another authorised interruption | Closes the active segment as paused |
| Resume | A previously paused job is ready to continue | Opens a new active segment on that job |
| Finish | The mechanic's work is complete and ready for the next workshop stage | Closes the active segment as finished |
Start a reliable session
- Open the exact assigned job and confirm it is in progress.
- Check the work panel for another active job or an existing completed session.
- Choose Start or Resume once, then wait for confirmation.
- Confirm the active-time counter and start timestamp are visible.
- Keep normal notes and inspection evidence separately; the timer measures time, not task detail.
Pause versus finish
Pause means the same mechanic may return to the job. It is appropriate before moving an in-progress job to awaiting parts. Resume creates the next active segment, while saved time remains in history.
Finish means the mechanic's recorded work is complete. The job can then be sent to quality check when the frontend confirms a finished session and no timer remains active. If work later genuinely resumes, the office should first ensure the job status reflects that change.
Duration and labour history
The panel distinguishes active elapsed time, saved closed-session time and total time. Closed sessions retain their start, end, duration and whether they ended through pause or finish. The job labour total is synchronised from closed history.
An active display can continue counting locally between server snapshots, but the saved result comes from the confirmed session. Refresh the job if a phone was suspended for a long time or another authorised action changed the job elsewhere.
Conflicts and safe retry
If another job already has an active session, MotoDesk identifies that conflict instead of opening overlapping time. If two actions arrive close together, only the valid current-state change is accepted. A connection failure can make the visible result uncertain even when the server received the action.
When the interface offers Retry same request, use it rather than creating a new action repeatedly. MotoDesk can return the original result for that pending action. After retry, refresh and verify the active session and history before pressing another timer control.
| Conflict | Resolution |
|---|---|
| Active session on another job | Pause or finish that exact job first |
| No active session | Refresh; start or resume only if the job state allows it |
| Session already closed | Refresh history; do not submit another close action |
| Job status changed | Refresh the job and follow the actions now offered |
Example day
The mechanic starts a brake job at 09:05, pauses at 09:42 while an advisor confirms a part, and resumes at 10:10 after the part is issued. At 10:48 the mechanic finishes, adds the inspection evidence and sends the job to quality check. The job shows two closed work segments whose durations contribute to the saved labour time.