Which Joker Portrayal Are You?

1
If there was an incident tomorrow, how quickly could you produce proof that every worker on site was competent and inducted for that site/task?* This field is required.
A: Not confident we could prove it
B: Same day, with some digging
C: Within an hour
D: Within 5 minutes (it’s all in one place)
2
Before someone travels to site, who signs off that they’re actually site-ready (tickets, medical, inductions, site requirements)?* This field is required.
A: No clear sign-off (we just do our best)
B: It depends who’s available
C: A named person, but it’s mostly memory / experience
D: A named person + a consistent checklist/process
3
How do you manage compliance for subcontractors (their tickets, inductions, medicals, licences) compared to your employees?* This field is required.
A: We don’t have a consistent process for subcontractors
B: We rely on the principal/client to check
C: We collect docs, but it’s stored separately
D: Same system + same checks before mobilisation
4
When a ticket/medical/induction gets updated, how do you make sure the old version doesn’t get used by mistake?* This field is required.
A: No consistent process
B: We keep both and hope people pick the latest
C: We manually replace files and rename them
D:Automatic replacement + clear “current” status
5
Where do you currently track worker licences, tickets and medicals?* This field is required.
A: In my head / scattered files
B: Spreadsheets owned by one or two people
C: Shared spreadsheets with some structure
D: A central system that flags expiries automatically
6
How confident are you that nobody turns up to site with an expired ticket?* This field is required.
A: We find out at the gate
B: We usually catch issues, but only after a scramble
C: We have a manual process that mostly works
D: We get proactive alerts and have a clear view of expiries
7
How easy is it to see, for each person, all their current tickets, medicals and inductions in one place?* This field is required.
A: Very hard it’s spread across different files/folders
B: Possible, but only with a lot of digging
C: We can usually piece it together from a main spreadsheet
D: Very easy one view per person with everything visible
8
How do you assign people and equipment to jobs?* This field is required.
A: Phone calls, texts, and whiteboards
B: Spreadsheets built for each shutdown / project
C: A calendar tool + manual cross‑checking
D: A scheduler that shows who’s compliant and available
9
How often do you reshuffle people at the last minute due to compliance issues?* This field is required.
A: Weekly
B: A few times a month
C: Rarely
D: Almost never – we can see compliance before assigning
10
Can your crews see where they’re meant to be and when, without calling someone?* This field is required.
A: No they usually text or call
B: Some can, most still need to ask
C: We send out rosters manually
D: They have a live schedule they can check themselves
11
How do you decide who needs what training or VoC next?* This field is required.
A: We react when someone’s turned away or fails an audit
B: We occasionally run a manual review
C: We track some training needs in a spreadsheet
D: We run a structured Training Needs Analysis with clear priorities
12
Do you have a clear view of skills gaps for key roles or sites?* This field is required.
A: No we’re mostly reactive
B: Roughly, but it’s manual and time‑consuming
C: We have some visibility, but it’s not complete
D: Yes we can see current, due soon, and gaps by role/worksite
13
When a client or auditor asks for proof of compliance, how long does it take?* This field is required.
A: Hours or days
B: 1–2 hours with a scramble
C: 15–60 minutes
D: A few minutes – we can run a report instantly
14
Do you have regular, reporting for skills, expiries, and compliance?* This field is required.
A: No it’s all ad‑hoc
B: Occasionally, when someone has time
C: We have some manual reports
D: Yes reports are automated and scheduled
15
Do you have a clear view of skills gaps for key roles or sites?* This field is required.
A: No we’re mostly reactive
B: Roughly, but it’s manual and time‑consuming
C: We have some visibility, but it’s not complete
D: Yes we can see current, due soon, and gaps by role/worksite
16
Email* This field is required.
example@example.com
17
Calculation
18
High Compliance Risk

Indicative peer benchmark: 60% of Australian contractors fall in this band. Typically known as the “firefighting” band.

Right now, compliance is getting managed poorly and is exposing you to extra cost and risk. It lives in people’s heads, inboxes and spreadsheets, and it depends on last‑minute checking to get crews through the gate. That works… until a shutdown happens, a principal contractor changes requirements, or someone asks for proof “right now”.

When the system is fragile, you don’t just feel stressed you wear real cost: delayed mobilisation, missed shifts, crew swaps, and admin time that quietly eats your margin.

What this typically costs (even when nothing “goes wrong”)

For a 10–25 person contractor, weak compliance and mobilisation commonly shows up as:

2–6 hours/week of avoidable admin chasing and checking (and it usually sits with one key person)

Gate/requirement issues that trigger rework: calls, screenshots, re-uploads, re-bookings, crew reshuffles

That combination often lands in the tens of thousands per year - and in a shutdown-heavy year it can push into six figures simply through disruption and lost utilisation. This is also the zone where scrutiny hits fast after any serious incident or audit request.

Put simply: if you can’t quickly prove who was compliant, for what site, on what day, you’re exposed, commercially and operationally. (This isn’t legal advice. It’s practical risk reality.)

How to improve (without creating more admin)

Stabilise the basics (next 7 days)

Create one source of truth for every worker: tickets, inductions, medicals, VOCs, key docs, expiry dates

Define “site‑ready” as yes/no (not “almost”)

Run a 48‑hour pre‑mobilisation check every time (no exceptions)

Tighten control (next 30 days)

Set automatic reminders well before expiry dates (not the day before)

Standardise document naming so you can find proof fast

Lock it in (ongoing)

Build a repeatable mobilisation process so the business doesn’t rely on one person “remembering everything”

Make compliance visibility part of weekly ops: what’s expiring, who’s deployable, what’s blocked, what needs booking

GO! Site Ready supports this by keeping tickets, inductions, medicals, documents, expiries, and availability in one place so mobilisation becomes a process, not a scramble.
19
Moderate Compliance Risk

Indicative peer benchmark: 28% of Australian contractors fall in this band. Often the “mostly covered” band.

Compliance and contractor mobilisation isn’t a mess, it’s just not controlled. You’ve got the documents. Most people are compliant most of the time. The problem isn’t effort; it’s repeatability.

This is the zone where things run fine… until complexity hits. Add multiple sites, shifting requirements, subcontractors, or a key admin person being away, and the cracks show up fast: repeated checking, double-handling, and last‑minute surprises. You’re not in constant firefighting but you’re paying a “friction tax” every week.

What this looks like on the ground

In a “mostly covered” setup, the symptoms are usually:

Compliance info exists, but it’s scattered (folders, inboxes, spreadsheets, portals)

The hard question takes too long: “Who’s compliant for Site X next Monday?”

Expiries get handled… but sometimes too late (bookings become urgent instead of planned)

Site requirements sit as “tribal knowledge” (one person knows, or it’s buried in emails)

Subcontractors create noise: random formats, inconsistent naming, proof is slow to pull

Mobilisation relies on buffers (“we’ll allow extra time”), which feels safe but reduces throughput

What this typically costs

For a 10–25 person mining contractor, “mostly covered” compliance typically costs $50k–$120k per year in avoidable admin + disruption.

At this maturity level, the main leakage is time + missed windows:

Extra admin hours chasing, checking, re-uploading, confirming

Supervisors/leading hands pulled into paperwork and calls

Crews waiting for a green light, or being reshuffled late

In mining and heavy industry, small delays can carry serious consequences. Workforce readiness isn’t the only cause of downtime - but when mobilisation is slow or uncertain, you feel the same operational hit: lost hours, missed access windows, pressure on supervisors, and margin leakage.

How to improve

The goal here isn’t “more compliance work”. It’s making readiness visible and repeatable.

Make the rules visible (next 7–14 days)

Write down what each site actually requires (tickets, medicals, inductions, role/VOC, documents)

Keep it in one place so it’s not dependent on memory or inbox archaeology

Move to a clean readiness status (next 14–30 days)

Map every worker against each site’s requirements

Use a clear yes/no “site‑ready” status (not “almost”, not “should be right”)

Get ahead of expiry pain (ongoing)

Use a simple 30/60/90-day runway so expiries are booked calmly, not urgently

Aim for “no surprises” — especially before shutdown periods

Link scheduling to readiness (ongoing)

You should be able to answer: “Who’s available and compliant for this site next Monday?” in under a minute

If scheduling isn’t connected to readiness, you’ll keep paying the double-handling tax GO! Site Ready helps by matching site requirements to worker compliance, tracking expiries with runway, and keeping proof easy to pull when a client asks - so mobilisation becomes consistent, not dependent on one person holding it all together.
20
Low Compliance Risk

Indicative peer benchmark: 12% of Australian contractors fall in this band. Often named the “Controlled” band.

You’re doing what most contractors say they do but you’ve actually made it repeatable. Compliance isn’t living in someone’s head. Mobilisation doesn’t depend on heroics. When sites change requirements or you’re ramping up for a shutdown, you don’t scramble you adjust and keep moving.

This is where strong contractors win: fewer surprises, faster mobilisation, better utilisation, and less margin leakage.

What this looks like on the ground

Well done! your setup is working really well.

There’s one source of truth for tickets, medicals, inductions, VOCs and key documents

Site requirements are written down and easy to check (not buried in emails)

You can answer quickly: “Who’s site‑ready and available for Site X next Monday?”

Expiries are managed with runway - booked calmly, not urgently

Subcontractors are kept tidy: standard doc requirements + consistent naming

Proof is easy to pull when a client asks, audit requests don’t derail the week

Mobilisation is a process

What this typically saves you

At this level, you're avoiding the costs that hit "mostly covered" contractors hard:At this maturity level, the main leakage is time + missed windows:

$10k–$30k/year in avoidable admin + coordination timeSupervisors/leading hands pulled into paperwork and calls

$10k–$20k/year in supervisor/leading hand disruption

$10k–$70k/year in gate turnarounds, crew swaps, and lost utilisation

In mining and heavy industry, small delays can carry serious consequences. Workforce readiness isn’t the only cause of downtime - but when mobilisation is slow or uncertain, you feel the same operational hit: lost hours, missed access windows, pressure on supervisors, and margin leakage.

How to improve

Even strong systems break when headcount and sites increase. The next step is to make sure your standard scales:

Keep site requirements current and owned (review monthly or whenever a client updates requirements)

Maintain a strict yes/no "site‑ready" status so "nearly" doesn't creep back in

30/60/90-day view, reviewed weekly, no surprises before shutdown periods

Availability and compliance stay linked so scheduling doesn't create double-handling

GO! Site Ready supports this level by keeping requirements, readiness, expiries, and proof in one place so your current standard stays consistent as workloads, sites, and subcontractors increase.
Should be Empty: