INTERNAL DASHBOARDS

Qatar businesses producing Arabic-language board reports by manually reformatting English Power BI exports into Arabic Word documents are solving a translation problem that an Arabic-native Power BI dashboard with RTL layout eliminates permanently

Internal dashboards for Qatar businesses — built in Power BI with Arabic right-to-left layout, QAR currency formatting, Ramadan segmentation, and Qatarisation ratio tracking for government-linked entities and private sector organisations.

Request your Dashboard Diagnostic → View the evidence →
This is for you if

Qatar government-linked entities and semi-government organisations tracking Vision 2030 KPIs, Qatarisation ratios, and operational performance need Arabic-language dashboards built for ministerial and board reporting that present structured, formally labelled performance data aligned to the Qatar National Vision 2030 pillars — economic development, social development, human development, and environmental development. A Power BI dashboard built with Arabic RTL layout, Vision 2030 KPI structure, and Qatarisation headcount tracking connected to the HR system provides the reporting layer required for government performance reviews without a manual compilation step. The dashboard format matches the formal reporting conventions expected for ministerial presentations and government board meetings.

Qatar retail and hospitality businesses tracking sales by outlet, GCC-national versus expatriate customer segmentation, Ramadan versus non-Ramadan trading performance, and promotional campaign impact need dashboards that reflect the specific trading calendar and customer segmentation structure of the Qatar market. Ramadan performance is not comparable to standard monthly performance without an Islamic calendar dimension that flags Ramadan months and adjusts year-on-year comparisons for the Ramadan date shift. A dashboard with Ramadan segmentation built into the data model allows retail and hospitality businesses to isolate Ramadan trading performance, compare it year-on-year on a like-for-like basis, and measure the impact of Ramadan-specific promotional activity separately from non-Ramadan performance.

Qatar real estate developers tracking project sales pipeline by development, unit type, payment plan milestone collection, and nationality of buyer need a live sales dashboard connected to their CRM and payment tracking system that shows pipeline status, completion risk, and collection performance in real time rather than from a weekly manually compiled report. A dashboard showing units sold, units reserved, payment milestone collection by instalment schedule, and buyer nationality breakdown allows the sales director and project finance team to see the complete pipeline position across all active developments simultaneously. Payment milestone alerts for upcoming instalment collection dates can be surfaced as dashboard KPIs, reducing the risk of missed collection follow-up.

Qatar professional services and financial firms tracking client revenue, project utilisation, GCC country exposure, and Islamic finance versus conventional product split need a bilingual Arabic-English management dashboard that serves both Qatari national and expatriate senior management in the appropriate language. A bilingual dashboard with an Arabic-English language toggle allows the same report to serve a mixed-language leadership team without maintaining two separate versions. For financial firms with Islamic finance products, a product type dimension in the revenue model distinguishes Islamic finance revenue from conventional product revenue, providing the split required for Sharia supervisory board reporting alongside standard operational performance metrics.

What's broken

Arabic RTL Power BI Layout Not Configured

Qatar businesses with Arabic-language Power BI dashboards are using a left-to-right layout that conflicts with Arabic reading direction, resulting in text overflow on axis labels, misaligned chart titles, reversed chart axis orientation, and slicer panels that open from the wrong side of the canvas. These are not cosmetic issues — they make the report unprofessional and difficult to read for an Arabic-speaking management audience. Arabic RTL layout configuration in Power BI requires specific report canvas settings applied at the report level, combined with visual-level formatting adjustments for each chart type. Bar charts, for example, need the horizontal axis reversed so that the highest value bar extends to the left rather than the right. Without RTL configuration, an Arabic-language Power BI dashboard is effectively an English-layout dashboard with Arabic text pasted into it.

Ramadan Segmentation Not Built Into the Data Model

Qatar retail and hospitality dashboards comparing monthly performance without an Islamic calendar dimension are producing year-on-year comparisons that are contaminated by the Ramadan date shift. Ramadan moves approximately eleven days earlier each year against the Gregorian calendar, meaning that a month-on-month comparison that appears to show a revenue decline in March in one year and a revenue increase in March the following year may be entirely explained by Ramadan falling in March in the first year and in February in the second. A custom date table in Power BI that includes a Ramadan flag — marking each day as Ramadan or non-Ramadan based on the Islamic calendar for each year — allows retail and hospitality businesses to compare Ramadan performance to prior Ramadan periods on a like-for-like basis and to isolate non-Ramadan performance trends from Ramadan effects. Without this dimension, trading pattern analysis in Qatar retail and hospitality is structurally unreliable.

QAR Currency and Arabic Numeral Display Not Configured

Qatar dashboards displaying financial metrics in USD with Western Arabic numerals (0123456789) are formatted incorrectly for a Qatari management or government audience. Senior Qatari management and government entities expect financial figures displayed in QAR with Eastern Arabic numeral formatting (٠١٢٣٤٥٦٧٨٩) in formal reporting contexts. QAR currency symbol and denomination formatting requires a custom DAX format string in Power BI, as QAR is not in the default Power BI currency list for all report locales. Eastern Arabic numeral display is not natively supported as a global Power BI setting and requires a custom visual or a calculated column that converts Western numeral strings to Eastern Arabic numeral characters. Getting these formatting elements correct is required for formal board and government reporting; an incorrect numeral format in a ministerial presentation is a significant presentation failure.

No Qatarisation Ratio Dashboard

Qatar private sector businesses subject to Qatarisation requirements — the policy requiring a defined proportion of Qatari nationals in the workforce — are tracking their Qatari national headcount manually for quarterly MADLSA (Ministry of Administrative Development, Labour and Social Affairs) reporting. HR teams count Qatari national employees by department and level from the HR system each quarter, compile the ratio manually, and submit the report without any dashboard visibility into whether the ratio is on track between reporting periods. A live Qatarisation ratio dashboard connected to the HR system — showing current Qatari national headcount, total headcount, Qatarisation ratio by department, and the ratio trend over the past twelve months — gives HR leadership and the CEO visibility into Qatarisation compliance in real time, rather than only at the point of the quarterly MADLSA submission.

What we engineer

Connect to deployed systems with Arabic-native configuration

Ignited Nepal builds internal dashboards for Qatar businesses that connect to SAP, Oracle, Microsoft Dynamics, and operational systems already deployed, with Arabic-native layout, QAR currency formatting, Ramadan segmentation, and Qatarisation tracking built into the data model from the start of every Qatar engagement. The RTL layout configuration is not a post-build adjustment — it is a design decision that affects the report canvas settings, visual placement, and axis orientation of every chart in the dashboard.

Configure the Arabic RTL layout

The Arabic RTL layout is configured at the Power BI report canvas level using the right-to-left reading direction setting, combined with individual visual-level adjustments for chart axis orientation, slicer panel direction, and text alignment. Bar and column chart axes are reversed so that values extend from the right. Card visuals and KPI scorecards are aligned to the right. Slicer panels open from the right side of the canvas. Every visual is reviewed against the RTL reading pattern before the report is signed off, and the complete report layout is tested with Arabic-language content in every label position to confirm there is no text overflow or misalignment.

Build the Ramadan segmentation dimension into the date table

The Ramadan segmentation dimension is built into the date table as a Boolean flag column — Ramadan: Yes / No — calculated from the Islamic calendar dates for each year in the model's date range. Ramadan start and end dates for each Gregorian year are stored in a reference table that is updated annually as official Ramadan dates are confirmed. The date table also includes a Ramadan day number column, allowing analysis of performance by day within Ramadan as well as comparison of total Ramadan period performance across years. A Ramadan comparison matrix allows management to compare this year's Ramadan trading against prior years on a day-by-day and total-period basis, adjusted for the Gregorian date shift.

Apply QAR currency and Eastern Arabic numeral formatting

QAR currency formatting is applied using a custom DAX format string that prepends the QAR symbol and formats amounts in QAR denomination. Eastern Arabic numeral display is implemented where required using a custom calculated column that maps Western digit characters to their Eastern Arabic equivalents, or by using a report theme with an appropriate Arabic numeral font. The approach depends on the specific reporting context and the Power BI version in use.

Structure the dashboard around the Vision 2030 KPI framework

For Qatar government-linked entities, the dashboard is structured around the Qatar National Vision 2030 KPI framework, with pillar-level performance indicators, Qatarisation ratio tracking, and operational KPIs presented in the formal structured layout expected for ministerial reporting. Qatarisation ratio data is connected to the HR system — SAP SuccessFactors, Oracle HCM, or the client's HR platform — via API or scheduled data export, and is displayed as a live ratio with department-level breakdown and trend chart.

Build bilingual Arabic-English dashboards

For bilingual Arabic-English dashboards, the same translations table architecture used for Canadian French-English dashboards is applied, with an Arabic-English language toggle driving DAX filter variables that switch all visible text between Arabic and English simultaneously. The Arabic version uses RTL layout; an English version of the same report can be configured with LTR layout for expatriate management users.

Request your Dashboard Diagnostic →
What changes

Before
After
Before Qatar businesses with Arabic-language Power BI dashboards are using a left-to-right layout that conflicts with Arabic reading direction, resulting in text overflow on axis labels, misaligned chart titles, reversed chart axis orientation, and slicer panels that open from the wrong side of the canvas. These are not cosmetic issues — they make the report unprofessional and difficult to read for an Arabic-speaking management audience. Arabic RTL layout configuration in Power BI requires specific report canvas settings applied at the report level, combined with visual-level formatting adjustments for each chart type. Bar charts, for example, need the horizontal axis reversed so that the highest value bar extends to the left rather than the right. Without RTL configuration, an Arabic-language Power BI dashboard is effectively an English-layout dashboard with Arabic text pasted into it.
After Arabic-language board reports are produced directly from the dashboard without a manual reformatting step. The manual process of exporting an English report and reformatting it in Arabic Word disappears; the Arabic board report is a scheduled Power BI export from the Arabic-native dashboard.
Before Qatar retail and hospitality dashboards comparing monthly performance without an Islamic calendar dimension are producing year-on-year comparisons that are contaminated by the Ramadan date shift. Ramadan moves approximately eleven days earlier each year against the Gregorian calendar, meaning that a month-on-month comparison that appears to show a revenue decline in March in one year and a revenue increase in March the following year may be entirely explained by Ramadan falling in March in the first year and in February in the second. A custom date table in Power BI that includes a Ramadan flag — marking each day as Ramadan or non-Ramadan based on the Islamic calendar for each year — allows retail and hospitality businesses to compare Ramadan performance to prior Ramadan periods on a like-for-like basis and to isolate non-Ramadan performance trends from Ramadan effects. Without this dimension, trading pattern analysis in Qatar retail and hospitality is structurally unreliable.
After Ramadan trading analysis is accurate for the first time. Year-on-year retail and hospitality comparisons account for the Ramadan date shift; management can see true Ramadan period performance versus prior years without the distortion caused by comparing Gregorian months that have different Ramadan overlap each year.
Before Qatar dashboards displaying financial metrics in USD with Western Arabic numerals (0123456789) are formatted incorrectly for a Qatari management or government audience. Senior Qatari management and government entities expect financial figures displayed in QAR with Eastern Arabic numeral formatting (٠١٢٣٤٥٦٧٨٩) in formal reporting contexts. QAR currency symbol and denomination formatting requires a custom DAX format string in Power BI, as QAR is not in the default Power BI currency list for all report locales. Eastern Arabic numeral display is not natively supported as a global Power BI setting and requires a custom visual or a calculated column that converts Western numeral strings to Eastern Arabic numeral characters. Getting these formatting elements correct is required for formal board and government reporting; an incorrect numeral format in a ministerial presentation is a significant presentation failure.
After QAR currency and Eastern Arabic numeral formatting meets the standard expected for formal Qatari management and government reporting. Financial figures are displayed in the correct format for the audience without a manual reformatting step after export.
Before Qatar private sector businesses subject to Qatarisation requirements — the policy requiring a defined proportion of Qatari nationals in the workforce — are tracking their Qatari national headcount manually for quarterly MADLSA (Ministry of Administrative Development, Labour and Social Affairs) reporting. HR teams count Qatari national employees by department and level from the HR system each quarter, compile the ratio manually, and submit the report without any dashboard visibility into whether the ratio is on track between reporting periods. A live Qatarisation ratio dashboard connected to the HR system — showing current Qatari national headcount, total headcount, Qatarisation ratio by department, and the ratio trend over the past twelve months — gives HR leadership and the CEO visibility into Qatarisation compliance in real time, rather than only at the point of the quarterly MADLSA submission.
After Qatarisation ratio is visible in real time between quarterly MADLSA submissions. HR leadership and the CEO can see the current ratio and its trend across departments without waiting for the quarterly manual count; compliance risk is visible before the submission deadline, not at it.
How it works

  1. 01

    Discovery and data audit.

    We map every data source — SAP, Oracle, Dynamics, CRM, HR system — and document available data, Arabic language requirements, Qatarisation reporting obligations, and the reporting format conventions expected for board or ministerial presentation. We confirm QAR currency requirements, Vision 2030 KPI framework applicability, and Ramadan segmentation requirements at this stage.

  2. 02

    Data model design.

    We design the Power BI data model: Ramadan date table with Islamic calendar flags, Qatarisation ratio dimension, QAR currency format strings, and bilingual Arabic-English translations table where required. Arabic RTL layout conventions are agreed before build begins.

  3. 03

    Data connections and transformation.

    We connect to SAP, Oracle, Dynamics, or the client's HR platform via the appropriate API or certified connector. The Ramadan date reference table, Islamic calendar dimension, and Qatarisation headcount data connection are built and tested at this stage.

  4. 04

    Dashboard build and Arabic RTL configuration.

    We build all report pages with RTL canvas settings, Arabic-language labels, QAR currency formatting, and Eastern Arabic numeral display where required. Ramadan segmentation visuals, Qatarisation ratio tracking, and Vision 2030 KPI structure are built for government-linked entity clients. Bilingual language toggle is configured where required.

  5. 05

    Automated reporting and Arabic export setup.

    Scheduled Power BI subscription emails and PDF exports for Arabic-language board reports are configured and tested. Export format, page layout, and distribution list are agreed with the client before handover.

  6. 06

    Handover, documentation, and training.

    We deliver data model documentation in Arabic and English, an Arabic-language user guide, and a training session for Power BI report owners. A 30-day hypercare period covers any RTL layout, Arabic label, or data connection issues identified during the first month of live use.

Request your Dashboard Diagnostic →
Common questions

Frequently asked questions about Internal Dashboards

How do I configure an Arabic right-to-left (RTL) layout in Power BI for a Qatar business dashboard?

Arabic RTL layout in Power BI is configured at the report canvas level by setting the text direction to right-to-left in the report settings, which adjusts the default text alignment and reading direction for text elements across the report. This canvas-level setting must be combined with visual-level adjustments for each chart type: horizontal bar charts require the category axis to be reversed so that bars extend from right to left; slicer panels must be positioned and configured to open from the right side of the canvas; KPI cards and text boxes must be right-aligned. The RTL canvas setting does not automatically adjust all visual elements — each chart type behaves differently and requires individual review and adjustment. Matrix and table visuals require column order reversal for RTL reading direction. The complete RTL configuration should be tested with actual Arabic-language content in every label position before the dashboard is presented to a management audience, as text overflow and truncation issues only become visible with full-length Arabic strings.

How do I add a Ramadan segmentation flag to a Power BI data model for a Qatar retail or hospitality dashboard?

Ramadan segmentation is added to the Power BI date table by creating a Ramadan reference table — containing the confirmed start date and end date of Ramadan for each year in the model's date range — and joining it to the main date table to generate a Boolean Ramadan flag column (Ramadan = True / False) for each date. The Ramadan start and end dates for each year must be sourced from a reliable Islamic calendar reference and updated annually when confirmed official Ramadan dates are announced, as Ramadan dates depend on moon sighting and may vary by one day from astronomical prediction. Additional columns derived from the Ramadan flag — Ramadan day number within the Ramadan period, pre-Ramadan preparation period flag, and post-Eid period flag — allow more granular analysis of trading patterns around Ramadan. Measures comparing Ramadan-period performance across years use the Ramadan flag to filter and aggregate data by Islamic calendar period rather than Gregorian calendar month.

How do I display QAR currency and Eastern Arabic numerals in a Power BI dashboard for Qatar?

QAR currency display in Power BI requires a custom DAX format string applied to each financial measure, as QAR is not available as a pre-configured currency format in all Power BI locale settings. The format string specifies the QAR symbol (ر.ق) and the decimal and thousands separator conventions appropriate for QAR denomination. Eastern Arabic numeral display — using the characters ٠١٢٣٤٥٦٧٨٩ instead of Western Arabic numerals 0-9 — requires either a custom visual that renders text using an Eastern Arabic numeral font, or a calculated column that converts numeric values to a text string using a character substitution function that maps each Western digit to its Eastern Arabic equivalent. The text string approach converts numbers to display text, which affects sorting and aggregation behaviour in visuals and must be handled carefully to preserve correct sort order in charts and tables. For formal government and ministerial reporting contexts, Eastern Arabic numeral display is often required only in specific label positions rather than universally, so a targeted approach applying the conversion only where needed is typically more practical than a report-wide numeral substitution.

How do I build a Qatarisation ratio tracking dashboard connected to an HR system for MADLSA reporting?

A Qatarisation ratio dashboard requires a live connection to the organisation's HR system — SAP SuccessFactors, Oracle HCM, Microsoft Dynamics HR, or a local HRIS — to retrieve current employee records including nationality, department, level, and employment status. The Power BI data model aggregates headcount by nationality (Qatari national versus non-Qatari) at department, business unit, and total organisation level, and calculates the current Qatarisation ratio as a measure. A Qatarisation target table — specifying the required Qatarisation ratio by department or total headcount as set by MADLSA — is loaded into the model as a reference table, and a variance measure shows current ratio against target. The dashboard displays the current ratio, the twelve-month ratio trend, a department-level breakdown, and the days remaining to the next MADLSA quarterly submission. HR data connections are typically built via a scheduled data export from the HR system to a secure staging location, or via direct API connection where the HR platform supports it, with a daily refresh cadence to keep headcount data current.

What is the best business intelligence tool for a Qatar government-linked entity or large private company — Power BI, SAP Analytics Cloud, or Oracle Analytics?

Power BI is the most widely deployed business intelligence tool among Qatar private sector businesses and a significant proportion of Qatar government-linked entities, primarily because of the Microsoft 365 ecosystem integration and the lower per-seat cost compared to SAP Analytics Cloud and Oracle Analytics. Power BI's Arabic RTL support, while requiring manual configuration, is achievable to a high standard with experienced Power BI developers and is sufficient for formal board and ministerial reporting. SAP Analytics Cloud is the natural choice for Qatar organisations running SAP ERP as their primary operational system, as the native SAP data connection eliminates the integration complexity that Power BI faces when connecting to SAP; for SAP-centric entities, SAP Analytics Cloud provides tighter financial planning and consolidation capability alongside dashboard reporting. Oracle Analytics Cloud is the equivalent choice for Oracle ERP environments. For Qatar government entities that are not SAP or Oracle shops and are operating Microsoft infrastructure, Power BI is the most practical and cost-effective path to an Arabic-native dashboard with the Qatarisation tracking and Vision 2030 KPI structure required for government performance reporting.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

Qatar businesses spending hours each month reformatting English Power BI exports into Arabic Word documents are maintaining a workaround for a problem that an Arabic-native dashboard solves permanently. A Power BI dashboard built with Arabic RTL layout, QAR currency formatting, Ramadan segmentation, and Qatarisation ratio tracking is not a niche specialisation — it is the correct configuration for any business intelligence dashboard used for formal management reporting in Qatar. Ignited Nepal builds these dashboards for Qatar businesses and government-linked entities, from data model design through to Arabic-language export automation and handover. The first step is a Dashboard Diagnostic, where we map your data sources, confirm your Arabic language and Qatarisation reporting requirements, and design the data model that produces accurate, Arabic-native reporting from day one.

Request your Dashboard Diagnostic →