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

Readiness

A Digital Duty of Care readiness checklist for small and medium businesses

A hand ticks items off a checklist in a notebook.

An eight-step checklist that helps small and medium businesses prepare for the Digital Duty of Care bill, with each step tied to the bill.

Why prepare before the bill passes?

On 19 November 2026, the bill page shows the Online Safety Amendment (Digital Duty of Care) Bill 2026 as “Before Senate”. The House of Representatives passed it on 28 October 2026. A Senate committee is due to report on 20 November 2026.

Section 2 of the bill text as passed by the House delays the duty for 12 months after Royal Assent. That sounds like a long time. But the duty asks for a written risk assessment, measures against each risk and records kept for six years. A small business with no staff for compliance needs that time.

The Senate can still amend the bill. This checklist follows the bill as the House passed it. We will update it if the text changes.

Step 1: Do you run an online service?

List every online service your business runs. Section 25B of the bill lists the kinds of online service. For most small businesses, the relevant ones are:

  • A website or online store, which can be a designated internet service under section 14 of the Online Safety Act 2021.
  • A chat, messaging or online game feature between users, which can be a relevant electronic service under section 13A of the Act.
  • An AI chatbot or other tool that generates material, under section 25B(1)(h) of the bill.

For each service, note who provides it and who controls it day to day. Section 25B(2) says both can be a person responsible for the service.

Step 2: Who uses each service?

Note who uses each service and whether children can use it. The duty protects everyone in Australia from seriously harmful material (section 25D). It also protects children from a wider list of harms (section 25E) and from harmful design features (section 25C). If children can reach your service, more of the duty applies.

Step 3: Which features carry risk?

For each service, list the features that let users post, chat, upload or receive generated content. Section 27(2)(a) asks each risk assessment to identify the design features and other systems that give rise to risk.

Common features with risk are:

  • Comments, reviews and forums.
  • Live chat between users.
  • AI chatbots and AI image tools.
  • Member areas with profiles or direct messages.
  • Uploads of images or files.

Step 4: Write the first risk assessment

Section 27(2) sets out what the assessment must hold. For each feature:

  • Name the reasonably foreseeable risks and the people they can affect.
  • Rate the likelihood and the potential severity of each risk.
  • Document the measures you have in place or plan to add.
  • Record how effective you expect each measure to be, why, and for how long.
  • Set a date to review the measures.

The revised explanatory memorandum says not all providers have the same risks. Your assessment needs to fit your service, not a large platform. Our article on what a risk assessment asks for explains each part of section 27.

Step 5: Put measures in place

The duty in section 26 asks for appropriate action, including effective measures against the risks in your assessment. Section 26A says the measures must be proportionate to the risk, and that cost must not count.

The memorandum gives examples of measures:

  • Terms of use that set standards of behaviour and ban abuse.
  • A clear way to report harmful content, and a process to act on reports.
  • Content moderation.
  • Age assurance where children can reach adult material.
  • Safety by design.

eSafety publishes material on Safety by Design, including assessment tools for companies of different sizes.

Step 6: Test your AI tools

If you run a chatbot or another AI tool, test it before launch and after each change. The memorandum lists controls for public-facing generative AI services: testing before deployment, testing against foreseeable misuse, safeguards on prompts and outputs, a way to report harmful outputs, monitoring and review.

Section 27(3) also says you must assess risks again before any significant change to the service. The memorandum gives adding a generative AI tool as an example of such a change. Our article on chatbots and user content explains what the bill says about AI tools.

Step 7: Set up your records

Section 27(3) says you must keep each risk assessment for at least six years and give it to the eSafety Commissioner within 30 days of a request. Set up:

  • One place to keep each dated version of the assessment.
  • Copies of each version of your terms of use and moderation rules.
  • A log of complaints, actions and replies.
  • A note of the third-party tools you use and who supplies them.

eSafety can also ask for transparency reports (section 192B) and for information on how your features work (section 28A). Good records make those answers fast. Our article on the records the duty asks you to keep explains each rule.

Step 8: Set a review cycle

Section 27(3) asks for a new risk assessment at least once a year, and before any significant change to the service. Put the yearly review date in your calendar now. Also add a rule that any new feature, plugin or AI tool triggers a review before it goes live.

What does a breach cost?

Section 26C sets a civil penalty of up to 60,000 penalty units for a breach of the duty. Section 27B sets the same maximum for a failure to conduct, make available or keep risk assessments. The Commissioner can also use formal warnings, remedial directions and infringement notices, and a court decides any penalty amount.

Where can I get help?

Use the eight steps as your plan for the year ahead. We are building tools for each step, from a free readiness check to an evidence vault, and they are coming soon. Our guide How Smart Digital Care works shows the path from a free check to complete, dated records. To see them, visit our products page. To ask a question about your business, use our contact page.

Sources

Frequently asked questions

Do I need to wait for the bill to pass before I prepare?

No. None of the eight steps in this checklist needs the bill to pass first.

Which step takes the longest?

The first written risk assessment. Section 27(2) sets out what it must hold, so it is the place to start.

How long must I keep each risk assessment?

Section 27(3) says at least six years. You must also give it to the eSafety Commissioner within 30 days of a request.

How often must I do a new risk assessment?

Section 27(3) asks for a new risk assessment at least once a year, and before any significant change to the service.

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.