When corporate website development in Dubai runs late, design and code are rarely the cause in our experience. The usual cause is that six or seven people have a right to comment, nobody has the right to decide, and the Arabic, legal and compliance reviews arrive after the English pages were supposed to be finished. The fix is a written approval chain agreed before the first wireframe: one accountable owner, a fixed list of approvers per page type, parallel review windows, and a CMS that will not publish a page until its required sign-offs are in.
Key takeaways
- Sequential review is expensive: six approvers taking three working days each is 18 working days for one round, before any changes are made.
- Separate the people who are consulted from the people who approve, and name one person who breaks ties.
- Regulated sectors carry their own gate. A Dubai clinic’s social media promotion needs its Medical Director’s approval under DHA standards, and property advertising in Dubai needs a Dubai Land Department permit.
- Arabic parity is a governance decision, not a translation task, and the Arabic reviewer needs the same authority as the English one.
- Build the approval rules into CMS roles so a draft cannot go live without the right person pressing publish.
Why corporate website projects stall in the approval chain
A small business website has one decision-maker, usually the owner. A corporate site in Business Bay or DIFC might have a managing director, a group marketing head, a brand guardian at a parent company overseas, in-house counsel, an IT or information security lead, a compliance officer and whoever owns the Arabic content. Each of them is right to care. The problem is order.
Take the arithmetic. If six reviewers see a page one after another and each takes three working days, a single review round costs 18 working days. If the homepage needs a second round, that becomes 36. Put the same six people in one parallel window of three working days, add two days for someone to merge the comments, and the round costs five. Only the routing changed.
The second cause is late arrival. One issue we often see is legal review being scheduled after the design is approved and the copy is written, at which point a lawyer who removes a claim from the hero section also removes the reason the layout works.
The third is feedback without authority. A regional director who writes “not sure about the blue” in a shared document has created a task, because nobody knows whether it is a preference or an instruction.
Map who approves what before design starts
Write the approval chain as a table in the project charter, and get the executive sponsor to sign the table itself. On a corporate build it is the most useful page in the charter, and agreeing it takes less time than one sequential review round.
| Role | Approves | Is consulted on | Should not approve |
|---|---|---|---|
| Executive sponsor | Scope, budget, launch date, homepage message | Sitemap | Individual page copy or colours |
| Marketing or brand owner | Design system, page templates, English copy | Arabic tone, imagery | Privacy notice wording |
| Legal counsel | Privacy notice, terms, consent text, claims about results | Case studies, testimonials, image rights | Layout and design |
| Compliance or regulated reviewer | Sector claims, permit numbers, disclaimers | Service descriptions | Brand choices |
| Arabic content owner | Arabic copy and Arabic page layouts | English source copy | English wording |
| IT or information security | Hosting, forms, integrations, admin access | Analytics and cookie tools | Content |
The last column matters most. Once counsel is told in writing that layout is outside their remit, their layout comments become suggestions the brand owner can decline without a meeting.
Consulted is not the same as approves
Keep approvers to one person per area. If the group brand team in London and the local marketing head in Dubai both want to approve design, pick one and make the other consulted, with a fixed window to comment.
Set review windows and a silence rule
Agree a response window (three working days is workable for most pages) and state what happens if it lapses. For a corporate client we would usually recommend that silence counts as approval for consulted parties, but never for legal or compliance. Those two are sign-offs, and a missing sign-off holds the page, not the project.
Name one tie-breaker. Usually the executive sponsor, sometimes the marketing head. When two approvers disagree, the tie-breaker decides within two working days and the decision is logged.
Brand governance that holds up after launch
A brand guideline PDF does not govern a website; a design system does. Approved headings, buttons, colour pairs, image ratios and card layouts exist as reusable components in the CMS, and editors assemble pages from them instead of styling text by hand.
That shifts where approval happens. The brand owner signs off the component library once, carefully, including the Arabic mirrored versions. After that, a new service page built from approved components needs a content review, not a design review. A new component, such as a pricing table nobody planned for, goes back to the brand owner.
Two restrictions are worth building in. Limit the colour and font options in the editor to the approved set, so nobody can pick a near-miss shade. And limit who can create new page types, because a page type is effectively a new template and should be treated as a design change. If the brand guidelines themselves are still unsettled, finish that branding work before the component library is built, not alongside it.
Legal and regulated-sector review
Legal review goes faster when the lawyer receives a defined list rather than a staging link. That list is usually the privacy notice, the website terms, the consent wording on every form, any statement about outcomes or rankings, client names and logos used as proof, testimonials, and third-party images. Send it as a pack at the content stage.
The UAE government portal page on data protection laws (last updated 4 December 2025) lists the federal Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, and separately the DIFC Data Protection Law, DIFC Law No. 5 of 2020. Tell the reviewer where the entity is registered before the privacy notice is drafted.
Clinics and healthcare groups
The Dubai Health Authority’s Standards for Medical Advertisement Content on Social Media, version 1.1, issued 3 August 2022 and effective 3 October 2022, require the health facility’s Medical Director to approve any social media advertisement that uses the facility’s name or location (clauses 5.3 and 5.4). Clause 6.11 bars absolute and exaggerated terms including “unique”, “the best”, “100%” and “immediate results”, and Appendix 2 prohibits patient testimonials without written consent and before-and-after images without a disclaimer that outcomes vary.
That standard is written for social media, not websites, but a clinic’s service pages usually become the source text for its posts, so web copy that would pass it saves a second review. On the approval table, the Medical Director belongs in the compliance row for every treatment page, and doctor profile pages should show each doctor’s title and speciality as per their DHA licence, which clause 8.1.3 requires on social media.
Developers and brokerages
The Dubai Land Department’s Real Estate Ad Permit service lists electronic advertisements and real estate promotion platforms among the covered types. As published on the DLD page when checked on 13 September 2026, most permits cost AED 1,000 plus an AED 20 Knowledge and Innovation fee, a project launch event permit costs AED 5,000, processing takes one working day, and brokers must supply the marketing contract with the property owner. For a website, the governance answer is a listing template with a mandatory permit field, so a listing without a permit reference cannot be saved as ready to publish.
Arabic parity as a governance decision
Parity has to be defined before anyone translates anything. There are three honest options. Full parity means every page and every future page exists in both languages. Core parity covers the homepage, main service pages, contact and legal pages, with news and blog in English only. Staged parity launches English first with a dated commitment for Arabic. What fails is leaving it undefined, so Arabic becomes a backlog that grows with every English page.
For companies selling online it is also a legal question. The UAE government’s consumer protection page (updated 2 September 2026) states that e-commerce businesses must provide information in Arabic about the product or service. Counsel should confirm which pages that touches before parity is chosen; our piece on website development in Dubai covers the wider rules.
Approve both languages in the same round
Arabic copy reviewed three weeks after English copy produces two approved versions that say different things. Put English and Arabic for each page into the same review window, with the Arabic content owner as a named approver who can reject a page. Without that authority, English wins every disagreement.
Why a half-published pair causes technical problems
Google’s documentation on localized versions of your pages (last updated 22 December 2025) says each language version must list itself and all other language versions, and that Google does not use hreflang or the HTML lang attribute to detect a page’s language. So an English page published before its Arabic twin leaves the language pairing incomplete, and an “Arabic” page whose body is still English placeholder text is read as English whatever its tags say. A parity rule that publishes pairs together avoids both.
Layout approval needs the same discipline. The W3C’s guidance on the dir attribute says to set dir=”rtl” on the html element and not to set base direction in CSS. Have the Arabic reviewer approve mirrored templates at the design stage, while a label that does not fit is still a design fix.
Build the approval rules into the CMS
An approval chain that lives only in a spreadsheet is ignored the first time someone is in a hurry, so let the CMS enforce it. WordPress’s roles and capabilities documentation describes a Contributor as somebody who can write and manage their own posts but cannot publish them, an Author as somebody who can publish their own posts, and an Editor as somebody who can publish and manage posts including those of other users. Give most staff Contributor access and reserve Editor for the people in the approval table.
Strapi, a headless CMS, treats publish as a separate permission from create and update in its role-based access control, and custom roles are available on the free tier. Its Review Workflows feature adds stages such as “Ready to review”, with rules on which roles can move content into and out of each stage, but the documentation marks it as an Enterprise plan feature. Publish permissions alone still give you a working gate. Our comparison of WordPress and Strapi goes further into the editing trade-offs, and our CMS development page covers bilingual Arabic and English CMS builds and editor training.
Keep revision history switched on. The DHA standard above asks medical directors to archive posts with their edits for audit (clause 7.1.13), and a corporate legal team will ask the same question after any complaint: what did the page say, and who approved it.
A stage-by-stage sign-off plan
The gates below suit a corporate site of 20 to 60 pages with an Arabic version. The windows are planning recommendations, not industry figures.
| Gate | What is signed | Approvers | Suggested window |
|---|---|---|---|
| 1. Charter | Scope, approval table, parity option, launch date | Executive sponsor | 5 working days |
| 2. Structure | Sitemap, page types, content model | Marketing owner, IT | 3 working days |
| 3. Design system | Components in English and mirrored Arabic | Brand owner, Arabic owner | 5 working days |
| 4. Content packs | Copy per page in both languages | Marketing, Arabic owner, compliance | 3 working days per batch |
| 5. Legal pack | Privacy notice, terms, consent text, claims | Legal counsel | 5 working days |
| 6. Acceptance | Staging site against agreed tests | Marketing owner, IT | 5 working days |
| 7. Go-live | Launch checklist | Executive sponsor | 1 working day |
Gate 4 is where time goes. Send content in batches of five to eight pages, planned in a website design brief, so the build team always has approved pages to work on. Gate 6 goes faster when acceptance tests were written into the contract; WCAG 2.2, the W3C Recommendation dated 12 December 2024, gives testable accessibility criteria such as keyboard focus not being entirely hidden by other content.
What goes wrong after launch
Once the project team disbands, the site drifts. Team and doctor profiles stay up after people leave, offers outlive their dates, listings stay live after the unit sells, and new pages appear in English only because the Arabic owner was never told.
A content ownership register handles most of it. One row per page, with an owner by role rather than by name, a review date, and whether the page carries regulated content. Regulated pages get a quarterly review; everything else every six to twelve months. When someone leaves, the new holder of the role inherits the pages.
