Public Sector Intranet Requirements for Australian Government Agencies
A government intranet has a harder job than most public websites. It has to serve staff who have no choice but to use it.
That changes the standard. A public site that frustrates someone loses a visitor. An intranet that frustrates someone costs the agency that person's time, every day, and quietly pushes work back into email and shared drives.
This guide sets out the requirements worth writing into a specification before you approach the market, and the ones agencies should be able to answer without hedging.
Key Takeaways
- Since 1 July 2024 the Digital Service Standard applies to new and replacement staff-facing services, so a new intranet is in mandatory accessibility scope.
- Establish which WCAG version you are being quoted against. WCAG 2.2 Level AA is the current reference point, and older contracts still cite 2.1.
- Findability is the requirement staff actually care about. Search, filtering and a directory that works beat any amount of visual polish.
- Integration with existing systems determines whether the intranet becomes the front door or another silo.
- Ask for evidence of delivery at your scale, in your sector, with the same compliance obligations.
Accessibility Is Not Optional, and the Version Matters
The Commonwealth Digital Service Standard v2.0 carries the accessibility and inclusion criteria, and since 1 July 2024 it applies to new and replacement staff-facing services as well as public-facing ones. Only existing staff-facing services sit outside that scope. A new intranet is a new staff-facing service.
Be careful not to confuse this with the Digital Access Standard, which is a separate instrument about reducing duplicate entry points and myGov onboarding. It says nothing about accessibility.
On version, WCAG 2.2 Level AA is now the reference point for Australian government digital services and for Digital NSW. The Standard no longer pins a version number, it requires the latest, and that is 2.2. Plenty of older policy documents and live contracts still cite 2.1. The practical instruction for a buyer is simple: establish in writing which version you are being quoted against, because the difference is real work.
Underneath the standards sits the Disability Discrimination Act 1992, and that obligation binds the organisation providing the service. A supplier contract does not transfer the statutory duty.
Findability Is the Real Requirement
Ask staff what is wrong with the current intranet and you will hear the same answer in different words. They cannot find things.
That makes search, filtering and structured content the core of the specification, not a nice-to-have at the end of it. A policy nobody can locate has the same operational value as a policy that was never written.
What Works
Webcoda's intranet work has consistently centred on this problem. For NSW Justice Health, that meant a searchable, filterable and exportable employee directory, a media hub with trending-document filtering, and a knowledge hub for policy storage. For MA Financial Group, an employee directory with filtering and messaging alongside a secure knowledge hub with filter, search and sort.
The pattern repeats because the problem repeats. Staff need to find a person, a document or a policy, and the interface either helps them or does not. Where the policy library is large, an assistant that answers from your own documents is worth scoping alongside conventional search, though it depends entirely on the content being structured well enough to retrieve.
Integration Decides Whether It Gets Used
An intranet that does not connect to the systems staff already use becomes another place to check. Another tab, another login, another thing to forget.
The requirements worth specifying are the connections: identity and single sign-on, document management, the HR system that feeds the staff directory, and any operational feed that gives people a reason to visit daily. For NSW Health at 1 Reserve Road, that included a staff directory and an interactive floor plan, which is a small feature that answers a genuinely frequent question.
At the Anglican Schools Corporation, Webcoda delivered 17 schools from one platform, with custom reusable web parts covering knowledge libraries, galleries, news carousels and event calendars, a staff directory showing org structure and online status, a document hub, a live lesson-schedule feed and per-school colour and logo theming across more than ten page templates. Multi-entity delivery of that kind is common in government too, where one department hosts several agencies or regions with distinct identities.
Governance, Security and the Long Tail
Intranets rot faster than public sites because nobody outside the organisation sees them decay. Content governance and workflow belong in the specification: who publishes, who approves, what expires and who is told when it does.
Security and privacy compliance need the same treatment, particularly where an intranet holds staff personal information or sensitive operational material. Webcoda built Metropolitan Memorial Parks with security and compliance requirements around sensitive family information, and that project also recorded a 45% reduction in time-to-content through improved navigation and a 30% decrease in administrative tasks.
Those two numbers are worth holding in mind when someone argues that navigation is a cosmetic concern.
What to Ask For During Procurement
Ask for delivery evidence at your scale, in your sector, under your obligations. Not a logo wall. Specific projects, with the problems named and the mechanisms described.
Ask which WCAG version is being quoted, and whether accessibility is tested during build or audited at the end. Ask how content governance is enforced rather than merely documented. Ask what happens in year three, when the launch team has moved on.
Where Webcoda Fits
Webcoda is a Microsoft Partner and has delivered SharePoint intranets for NSW Justice Health, NSW Health at 1 Reserve Road and Mid North Coast Local Health District, MA Financial Group, Saluda Medical and the Anglican Schools Corporation. The intranets and extranets practice sits alongside government work including Infrastructure NSW.
Accessibility is built to the WCAG guidelines during design and development rather than retrofitted, and platform advice comes from working across SharePoint, Umbraco, Xperience by Kentico and HubSpot rather than from a single vendor relationship.
Frequently Asked Questions
Yes, for new and replacement services. Since 1 July 2024 the Digital Service Standard v2.0 applies to new and replacement staff-facing services as well as public-facing ones, so a new government intranet is in mandatory scope. Only existing staff-facing services are excluded.
WCAG 2.2 Level AA is the current reference point for Australian government digital services and for Digital NSW, because the Standard requires the latest version rather than naming one. Many existing contracts and older policy documents still cite WCAG 2.1 Level AA, so the useful step is to establish in writing which version you are being quoted against before comparing prices.
It is a strong fit where the agency already runs Microsoft 365, because identity, document management and permissions are already in place and do not need rebuilding. It is a weaker fit where the intranet needs to behave like a public-facing content platform with sophisticated publishing workflows. The honest answer depends on what else you run.
Put content governance in the specification rather than the training deck. Define who publishes, who approves, what expires and who gets told when it does, then require the platform to enforce it. Intranets decay quietly because no external audience notices, so the enforcement has to be built in.
Yes, and it is a common requirement. Webcoda delivered 17 schools from a single platform for the Anglican Schools Corporation, with per-entity colour and logo theming, shared reusable web parts and more than ten page templates. The same pattern applies to a department hosting several agencies or local health districts.
Talk to Webcoda
Webcoda is a Sydney-based, B Corp certified digital agency that has been building websites and enterprise web applications since 2005, for organisations including Sony, BridgeClimb, the Australian Federal Government and NSW Health. We are an Umbraco Gold Partner, a Gold partner for Xperience by Kentico and a HubSpot Solutions Partner, so platform advice comes without a single-vendor agenda.
Get in touch to talk through your project, or browse our full range of services and platforms.
