INTERNAL DASHBOARDS

UAE businesses producing Arabic-language performance reports for senior leadership by manually translating English Power BI dashboards into a Word document every month are spending 10-15 hours a month on a task that a configured Arabic Power BI dashboard makes instant

Build bilingual Arabic-English dashboards in Power BI with correct RTL layout, Ramadan period segmentation, and GCC country breakdowns for senior management reporting.

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

Retailers and fast-moving consumer goods companies operating across the GCC need a sales dashboard that tracks performance by country, product category, and channel with Ramadan versus non-Ramadan period segmentation built in as a standard filter. These businesses currently produce monthly performance decks that aggregate GCC performance without country-level visibility and compare months without accounting for the structural difference between Ramadan and non-Ramadan trading periods. A Power BI dashboard with a GCC country dimension and a Ramadan flag on the date table gives the commercial director country-level performance and seasonality-adjusted comparisons in a single view.

Hotel groups and restaurant operators with properties across Dubai and Abu Dhabi tracking occupancy, RevPAR, F&B revenue, and event bookings need a property performance dashboard available in both Arabic and English, with the Arabic view configured for senior Arabic-speaking ownership and the English view for the international general management team. These businesses currently produce separate weekly reports for different leadership levels in different formats. A bilingual Power BI environment with role-based views for Arabic and English users gives both leadership levels access to the same data in their preferred language simultaneously.

Property developers tracking active projects, unit sales pipeline, buyer nationality breakdown, and payment plan milestone collection rates need a project and sales dashboard that connects the project management system, CRM, and accounting platform in one view. UAE real estate dashboards specifically require buyer nationality as a dimension (UAE national, GCC, Arab non-GCC, European, Asian, Other) because payment plan structures, registration fees, and mortgage eligibility differ by nationality. A live dashboard that tracks payment plan milestone collection by project, unit type, and buyer nationality gives the CFO and sales director visibility into collection risk before it becomes a cash flow problem.

Consulting, legal, and accounting firms operating across the UAE and GCC with billable staff and multi-currency client engagements need a project profitability and utilisation dashboard that shows revenue concentration by client, billable utilisation by team, and margin by engagement type across the GCC client base. These firms are currently tracking utilisation in a timesheet system and invoicing in an accounting platform (SAP, Oracle, or Sage) with no live view connecting the two. A connected dashboard gives the managing partner a current view of which clients represent the highest revenue concentration risk, which teams are approaching capacity, and which engagements are delivering below-target margins.

What's broken

Arabic-language dashboard not configured

UAE enterprises producing board and senior management reports in Arabic are translating the English Power BI or Tableau dashboard into a Word document or PowerPoint manually, every reporting cycle. The Arabic report is not a live dashboard — it is a static document compiled from the live dashboard's output. Arabic Power BI configuration requires right-to-left layout on every page, Arabic numeral format settings, Arabic font selection (typically Dubai or Cairo), and bilingual field labels where both Arabic and English text need to appear in the same chart. Most UAE businesses have not completed this configuration because the Power BI administrator who set up the original environment was not briefed to do it. The result is that Arabic-speaking leadership is receiving information that is days behind the English dashboard and formatted for reading in a document, not for interactive analysis.

Ramadan performance not segmented

UAE retail and hospitality dashboards comparing monthly performance without isolating the Ramadan trading period are producing trend lines and year-on-year comparisons that are not meaningful for those months. Ramadan creates a structural shift in trading patterns — lower daytime footfall and transaction volume, higher evening and late-night activity, higher average transaction values in food and gift categories, and lower average transactions in discretionary non-food categories. When a monthly performance comparison does not flag that one month contains Ramadan and the comparison month does not, the observed variance is interpreted as performance change when it is actually a structural calendar effect. UAE dashboards require a Ramadan flag field on the date table so that any comparison metric can be filtered to show Ramadan versus non-Ramadan periods separately.

GCC country breakdown absent

UAE businesses with operations in Saudi Arabia, Qatar, Kuwait, Bahrain, and Oman are aggregating GCC revenue in a single "international" line in their dashboards. Country-level revenue, growth rate, margin, and team performance are invisible. The commercial decision to invest in one GCC market over another is being made without country-level profitability data because the dashboard has not been built with a GCC country dimension. Adding a GCC country dimension to the data model requires tagging transactions, customers, and staff records with a country code at the source system level and then surfacing that dimension in the dashboard. In businesses where source systems already hold the country data, adding the dimension to the dashboard is a data model change, not a new data collection exercise.

No real-time data access for UAE leadership

UAE leadership teams in many enterprises are receiving performance data through a weekly PowerPoint or PDF report compiled by the analytics team and circulated Sunday morning before the weekly leadership meeting. By the time the report is reviewed in the meeting, the data in it is between three and seven days old. The analyst team has access to the live Power BI or Tableau dashboard but the leadership team does not have a configured view that matches their level of reporting. The data exists in the live system. The gap is that the leadership view has not been designed and made accessible to them directly. When the leadership team has direct access to a live dashboard designed for their level of reporting, the Sunday morning compilation process is replaced by a standing dashboard that they can review before any meeting without waiting for the analyst team to prepare a document.

What we engineer

Assess the existing business intelligence environment

We begin by assessing the existing business intelligence environment. Most UAE enterprises have Power BI deployed at some level. We document which data sources are currently connected, what the existing dashboard covers, who has access to it, and what the current Arabic-language reporting process looks like. We identify the gap between the live English dashboard and the Arabic report that leadership receives, and we design the solution to close that gap rather than rebuild the entire environment from scratch.

Configure the Arabic Power BI environment

We configure the Arabic Power BI environment. This includes setting up RTL page layout for all Arabic report pages, configuring Arabic numeral display where required, selecting appropriate Arabic fonts, and building a bilingual label structure that allows the same calculated measures to display their labels in Arabic or English depending on which report page is active. For businesses that require Arabic and English as switchable views within a single report, we build the toggle mechanism that switches the display language without changing the underlying data.

Build the Ramadan segmentation into the date table

We build the Ramadan segmentation into the date table. The date table is the foundation of all time-based analysis in Power BI. We add a Ramadan flag field to the date table that marks every date that falls within a Ramadan period (based on the confirmed Hijri calendar dates for each year in the data range). All time comparison measures (month-on-month, year-on-year, rolling averages) can then be filtered by Ramadan versus non-Ramadan, and any comparison that crosses a Ramadan period is flagged in the dashboard view.

Add the GCC country dimension to the data model

We add the GCC country dimension to the data model. Where source systems already hold country data at the transaction or customer level, we surface that dimension through the data pipeline into the Power BI model. We build GCC country filters into each relevant dashboard page so that the commercial director can view UAE-only performance, GCC aggregate performance, or any individual GCC country view from the same dashboard.

Design role-based dashboard views for each leadership level

We design role-based dashboard views for each leadership level. Arabic-language senior leadership views are designed for the information density and format appropriate to board and ownership reporting. English-language operational views are designed for the management team using the live dashboard for daily decision-making. Each view shows the metrics relevant to the user's function without exposing data outside their reporting scope.

Deliver the configured environment with documentation

We deliver the configured environment with documentation covering the Arabic layout configuration, the Ramadan date table logic, the GCC country dimension, and the role access structure. We conduct handover sessions in both English and Arabic (where required) and provide 30 days of support for the live operation period.

Request your Dashboard Diagnostic →
What changes

Before
After
Before UAE enterprises producing board and senior management reports in Arabic are translating the English Power BI or Tableau dashboard into a Word document or PowerPoint manually, every reporting cycle. The Arabic report is not a live dashboard — it is a static document compiled from the live dashboard's output. Arabic Power BI configuration requires right-to-left layout on every page, Arabic numeral format settings, Arabic font selection (typically Dubai or Cairo), and bilingual field labels where both Arabic and English text need to appear in the same chart. Most UAE businesses have not completed this configuration because the Power BI administrator who set up the original environment was not briefed to do it. The result is that Arabic-speaking leadership is receiving information that is days behind the English dashboard and formatted for reading in a document, not for interactive analysis.
After Arabic-speaking senior leadership and board members have direct access to a live Power BI dashboard in Arabic with correct RTL layout and Arabic numeral formatting. The manual translation process from English dashboard to Arabic Word document is eliminated. Leadership receives the same data the analyst team has, at the same time, in the format they can read and use directly.
Before UAE retail and hospitality dashboards comparing monthly performance without isolating the Ramadan trading period are producing trend lines and year-on-year comparisons that are not meaningful for those months. Ramadan creates a structural shift in trading patterns — lower daytime footfall and transaction volume, higher evening and late-night activity, higher average transaction values in food and gift categories, and lower average transactions in discretionary non-food categories. When a monthly performance comparison does not flag that one month contains Ramadan and the comparison month does not, the observed variance is interpreted as performance change when it is actually a structural calendar effect. UAE dashboards require a Ramadan flag field on the date table so that any comparison metric can be filtered to show Ramadan versus non-Ramadan periods separately.
After Ramadan versus non-Ramadan performance comparisons become structurally sound. The commercial director can view sales performance for Ramadan 2024 against Ramadan 2023 rather than comparing Ramadan months against non-Ramadan months. The structural calendar effect of Ramadan is separated from genuine performance change, which means performance conversations are based on comparable periods.
Before UAE businesses with operations in Saudi Arabia, Qatar, Kuwait, Bahrain, and Oman are aggregating GCC revenue in a single "international" line in their dashboards. Country-level revenue, growth rate, margin, and team performance are invisible. The commercial decision to invest in one GCC market over another is being made without country-level profitability data because the dashboard has not been built with a GCC country dimension. Adding a GCC country dimension to the data model requires tagging transactions, customers, and staff records with a country code at the source system level and then surfacing that dimension in the dashboard. In businesses where source systems already hold the country data, adding the dimension to the dashboard is a data model change, not a new data collection exercise.
After GCC country-level performance is visible in every commercial view. The decision about where to invest sales and marketing resources across the GCC is supported by country-level revenue, growth rate, and margin data rather than an aggregated international line. Markets where growth is strong are visible. Markets where margin is below the GCC average are visible.
Before UAE leadership teams in many enterprises are receiving performance data through a weekly PowerPoint or PDF report compiled by the analytics team and circulated Sunday morning before the weekly leadership meeting. By the time the report is reviewed in the meeting, the data in it is between three and seven days old. The analyst team has access to the live Power BI or Tableau dashboard but the leadership team does not have a configured view that matches their level of reporting. The data exists in the live system. The gap is that the leadership view has not been designed and made accessible to them directly. When the leadership team has direct access to a live dashboard designed for their level of reporting, the Sunday morning compilation process is replaced by a standing dashboard that they can review before any meeting without waiting for the analyst team to prepare a document.
After The Sunday morning report compilation is replaced by a live leadership dashboard. The analytics team's time is redirected from compiling a weekly report to analysing the data the dashboard makes available. Leadership arrives at the weekly meeting with the performance view already in front of them, not waiting for the analyst team to finish the deck.
How it works

  1. 01

    Existing BI environment assessment.

    We review the current Power BI or Tableau environment, document the data sources connected, assess the current Arabic reporting process, and identify the specific gaps between the live English dashboard and the Arabic leadership report. We agree on the scope of work before any configuration begins.

  2. 02

    Arabic layout and bilingual configuration design.

    We design the Arabic RTL page layout, bilingual label structure, Arabic font selection, and numeral format configuration. We produce a design specification for the Arabic views that is reviewed and approved before the build begins.

  3. 03

    Ramadan date table configuration.

    We build or update the date table with the Ramadan flag field, validate the Hijri calendar dates for every Ramadan period in the data range, and test the Ramadan filter across all time comparison measures to confirm that Ramadan and non-Ramadan periods are correctly segmented.

  4. 04

    GCC country dimension and data model update.

    We add the GCC country dimension to the data model, connect country-tagged data from source systems, and validate country-level aggregations against source system totals for each GCC market.

  5. 05

    Role-based view build and bilingual QA.

    We build the dashboard views for each audience level and run a bilingual quality assurance check: every metric in the Arabic view is validated against the same metric in the English view to confirm that the underlying data and calculations are identical and that the RTL layout renders correctly on both desktop and mobile.

  6. 06

    Handover, documentation, and Arabic-language support.

    We deliver the configured environment with documentation in both English and Arabic where required. We conduct handover sessions with the analytics team and with senior Arabic-speaking leadership users. We provide 30 days of support for configuration questions and adjustments.

Request your Dashboard Diagnostic →
Common questions

Frequently asked questions about Internal Dashboards

How do I build an Arabic-language Power BI dashboard with right-to-left layout for a UAE business?

Power BI supports RTL layout through the report page settings, where the text direction can be set to right-to-left for each page individually. Arabic font support requires adding an Arabic-compatible font (Dubai, Cairo, or Noto Sans Arabic) to the report visuals' font settings. Arabic numeral display (Eastern Arabic numerals) is configured in the visual formatting settings for any text card or table visual that displays numbers. Report pages designed for Arabic-speaking users are built as separate pages within the same Power BI report file, using the same underlying data model and calculated measures as the English pages, with RTL layout and Arabic labels applied to each visual. This approach means that the underlying data and calculations are maintained in one place while the presentation layer is adapted for Arabic and English audiences separately.

How do I segment Ramadan vs non-Ramadan performance in a UAE retail or hospitality dashboard?

Ramadan segmentation requires a Ramadan flag column in the Power BI date table. For each date in the date table, the Ramadan flag is set to TRUE if the date falls within a confirmed Ramadan period (based on the official UAE moon-sighting calendar for each year) and FALSE otherwise. This flag is then used as a filter in time comparison measures so that month-on-month and year-on-year comparisons can be run in two modes: including all dates, or restricted to Ramadan dates only in both the current and comparison period. For UAE retail and hospitality dashboards, the Ramadan filter is added to the report filter panel so the analyst or commercial manager can toggle between the full-period view and the Ramadan-segmented view without changing the report design.

How do I add a GCC country breakdown dimension to a UAE business performance dashboard?

A GCC country breakdown requires that source system records (transactions, customers, sales orders, or staff assignments) are tagged with a country code at the point of entry. If the source system (SAP, Oracle, Salesforce, or a custom ERP) already holds country data at the record level, the country field is mapped through the data pipeline into the Power BI data model as a dimension. A GCC country dimension table is added to the model with the six GCC country codes (AE, SA, QA, KW, BH, OM) and their Arabic and English display names. This dimension table is related to the fact tables (sales, revenue, cost) via the country code. Country-level filters are then added to each relevant dashboard page, allowing the user to view aggregate GCC performance or drill to any individual GCC country.

How do I connect UAE accounting systems (SAP, Oracle, Sage) to Power BI for a live financial dashboard?

SAP connects to Power BI via the SAP HANA connector or SAP BW connector, both available natively in Power BI Desktop. Oracle connects via the Oracle Database connector in Power BI, which requires the Oracle Data Access Client installed on the machine running the Power BI Gateway. Sage connects to Power BI via the Sage connector available in Power BI's Get Data menu or via a third-party connector depending on the Sage version in use. For all three systems, a Power BI On-premises Data Gateway is required if the accounting system is hosted on-premises rather than in the cloud. The gateway runs as a service on a server within the company network and manages the data transfer between the on-premises system and the Power BI cloud service. Once connected, financial data refreshes on the schedule configured in the gateway settings, typically daily or multiple times per day.

What is the best business intelligence tool for a UAE enterprise — Power BI, Tableau, or Qlik?

Power BI is the dominant choice in the UAE and wider GCC enterprise market for three reasons: it integrates directly with the Microsoft 365 environment that most UAE enterprises already use, it has native Arabic RTL support that Tableau and Qlik require more configuration work to replicate, and its per-user licensing at the Microsoft 365 E3 or E5 level is included in many existing enterprise agreements. Tableau is used in UAE enterprises where the analytics team has strong Tableau skills from prior roles and where self-serve analytics for non-technical business users is a priority. Qlik is used in some UAE enterprises, particularly in sectors where Qlik has strong regional partner support. For a UAE enterprise building a new business intelligence environment or adding Arabic-language dashboard capability, Power BI is the recommended starting point unless the business has an existing investment in Tableau or Qlik skills and licences.

Start here

Your Power BI environment already holds the performance data your senior Arabic-speaking leadership needs. The gap is not the data — it is the Arabic-language view, the Ramadan segmentation, and the GCC country dimension that make the data accessible and meaningful for the leadership team making the decisions. We configure the existing environment for the Arabic leadership view, build the Ramadan date logic, and add the GCC country dimension so that the same live data the analyst team uses is available to senior leadership in the format they need. If you want to understand the scope of the Arabic configuration work required for your existing environment before committing to a build, start with a diagnostic conversation.

Request your Dashboard Diagnostic →