If you’re working through the National Code, Clause 1.4k is where the work gets operational.
Most teams get to this point having already updated policies, delivered training, and mapped out processes.
The question shifts from “have we done the work?” to “can we show that it actually works?”
This article breaks down what Clause 1.4k asks of your organisation, where most teams get stuck, and a practical place to start.
What is Clause 1.4k?
Clause 1.4k is part of the National Higher Education Code to Prevent and Respond to Gender-based Violence. It requires providers to conduct a systemic review of responses to disclosures and formal reports, identify barriers, gaps, and opportunities for improvement, and embed this into a Whole-of-Organisation Plan.
This is an operational requirement, not a policy one. We’ve written more about what the National Code means for higher education here.
Here is the Clause directly from the Act
What the requirement actually involves
Most teams can read Clause 1.4k and understand what it is asking.
The difficulty is translating that into something measurable.
You’ve started to put the work in. Mapping things out, working through spreadsheets, going back and forth over email to understand what sits where and who is responsible. Policies have been updated, training delivered, processes pulled together.
But the question becomes something else.
Did we do it right? Have we missed anything? And how does this measure up?
Because the expectation is not just that something exists. It’s that it is consistent, understood, and can be demonstrated. That it aligns with what is expected across the sector and, more importantly, with what the regulator requires.
The challenge isn’t understanding the requirement but if the action is “right”
From what we’re seeing across Institutes of HIgher Education, the challenge is not understanding what Clause 1.4k says. It’s being confident in how it’s been applied.
Common issues include no clear view of how disclosures are actually handled across the organisation, responses that vary depending on who is involved, processes spread across teams and systems, work being pulled together manually without a clear structure, and uncertainty about what “good” looks like in a regulatory context.
Most organisations have parts of this in place. What’s missing is a clear view of how it all fits together.
What a systemic review actually looks like
A systemic review is not a document, a one-off audit, or a policy review. It is an understanding of how your system operates in practice.
This means understanding what actually happens when a disclosure or report is made, mapping how decisions are made across teams, identifying where responses slow down or break down, assessing how consistent those responses are, and being able to show how this is improving over time.
That requires visibility across frontline response, escalation pathways, decision-making, and outcomes.
Where to start: the seven steps
If you’re approaching Clause 1.4k, the starting point is not to build something new. It’s to get a clear view of what already exists.
Step 1: Choose a real scenario
Start with a real disclosure or report. Not a hypothetical process. Something that has happened, or would realistically happen in your organisation.
The goal is to work with something concrete. A real scenario will surface real gaps in a way that a process map on paper never will.
Step 2: Map what actually happens
Work through the scenario step by step.
Where does it come in? Who receives it first? How is it recorded? Who is involved next?
Focus on what actually happens, not what is meant to happen. These are often very different things.
Step 3: Follow the decision points
Look at where decisions are made throughout the process.
Who is making them? What are they based on? Is there clear guidance, or does it rely on individual judgement?
This is where variation tends to live. And variation is what Clause 1.4k is asking you to find.
Step 4: Track how it moves across teams
Most responses don’t sit in one place. They move between teams, systems, and people.
Map this movement. Where does it go? Who picks it up next? What happens at each handover?
This is where things often become unclear, and where ownership gaps tend to appear.
Step 5: Look for variation
Repeat this across a small number of scenarios. You are not trying to map everything. You are looking for patterns. Where does the response differ? Between teams? Between individuals? Between similar cases?
Variation isn’t always a problem. But unexplained variation usually is.
Step 6: Identify where it breaks down
Look for the points where the process slows down, stalls, or relies on one person knowing what to do.
Common signs include unclear ownership, delays or bottlenecks, duplicated steps, and reliance on individual knowledge rather than system design.
These are the gaps Clause 1.4k is asking you to identify and address.
Step 7: Step back and connect it
Once you’ve worked through several scenarios, step back.
This is where the systemic part comes in. You start to see how the system actually operates, where the gaps are, and what needs attention first.
The goal is not a perfect picture. It’s a clear one. Something you can understand, explain, and stand behind.
That’s the work Clause 1.4k is asking for.
What comes next
Once you have a clear view of how responses actually work across your organisation, the assessment moves into identifying what needs to change and how to demonstrate consistent improvement over time.
We’ve put together a step-by-step guide to the full Clause 1.4e review process, with practical tools to help you move from a fragmented view to something you can report on and act from.
