You’ve just opened the email. Your CM3 submission has come back — not approved, but rejected, with a list of assessor findings that reads like a foreign language. Meanwhile, your client’s procurement team is waiting on your prequalification before they can raise the purchase order, and every day this drags on is a day you’re not on site earning.
If that’s you right now, take a breath. A rejected CM3 submission is common, it’s fixable, and in most cases the problems fall into a handful of predictable categories. I’ve reviewed a lot of failed submissions over the years, and the same issues come up again and again. This article walks through why contractors fail CM3 assessment, what the rejection email doesn’t spell out, and the fastest way to get through — whether you’re resubmitting or starting fresh.
Quick context if you’re new to this: CM3 is a contractor WHS/OHS prequalification scheme run by Greencap (a Wesfarmers company). Your documentation goes through a desktop assessment by qualified WHS assessors, and the requirements scale with the risk profile of your trade. If you want the full background first, start with our guide on what CM3 is.
Why CM3 submissions actually get rejected
Rejections rarely come down to one big mistake. It’s usually two or three of the following stacked on top of each other.
Generic SWMS that don’t match your declared risk profile
This is the most common failure I see. A contractor declares high-risk construction work — working at heights, electrical, confined spaces, whatever applies to their trade — and then uploads a Safe Work Method Statement bought online or borrowed from a mate that doesn’t address those specific risks. The assessors compare your SWMS against the work you’ve declared. If you’ve told them you do roof work and your SWMS never mentions fall prevention, that’s a finding. A template is a starting point, not a submission.
Questionnaire answers that contradict your evidence
The CM3 questionnaire asks what your business does and how you manage safety. Your uploaded documents are the proof. When the two don’t line up — you answer “yes, we have a documented incident reporting process” but nothing in your uploads shows one — the assessor has to treat the answer as unsupported. Contradictions are worse than gaps, because they undermine confidence in the whole submission.
Entity and ABN mismatches on insurances
A surprisingly frequent one. Your CM3 registration is under your Pty Ltd, but your public liability certificate names your old sole-trader entity, or the ABN on your workers compensation certificate doesn’t match the ABN you registered with. To an assessor, that insurance doesn’t cover the entity being assessed. Check every certificate: legal entity name, ABN, and trading name should all match your registration exactly.
Expired documents
Insurance certificates of currency, licences, training cards — if it lapses before or during assessment, it’s a finding. Contractors often upload whatever’s in the folder from last year without checking dates. It takes five minutes to verify and saves a full rejection cycle.
Missing training evidence for the work you’ve declared
If you declare electrical work, the assessors expect to see electrical licences. Declare working at heights, they expect heights training. Declare operating plant, they want the relevant high-risk work licences or verification of competency. The rule is simple: every activity you tick should be backed by evidence that the people doing it are trained to do it. Declared work with no matching training records is one of the fastest routes to rejection.
Ignoring assessor feedback — or only answering part of it
This is the one that turns a two-week process into a two-month ordeal. The rejection email lists findings; the contractor fixes the first two, skims the rest, and resubmits. Back it comes. Every finding needs a direct, complete response — and if you don’t understand what a finding is actually asking for, guessing at it usually costs you another cycle.
What the rejection email doesn’t tell you
Here’s the part that catches most contractors off guard: assessors reassess the whole submission each cycle, not just the items they flagged last time. So when you fix the two findings from round one and resubmit, the assessor reviews everything again — and may raise new findings on documents they didn’t comment on before, especially if your fixes changed the picture. It can feel like the goalposts are moving. They’re not; the submission is simply being looked at fresh, as a whole, every time. This is exactly why partial fixes are so costly: each resubmission cycle typically adds a week or more while your client’s purchase order sits waiting.
The other thing the email doesn’t teach you is how to read the feedback properly. Assessor findings are written in WHS-system language — “objective evidence,” “documented process,” “demonstrated implementation.” When a finding says your evidence doesn’t demonstrate something, it’s usually asking one of three questions: does the document exist, does it actually cover the declared risk, and is there proof it’s used in practice (signed records, completed forms, dated registers)? Before you touch anything, map every finding to one of those three questions. If you can’t tell which one it is, that’s a sign to get help rather than burn another cycle finding out.
How to pass first go (or on the resubmission)
Whether you’re preparing a fresh submission or rescuing a rejected one, the sequence is the same.
- Lock down your risk profile first. Only declare the work you actually do. Every declaration creates an evidence obligation, and over-declaring is the number one way contractors create work for themselves.
- Build the evidence to match — before you answer the questionnaire. Gather the nine documents CM3 asks for and check each one against your declared activities. If you’re building documents from scratch, professionally structured templates beat a blank page — but they must be tailored to your trade and your declared risks.
- Verify entity details on everything. Same legal name, same ABN, across your registration, insurances and licences. No exceptions.
- Check every expiry date — and if anything expires within the assessment window, renew it before you submit.
- Answer the questionnaire from your evidence, not from memory. Every “yes” should point to a specific uploaded document. If you can’t point to one, either create the evidence or change the answer.
- If you’re resubmitting, respond to every finding completely — then re-check the rest of the submission as if it were being assessed for the first time. Because it will be.
- If you’re on multiple client portals — say CM3 for one client and Avetta or CBRE Pulse for another — build your documentation once, properly, so the same core system serves every portal instead of reinventing it each time.
Do all of that and you’ve given yourself the best possible shot. To be clear, nobody outside Greencap can promise you an approval — the decision always sits with CM3’s assessors. What you can control is submitting evidence that gives them no reason to say no.
Stuck right now? Fastest way out
If your submission has been rejected — or it’s been sitting half-finished for weeks while the client chases you — this is exactly what we do. iHSEQ provides CM3 prequalification help for contractors across Australia: we review the assessor feedback line by line, identify every gap (including the ones they haven’t flagged yet), fix the documentation, and get your submission back in properly — once, not four times.
The fee is fixed at $650 + GST, and the price quoted is the price paid — no surprises partway through. You stay in control throughout: we prepare everything, but the declarations remain yours, so you review and authorise before anything is submitted. We’re based in Silverwater, Sydney, and work with trade contractors Australia-wide.
The consultation costs nothing. Call 0415 530 008 or get in touch through the site — we’ll call you back within one business day, tell you honestly what’s wrong with your submission, and give you a clear path to getting it through. Your client’s PO is waiting; let’s not give it a reason to wait longer.




















