How to Assess a NSW Government Website Development Partner
Most "best agency" lists give a NSW agency a shortlist. They can't tell you which partner will still be answering the phone when a privacy officer asks where last year's form submissions actually live. That's the gap this guide is meant to fill.
It's written for NSW departments, statutory bodies and councils buying a public-facing website, not an intranet. It works through the four things that separate a capable government website developer from a merely good-looking one: accessibility, data sovereignty, systems integration and public sector delivery fit. For each one, it sets out the evidence worth asking for. Then it says plainly where Webcoda fits, and where it doesn't.
Key Takeaways
- NSW Government agencies must buy ICT through the NSW ICT Purchasing Framework, so check early that a partner can contract on the terms your project needs.
- Digital NSW's design standards say to comply with WCAG 2.2 at Level AA. Ask which version a partner is quoting against, because older contracts still cite 2.1.
- Data sovereignty in NSW is mostly a contract and configuration question. Ask where every copy of your data sits, including backups, logs and form submissions.
- Integration claims are cheap. Ask for named systems a partner has connected, and what happens when the other system goes down.
- The right partner will tell you when it's the wrong one.
Start With How NSW Buys
Before you judge anyone's portfolio, check they can be bought the way your agency has to buy. The NSW Government's ICT Purchasing Framework page says all NSW Government agencies must use the framework when buying ICT goods and services. It has two contract tracks: Core& for lower-risk work up to $1 million (excluding GST), and MICTA/ICTA for higher-risk work or anything over that figure.
The ICT Services Scheme sits alongside it. Its buy.nsw page says registered suppliers can take on low-risk contracts up to $150,000 (excluding GST), while advanced suppliers can take on high-risk contracts valued over $150,000 (excluding GST). So a partner's scheme status limits what you can award them through the scheme. (It's a dull question. Ask it anyway, before anyone falls in love with a design concept. It's the same logic as checking a builder's licence before the slab's poured, not after.)
Councils are a slightly different case. The framework page is written for NSW Government agencies, so a council's own procurement team should confirm which arrangements apply before the shortlist is drawn up.
Accessibility: Test the Process, Not the Promise
Every agency pitch says "WCAG compliant". It's close to meaningless on its own.
The useful reference point is Digital NSW. Its design standards tell teams to comply with WCAG 2.2 at Level AA (AAA where achievable) and to keep reviewing compliance after launch, and they point teams to the NSW Design System. The NSW Design System says its components have been updated to achieve compliance with WCAG 2.2 Level AA, and it notes that a product's accessibility still depends on how those components are implemented. That's a strong start, but it isn't a free pass. A compliant component can still be configured badly, and a CMS that lets editors paste in an untagged PDF can undo a perfectly accessible template within a week.
So the question isn't "are you compliant?" It's "how do you keep us compliant?" Here's what's worth asking for:
- Which WCAG version and level the quote is written against, in writing. If it says 2.1, ask why. I'd treat a partner who can't answer this straight away as a warning sign.
- How accessibility is tested: automated scans alone miss a lot, so ask about keyboard and screen reader checks too.
- Whether the CMS guards editors from common mistakes, such as missing alt text or skipped heading levels.
- Who fixes accessibility defects found after go-live, and on what terms.
One honest note. The legal duty under the Disability Discrimination Act sits with the organisation providing the service. A supplier contract doesn't move it. That's why process evidence matters more than a badge.
Data Sovereignty Is Mostly a Contract Question
"Is it hosted in Australia?" is the question everyone asks. It's the right instinct and the wrong level of detail.
The NSW Privacy and Personal Information Protection Act 1998 restricts agencies disclosing personal information outside NSW, under section 19(2). The Information and Privacy Commission's guidance draws a line that matters for website projects: giving personal information to a contracted cloud data storage provider may be considered a "use" rather than a disclosure, so long as certain conditions are met. Where agencies rely on the "reasonable steps" ground for a disclosure, the IPC expects, at a minimum, an enforceable contract with the recipient. In other words, the contract is doing the heavy lifting.
Two more NSW instruments raise the stakes. Since 28 November 2023, the Mandatory Notification of Data Breach scheme under the same Act has required agencies (councils included) to assess suspected breaches within 30 days and notify eligible ones. Your developer's incident response is now part of your own clock. And State Records NSW's general authority GA50 allows State records to be stored with service providers outside NSW, including cloud services, only under conditions, including an appropriate risk assessment, contractual arrangements for safe custody and ownership of the records staying with the public office.
So ask a partner to map every place your data lands:
- Hosting region, and where backups and disaster recovery copies are kept.
- Where form submissions go, and how long they're kept.
- Analytics, search, chat or translation plugins that send data elsewhere.
- Who holds admin access to the CMS and servers, and which subcontractors touch any of it.
- How they'd notify you of a suspected breach, and how fast.
I'd ask for that map as a one-page diagram before the contract is signed. If a partner needs a fortnight to produce it, that tells you something too.
AI is where this gets slippery. The IPC's guide to the privacy risks of generative AI tools flags cross-border data transfers as a risk, and says agencies may need to meet cross-border requirements for personal information entered into a generative AI service. If you want a chatbot or AI search on a public site, the partner should be able to name the model, the region it runs in and whether your content is retained. Webcoda's AI integration work offers Australian Azure regions or the client's own tenancy, confirmed in writing. That's a commitment in a contract, not a certification, and it's worth being clear about the difference.
Systems Integration: Ask What They've Actually Connected
A government website is rarely just pages. It feeds a CRM, takes bookings, pushes enquiries into case management, pulls in event listings or publishes data from somewhere else. That's where projects go sideways, not on the home page.
My view is simple: weight integration evidence above anything in a pitch deck. Ask for the names of systems a partner has connected, in production, and ask them to walk you through one. Good answers cover authentication, what gets logged, how failures are retried and who's alerted when the other system falls over at 2am on a Sunday.
Cyber security belongs here too. The NSW Cyber Security Policy's mandatory requirements include identifying and managing third-party service provider risks, and Digital NSW sets Essential Eight Maturity Level 1 as the minimum for agencies. Your web partner is one of those third parties. Expect them to explain how they patch the CMS, how admin accounts use multi-factor authentication and how they'd hand you everything if you parted ways.
Public Sector Delivery Fit
This is the softest criterion and, in my view, one of the most important.
Public sector websites outlive the people who commissioned them. Teams change, a machinery-of-government shift renames the agency, and the editors who inherit the CMS weren't in the room when it was chosen. So CMS strategy matters as much as the build. Ask a partner why they'd recommend a particular platform for you, and what it would cost you to leave it. I think the second answer is the more revealing one. A partner who works across several CMSs can answer that without a single-vendor agenda.
Ask for a content migration plan, not just a design. Ask how editors are trained and how approvals work inside the CMS. And ask who you'll actually be working with in month 18, long after launch, because that's when the real relationship starts.
None of this makes the choice easy. You're judging something that won't exist for months, on the word of people you've just met, and everyone on the evaluation panel is guessing a little. Asking for evidence doesn't remove the guesswork. It just makes the guesses better.
Where Webcoda Fits
Webcoda is a Sydney agency, based in Surry Hills, that has been building websites since 2005. Its government work includes the Infrastructure NSW website, designed and developed on Umbraco with a bespoke project timeline that exports to PDF and flexible CMS content modules. The Visit Newcastle site, built on Kentico Xperience with systems integration, won the Kentico best Government site award. Webcoda has also worked with NESA, Newcastle City Council and NSW local councils, and built SharePoint intranets for NSW Justice Health and NSW Health.
On integration, the honest shape of the portfolio is website-to-CRM: Sydney Zoo's CustomLinc ticketing linked through to HubSpot CRM, UTS College's HubSpot CRM integration, and Abano Healthcare Group's Umbraco forms feeding HubSpot CRM objects. If you're replatforming, Webcoda builds on Umbraco, Xperience by Kentico, HubSpot CMS and Kontent.ai, its CMS advice helps with the choice, and its systems integration work handles the connections.
When isn't Webcoda the right fit? If you've standardised on Drupal or WordPress, you need a partner who builds on them, and Webcoda doesn't. If the job is a large ERP or core transactional platform, a big systems integrator is probably the better call. And if your procurement needs a formal security accreditation such as an IRAP assessment, know that Webcoda's data residency commitments are contractual, not certified. I'd rather say that here than have you find out in clarifications.
Frequently Asked Questions
There's no official ranking, so shortlist on evidence: named NSW public sector work that's live today, a clear WCAG 2.2 AA testing process, a written map of where your data is stored, and integrations they can walk you through. Webcoda's NSW work includes the Infrastructure NSW website on Umbraco, the award-winning Visit Newcastle site on Kentico Xperience, and intranets for NSW Health and NSW Justice Health.
Digital NSW's design standards tell teams to comply with WCAG 2.2 at Level AA, with AAA where achievable, and to keep reviewing compliance. Some existing contracts and older policy documents still cite WCAG 2.1, so confirm in writing which version a partner is quoting against.
Not as a blanket rule. Section 19(2) of the PPIP Act restricts disclosing personal information outside NSW, and IPC guidance says giving personal information to a contracted cloud data storage provider may be considered a use rather than a disclosure, so long as certain conditions are met. In practice the contract matters most, so get the hosting location confirmed in writing.
NSW Government agencies must use the ICT Purchasing Framework: Core& contracts for lower-risk work up to $1 million (excluding GST), and MICTA/ICTA for higher-risk work or larger values. Councils should check with their own procurement team which arrangements apply.
Yes, if the model runs in an Australian region and the contract says so. The IPC's generative AI guidance says agencies may need to meet cross-border requirements for personal information entered into these tools, so ask a partner to name the model, its hosting region and its data retention terms. Webcoda offers Australian Azure regions or the client's own tenancy for AI work, confirmed in writing.
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.