Register
Fix the target register: Saudi-flavoured modern standard Arabic for enterprise channels, with a stated exception policy.
Done when: A sample of outputs is judged in-register by a native reviewer.
A scored rubric for Arabic AI: register, terminology, entities, retrieval and rendering, evaluated, not assumed.
The business problem
Models trained mostly on English get terms, names and tone wrong, and nobody measures it before launch.
What you hear inside the organisation
The chatbot answers in Arabic nobody speaks.
It mixes up customer names.
Search fails on Arabic spelling variations.
The vendor says Arabic is supported.
Who it serves and what changes
Client teams and what they need
Customer experience
Arabic that sounds natural to Saudi users
AI product teams
A test they can run before release
Brand and communications
Consistent terms and tone
Procurement
A fair way to compare vendors
The outcome you get
A worked example
The problem we saw
The assistant passed vendor demos, but customers found its Arabic stiff, it misread names, and search missed common spellings.
How the framework solved it
We tested register, terminology, names, retrieval and display on the operator's own content, and compared vendors on the same test.
The business result
The operator picked the model that served Saudi customers best, fixed the gaps before launch, and now retests with every update.
Illustrative example based on common client situations.
In short
Arabic Quality Standard (AQS): A scored rubric for Arabic AI: register, terminology, entities, retrieval and rendering, evaluated, not assumed.
Arabic is usually treated as a translation task at the end of a project, which is why Arabic output reads as translated.
How it works
The standard is symmetric: an Arabic release blocked for quality is treated exactly like an English one. Parity is the point.
Fix the target register: Saudi-flavoured modern standard Arabic for enterprise channels, with a stated exception policy.
Done when: A sample of outputs is judged in-register by a native reviewer.
Fix one Arabic term per domain concept, with the transliteration policy for product and technical names.
Done when: Terminology is enforced in generation, not corrected afterwards.
Handle Saudi names, addresses, national identifiers, Hijri and Gregorian dates, currency and numerals correctly.
Done when: Format handling passes a fixed test set drawn from real record shapes.
Evaluate Arabic retrieval separately: diacritics, morphology, synonymy and mixed-script documents.
Done when: Arabic retrieval quality is measured on its own set, not inferred from English.
Check right-to-left layout, mixed-direction text, numerals, truncation and screen-reader output.
Done when: Arabic scores at or above the English threshold before release.
Is it right for you?
A strong fit if
Probably not yet if
Free assessment
A working session with our senior team. We review what fits your situation, what does not, and where to start.
A focused conversation
We listen to your situation and goals.
Fit review
Which parts of this framework apply to you, and which do not.
A written view
Clear next steps, whether or not you work with us.
Go deeper
Open only the part you need: how it starts, what your team keeps, maturity levels, sector rules and the evidence a reviewer will ask for.
Arabic is usually treated as a translation task at the end of a project, which is why Arabic output reads as translated. AQS makes Arabic quality a release condition with a measurable rubric applied to the same evaluation set as English.
Version
v1.0
Last reviewed
August 2026
Family
Saudi Data & AI Standards
How this was developed: Drafted in Arabic first, then mirrored to English. The rubric was built from review findings on Arabic enterprise channels and reconciled with the evaluation obligations in the standards below.
Arabic evaluation set
A golden set built from real Arabic records and questions.
Bilingual glossary
One approved term per concept, enforced during generation.
Rubric scorecard
Register, terminology, entities, retrieval and rendering scored per release.
Banking & finance
Product and contractual terminology must match the approved Arabic of the customer agreement.
Fix the target register: Saudi-flavoured modern standard Arabic for enterprise channels, with a stated exception policy.
Exit gate
A sample of outputs is judged in-register by a native reviewer.
Artefacts
Fix one Arabic term per domain concept, with the transliteration policy for product and technical names.
Exit gate
Terminology is enforced in generation, not corrected afterwards.
Artefacts
Handle Saudi names, addresses, national identifiers, Hijri and Gregorian dates, currency and numerals correctly.
Exit gate
Format handling passes a fixed test set drawn from real record shapes.
Artefacts
Evaluate Arabic retrieval separately: diacritics, morphology, synonymy and mixed-script documents.
Exit gate
Arabic retrieval quality is measured on its own set, not inferred from English.
Artefacts
Check right-to-left layout, mixed-direction text, numerals, truncation and screen-reader output.
Exit gate
Arabic scores at or above the English threshold before release.
Artefacts
Arabic added after launch reads as translated and is rarely re-evaluated. Build the Arabic set first.
Dialect in a banking or government channel reads as unserious. Fix the register and test for it.
Scores from an English set say nothing about Arabic retrieval or morphology.
Score an Arabic AI channel before it ships. Tick only what has been evaluated, not what is intended.
Most statements have no artefact behind them. Start with one domain and produce the evidence before widening scope.
Scoring is deterministic and runs entirely in your browser. Nothing is stored or sent.
ISO/IEC 42001: AI management systems
International Organization for Standardization, management system requirements for AI.
NIST AI Risk Management Framework 1.0 and Generative AI Profile
National Institute of Standards and Technology, Govern, Map, Measure, Manage.
SDAIA AI Ethics Principles
Saudi Data & AI Authority, national principles for AI.
EU AI Act
Risk tiering, documentation and transparency obligations.
Citations describe the parts of each standard the framework answers. Bilytica is not an accreditation or certification body.
In Saudi Arabia
This family exists because the Saudi control set, Arabic quality and the in-country deployment ruling are not add-ons to a global method. They decide whether a system is allowed to run at all.
SDAIA, PDPL
National AI ethics principles applied as testable controls.
Each principle becomes a check with a pass condition and a named reviewer.
Ethics review record per release, in Arabic.
Arabic quality standard
Saudi Arabic output has to be correct in register, terminology and numerals, in front of a customer.
Arabic evaluation sets built from Saudi content, scored before release.
Arabic quality score with the failing cases attached.
NCA ECC
Deployment location and network boundaries are a documented decision.
A deployment ruling per data class states what may leave Saudi Arabia and what may not.
Signed residency ruling referenced by the architecture record.
Where it runs
The default is in-country, in your environment. Any exception is written down with the data class, the reason and an expiry date.
Arabic, as it is spoken here
Arabic is the governing version of every artefact in this family, with English supplied alongside.
Saudi-flavoured modern standard Arabic for enterprise channels, with dialect permitted only where the channel and the audience justify it.
On its own golden set, with morphology and diacritic variants included deliberately rather than filtered out.
Yes. The same rubric governs interfaces, assistant output and published content so one voice is used everywhere.
Curated links across our Saudi hubs, sector pages and long-form blog research.