DSA complaint and dispute workflows for online platforms

This workflow supports online platform decisions covered by the DSA internal complaint-handling rules: whether to remove, disable access to, restrict visibility of, or leave up information after a notice; whether to suspend or terminate a service or account; and whether to suspend, terminate, or otherwise restrict monetisation. The complaint channel must also cover individuals or entities that submitted notices when the platform decided not to act on the notice.

Before building the queue, confirm the service role and enterprise-size treatment. The DSA Article 20 internal complaint rules sit in the online-platform section, which Article 19 excludes for qualifying micro and small online-platform providers subject to its 12-month post-loss and VLOP rules. Recommendation 2003/361/EC sets the size tests: fewer than 10 staff and no more than EUR 2 million annual turnover or balance-sheet total for a microenterprise, and fewer than 50 staff and no more than EUR 10 million for a small enterprise, after counting partner and linked enterprises as required. Article 17 statements of reasons sit in the hosting section and are not removed by that platform-section exclusion.

The internal complaint system should be an electronic, free-of-charge path that is easy to access and user-friendly. It should help users submit sufficiently precise and adequately substantiated complaints without requiring them to understand internal policy taxonomies.

Treat the appeal as a review of the original moderation decision, not as a customer-support message. Article 20 requires timely, non-discriminatory, diligent, and non-arbitrary handling, and the final complaint decision must be supervised by appropriately qualified staff rather than made solely by automated means.

The user must be able to understand the original moderation decision. For each covered restriction, the statement of reasons should identify the measure, territorial scope and duration where relevant, the facts and circumstances relied on, any automated means used, the legal or contractual ground, and the available redress options.

Notice/action appeals need two linked records: the notifier-facing decision after the Article 16 notice and the affected-recipient statement of reasons when content or account restrictions are imposed. Keeping those records linked avoids losing the reason why a notice was rejected, why content was restricted, or why a later complaint reversed the outcome.

The user-facing response should clearly explain certified out-of-court dispute settlement and other redress options. Article 21 does not require the recipient to exhaust the platform's internal complaint system first: eligible disputes include complaints that were not resolved internally, and the recipient may select any certified body whose expertise and language coverage fit. The body does not need to be based in the recipient's country.

The hand-off should not suggest that out-of-court dispute bodies bind the parties. Under Article 21, both parties must engage in good faith with the selected certified body, but the certified body cannot impose a binding settlement. Court proceedings remain available under applicable law.

A durable DSA complaint workflow should produce records that explain what happened to the user, what the platform reviewed, who supervised the decision, what was changed, and what was reported. These records should be specific enough for transparency reporting, regulator questions, user follow-up, and internal quality sampling.

Review the workflow periodically against real cases. The most important quality signals are reversals, late responses, unsupported legal or terms grounds, automation-only outcomes, missing redress text, missing DSA Transparency Database submissions, and repeat disputes sent to certified bodies.