Practical planning questions for work connected to Qatar

Questions to resolve

• Arabic and English content requirements, who reviews each version, and right-to-left testing.
• QAR display, taxes and invoicing inputs approved by the client, payments, refunds, settlement, and reconciliation.
• Personal-data handling, processors, hosting, cross-border vendors, access, retention, security, and incidents.
• Accessibility, mobile use, procurement or enterprise requirements, account ownership, and qualified local review.

Language and localization

Define the language used for contracts, meetings, technical documentation, support, and user-facing content. Machine translation can assist drafting but should not be treated as certified or automatically publication-ready.

Privacy and data

Document what information is collected, why it is needed, who can access it, which vendors process it, where it may travel, how long it is retained, and how correction, export, deletion, and incidents are handled.

Payments and commerce

Define currency display, approved tax and invoicing inputs, providers, settlement, refunds, subscriptions, disputes, reconciliation, failed states, and support.

Accessibility and usability

Set a target before design and testing. Include keyboard use, screen-reader structure, focus states, contrast, errors, labels, mobile interaction, right-to-left behavior where applicable, and representative testing.

• Qatar MCIT — Digital Agenda 2030
• Qatar MCIT — e-commerce guidelines
• Qatar Central Bank — retail payment systems
• US Government — Consolidated Screening List