Saudi Contractors Authority
Project charter
Muqawil Platform — Release 4
1Project identity
Required at this stage- Project name
- Muqawil Platform — Release 4
- Project code
- PRJ-2026-014
- Project sponsor
- Eng. Majed S. Al-RasheedEng. Majed S. Al-RasheedHead, Digital Transformation SectorP-011m.alrasheed@sca.sa
- Project manager
- Eng. Sultan F. Al-GhamdiEng. Sultan F. Al-GhamdiProject Manager, Muqawil Platform — Release 4P-005s.alghamdi@sca.sa
- Project owner
- Badr N. Al-HaqbaniBadr N. Al-HaqbaniDirector General, Membership & Contractor ServicesP-046b.alhaqbani@sca.sa
- Portfolio & programme
- Digital Services & Platforms PortfolioMuqawil & e-Services Programme
- Type & methodology
- Digital · Hybrid
- Current phase
- 4Execution
2Background & rationale
Required at this stageThe Authority runs 68 e-services for contractors through five separate channels and legacy systems that do not talk to each other; a contractor deals with several departments and service centres for a single request, and issuing or renewing a membership takes 21 days on average. Release 4 of the Muqawil platform brings them into one digital journey that meets Digital Government Authority standards.
3Objectives
Required at this stage- 1Bring 68 contractor e-services into Muqawil with a single journey
- 2Cut the average time to issue or renew a membership from 21 days to 5
- 3Lift contractor satisfaction with digital services to 88%
- 4Reduce cost per transaction by 60%
4Scope
Required at this stageIn scope
- A unified Muqawil portal compliant with Digital Government Authority standards, including the membership-fee calculator
- Single sign-on through Nafath; notifying defendant agencies and receiving their replies through the Government Service Bus
- A configurable, no-code request workflow and forms engine
- Migration of memberships, open requests and contractor data from legacy systems
- Change management and training for 420 SCA and service-centre staff
Out of scope
- The mobile app (separate project PRJ-2026-015)
- Re-engineering procedures that would need changes to the Authority’s statute or its bylaws
- The Administrative Execution Platform (a separate project)
5High-level requirements
Required at this stage- 1Single sign-on through Nafath for contractors, company representatives and project owners
- 2Commercial-register, Balady and Etimad data pulled automatically through the Government Service Bus
- 3A request workflow and forms engine the business configures without code
- 4A unified company file with each request’s status, its certificates and membership, and instant notifications
- 5Full WCAG 2.1 AA accessibility
- 6Government-cloud hosting with NDMO data classification
6Deliverables
Required at this stage| 1 | Business requirements document | 2025-08-31 |
| 2 | UX prototype | 2025-09-15 |
| 3 | Solution & integration design | 2026-10-15 |
| 4 | Wave 1 service package (24 services) | 2026-09-30 |
| 5 | Nafath integration interfaces | 2026-10-31 |
| 6 | Government Service Bus integration interfaces | 2026-11-15 |
| 7 | Data migration plan | 2026-10-10 |
| 8 | Master test plan | 2026-06-30 |
7Key milestones
Required at this stage- Charter approved2025-01-05
- Build & run contract signed2025-04-30
- Advance payment (10%) released2025-05-25
- Requirements & design signed off2025-09-30
- Internal pilot (MVP) live2026-03-31
- Data classification approved by the data office2026-06-30
- Wave 1 development complete (24 services)2026-09-30
- Nafath & Government Service Bus integration complete2026-10-31
- Penetration test passed, security sign-off2026-12-15
- User acceptance testing complete2027-01-31
- Official launch of Release 42027-03-01
- Final acceptance & final payment2027-03-31
8Budget
Required at this stage- Build & run contract (incl. approved variation)59.0%51M
- Cloud hosting10.6%9.2M
- Identity & integration licences8.3%7.2M
- SCA internal team7.1%6.1M
- QA & project office support6.3%5.4M
- Change management & training3.6%3.1M
- Contingency reserve (5%)5.1%4.4M
9Timeline
Required at this stage10Key risks
Required at this stage- HighNafath and Government Service Bus interfaces late
- HighVendor integration engineers in short supply
- MediumLate requirement sign-off by the service-owning departments
- MediumMembership and service-centre staff resisting the digital procedures
- MediumCritical penetration-test findings
11Constraints
Required at this stage- Approved budget SAR 86.4M including VAT
- Hosting on the government cloud inside the Kingdom only
- Compliance with the ECC and the Personal Data Protection Law
12Assumptions
Required at this stage- Nafath and Government Service Bus test environments available as agreed
- Service-owning departments sign off requirements within 10 working days
- The vendor’s named team stays for the whole build
13Stakeholders
Required at this stage- Eng. Majed Al-RasheedHead of Digital Transformation — project sponsor
- Dr. Abdullah Al-QahtaniSecretary-General of the Authority
- Digital Government AuthorityRegulator
- National Information Center (Nafath)Integration partner
- Badr Al-HaqbaniMembership & Contractor Services — project owner
- Eng. Waleed Al-JuhaniFacilities O&M — owner of contractor service-centre readiness
- Membership and service-centre staffInternal users
- Member contractors and project ownersBeneficiaries
14Success criteria
Required at this stage- 168 e-services live on the platform at close
- 299.9% availability in the first six months
- 3Penetration test passed with no critical or high findings
- 470% of walk-in requests at HQ and the branches moved online within 12 months
15Governance structure
Required at this stage- Projects Steering CommitteeStrategic decisions, escalations, major gatesMonthly
- Change Control BoardApproves scope, cost and schedule changesWeekly
- PMO CommitteeMethodology compliance, data quality, stage gatesFortnightly
- Project management teamDay-to-day control, risks, impediments, the periodic update cardWeekly