Independent guidance on Australia's Digital Duty of Care. Smart Digital Care is an independent guidance provider and is not a government agency.

Risk assessment

What a risk assessment under the Digital Duty of Care bill asks for

Two people map out ideas together on a whiteboard.

Section 27 of the Digital Duty of Care bill asks for written risk assessments. Learn what each one must hold, how often to do it and how long to keep it.

Why does the bill ask for a risk assessment?

The risk assessment is the base of the whole duty. New section 26 of the bill text as passed by the House says the duty includes effective measures against “risks identified in risk assessments conducted in accordance with section 27”.

The revised explanatory memorandum gives two reasons. First, the assessment makes a provider find and deal with risks before harm happens. Second, it gives the eSafety Commissioner evidence of whether the provider meets the duty.

What must the risk assessment identify?

Section 27(2)(a) lists five things that each assessment must identify:

  • The reasonably foreseeable risks of the service.
  • The material or conduct that gives rise to those risks.
  • The design features of the service that give rise to those risks.
  • Other systems or processes that give rise to those risks.
  • The persons who can be affected by those risks.

A design feature is a part of how the service works, for example comments, a recommendation feed, direct messages or an AI tool. The memorandum names features that rely on or interact with AI as an example of a high-risk feature. Our article on chatbots and user content looks at AI tools in more detail.

The memorandum also asks providers to look past single posts. A service must consider cumulative harm, for example a campaign of many small abusive messages sent to one person by many users.

How does the assessment rate each risk?

Section 27(2)(b) asks you to assess the likelihood and the potential severity of each risk. This links to section 26A. That section says an action must be proportionate to the level of risk, judged by how likely harm is and how serious it can be.

In practice, this means a simple scale for likelihood and severity, applied the same way to every risk. A rare but serious risk, such as an adult contacting a child through a chat feature, can rank above a common but minor one.

What must the assessment record about your measures?

This part of section 27 is the most detailed. The assessment must document the measures you have in place, or plan to put in place, to reduce each risk. It must then record four facts about those measures:

  • How effective you expect the measures to be.
  • The basis for that expectation.
  • How long you expect the measures to stay effective.
  • How long you expect the measures to stay in place.

The assessment must also provide for regular review and reassessment of the measures. So the assessment is not a one-time report. It is a record that shows a cycle: find a risk, act on it, check the result.

The memorandum gives examples of measures. They include terms of use that set standards of user behaviour, complaint handling, content moderation, age assurance and safety by design. eSafety describes Safety by Design as building safety into a service from the start, rather than adding safeguards after a problem occurs.

How often must the assessment be done?

Section 27(3) sets two triggers:

  • At least once a year, or more often if the Commissioner sets a shorter interval by legislative instrument.
  • Before any significant change to the service that can introduce new or additional risks.

The memorandum gives an example of a significant change: adding a generative AI tool to an existing service. It also says that normal software updates and security patches do not need a new assessment, if they do not change the safety of the service.

How long must the assessment be kept?

Section 27(3) says each assessment must be kept for at least six years. It must be made available to the Commissioner within 30 days after a request.

Six years is a long time for a small business. Staff change, suppliers change and websites are rebuilt. A business needs a place to keep each version of the assessment, with its date, so it can produce the right version on request. Our article on the records the duty asks you to keep sets out a simple records plan.

Can eSafety add more requirements?

Yes. Section 27(4) lets the Commissioner set further requirements by legislative instrument. These can cover the manner and form of the assessment, the detail to include, the standards or benchmarks to use, and further matters to cover.

No such instrument exists yet, because the bill is not yet law. On 19 November 2026, the bill page shows the status “Before Senate”. Section 28 of the bill also lets the Commissioner publish guidelines on how to meet the duty. The memorandum says those guidelines will not be binding.

What happens if a business does not do one?

Section 27B makes it a breach to fail to conduct, make available or keep risk assessments in line with section 27. The maximum civil penalty is 60,000 penalty units, the same as for the duty itself. The Commissioner can also give a formal warning or a remedial direction.

How can a small business start?

You do not need to wait for the bill to pass to start the groundwork. These steps cost little:

  1. List each online service you run and who controls it.
  2. For each service, list the features that let users post, chat or see content from others.
  3. Write down what can go wrong with each feature, and who it can affect.
  4. Note what you already do about each risk, and how you know it works.
  5. Save the list with today’s date, and set a date to review it.

To see the readiness tools we are building for this work, visit our products page. Our readiness documents are coming soon. They turn your answers into a gap report and a draft risk assessment, and the guide From gaps to documents explains how. To talk to us about your business, use our contact page.

Sources

Frequently asked questions

What must a risk assessment identify?

Section 27(2)(a) lists the reasonably foreseeable risks, the material or conduct behind them, the design features and other systems that give rise to them, and the persons they can affect.

How often must I do a risk assessment?

At least once a year, and before any significant change to the service that can add risk. Normal software updates and security patches do not need a new assessment if they do not change the safety of the service.

What happens if I do not do a risk assessment?

Section 27B makes it a breach to fail to conduct, make available or keep risk assessments. The maximum civil penalty is 60,000 penalty units.

Can eSafety add more requirements?

Yes. Section 27(4) lets the Commissioner set further requirements by legislative instrument. No such instrument exists yet.

Find out if the duty applies to you

Send us a question about your business, or compare the plans for the readiness tools we are building.