> For the complete documentation index, see [llms.txt](https://docs.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roaddirect.co.nz/eboard/calendar/job-status.md). # Job status ## Job status Users with [access levels](/getting-started/user-access-levels.md) of Basic User and above can select a job status option. Only one option can be selected. Users with access levels above Basic User can also mark a status as ‘Actioned’. These boxes allow better communication about the status of a job between on-site staff and your operations staff. On-site staff can select a job status based on information from the client’s crew or sub-contractor on-site. Initially, when an option is selected by staff on-site, the job will be highlighted red on the Calendar. This provides immediate visual indication that the job 'Requires Attention' by operations staff (or other appropriate staff member). When an operations staff member ticks 'Actioned', the job highlight colour will change (as per table below). This indicates the operations staff member has confirmed the status with the client Both the chosen status option and the 'Actioned' checkbox record the initials of the staff member who updated these fields. Refer to the table below for highlight colours: | Job Status | Selected highlight | Actioned highlight | | ------------------------------------------ | ------------------ | ------------------ | | Job Completely Finished (Ready to Invoice) | Red | Dark Grey | | Job Ongoing – Dates Confirmed | Red | Light green | | Job Ongoing – Dates TBC | Red | Grey | | Job Becomes Dry Hire & Handover Completed | Red | Dark green | If no status has been selected, or the job has not been indicated as a cancelled/call-out job (see [Cancellation/Call-out status](#cancellationcall-out-status)), the job will not be highlighted. A suggested use of these colours: * Operations staff should aim to have no red highlighted or un-highlighted jobs for a day * Jobs that remain red or un-highlighted at the end of the day should be investigated by operations staff: * the job status needs to be set and actioned by the end of the day, whether it is either Cancelled, Callout, Ongoing, Dry hire or Ready to invoice * jobs with no status set may indicate that the job has not gone ahead as planned and should be removed from that day ## Cancellation/Call-out status Users with [access levels](/getting-started/user-access-levels.md) of Basic User and above can choose cancellation/call-out status options. You may check more than one option (for example, if a call-out job was cancelled while staff were on their way to the job). Cancellation/call-out status highlights the job on Calendar view, with its own highlight colour for each of these options: * Call out * Job Cancelled After Left Base * Job Cancelled While You Were At Base If a cancellation/call-out status is checked, the highlight colour will "trump" the job status highlight colour, even if the job status has been 'Actioned'. The job status can still be viewed by clicking on 'Job status' in the context menu for each job on the Calendar. A suggested use of these colours: * The colours can indicate to TTM managers what steps may need to still happen for the job (for example, a retrospective TMP may need to be sent to the RCA) * The colours can indicate that special invoicing rules need to be applied for these types of jobs (for example, minimum charges, cancellation fees or call out fees etc.) ## Additional Resources [Job Status tutorial (YouTube)](https://youtu.be/6iMENGBeCJs) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.roaddirect.co.nz/eboard/calendar/job-status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.