Year 7 reading level isn't a target. It's a constraint that should change how you write everything.
The Australian Government Style Manual asks for a year 7 reading level for government content in Australia. Most agencies treat this as a check at the end of editing. That is the wrong place for it.
A year 12 paragraph cannot be cut down to year 7 by swapping in shorter words. The reading level is set by sentence shape, not vocabulary. By the time you measure, the structure has already chosen for you.
In my experience, the same pattern shows up everywhere. A team runs the draft through a tool, gets a year 11 score, and starts deleting "ensure" and "utilise". The score does not move. They blame the tool.
What sets the reading level
A year 7 reader handles short sentences with one main idea. They follow a list better than a clause. They lose the thread when a verb sits eight words after its subject.
The structure decides the score before the words go in. Three things drive it:
Sentence length. Aim for 15 to 18 words. Anything over 25 is a hazard.
Sentence shape. One subject, one verb, one main idea. Cut the connectors.
Paragraph density. One claim per paragraph. Two at most.
Vocabulary matters last. If the sentence is the wrong shape, no word swap will fix it.
Why edit-stage checks fail
Australian readability assessments such as the Ethos CRS scorecard keep finding the same gap. Federal agency content scores at year 12 or higher, even though those agencies cite the Style Manual's year 7 target.
That gap is not a writing problem. It is a process problem.
The drafter writes in their own register. The subject matter expert marks it up in policy register. The editor is asked to flatten the result down to year 7 in the last hour before sign-off. The structure is locked by the time it arrives.
You cannot edit a year 12 paragraph into a year 7 paragraph. You can only re-write it. That is a different cost and a different skill, and it never gets scoped that way.
The Digital Inclusion Standard makes this a compliance question
The Digital Inclusion Standard took effect for all public-facing Australian Government services on 1 January 2026. Its "Make it accessible" criterion ties reading level to compliance, not style.
This shifts the conversation. Readability is no longer something a content team negotiates with a comms director. It is now something the agency must show in its assurance reporting.
If the page scores year 12, the page does not meet the standard. The risk is real, and it sits with the accountable officer.
What to do instead
Decide the reading level before the first sentence is drafted. Treat it as a constraint on the brief, not a target for the edit.
Three changes that work:
Brief writers in plain structure, not plain words. Set sentence length and shape rules. Hand them a one-page guide, not a Style Manual extract.
Move the readability check forward. Score the first paragraph, not the final draft. If the structure is wrong at sentence two, fix it before you write sentence three.
Stop using Microsoft Word's reading score as the only check. It rates syllables and sentence length, not whether a year 7 reader could act on the page. Pair it with a small user test, even a five-minute one.
A team I worked with last year cut average sentence length from 26 words to 16 words across one service. The reading score dropped from year 12 to year 8. They did this without changing a single piece of policy content. They changed the shape.
What this article tries to do
This piece is written at year 7. The sentences are short. Each paragraph holds one idea. The structure was decided before the first word was typed.
If your draft does not look like this, the score will tell you. But the score is a symptom. The structure is the thing.
What would change if your team treated the reading level as a constraint on the brief, not a target for the edit?