Overview

Quick answers to the questions operations teams ask most often about Central-Ops: generating jobs, allocations and conflicts, job acknowledgements, clocking on and off, the Driver's Kiosk and timesheets, booking changes, kilometres, the driver's tablet and fatigue. Each answer is short and links to the full article when you need more detail.

How to use this page

Questions are grouped by topic. To find an answer quickly:

  1. Press Ctrl + F (Cmd + F on a Mac) and type a keyword from your question, such as conflict, acknowledge or odometer. Press Enter to jump to each match on the page.
  2. Or click a topic in the contents list below to jump straight to that section.

Each section ends with 🧠 links to the full articles if you need more detail.

<aside> 💡 ❕ Note: If your question isn't answered here, email our support team at [email protected].

</aside>

Generating Jobs

Can I generate jobs for the same week more than once?

Yes. Central-Ops doesn't stop you generating the same rosters for the same dates again, so take care — each run creates another set of jobs. If it happens by mistake, see I generated jobs for the wrong dates below.

Do I need to stay on the Generate Jobs page until it finishes?

No. Generating jobs runs as a background batch, so you can close the page or carry on with other work. The batch status moves from Scheduled to In Progress, then to Succeeded or Failed.

How do I know if a job generation failed?

The Failed Generate Jobs Operation tile on the Operations page shows how many generations have failed. The reason for each failure is shown in the Fail Details column on the Generate Jobs page. The count stays on the tile until you either acknowledge the failure or fix it and run it again.

Why did my job generation fail?

If any part of a batch fails, no jobs are created from that batch at all. The most common causes are: