Unified Government e-Services Platform
Remove from watchlistOne platform for 68 citizen e-services in a single journey — civil-status records, documents, building permits, local fees — checking identity against the civil registry and linking the ministries through the national interoperability framework.
Budget (BAC)
Actual cost
60% of budget
Progress
Estimate at completion
+SYP 90M
SPI · CPI
Forecast finish
42 days behind baseline
ExecutionStage 4 of 5
Next gate:Closure31 March 2027
- Pre-start · CompletePre-start · Complete
- Gate into «Initiation»DecisionGoDate22 September 2024Initiation · CompleteInitiation · Complete
- Gate into «Planning»DecisionConditional goDate5 January 2025Planning · CompletePlanning · Complete
- Gate into «Execution»DecisionConditional goDate27 April 2025Execution · Current stageExecution · Current stage
- Gate into «Closure»DecisionNot held yetDate31 March 2027Closure · Not startedClosure · Not started
Scope statementRequired at this stage
What the project delivers, what it does not, and when a deliverable counts as accepted.
The project delivers the unified government e-services platform: 68 government e-services — civil-status extracts, the «no criminal record» certificate, vehicle and property services, building permits, local fees and utility subscriptions — in a single citizen journey, with identity checked against the civil registry, ministry data through the national interoperability framework and fees by bank e-payment, and a no-code request workflow and forms engine; transaction records are migrated and 420 staff at the governorate citizen service centres trained, within SYP 2.16bn and an official launch targeted for March 2027.
In scope
- One government e-services platform in Arabic and English, meeting accessibility standards, with the service catalogue and a fee calculator
- Citizen identity checks against the civil registry, links to the ministries under the national interoperability framework, and bank e-payment
- A configurable, no-code request workflow and forms engine
- Migration of open requests and service records from the ministries’ current systems
- Change management and training for 420 staff of the citizen service centres in the governorates
Out of scope
- The mobile app (separate project PRJ-2026-015)
- Changing procedures that would need changes to the laws or regulations in force
- Automating the civil registry itself (separate project PRJ-2026-011)
Acceptance criteria
- Wave 1 service package24 services pass UAT at 98% with no critical defects
- Civil-registry & interoperability-framework interfacesProduction sign-off from the Ministry of Interior and the interoperability-framework operator
- Open-transaction migration100% record-count match, 99.5% on mandatory fields
- Platform at launchUnder 2 s for 95% of requests; 99.9% availability
- CybersecurityNo critical/high pen-test findings; national controls compliance certificate
Scope baselineRequired at this stage
Every approved change creates a new baseline
- 1
SB-1Superseded2025-02-16
First baseline with charter V3
BudgetSYP2.1BFinish2027-03-31 - 2
SB-2Current2026-02-24
Sign-in for legal agents and delegates added (+SYP 60M, +18 days absorbed)
BudgetSYP2.2B+2.9%Finish2027-03-31CR-2026-001 - 3
SB-3Proposed2026-10-29
Proposed: civil-record transfer & merge (+SYP 46.25M, +21 days)
BudgetSYP2.2B+5.1%Finish2027-04-21CR-2026-004
Requirements registerRequired at this stage
25 requirements of five kinds, with the trace status of each
By type
- Business4
- Functional7
- Technical6
- Regulatory4
- Security4
Fully traced
92%
23/25 · linked to a deliverable, task and test
Test passed
28%
7/25 · test result is a pass
Accepted
28%
7/25 · signed off by the business owner
Display options
| REQ-001 | One citizen journey for every e-service from a single account | Business | Must | Approved | Basel Al-MahayniBasel Al-MahayniDirector General, Digital Government Services & Portfolio Manager, Digital Government Services & DataP-003basel.almahayni@psa.gov.sy | SB-1 | |
| REQ-002 | Cut transactions that need checking from 21 days to 5 | Business | Must | Approved | Basel Al-MahayniBasel Al-MahayniDirector General, Digital Government Services & Portfolio Manager, Digital Government Services & DataP-003basel.almahayni@psa.gov.sy | SB-1 | |
| REQ-003 | A citizen account with each transaction’s status, issued documents and notifications | Business | Should | Approved | Hiba Al-ShamiHiba Al-ShamiSenior Business Analyst — Government ServicesP-006hiba.alshami@psa.gov.sy | SB-1 | |
| REQ-004 | Citizen identity checked against the civil registry at sign-in | Functional | Must | In progress | Hamza Al-HusseinHamza Al-HusseinSenior Software Engineer – IntegrationP-030hamza.alhussein@psa.gov.sy | SB-1 | |
| REQ-005 | Legal agents and delegates sign in, with a power-of-attorney check | Functional | Must | In progress | Hamza Al-HusseinHamza Al-HusseinSenior Software Engineer – IntegrationP-030hamza.alhussein@psa.gov.sy | SB-2 | |
| REQ-006 | Pull ministry data through the national interoperability framework | Functional | Must | In progress | Hamza Al-HusseinHamza Al-HusseinSenior Software Engineer – IntegrationP-030hamza.alhussein@psa.gov.sy | SB-1 | |
| REQ-007 | A request forms engine the business configures without code | Functional | Must | Completed | Hiba Al-ShamiHiba Al-ShamiSenior Business Analyst — Government ServicesP-006hiba.alshami@psa.gov.sy | SB-1 | |
| REQ-008 | A transaction workflow with action time limits and auto-escalation | Functional | Must | Completed | Hiba Al-ShamiHiba Al-ShamiSenior Business Analyst — Government ServicesP-006hiba.alshami@psa.gov.sy | SB-1 | |
| REQ-009 | Citizen data refreshed from the civil registry within one working day, source recorded | Functional | Should | In progress | Dr. Firas Al-ObaidDr. Firas Al-ObaidDeputy President, StatisticsP-016firas.alobaid@psa.gov.sy | SB-1 | |
| REQ-010 | A chat assistant for citizens’ frequent questions | Functional | Could | Deferred | Hiba Al-ShamiHiba Al-ShamiSenior Business Analyst — Government ServicesP-006hiba.alshami@psa.gov.sy | — |
Traceability matrixRequired at this stage
Requirement → deliverable → task → test → acceptance. 2 requirements have a gap.