Readiness plan / gate 02
Make every Saudi-specific assumption an owned test item
- Arabic
- Human-reviewed when scoped
- Direction
- RTL for actual Arabic experiences
- Currency
- SAR where applicable
Arabic and RTL require a content operation
A future Arabic experience needs a qualified owner for translation, terminology, tone, legal and customer text, navigation, errors, accessibility labels, metadata, structured data, and updates. Engineering tests direction, mixed scripts, wrapping, controls, focus order, search, names, and forms. English content keeps en-SA; reviewed Arabic uses ar-SA and RTL.
- Named reviewer and update owner
- Correct language and direction metadata
- Mixed-script and numeral tests
- No machine translation presented as approved
Local formats follow the workflow
Use SAR, +966 telephone data, Saudi addresses, identity fields, Hijri or Gregorian dates, Arabic and Latin names, and e-invoice data only when the client-approved process requires them. Test with fictional structurally realistic values and provider sandboxes, never live credentials or copied identities.
- Field-level necessity
- Approved fictional fixtures
- Calendar and number behavior
- Provider-specific validation
Sector and vendor context must be declared
Government, finance, health, education, commerce, and ordinary private operations can have different owners and requirements. The client identifies the sector and qualified reviewers. Every hosting, identity, payment, invoice, analytics, AI, or messaging vendor receives an owner, data map, access scope, support route, and exit plan.
- Organization and sector
- Government-work applicability decision
- Vendor and data register
- Release-time reachability check
Assign owners to the readiness matrix
Name the users, language editions, sector, data, providers, formats, devices, and people who can approve each release criterion.
Prepare the project brief