A knocked-back SWMS feels personal, but it is usually mechanical: the reviewer checked for a handful of specific things, one was missing, and the document bounced. That is fixable today if you work the problem in order instead of resubmitting the same file with a new date.
First, read what the reviewer actually said
Most builders return a SWMS with a reason, even a short one. "Not site-specific" means your document describes a generic job, not this address and this scope. "Controls inadequate" usually means everything in your controls column is PPE. "Wrong legislation" means you cited another state's regulations, or federal-sounding boilerplate. If the rejection came with no reason at all, ask for one before you touch the document. A two-line email saves you from guessing wrong.
The four failures behind most knock-backs
**1. Generic content.** The site address is on page one and never matters again. The hazards could belong to any job in the country. Reviewers read hundreds of these documents and clock a template within a paragraph. The fix is not more words, it is your words: this site, this scope, these plant items, this crew.
**2. The wrong state's legislation.** A SWMS written for NSW cites the WHS Regulation. Take the same document to a Victorian job and it is wrong: Victoria runs its own OHS Regulations and does not use the harmonised numbering. Check every citation matches the state the job is in. Why SWMS get rejected covers the common citation traps.
**3. Controls out of hierarchy order.** Reg 36 puts the hierarchy of controls in law: eliminate or substitute first, then isolation and engineering, then administrative controls, then PPE. A controls column that opens with "wear gloves and hi-vis" for a fall hazard tells the reviewer nobody thought about the higher-order fixes. Reorder the controls and the same job reads completely differently.
**4. No consultation or sign-off.** Reg 299 requires the SWMS before the work starts, and reviewers expect evidence the crew doing the work has seen it: a sign-on block with names and dates. An unsigned SWMS reads as a document nobody uses.
Triage it in an hour
Work through the reviewer's reasons in this order: fix the legislation first (it is the fastest check), rewrite the hazard and control rows that are generic, reorder controls into hierarchy order, then add the sign-on block if it is missing. Run the result against a builder's review checklist before you send it back, because the second rejection costs more goodwill than the first.
Resubmit like a professional
Reply to the same thread, name what changed ("added trench collapse controls per your note, corrected citations to Victorian OHS Regs"), and attach the revised document with a new revision date. Reviewers accept fast when you make the diff obvious. Do not argue a point unless you are certain: if the reviewer wants a control you think is overkill, adding it is almost always cheaper than the standoff.
Stop it happening again
If your SWMS keeps bouncing, the template is the problem. How to review a SWMS shows you what reviewers check so you can self-audit before submitting. Or skip the cycle: generate a site-specific SWMS that is written for your exact job and state, verified before delivery, with free corrections within 24 hours if the builder wants changes, for A$39.