Government and Semi Government Web Projects in the UAE

Government website development UAE projects follow a different path from private sector work: vendors usually register on an official procurement portal first, respond to a formal tender with separate technical and commercial submissions, and then build to published federal or emirate standards for accessibility, design and security. This guide walks through vendor registration, the usual tendering stages and the web standards to plan for, and ends with a qualification checklist to verify against the current portals before you bid.

How government website development UAE projects differ from private work

A private client can choose an agency after a few meetings. A ministry, federal authority or emirate level department generally cannot. Public money is spent under procurement rules, so the process is documented, time bound and auditable. That changes almost everything about how a web project is won and delivered.

• The buyer is a committee, not a person. Evaluation is shared between technical, procurement and finance reviewers, and each scores against written criteria.
• Requirements are fixed early. The tender document defines scope, and changes after award usually need formal variation approval.
• Standards are external. Accessibility, bilingual content, design consistency and information security often follow government policies rather than the project team's preferences.
• Accountability continues after launch. Support obligations, service levels and handover documentation are part of the contract, not an afterthought.

Semi government organisations, such as government owned companies and authorities with their own boards, sit between the two worlds. Their processes vary widely, which is covered later in this guide.

Step one: vendor registration

Registration is the gate. Many entities can only invite or award to suppliers already on their register, so leaving this until a tender appears is a common and avoidable mistake. The UAE has separate registration routes at federal and emirate level, and some individual entities keep their own supplier lists as well.

Federal registration

The Ministry of Finance Federal Supplier Register is the starting point for suppliers to federal entities. Secondary sources describe a UAE PASS login and a document list for domestic suppliers that includes the trade licence and VAT registration certificate. Confirm the current document list, processing time and any renewal requirement directly with the Ministry of Finance, as these details have changed as the platform has developed.

Dubai and Abu Dhabi registration

Dubai Government tenders are commonly run through the eSupply portal, and Abu Dhabi entities use the Abu Dhabi Government Procurement Gate. Published guides describe different routes depending on where your trade licence is issued, and several entities in both emirates also publish their own supplier registration pages. Treat any step by step guide you find online as a pointer only, and confirm the process with the portal operator or the entity you want to supply.

Documents to prepare in advance

Registration requirements differ by portal, but most ask for some combination of the following. Keeping them current saves days when a tender opens.

• Valid trade licence with activities that match web, software or IT services
• VAT registration certificate from the Federal Tax Authority, where applicable
• Company profile, authorised signatory details and authorisation letter
• Bank letter confirming account details
• Any in country value or similar certificates the entity asks for
• Insurance certificates and audited financial statements, if requested in prequalification

The government tender UAE process, stage by stage

Each government tender in the UAE follows the entity's own procurement policy, so stage names and timings vary. The sequence below reflects how most formal web tenders run and helps you plan resources. The official UAE government portal gives a general overview of tendering and awarding; the rules in the specific tender document always take priority.

1. Prequalification or request for information. The entity asks for capability statements, relevant experience and team profiles to build a shortlist.
2. Tender issue. The request for proposal sets out scope, evaluation criteria, submission format and deadlines.
3. Clarification window. Bidders submit written questions by a fixed date. Answers are usually shared with all bidders.
4. Submission. Technical and commercial proposals are typically submitted separately, often through the portal, and late submissions are normally rejected.
5. Technical evaluation. The committee scores the technical proposal first. Bidders below the threshold may not have their commercial offer opened.
6. Presentations or demonstrations. Shortlisted bidders may be asked to present the approach, the team or a prototype.
7. Commercial evaluation and negotiation. Combined scores decide the preferred bidder, sometimes followed by a best and final offer.
8. Award and contract. Contract terms, service levels, security obligations and payment milestones are finalised before work starts.

Two practical points matter at every stage. First, every answer should map to an evaluation criterion, because reviewers score what is written, not what is implied. Second, use the clarification window: a vague requirement left unchallenged becomes a scope dispute after award.

Government web standards to build for

Government web standards in the UAE are published by several bodies, and the tender will usually name the ones that apply. These are the areas to plan for from the first proposal draft.

Accessibility

The National Digital Accessibility Policy sets expectations for federal digital services, and public reporting describes WCAG 2.1 at level AA as the reference standard. Plan accessibility into design and development rather than testing for it at the end: semantic structure, keyboard navigation, colour contrast, text alternatives, accessible forms and right to left layouts all need attention. Confirm the exact level and any newer version the entity requires.

The UAE Design System

The Telecommunications and Digital Government Regulatory Authority publishes the UAE Design System, a set of components, blocks and patterns for federal government websites. Its documentation explains how to install and use it, and it includes assessment criteria that entities can use to evaluate their sites. If a tender references it, show in the proposal how your front end will use the components rather than recreating them.

Bilingual content and identity

• Arabic and English versions with equal quality, correct right to left layout and consistent navigation
• UAE PASS sign in where the service involves identity, following the integration requirements the entity provides
• Consistent government branding rules, which are usually supplied in the tender pack

Security, hosting and data

Expect requirements on hosting location, penetration testing, vulnerability management, access control and incident reporting. Each emirate and many entities have their own information security policies, so ask which apply and request the documents during clarifications. Personal data handling is also a frequent evaluation item.

Semi government procurement: what changes

Semi government procurement is less uniform. Government owned companies, zone authorities and similar bodies often run their own procurement policies, supplier portals and ERP based sourcing systems. Some follow government standards voluntarily, and the UAE Design System has been described as open to semi governmental entities, but adoption is a decision for each organisation.

In practice, expect three differences:

• Commercial flexibility. Negotiation and phased contracts are more common than in federal tenders.
• Brand independence. Many semi government bodies have their own brand guidelines and do not use federal design components.
• Integration depth. Websites often connect to CRM, ERP and customer service systems, so integration experience carries more weight in evaluation.

Before bidding, ask which procurement policy applies, who owns the website after launch and whether the organisation expects government standards to be followed.

Vendor registration and qualification checklist

Use this list to check readiness before a tender opens. Verify every item against the current portal and tender document, because requirements change and portals are updated.

• Active registration on each portal relevant to the entities you target, with renewal dates tracked
• Trade licence activities that match the services in the tender
• Current VAT certificate and company documents uploaded and matching your licence details
• Named project team with CVs, including bilingual content and accessibility expertise
• Relevant reference projects you are permitted to name, with permission confirmed in writing
• Accessibility testing method and tools described in writing
• Information security policy, secure development practice and penetration testing approach
• Hosting proposal that meets the entity's data location requirements
• Support model with service levels, escalation contacts and response times you can actually meet
• Handover plan covering documentation, source code, credentials and training

Writing a stronger technical proposal

Mirror the evaluation criteria

Structure the proposal in the same order as the evaluation table. If a criterion is worth significant weight, give it a clear section with evidence, not a paragraph buried elsewhere. Reviewers working through dozens of submissions reward clarity.

Show method, not adjectives

Replace general claims with how you work: the discovery workshops you will run, how content migration will be checked, the accessibility testing sequence and how defects are tracked. Include sample deliverables such as a sitemap extract or a test plan outline where the tender allows.

Be realistic about the team

Name the people who will do the work and keep them on the project. Committees notice when a strong team in the proposal is replaced after award, and some contracts restrict key personnel changes.

Hypothetical example: a federal service portal

Hypothetical example: a federal authority tenders a bilingual information portal with UAE PASS sign in for a small number of services. A strong response would map each page type to UAE Design System components, describe accessibility testing at the component and page level, explain the identity integration approach and list the security tests planned before launch. A weak response would focus on visual concepts and leave standards to a closing paragraph.

Common reasons bids are rejected

• Registration not completed or expired when the tender closed
• Commercial information included in the technical envelope
• Missing signed declarations or forms required by the tender pack
• Assumptions that quietly change the scope
• Late submission, often caused by portal upload issues on the last day

Most of these are administrative, which makes them preventable. Assign one person to own compliance with the submission format, separate from the people writing the content.

Working with Codeeo on public sector web projects

Codeeo has delivered 200+ projects across the UAE and the US, with a team of 80+ across Dubai, Riyadh and Karachi and an office in Dubai where clients can meet the team in person. For government and semi government work, the relevant services are website design and development, UI/UX design, custom software and business systems, mobile app development and Microsoft Dynamics 365 and CRM. If you are preparing a tender scope or reviewing an existing public facing site, a website audit can give you a clear starting point.

For related reading, see how to approach running a web agency RFP in the UAE, a weighted framework for scoring proposals, vendor onboarding requirements and capex and opex treatment for web projects. To discuss a project, contact the Codeeo team.