Design and distribution obligations set out how financial products must be designed, marketed and sold so they reach the right consumers. If you issue or distribute retail financial products, you need to understand DDO, how to prepare a Target Market Determination (TMD), when to notify regulators of significant dealings, and practical steps to evidence compliance.
What are Design and Distribution Obligations (DDO)?
Design and distribution obligations require issuers and distributors of retail financial products to take steps to ensure products are targeted at appropriate consumers and that distribution is controlled, monitored and reported. The objectives are product governance and consumer protection: to reduce mismatches between product features and consumer needs, and to provide regulators with timely information about distribution failures.
DDO applies to many retail financial products, and its core components are:
- A Target Market Determination (TMD) prepared by the issuer
- Distribution conditions and reasonable-step obligations for distributors
- Significant dealing notifications to the regulator where distribution materially deviates from the TMD
The regulator's guidance is set out in Regulatory Guide RG 274 and related ASIC materials.
Who must comply? (Issuers vs Distributors)
Understanding roles is critical because obligations differ by role.
Issuers (product creators)
- Must create and maintain a TMD for each retail product or product class
- Define the target market, distribution conditions, review triggers and monitoring arrangements
- Retain TMD records and publish or provide copies to distributors on request
Distributors (platforms, advisers, brokers, dealers)
- Must take reasonable steps to distribute according to the TMD and distribution conditions
- Keep records of distribution activities and any dealings outside the TMD
- Notify the regulator of significant dealings when required
DDO applies to retail products; wholesale-only products may be excluded but consider how secondary distribution or mixed-client bases can bring products into scope. If your product relates to asset finance, consumer lending or vehicle finance, ensure your TMD reflects the specific characteristics of that product class.
Key requirements — Target Market Determination (TMD)
A TMD is the foundational document under DDO. It must be concise, tailored and kept up to date.
- Product description and objectives: plain-language description of the product and its key features
- Target market (class of consumers): characteristics and circumstances of consumers for whom the product is suitable
- Distribution conditions: permitted channels, distributor types, channel restrictions and limits
- Review triggers and review periods: events or timeframes that will prompt a review (e.g., claims data, complaint spikes, changes in product features)
- Reporting arrangements: what distributors must report, how often, and the format
- Record-keeping requirements: where and how the TMD will be stored and who to contact at the issuer
- Start and end dates; issuer contact: effective date, review frequency and issuer contact details
- Map product features and likely consumer needs (use customer personas)
- Identify risk factors and exclusion criteria (who should not hold the product)
- Draft a one-page summary plus a structured TMD document that includes the mandatory elements
- Define objective distribution conditions (e.g., accredited advisers only, platform filters, minimum customer income)
- Set measurable review triggers and monitoring KPIs (complaints per 1,000 policies, default rates, redemption rates)
- Circulate TMD drafts to legal, compliance, sales and a sample of distributors for practical feedback
- Finalise and publish the TMD and retain version control
Key requirements — Distribution conditions and record-keeping
Distribution conditions restrict how the product may be sold. Record-keeping creates an auditable trail.
Distribution conditions — examples
- Channel restrictions (e.g., digital platform only; adviser-panel only)
- Adviser accreditation levels and training requirements
- Customer eligibility checks (income, experience, purpose)
- Post-sale communications and cooling-off measures
What "reasonable steps" look like for distributors
- Implement platform filters that block out-of-target consumers
- Require adviser attestation that a sale meets TMD criteria
- Maintain training logs and accreditation certificates
- Run periodic sample file reviews and audit outcomes
Record retention — practical rules
- Keep TMDs, distributor agreements, monitoring reports and material records for at least the period required by the regulator (retain version histories)
- Store records in searchable, access-controlled systems to produce evidence quickly
- Ensure records include dates, distribution numbers, complaints and remediation actions
Significant dealing notifications: when and how to report
A significant dealing occurs when distribution materially deviates from the TMD and affects a class of consumers.
Significant dealing triggers typically include a material breach of distribution conditions, a measurable spike in harms (e.g., high complaint rates) or mass sales to out-of-target consumers. Examples: thousands of sales via an unapproved channel, system error causing mis-selling, or a surge in defaults.
What to include in a notification
- Identification of the product and TMD version
- Description of the dealing and why it is significant
- Estimated number of affected consumers and materiality metrics
- What actions have been taken (stop-sale, remediation, remedial communications)
- Short- and medium-term remediation plans and timelines
Notify the regulator as soon as practicable once you become aware of a significant dealing and provide updates as new information emerges. Use the regulator's online portal for lodgement and follow the portal guidance for format and attachments. Prepare a template significant dealing notification internally so legal and compliance can quickly populate and lodge it under short timelines.
Enforcement, sanctions and regulatory expectations
Regulators can use a range of enforcement tools where DDO obligations are breached.
Common enforcement outcomes
- Directions to stop distribution or to recall or vary disclosures
- Requirements to notify affected consumers and to undertake remediation
- Civil penalties and infringement notices
- Court action, injunctions and enforceable undertakings
- Public enforcement which can damage reputation and commercial partners
- Prompt reporting of significant dealings
- Evidence that reasonable steps were taken and remediation was proportionate
- Proactive reviews and documented TMD changes when distribution outcomes diverge from expectations
Enforcement grid (summary)
| Action | Typical regulatory response |
| Failure to have a TMD | Direction to prepare TMD; possible penalty |
| Repeated misdistribution | Remediation + fines or enforceable undertaking |
| Late or no significant dealing notification | Formal censure, fines, increased supervision |
| Poor record-keeping | Orders to improve systems; potential sanctions |
Previous enforcement actions have involved large-scale product distribution through unvetted online aggregators, or failure to act on complaint trends. These often result in remediation requirements and public enforcement statements.
Practical compliance checklist (issuer and distributor versions)
Issuer checklist (core tasks)
- Create a TMD for each retail product and document version control
- Define distribution conditions and measurable review triggers
- Publish or provide TMDs to distributors and maintain a single source of truth
- Implement monitoring metrics and dashboards (complaints, sales by channel, returns)
- Prepare significant dealing notification templates
- Schedule periodic TMD reviews and ad-hoc reviews after triggers
Distributor checklist (core tasks)
- Obtain and store issuer TMDs and ensure staff can access them
- Implement channel controls (platform flags, accreditation checks)
- Train sales staff and maintain training records
- Monitor distribution against TMD and report deviations promptly
- Retain distribution records and evidence of "reasonable steps"
- Have escalation pathways for potential significant dealings
Implementation timeline (suggested)
- Week 0–4: Gap analysis and TMD drafting
- Week 4–8: Systems changes (platform filters, reporting)
- Week 8–12: Training and go-live with monitoring
- Ongoing: Monthly monitoring; reviews triggered by metrics
Sample TMD elements and significant dealing scenarios
Sample one-page TMD summary
- Product: Fixed-rate personal loan (12–60 months)
- Target market: Consumers seeking small-to-medium unsecured credit for home improvements; income > $10k; no recent defaults in 12 months
- Distribution conditions: Online direct channel and accredited brokers only; no kiosk or third-party aggregator distribution
- Review triggers: Complaints > 3% per 1,000 loans in a quarter; default rate > 2% in first 6 months
- Reporting: Monthly sales by channel; complaints and remediation logs
- Effective date: 01/01/2026 — Issuer contact: compliance@[issuer].com
Sample scenario 1 — system misconfiguration
A campaign inadvertently targeted consumers outside the TMD due to a filter error on a marketplace platform. 2,500 consumers outside the TMD received offers and the complaint rate rose rapidly. The issuer stopped the campaign, isolated the affected cohort, notified the regulator within 48 hours, initiated remediation offers and refunds, and reviewed platform controls. The notification included: product ID, TMD version, number affected, steps taken, remediation plan and timing.
Sample scenario 2 — adviser mis-selling cluster
An adviser network sold a structured product to customers whose investment objectives did not match the TMD. A pattern across multiple advisers indicated a systemic issue. The distributor suspended the adviser panel, notified the issuer and regulator, initiated reviews of adviser accreditation and re-training, and reached out to affected clients.
Common pitfalls and how to avoid them
- Over-broad TMDs that effectively say "suitable for everyone" — defeats the purpose
- Poor version control and lack of a single authoritative TMD
- Weak distributor controls — relying on trust rather than platform or process controls
- Insufficient monitoring metrics or delayed review triggers
- Slow or incomplete significant dealing notifications
- Keep TMDs specific, measurable and time-bound
- Use centralized document management with clear version history
- Implement automated channel controls and require distributor attestations
- Define clear KPIs and quarterly dashboards for early detection
- Build a rapid-response notification protocol with pre-prepared templates
- Maintain system logs showing filters applied
- Keep training attendance and assessment records
- Store audit trails of adviser attestations and file reviews
How DDO intersects with other regulatory obligations
DDO interacts with multiple regulatory areas — licensing, disclosure, product intervention and consumer remediation.
- Disclosure and disclosure documents: TMDs complement disclosure obligations but do not replace them
- Licensing and conduct obligations: Distributors must remain compliant with licensing conditions and best interests duties where applicable
- Product intervention and market powers: Regulators may use product intervention powers alongside DDO enforcement if consumer harm is systemic
- Record-keeping and reporting: Align DDO record retention with other statutory retention requirements
Map DDO obligations to pre-existing compliance frameworks (e.g., complaints handling, incident management) so reporting and remediation are coordinated across teams.
FAQ
When is a product "retail" for DDO purposes?
A product is generally retail if it is offered to consumers who are not wholesale clients. Where distribution mixes client types, assess whether retail distribution occurs and prepare a TMD accordingly.
How long must you keep TMD records?
Keep TMDs and distribution records for a sufficiently long period to demonstrate compliance — align with statutory retention requirements and your internal policies. Maintain version history and archived copies.
Can a distributor create its own TMD?
Distributors should rely on the issuer's TMD. If a distributor believes additional segmentation is necessary, it should discuss changes with the issuer and document any additional conditions it applies (but not replace the issuer's TMD).
When must I lodge a significant dealing notification?
Lodge as soon as practicable once you become aware of a significant dealing. Use the regulator's guidance and portal for submission.
What are practical monitoring KPIs?
Sales by channel, complaints per 1,000 customers, early default rates, return or cancellation rates and adviser exception rates.
Key takeaways
This guide gives you a structured approach to DDO compliance: define the target market clearly, set measurable distribution conditions, implement monitoring and evidence "reasonable steps", and be ready to notify and remediate swiftly if a significant dealing occurs. Maintain a schedule to review TMDs at least annually or after any material product or market change.
Further reading
This article is general information only and is not legal, tax or financial advice.