Services · Mobile app development · HR management apps

HR apps built around Saudi labour rules, government platforms and Arabic first staff.

HR management app development Saudi Arabia employers need has to start from the Kingdom's own rules: the Labour Law and its 2025 amendments, the Personal Data Protection Law, Saudisation under Nitaqat, and the government platforms HR teams use every day, from Qiwa and GOSI to Muqeem and Absher. We build core HR apps that hold the employee record, leave, contracts, documents and approvals, and roll them out to offices and branches in every region you operate.

The scope here is core HR. Attendance tracking, payroll and recruitment are separate services on this site, and the HR app is designed to be the master record those systems connect to rather than a replacement for them. Codeeo's Saudi work is led from Riyadh.

Built for
Employers with staff in several Saudi regions, foreign companies entering the Kingdom and groups consolidating HR systems.
Typical timeline
Planned after discovery, with each regional rollout wave and its review dates agreed in writing before the build begins.
What you own
All source code, app store accounts, the HR portal, hosting and employee data, held in your organisation's own accounts.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the app can include

National HR requirements turned into everyday features.

Every Saudi employer works within the same national framework, wherever its people sit. The Ministry of Human Resources and Social Development sets the Labour Law and runs Qiwa, GOSI handles social insurance, the Ministry of Interior's systems govern iqamas and travel for expatriates, and SDAIA oversees how personal data is handled. A company with a head office in Riyadh, a branch in Jeddah and a warehouse in Dammam faces these rules in every location, often with different managers interpreting them. The features below make those national requirements part of the app's logic, so a leave rule, a contract term or a data permission works the same way in Tabuk as it does in Riyadh. We prioritise them in discovery according to where your HR team currently loses the most time and where the compliance risk is highest.

Explain your project
  • Hijri and Gregorian dates throughout

    Iqama and some government dates are issued in Hijri, while contracts and payroll often run on the Gregorian calendar. The app stores both, shows each employee their preferred calendar and calculates expiries, probation ends and leave correctly in either system. Contract dates entered by HR can be checked against the employee's documents.

    No more manual date conversions on expiry lists.

  • Contract register aligned with the Labour Law

    Contract type, duration, probation, notice and renewal recorded for every employee. Non Saudi staff contracts follow the written, fixed term form the amended Labour Law requires, and HR is reminded to document each one in Qiwa.

    Contracts that match both your policy and the law.

  • Resignation and exit workflow

    Resignations submitted in the app start a timer reflecting the response period in the amended Labour Law, with reminders to HR and the manager. Exit tasks follow: handover, asset return, GOSI and Qiwa updates and the end of service data sent to payroll. Withdrawals within the permitted window are handled too.

    Resignations answered in time and exits completed cleanly.

  • Saudisation view

    A live picture of Saudi and non Saudi headcount by entity, region and job family, with planned hires and exits shown beside it. HR can see how a proposed change is likely to affect the Nitaqat position recorded in Qiwa before it happens. Figures come from your own records; the official classification remains the one Qiwa shows.

    Workforce decisions taken with Saudisation in view.

  • Nafath sign in where approved

    Where your organisation has approved access through an authorised channel, employees can sign in or confirm sensitive actions with Nafath. Otherwise the app uses your corporate single sign on with multi factor authentication.

    Strong identity checks that staff already recognise.

  • Expatriate document tracking

    Iqamas, passports, dependants' documents, exit and re entry visas and work permits tracked per employee, with tasks raised for HR to complete in Muqeem, Absher Business or Qiwa. The app stores outcomes and evidence, never government portal passwords. Dependants' documents carry their own alerts.

    Expatriate paperwork stays current across every region.

  • PDPL consent and data requests

    Employee privacy notices, consent records where consent is the lawful basis, and requests to access or correct personal data, each logged with a response deadline. Sensitive fields such as health or family details sit behind tighter access. Retention periods are set per record type, and expired records are flagged for archiving.

    Personal data handled the way the PDPL expects.

  • Regional structure and approvals

    Entities, regions, cities and branches modelled as a hierarchy, with approval routes that follow it. A branch manager in Abha approves locally, while policy exceptions go to the regional HR lead and then to head office. Temporary delegations are supported while managers travel.

    Approvals stay local without losing central control.

  • National holidays and leave rules

    Founding Day, National Day and the Eid holidays configured centrally, along with Hajj, maternity, marriage, bereavement and sick leave rules. The Friday and Saturday weekend is the default, with exceptions for teams that work different patterns. Changes made centrally apply to every branch at once.

    Leave balances that are right in every branch.

  • Employee self service app

    Requests for leave, letters, document updates and personal details in Arabic or English from any phone, with notifications for approvals and expiring documents. Staff in remote branches get the same service as head office. Requests can be tracked to completion by the employee.

    One standard of HR service across the country.

Who this is for

Organisations that need one HR app across the Kingdom.

A single city employer can often manage with a packaged HR tool. The case for a custom app grows when staff are spread across regions, when several entities share HR, or when a business is new to Saudi rules and needs them built in from the first day. These are the four national situations we design for most. Each one shapes what goes into the first release and how the rollout across regions is sequenced.

01

Retail and service chains with branches nationwide

Chains with stores or service points in Riyadh, the Makkah region, the Eastern Province and smaller cities such as Buraydah, Abha or Tabuk need branch managers to act locally while HR keeps one standard. The app gives every branch the same request flows, routes approvals through regional managers and shows head office which branches have open document or contract tasks. New branches are added by HR in the portal on the day they open.

Local approvals, one national standard.

02

Foreign companies entering Saudi Arabia

Businesses licensed by the Ministry of Investment and hiring their first Saudi team need HR processes that fit the Labour Law from the start, not adapted later from another country. We build the contract register, Saudisation view and expatriate document tracking first, alongside policies written for the Saudi entity, so the new company begins with clean records. Senior staff arriving from abroad get onboarding checklists covering iqama, dependants and local policies.

03

Groups consolidating several HR systems

After acquisitions or years of separate growth, many groups have one HR tool per company and no shared view. We map the data from each, agree a single employee model and migrate in waves, keeping entity level separation where the law or your structure needs it while giving group HR one place to work. Old systems are retired only after the migrated records are reconciled.

04

Employers preparing for growth under Vision 2030

Organisations scaling up for tourism, logistics, industry or entertainment projects often hire across several regions at once. They need an HR app that grows with them: new entities, new branches and new job families added through configuration rather than new code, with Saudisation tracked as hiring speeds up.

Growth handled by configuration, not rebuilds.

How a nationwide HR app moves from plan to rollout.

  1. 01National discoveryWe hold workshops at our Riyadh office and by video with regional HR leads, collecting policies, entity structures, forms and the regional differences that actually exist in practice.
  2. 02Compliance and data designLabour Law rules, PDPL data categories, NCA hosting requirements and Saudisation reporting are written into the data model and permission design before screens are drawn.
  3. 03Arabic first product designSelf service, manager and HR portal screens are designed in Arabic first, mirrored for English, and tested with employees from different regions and roles.
  4. 04Core build and integrationsRecords, contracts, leave and approvals are built first, then connections to payroll, attendance, ERP and identity systems, each shown in working demos.
  5. 05Pilot regionOne region or entity goes live first. HR compares results with the old process, and we fix what the pilot reveals before the wider rollout.
  6. 06Rollout in wavesRemaining regions follow in planned waves, each with migrated data, trained HR officers and recorded guides, then continuing support and improvements.

Technology

What we build this with.

Flutter or React Native for the employee app, React or Next.js for the HR portal and a Laravel or Node backend, hosted in a Saudi cloud region with the access controls your NCA obligations call for.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

03Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Common questions about HR app projects in the Kingdom.

We set the plan after discovery, usually as a pilot region followed by rollout waves.

The main drivers are the number of entities and regions, how different your regional practices are, the quality of existing employee data and the systems the app must connect to. A pilot region lets you go live sooner and learn before the full rollout. We agree the pilot scope, each wave and every review date in writing after discovery, before any design work begins. If a fixed date applies, such as the opening of a new region, we shape the pilot scope around it.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews