Is the Saudi Platforms Code mandatory?
Yes. Compliance with the Platforms Code is required of Saudi government entities under a circular issued by the Digital Government Authority. Authority officials have stated that application is monitored through regulatory tooling and tracked within the annual digital transformation measurement. The obligation applies to platforms that are permanent, externally facing and public, which is narrower than everything an entity operates.
What the obligation rests on
The Digital Government Authority is the body that governs digital government in Saudi Arabia, and it issued the Platforms Code as the national reference for government interface design. The requirement to apply it reached entities as a circular, and the Authority both assesses application and grants the Platforms Code Application Certificate to entities that meet the criteria.
A note on precision, since it matters to anyone advising an entity: this page states the obligation and does not quote the circular’s reference number or its deadline. Those figures reach us only through workshop transcripts, and a misquoted circular number in front of a government client is worse than no citation. Verify them with the Authority directly.
Which platforms fall inside the scope
Three attributes place a platform in scope: it is permanent, it is externally facing, and it is public. All three have to hold.
- In scopeThe entity’s main portal, its service pages, its e-participation pages and its public mobile applications.
- Out of scope · temporaryA campaign microsite with an end date, an event site that closes after the event.
- Out of scope · internalSystems only staff reach, behind authentication and not offered to the public.
- Out of scope · not the entity’s interfaceA service delivered on a third party’s platform, where the entity does not control the interface being judged.
One distinction is routinely conflated with this one and should not be: whether a platform is in scope is a question about the Code. Whether a criterion can be measured automatically is a question about tooling. A platform can be fully in scope and still have criteria that no scanner will ever score.
What non-compliance actually costs
The practical consequence is not a penalty notice. It is that the entity’s platform is assessed against the criteria whether or not it has prepared for the assessment, that the result feeds the annual digital transformation measurement, and that the certificate — which peer entities display publicly — is not granted.
For an agency or vendor building on behalf of an entity, the exposure is more direct. Work delivered against a design that does not apply the Code is work the entity will have to pay to redo, and “it looks like the Code” is not the test. A component that visually matches the library while carrying none of the library’s markers has been rebuilt by hand, which means future library updates will never reach it — a distinct finding from “it looks wrong”, and one that caps a criterion at partial application.
Where to go next
The limits of this tool
XFix is an independent commercial tool. It is not part of the Digital Government Authority, is not endorsed by it, and does not act on its behalf. What it produces is an indicative estimate expressed as a range. It is not the Platforms Code Application Certificate and not a declaration of conformity. The certificate is issued by the Authority alone, and the Authority’s assessment remains the reference.
Its usefulness is in showing the gap early and with evidence. It does not stand in for the body that decides.