When someone can't start: asking for and allowing a start

When a requirement stops someone starting a job — an expired card, a missing unit, an induction the client insists on, a permit the job hasn't been granted — they shouldn't be left on site guessing. The phone says what is missing and who requires it, and the worker can ask a supervisor to let them start from the same card.

For how requirements are set up, see Eligibility: who is allowed to do the work.

On the phone: Why can I not start?

A worker's card in Work shows Not eligible (with the number of problems) or Needs attention when Maliru's background check has found something. Nothing is shown when everything is in place, before the work has been checked, or once it is over — a card is never painted green on a guess.

On a Not eligible card for work that hasn't happened yet, tap Why can I not start?. Maliru checks again there and then:

• If it has been put right since — a renewed card approved, or a card the office has now verified — the worker sees "You are clear to start this work."
• Otherwise Ask to start anyway opens: "A supervisor will see what is missing and decide." Each problem is listed with its source, for example "Site Induction is missing — required by Meridian Utilities". Add Anything they should know (optional), such as "card is in the van, certificate on my phone", and tap Ask. The worker sees "Asked. A supervisor will let you know."

Some requirements can't be waived by anyone — the credential or permit type is set to Stop the work; nobody can allow it. Asking is then refused, and the requirement has to be met first.

Clock-in gives the same answer. Trying to start blocked work is refused with "This work cannot start yet: …" and the reason.

In the office: Asking to start

Everyone with Override eligibility is notified straight away — "Someone is blocked from starting work", with what is blocking. Open Authorisations › Eligibility › Asking to start.

Each request is titled with the job's title and Asked by {name}, then shows Waiting to start, the problems exactly as they stood when the worker asked, and anything they wrote (They said: …). With no requests waiting, the tab reads "Nobody is waiting to start."

• Allow — a reason is required. "This is recorded against your name, and counted. It covers this job only." The worker is told "You can start this work", with your reason.
• Refuse — the reason is optional. The worker is told "You cannot start this work".

What an allow covers

Allowing a start waives the problems in the request, for that person, on that job. It doesn't clear the same problem on their other jobs, and it doesn't fix the credential or grant the permit. Their clock-in on this job goes through; the card can still read Needs attention, because the requirement still isn't met.

The office can make the same decision before the day: choosing Assign anyway while scheduling records an override for that person on that job, so they aren't refused on site. See Eligibility.

Every allow and refuse is written to the audit trail with who decided and why.

Who sees what

• The Asking to start tab only appears for people with Override eligibility. Owners have it; give it to others in Users › Edit access & role.
• Under Notification settings, the Authorisations & permits group has Someone is blocked from starting work, Your request to start work was granted, Your request to start work was refused and Scheduled work needs a compliance re-check.