-
Criterion 3. Leave no one behind
Digital Service Standard 2.0 criterion 3: leave no one behind -
Criterion 4. Connect services
Digital Service Standard 2.0 criterion 4: connect services -
Criterion 5. Build trust in design
Digital Service Standard 2.0 criterion 5: build trust in design -
Criterion 6. Don’t reinvent the wheel
Digital Service Standard 2.0 criterion 6: don’t reinvent the wheel -
Criterion 7. Do no harm
Digital Service Standard 2.0 criterion 7: do no harm -
Criterion 8. Innovate with purpose
Digital Service Standard 2.0 criterion 8: innovate with purpose -
Criterion 9. Monitor your service
Digital Service Standard 2.0 criterion 9: monitor your service -
Criterion 10. Keep it relevant
Digital Service Standard 2.0 criterion 10: keep it relevant -
Transition approach
Transitioning to the Digital Inclusion Standard -
digital.gov.au beta
digital.gov.au is a gateway for all things digital across government agencies and portfolios -
A deliberate effort to challenge assumptions and design for marginalised users will ensure the service is inclusive, accessible and useful for all.
-
Designing and building a connected, interoperable service grants users a simple, seamless experience and enables government to function as one.
-
When to apply
Apply Criterion 4 throughout Beta to ensure smooth integration with other government services and systems.
Adhere to this criterion across the Service design and delivery process whenever new functionality, integrations or upgrades are introduced.
Off -
Questions for consideration
- How will this service integrate with existing systems and data?
- What standardised protocols will be used to exchange data?
- How will we test for smooth interoperability with other platforms?
- How will the service accommodate future growth and change?
- What information does government already hold that the service could reuse?
- Which mechanisms will allow users to opt in or out of data sharing?
-
Making sure the service is useful, easy, inclusive, transparent and stable will build users’ trust and confidence in government.
-
Your responsibilities
To successfully meet this criterion, agencies will need to:
- adopt transparent data handling
- implement security measures
- maintain a reliable service
- be accountable for the service.
-
When to apply
Apply Criterion 5 throughout Beta to protect users’ digital rights and ensure robust security measures are in place.
As cyber threats become more prevalent and sophisticated, adhere to this criterion across the Service design and delivery process.
Off -
Questions for consideration
- How are users informed about the collection, use and storage of data?
- How will informed consent be obtained from users?
- Which encryption and authentication mechanisms will provide the most robust security?
- How does the service comply with data protection legislation and policies?
- What processes are in place to prevent misinformation?
- How is the service built to be resilient against cyber threats?
- What assurances are in place to promote ethical use of data?
-
Guidance and resources
- Australian Privacy Principles
- Privacy Act 1988
- Privacy for Government Agencies - Office of the Australian Information Commissioner
- Australian Cyber Security Strategy 2020 - Home Affairs
- Protective Security Policy Framework (PSPF) - Attorney General's Department
- Information Security Manual (ISM) - Australian Signals Directorate
- National Identity Security Storage - Home Affairs
- Building Trust in the Public Record - National Archives of Australia
- National Data Security Action Plan - Prime Minister & Cabinet
- Notifiable data breaches - Office of the Australian Information Commissioner
- Data and Digital Government Strategy | DDGS
- Essential Eight – Australian Cyber Security Centre
- System hardening and administration | Cyber.gov.au
- Better Practice Complaint Handling Guide – Commonwealth Ombudsman
-
Drawing on other agencies’ experiences and adopting common platforms, patterns and standards will deliver value for government and familiarity to users.
-
Questions for consideration
- What could be aligned with on the Australian Government Architecture?
- What platforms, patterns and standards could the service reuse?
- What are the alternatives to building from scratch?
- Which agencies run similar services that could be built upon?
- How can new or bespoke components be made for future reuse?
- What data do we already collect, and can it be repurposed?
-
Your responsibilities
To successfully meet this criterion, agencies will need to:
- ‘build once, use many times’
- design for a common, seamless experience
- reuse data where possible.
Connect with the digital community
Share, build or learn digital experience and skills with training and events, and collaborate with peers across government.