Effective Government

1. Executive Summary

This chapter begins with the question left by “The Rule of Law and Institutional Justice”. It has been established that the state is the enduring framework of public authority, sovereignty determines the ultimate decision-making authority, and law subjects that authority itself to rules and review. Yet this architecture does not produce a national renewal merely by existing. A decision may be lawful, a budget available and a plan announced, while the outcome stalls between allocation and expenditure, ministry, agency and governorate, signature and contractor, or application and service. Here lies the function of effective government: turning legal and political capacity into everyday implementation capability.¹

The adopted operational definition describes effective government as an executive system capable of turning policies, resources and laws into dependable, measurable public outcomes through clear responsibilities, a professional civil service, workable procedures, timely data reaching an official empowered to correct problems, and periodic review under the law. This definition distinguishes effectiveness from efficiency: effectiveness asks whether the public objective was actually achieved; efficiency asks how much time, cost and resources it required. An administration may efficiently perform an activity that changes no outcome, or achieve an important outcome at an unsustainable cost. The requirement is to combine both, not substitute one for the other.²

Iraq's baseline does not justify describing the entire administration as a failure. Earlier chapters established that Iraq is a functioning state with uneven capacities. The 2024 general census demonstrated the possibility of mobilising substantial national capacity when leadership, coordination, resources and data are available. Conversely, the Ministry of Planning announced 2,612 stalled projects in 2024. This is important as a stock of implementation gaps, not a “national failure rate”, because the total project denominator was not established in the same source. A government reform programme conducted with international partners also demonstrated that dozens of service processes could be re-engineered in Iraq, showing that bottlenecks can be changed when responsibility and procedures are redesigned rather than another administrative layer added.³

The greatest data problem in this chapter is that the indicators needed to assess implementation are not published nationally under standard definitions: service completion time, first-attempt completion, administrative burdens on citizens and businesses, satisfaction among users of a particular service, projects completed on time and within budget, and coverage of genuinely end-to-end digital services. The evidence file itself records inconsistencies among published or circulating digital-service percentages and between the definitions of an “available service” and an “end-to-end service”. The Vision therefore does not turn these figures into firm facts; it begins in 2027 by establishing a national administrative baseline before fixing precise numerical targets.⁴

The solution is not a new “Ministry of Efficiency”. The Vision proposes building specific functions within existing structures: an outcome owner for each major priority; a performance system linking inputs and activities to outputs and outcomes; a delivery function at the centre of government that monitors a limited set of priorities and identifies deviations early without implementing in place of ministries; a national programme to re-engineer services before digitising them; workforce and skills planning instead of sweeping judgments about employee numbers; a unified major-project portfolio; and a data system that makes measurement part of decision-making rather than a retrospective report.

The pathway to 2045 has four phases. From 2027 to 2030, the implementation gap becomes visible and measurable through baselines, service standards, outcome owners, the first redesigned service package and an initial performance dashboard. From 2031 to 2035, an “integrated government machine” links plans, budgets, projects and outcomes while expanding professional administration and interoperability. From 2036 to 2040, the focus shifts from establishing systems to productivity, quality and user experience. The goal for 2041–2045 is stable, outcome-oriented government above individuals, preserving institutional memory, standards and services through changes of ministers and governments.

2. From Authority Constrained by Law to Government Capable of Delivery

The preceding chapter concludes with a simple but consequential principle: state power becomes legitimate when it can apply the law to others and accepts its application to itself. This chapter does not rebuild the rule of law; it treats it as a permanent design constraint. Faster administration must not override the right to seek redress; a stalled project must not be addressed by violating jurisdictional rules; and digitisation does not entitle a system to collect unnecessary data. Government effectiveness here is constrained capability: lawful speed, reviewable efficiency and decisions that injured parties can challenge under the law.

The Constitution grants the executive broad powers to manage and implement public policy, prepare the budget and make regulatory decisions within its jurisdiction. Yet legal authority is not implementation capacity. Between them lies a chain of organisation, financing, resources, contracting, monitoring and coordination. The longer this chain becomes without a clear owner, data or an escalation route, the greater the likelihood that government will produce documents rather than outcomes.⁵

This chapter therefore measures neither “government strength” by the size of its apparatus nor “activity” by the number of decisions it issues. A large government may be slow, a small one incapable, and an active one may produce hundreds of initiatives without resolving a single problem. The measure is the institution's ability to move from a legitimate political intention to a sustained public outcome, and then determine whether the outcome justifies its cost and needs correction.

3. An Operational Definition of Effective Government and the Implementation Gap

In Iraq Vision 2045, effective government is the executive apparatus that turns policy, law and budgets into dependable, measurable public outcomes through defined responsibility, a professional civil service, clear procedures, executable financing, regular data, review and correction, while keeping decisions and procedures subject to law and rights. Under this definition, it is not enough for “the ministry to complete what was asked of it”. The request itself must be linked to a public outcome, and the cost, time and quality involved must be known.

The implementation gap is the difference between what the state decides, plans or funds and the outcome actually experienced by a citizen, project or economy. It may begin before implementation, when a priority is unclear or a project unready; emerge during implementation through delayed financing, conflicting jurisdictions, weak contracts or changed decisions; or appear after completion, when a building is finished but not operational, a platform launched but unused, or a transaction formally closed while the beneficiary still needs another visit.

Source: Evidence File V1-D02-C04; definitions edited to distinguish effectiveness, efficiency, activity and outcomes.

4. The Iraqi Baseline: Existing Capacity and an Insufficiently Measured Implementation Gap

The diagnosis must avoid two extremes: claiming that Iraqi administration is inherently incapable, and claiming that ministries, plans and platforms are enough to prove effectiveness. The project's internal evidence supports a more precise description: uneven capacities. The state can mobilise resources and undertake major national tasks in certain conditions, but it does not yet have a unified system making success repeatable from one ministry to another and one government to the next. The question is therefore not “Does capacity exist?” but “Has capacity become a system?”

The 2024 general census offers an important success case: a nationwide logistical and information operation requiring leadership, federal and local coordination, human and technical resources, a timetable and a database, producing a result usable for planning. Its analytical value lies not in the census itself but in its components: a defined objective, a clear owner, political priority, financing, protocols, training and data flows. These are the conditions that must become a repeatable way of working rather than an “exceptional case”.

Conversely, the stock of stalled projects is a direct warning. The official figure used in “The State First” — 2,612 stalled projects in 2024, with 997 addressed or moved forward under the Ministry of Planning's definition — does not permit calculation of a national stalling rate. It does establish, however, that the state carries a large stock of decisions and allocations yet to become functioning assets. This requires distinguishing causes of delay: readiness, land, design, financing, contracts, contractors, change orders, disputes or management, rather than automatically reducing them all to corruption.

The service baseline is even less complete. The evidence file reports conflicting numbers for digital services and their electronic completion rates, describing some as low-confidence or differently defined. The final version therefore adopts a clear decision: do not use “services published” or “accounts created” as outcome measures, and do not adopt a national end-to-end percentage before inventorying and defining services. An operational service baseline begins when we know the number of steps, documents and visits, processing time, user costs and first-attempt completion rate; we then measure what changes after reform.

Source: Evidence File V1-D02-C04 and the data-decision register; “The State First” chapter for the stalled-project figure. Conflicting or low-confidence values have not been turned into firm facts.

4.1 Four Types of Implementation Gap That Must Not Be Confused

Government does not stall in the same way every time. The first gap is a decision gap: an undefined objective, or one conflicting with others, leaves implementers unsure of the priority. The second is a design gap: a policy may be sound in direction but lack a clear legal, financial and operational route. The third is a delivery gap: the design exists, but financing, contracts, coordination or skills obstruct implementation. The fourth is a learning gap: the cycle ends without measurement or institutional memory, and the same problem recurs in a new programme for the same reason. Separating these types prevents every problem from receiving the same remedy.

The distinction matters because a “stalled project”, for example, may result from changing decisions, unresolved land issues, intermittent financing, a weak contract or poor site management. A “slow service” may reflect a legally required step, internal instructions, a staffing shortage at one point, a malfunctioning information system or fear of making decisions. Each diagnosis requires a different source and owner. The Vision therefore precedes solutions with two questions: where did the chain break, and is the problem in the rule or its implementation?

A fifth gap cutting across all four types is the data gap. When government does not know service times, unit costs, reasons for delay or project age, discussion rests on impressions. Collecting data alone, however, does not resolve obstruction; information must be linked to a warning threshold and an official able to intervene. “Visibility of implementation” is therefore an institutional objective in the first phase, not a peripheral statistical activity.

Table 2-A: Classifying the Implementation Gap Before Selecting a Remedy

Source: Iraq Vision 2045 analysis, drawing on Evidence File V1-D02-C04 and the “law or implementation?” principle in Chapter V1-D01-C03.

5. A State That Delivers, Not Merely Announces: The Government Implementation Chain

Political announcements are necessary to set direction, but they are not an implementation stage. Every priority must pass through a traceable chain, and it must be possible to identify the link at which deviation occurred. Without a clear legal basis, a decision may stop at the first challenge. Without an outcome owner, responsibility disperses until it disappears. Without financing or readiness, a programme becomes a promise. Without measurement data, a project may continue for years before the problem reaches decision-makers.

The Vision adopts an eleven-part implementation chain: decision or priority → legal basis and jurisdiction → outcome owner → financing and budget link → implementation plan and milestones → resources, contracting and readiness → actual implementation → measurement against baseline → accountability and review → corrective action → institutional memory preserving what the state has learned. Not every policy requires the same format, but every outcome requires equivalent logic: who owns it, how it is financed, how deviation is identified, and who can correct it.

Source: Editorial reconstruction of the implementation chain in Evidence File V1-D02-C04, incorporating financing, readiness, correction and institutional memory.

6. The Outcome Owner: Who Is Politically Responsible, and Who Implements Institutionally?

Unclear responsibility is among the costliest sources of obstruction. A ministry may own policy, a governorate local implementation, the Ministry of Finance funding, the Ministry of Planning monitoring, and another body data or land. If an outcome is framed as “the responsibility of all bodies”, the centre of government will not know whom to hold accountable when it is late. Every major outcome therefore requires one ultimately accountable owner, alongside clearly identified implementers, partners and advisers.

The chapter distinguishes four levels. Political responsibility rests with the minister or political leadership for the priority and outcome before the Council of Ministers, the public and oversight authorities within the constitutional system. Institutional responsibility rests with the ministry or agency holding the mandate and resources. Implementation responsibility rests with the programme or manager handling daily work. Partners supply necessary inputs without owning the entire outcome. A simplified RACI logic may be used: Responsible for execution, Accountable for the outcome, Consulted and Informed. The Vision does not, however, turn this tool into another reporting layer.

In interministerial programmes, an outcome owner does not eliminate specialisation. A designated committee chair or lead minister may be responsible for the shared outcome, while each ministry remains responsible for its own output. The committee must have a duration, task and closure milestones. A committee with no decision authority, deadline or output becomes a destination for transferred responsibility rather than a means of resolving the problem.

Source: Evidence File V1-D02-C04; simplified RACI adapted to a national vision, not a detailed project-management manual.

7. Measuring Ministry Performance: From Inputs to Impact

Measuring government performance means linking what a ministry consumes to what it produces and what subsequently changes, rather than merely counting its actions. Measurement begins with inputs: money, personnel, assets and data. Then come activities: campaigns, contracts, visits and transactions. Outputs follow: a road opened, a licence issued, a service delivered. Outcomes include shorter journeys, fewer outages, better access or a more orderly market. Finally, impact means long-term changes in productivity, health, safety or opportunity. A ministry should not be held solely responsible for an impact beyond its control, but neither should it hide behind activities it can multiply without producing outcomes.

Each ministry has a limited set of strategic outcomes, and each outcome has a clearly defined indicator, baseline, target, data owner, outcome owner and measurement frequency. This is accompanied by a “performance narrative”: why did the indicator deviate? Was the cause financing, higher-than-expected demand, legislative delay, a skills shortage or a mistaken assumption? What corrective action follows, who owns it and when will it close? This turns a dashboard from a display screen into a mechanism of governance.

A uniform dashboard must not be imposed mechanically on every ministry. Transaction time may be central to a licensing ministry, but not the most important measure for a ministry managing long-term policy. Some bodies are measured by infrastructure reliability, others by coverage, safety, data accuracy or timeliness. The requirement is a common model of logic, not identical substantive indicators.

Source: Evidence File V1-D02-C04; the inputs–activities–outputs–outcomes–impact principle, with quality and equity added as constraints on interpretation.

Indicator design itself needs safeguards against gaming. A body may select an easy indicator, reject difficult cases to improve completion rates, close complaints administratively without resolving them, or pressure frontline staff to meet short time targets at the expense of accuracy. Balanced indicators, independent sample checks, user-experience measurement, definition reviews and avoidance of rewards tied to a single manipulable indicator are therefore necessary. The stronger the performance incentives, the greater the need to verify data quality.

7.1 The Performance Review Cycle: Measurement Must End in a Decision

A performance system fails when it operates only once a year. Priorities need an appropriate rhythm: monthly or quarterly monitoring for critical programmes and projects, and annual review for broader outcomes. This does not mean continuous meetings. A good meeting answers only four questions: what is the outcome, what is the deviation, what explanation is supported by data, and what corrective decision follows, with an owner and closure date? If review changes neither resources, plans, procedures nor the problem definition, monitoring becomes administration without impact.

“Exception reports” replace lengthy reports. The centre of government does not need every project detail, but cases that exceed agreed limits or require decisions beyond the implementation team's authority. This reduces ministry burdens and prevents the centre of government from becoming a day-to-day manager. Stable performance within limits remains the body's responsibility, subject to audit where necessary.

At each year's end, the indicators themselves are reviewed. An indicator may prove no longer valid, or its definition may encourage undesirable behaviour. Changing it must not conceal failure; a documented decision must explain the amendment and preserve the historical series as far as possible. This matters because a government measuring performance over twenty years needs comparability, not numbers whose meaning changes every cycle.

Table 5-A: The Performance Review Cycle from Figure to Action

Source: Evidence File V1-D02-C04; exception reporting, periodic review and closure of corrective actions are central elements of the delivery function.

7.2 How Do We Prevent Managing the Numbers from Undermining Performance?

Every indicator creates an incentive, which may change behaviour in an unintended direction. A hospital rewarded only for waiting times may reclassify cases. An office rewarded for transaction counts may divide a service into more transactions. A project rewarded for physical completion may postpone commissioning tests. Outcomes must therefore not be measured with one indicator: time is paired with quality, quantity with outcomes, satisfaction with objective verification, and expenditure with actual delivery.

Safeguards include defining indicators before the period begins; publishing their owners and data producers; preventing bodies that benefit directly from a number from being the sole source of verification for high-risk indicators; using audit samples; retaining difficult cases rather than excluding them; and monitoring counter-indicators that reveal side effects. The aim is not to suspect every employee, but to design a system that recognises people respond to what is measured.

8. Performance and the Budget: No Outcomes Without Financing, No Meaningful Spending Without Outputs

This chapter does not address macro-fiscal policy, but an implementation issue: a ministry cannot be assessed if objectives are detached from programmes, programmes from budgets, and expenditure from outputs. Decision-makers must know which programme funds which outcome, what will stop if financing is delayed, and what has actually been achieved for the money spent. Expenditure rates alone may penalise a prudent body or reward one that spent quickly on an unready project.

Linkage requires three levels. First, coding programmes, projects and services so they can be connected to funding items. Second, fixing expected outputs and annual milestones rather than merely an “expenditure heading”. Third, reviewing performance and spending together in one cycle involving the implementing body and the planning and finance authorities. This does not mean the Ministry of Finance manages the project or the Ministry of Planning replaces the outcome owner. It means financing and adjustment decisions use one shared picture of time, cost and outcomes.

Programme and performance budgeting and spending reviews can support this transformation when used as linking tools rather than slogans. Implementation begins with measurable priorities and programmes, rather than attempting to convert the entire budget at once. As data mature, discussion can move from “How much was spent?” to “What service, asset or outcome did this expenditure purchase, and was this the best route?”

9. Reducing Administrative Obstruction: Protecting What Is Necessary and Removing What Adds No Value

Professional bureaucracy is not the problem; it is one of the modern state's tools for consistent treatment, record-keeping, separating public and private money, and subjecting decisions to rules. The problem is administrative burden that adds no protection, quality or accountability proportionate to the time and cost it imposes. Environmental approval or financial auditing may be necessary, whereas requesting a paper copy of information already held by government, or a third signature adding no real review, may be unnecessary friction.

Recurring sources of obstruction include sequential approvals, duplicate documents, unclear jurisdiction, overlapping bodies, no time limit, unnecessary personal attendance, requirements varying by employee, conflicting laws or instructions, fear of making decisions, centralisation of details that could be delegated, and disconnected data. Projects may also face financing or contracting delays. There is therefore no “single anti-bureaucracy law”: each process needs a map showing where costs arise and why.

Source: Evidence File V1-D02-C04 and the administrative-burden concept in the comparative literature used by the file.

10. Process Re-engineering: The Service as the Unit of Reform

Administrative reform becomes tangible when it selects a real service and maps its current “as-is” state: where does the user begin, how many documents are submitted, how many bodies handle the transaction, where does it wait, who rejects it and why? The desired “to-be” state is then mapped and steps adding no value removed. Only then is the process digitised. This is more effective than launching a general platform and asking every ministry to transfer its old procedures onto it.

The Vision measures each selected service using six initial indicators: number of steps, documents and visits; processing time; user cost; and first-time completion rate. Reasons for rejection and complaints closed with an actual solution are added. Reducing time is insufficient if rejection rates rise or users must make another visit outside the system. Nor is it enough to transfer the visit to a private intermediary whom citizens must pay.

Tools are used where appropriate: a unified form instead of several forms, a one-stop shop instead of users moving between agencies, a published time limit, tracking code, specific rejection reasons and a redress route. Tacit approval may be used only for low-risk services where permitted by law and where silence creates no risk to safety or others' rights. For high-risk services, explicit review remains part of quality; reform makes it faster and clearer rather than deleting it.

Some services can be organised around a “life event” rather than the organisational chart. A new birth, business formation, moving home or retirement may involve several bodies; from the citizen's perspective, it is one event. This does not remove ministries' jurisdictions, but requires government to design an interface and process that do not leave users managing intergovernmental coordination themselves.

The most useful Iraqi evidence here is the re-engineering of 99 service processes through government-performance improvement programmes documented in the evidence file. The Vision does not use this figure to claim comprehensive success, but to demonstrate that process mapping and redesign can work within actual Iraqi institutions. The task is to turn this approach from a funded or limited project into an enduring institutional capability within government.⁶

10.1 Service Standards, User Experience and Complaints

A service standard is an operational compact explaining what users are entitled to expect from administration: eligibility, necessary documents, normal processing time, fees, reasons for rejection and routes for redress. It does not mean every transaction is identical or that exceeding a deadline creates a right absent from law. It makes exceptions visible and reasoned, and prevents requirements from varying between employees.

User experience is not a cosmetic satisfaction survey. A user may be dissatisfied because a decision went against them even though the procedure was fair. The survey therefore measures manageable elements: clear information, ease of access, visits, understanding of steps, respectful treatment, tracking, waiting times, clarity of rejection reasons and complaint effectiveness. These data help locate friction invisible in transaction systems.

Complaints themselves are a data resource. Counting them is insufficient because an increase may indicate poor service or greater trust in the complaints channel. They must be classified by service and cause, with response time, resolved-closure rates and recurrence analysed. Repeated complaints about one document may be the strongest evidence that a procedure needs redesign. Complaints thereby become a government-learning loop rather than merely “public correspondence”.

Table 6-A: The Service-Standard Card Users Should See

Source: Iraq Vision 2045 editorial formulation, drawing on Evidence File V1-D02-C04 and gaps in service time, user experience and complaints.

10.2 The 2027 Service Baseline: Inventory Before Targets

Government cannot reform what it has not mapped consistently. The first task in 2027–2030 is not announcing a national service-time figure, but inventorying the highest-impact services and transactions: provider, recipient, legal basis, documents, fees, steps, duration and current channel. The inventory distinguishes an actual service to citizens or businesses from an internal procedure between government units, because mixing them inflates numbers without revealing the burden on users.

For each selected service, the starting position must reflect reality rather than the administrative manual's assumptions: actual visits, documents requested by staff, waiting and processing times, applications returned for missing items, rejection reasons, trackable transactions and available service channels. Differences between branches or governorates are recorded rather than merged into an artificial average. This is the starting point for defensible future targets.

The 2027 inventory divides services into three packages. The first covers frequently used services or those strongly affecting daily life, to reduce burdens quickly. The second covers services affecting investment and economic activity, to reduce uncertainty and cost. The third covers services with high legal, financial or safety risks, where clarity and time must improve without curtailing necessary oversight. Selecting a first package does not make the remaining services less important; redesign capacity is limited and must be built before expansion.

After the measurement year, each body publishes a “service card”, a standard definition of its duration and the calculation method. This prevents comparison of numbers that mean different things: one body may count from application entry, another from completion of documentation, and a third may exclude time awaiting another body's opinion. The Vision's rule is that an indicator does not become national until its definition, source and comparison limits are established.

Table 6-B: Minimum Requirements for the Service Inventory and 2027 Baseline

Source: The 2027 Baseline Development Programme in Evidence File V1-D02-C04; numerical values are established by measurement, not assumed in advance.

11. A Professional Civil Service: The Machinery of Government Continuity

An elected government has the right to set policy within the Constitution, while the professional administrative apparatus preserves knowledge, files and standards and turns policy into sustained work. This chapter therefore treats the civil service not as a payroll or headcount issue, but as the machinery of continuity. A change of minister should not reset a ministry to zero, nor should professional neutrality become resistance to a legitimate government programme.

Professionalism begins with merit-based recruitment and selection for positions that should be professional, alongside clear identification of political or leadership positions defined by the legal system. Modern job descriptions follow: what are the responsibility, output, authority and skills? Without descriptions, workforce planning, performance assessment and identification of surplus in one function and shortages in another are impossible. The Vision therefore rejects blanket claims that Iraq “has too many employees” or “needs more employees” before mapping the workforce by specialisation, location and function.

Middle management is the layer most important for continuity: it translates ministerial instructions into programmes, supervises staff and preserves memory across political cycles. It needs career pathways, training tied to real gaps, project, data and service-management skills, protection from politicisation of professional work, and accountability for poor performance or illegality. Training is not measured by course counts, but by whether performance changes, errors decline or unit capability improves.

Employee assessment must draw on multiple sources and not automatically hinge on one number. Some roles are assessed by time and accuracy, others by standards compliance, quality of analysis or soundness of decisions. Employees must know expectations and have the right to challenge unfair assessments. The system also needs a route for managing underperformance: support, training and improvement plans, followed by fair administrative measures if deficiencies persist. Protecting professional employees does not immunise them from accountability; accountability does not mean turning assessment into a political tool.

Source: Evidence File V1-D02-C04; analysis of patronage and recruitment corruption as a system is left to the next chapter.

11.1 Workforce Planning and Middle Management

Workforce planning starts with functions, not total headcount. Each body maps its services and programmes, deriving the skills, positions and locations it needs. An institution may have excess staff in paper-processing roles and acute shortages in data analysis, contract management or maintenance. Reducing total numbers without this map may remove scarce skills while preserving bottlenecks. Expanding numbers without defined functions and outputs likewise reproduces overcrowding.

Government needs a “critical positions register”: roles on which continuity of a service, project, record or decision depends, accompanied by succession plans and documented knowledge. One employee's departure should not take a password, process or knowledge of a long-term contract with them. Institutional memory is part of capacity, built through documentation, teamwork, considered rotation and succession planning, not by making institutions dependent on irreplaceable individuals.

Middle management requires a distinction between political and professional leadership. Ministers set policy and bear political responsibility; directors-general and professional leaders manage implementation under the law and provide truthful information even when uncomfortable. If the professional layer merely repeats what superiors want to hear, government loses its internal warning system. If it becomes a centre of resistance to elected policy, government loses its right to govern. The balance is professional neutrality with clear implementation responsibility.

Table 7-A: Workforce-Planning Questions Before Increasing or Reducing Staff

Source: Evidence File V1-D02-C04; the chapter's conclusion is that workforce imbalances differ across institutions, specialisations and areas and cannot be reduced to one national number.

12. Digital Government: From Digitising the Interface to Redesigning Government

The Vision uses four clearly bounded concepts. Digitisation converts paper material into digital form. E-government enables users to perform part of a procedure electronically. Digital government redesigns procedures, data and interactions so services work across institutions. Digital transformation changes working methods, decisions, skills and governance, not merely the interface. Confusing them makes electronic-form counts look like progress even if citizens still print the forms and take them to an office.

Effective government uses a service-maturity model. Level one provides clear online information. Level two permits electronic applications. Level three is hybrid, with part of a transaction starting digitally and continuing on paper. Level four is end-to-end completion from application to outcome and payment or notification without unnecessary attendance. Level five integrates services across institutions, reusing permitted government data. Level six is proactive, where law and data allow the state to initiate an entitlement or notification without repeated applications. Not every service must reach level six; the criteria are suitability, rights and risk.

Source: Evidence File V1-D02-C04; the model is edited from e-government, digital government, end-to-end service and interoperability concepts.

Digital success is measured by changes in service experience: less time, fewer visits and documents, higher completion, clear tracking and fewer errors. Registered-account counts are insufficient; citizens may register without using the service. Portal service counts are also insufficient; some entries may merely be links or forms. The digital-government dashboard therefore publishes maturity levels for each service, not a vague aggregate number.

The route must not be digital-only. A practical alternative is required for people unable to use the internet, alongside accessible interfaces for persons with disabilities, service-continuity plans for outages, privacy protection, minimum necessary data, audit trails and human review of important automated decisions. Digitisation here is an administrative and service function; national computing infrastructure, digital sovereignty and strategic cybersecurity belong in their specialised parts.

13. Interoperability and Data: The Right Information in the Decision-Maker's Hands

Interoperability does not mean opening every state database to every body. It means data definitions, authoritative registers, access permissions and exchange mechanisms enabling competent bodies to obtain necessary information from trusted sources, while recording who accessed it and why. The simple administrative question is: why does one government body ask citizens for a document another government body already holds? When the answer is “the systems are not connected”, a technical problem becomes a daily burden and transaction cost.

The “once-only” principle aims for individuals or businesses to provide information once to the competent body, after which it can be lawfully reused when another service needs it. It is not blanket permission to collect or circulate data. The authoritative register, owner, purpose, accuracy, retention period, access rules, audit trail and correction mechanism must be specified. An error in an authoritative register can spread across multiple services; data quality is therefore an implementation responsibility, not a secondary technical issue.

Data do not improve administration merely by existing. Administration improves when the right information reaches an official empowered to correct problems at the right time. Some indicators need daily updates, others monthly or quarterly. Every key indicator has a data owner, source, definition, update date and rule for missing values. When a project or service deviates from its standard, an alert and escalation policy activates rather than waiting for the annual report.

13.1 Data Governance and Quality: From a Dashboard Number to Decision Evidence

Every operational dataset needs governance: what is the authoritative source, who may amend records, who may read them, and what minimum quality is required before use in a decision? An error in contact data may inconvenience one user, but an error in an authoritative property, identity or entitlement register may block several services. The pursuit of interoperability must therefore not produce unsynchronised database copies in every body. The original remains a known reference, accessed through exchange when needed.

Data quality is measured through completeness, accuracy, timeliness, consistency and traceability. A complete but outdated value may be worse than a partial current one, and two sources using different definitions do not produce a valid average. This principle applies particularly to performance indicators: changes in the definition of “completed project” or “electronic service” must be recorded, not merged across years as though their meaning were unchanged.

The government dashboard does not display everything measurable. Leadership needs a few indicators linked to decisions; detail remains with ministries. Every alert must have a workflow: who reviews it, who validates the explanation and who can change the plan? A dashboard without a decision pathway may increase anxiety and centralisation without improving implementation.

Table 8-A: Data Quality Gates Before Use in Performance Assessment

Source: Evidence File V1-D02-C04, interoperability and data-management section, converted into applicable quality gates.

13.2 Continuity and Digital Inclusion: Services Must Survive Channel Failure

Real digital transformation increases government dependence on systems, connectivity and data, so service continuity must be built alongside it, not afterwards. A critical service needs a defined response to system failure: is an alternative channel available, what data are retained locally, who declares the outage, how are applications in progress recovered, and what is the maximum acceptable interruption? This chapter does not address cybersecurity engineering; it establishes continuity as an administrative condition of service quality.

Digitisation must also not become a new condition denying a right or service to those unable to use digital channels. Some users lack reliable connectivity, skills or a suitable device; some services require assistance because of disability, language or case complexity. “Digital by default” is therefore an organisational objective where appropriate, not “digital only”. An alternative may be an assistance centre or service window using the same system on the user's behalf, avoiding a completely parallel paper process.

Privacy is also a design constraint. “Once-only” does not mean every employee can see all a citizen's data; it means necessary data move on a legal basis under defined permissions, with an audit trail showing access and amendment. As administrative decisions become more automated, their reasons must remain explainable and important decisions affecting rights or obligations must permit human review. Technology reduces repetitive work, but does not transfer legal responsibility from the institution to the algorithm.

Digital-channel quality is measured by its ability to complete services, not registered-account counts. Government therefore monitors application starts and completions, abandonment points, outages, assistance needs and differences across groups and areas. If overall completion improves while a vulnerable group's gap widens, the improvement remains incomplete and requires alternative design or additional support.

Table 8-B: Operational Safeguards for Digital Government Services

Source: Digital and rights safeguards recorded in Evidence File V1-D02-C04; technical security and digital-infrastructure details are deferred to their specialised parts.

14. Public Project Management and Interministerial Coordination

A government project is a demanding test of state effectiveness because it combines planning, financing, land, design, contracting, supervision and operation in one chain. Before tendering, there must be a clear priority, proportionate feasibility assessment, readiness of land, designs, licences and financing, and a timetable and risk plan. Launching before readiness transfers the problem to the contractor or site, after which delay becomes a “surprise” despite having been foreseeable from the outset.

The Vision adopts this project chain: priority → feasibility and readiness → financing → design → contracting → implementation → control of time, cost and quality → handover → operation → benefit measurement. The major-project portfolio needs a unified register showing status, cause, amount and time, not just completion percentage. Change orders, disputes and suspension decisions must be recorded with their effects, enabling the state to learn from patterns of deviation rather than treating every project as a separate story.

Interministerial coordination is not a call for centralisation. The centre of government defines shared priorities, resolves disputes bodies cannot resolve themselves and sees the consolidated picture; ministries retain implementation ownership within their mandates. Joint committees are useful with a defined task, owner, output and deadline, but become burdens when they add another approval or assemble representatives lacking decision authority.

Source: Evidence File V1-D02-C04; no stalled case is attributed to corruption without evidence, and analysis of contract corruption as a system is left to the next chapter.

14.1 Implementation in a Federal State and Governorates Not Incorporated into a Region

A shared outcome does not imply centralised implementation. Some services are delivered federally, others locally, and others require federal funding or standards with governorate-level implementation. The system must identify which level holds authority, resources and data, and how outcomes are measured without federal monitoring becoming detailed management of a governorate or decentralisation erasing national standards where law requires them.

Shared programmes may use an “outcome agreement” or implementation agreement specifying outputs, financing, standards, data and each level's responsibilities. The chapter assumes no uniform legal form across all sectors; Iraqi federalism allocates powers differently by subject. Yet implementation machinery needs one language: who funds, implements, owns and operates the asset, produces data, and resolves disputes when responsibilities overlap?

Measurement must reveal geographic differences rather than hide them in a national average. Average service time may improve because Baghdad or a governorate centre improves while remote districts remain behind. Coverage and geographic equity are therefore added to performance indicators. Data direct additional capacity or redesign, rather than condemn an area or its employees without understanding their constraints.

Table 9-A: Federal–Local Coordination Questions in a Government Programme

Source: Government coordination principles in Evidence File V1-D02-C04; the distribution of federal powers is not reconsidered in detail here.

14.2 From Construction Handover to Operation and Benefit Measurement

One of the most common measurement errors is treating signature of an acceptance certificate as the project's end. In the vision of effective government, construction handover is a milestone, not the outcome. A plant, hospital, school or information system does not fulfil its purpose without an operator, staff, operating budget, maintenance, equipment and procedures enabling planned performance. “Operational readiness” therefore belongs in the investment decision from the outset, not in the final weeks before opening.

Before closure, the project owner establishes a transition-to-operation checklist: acceptance tests, defect resolution, transfer of documents, drawings and data, operator training, spare-parts stocks or maintenance contracts where necessary, operating finance and asset responsibility. For projects delivering direct services, a post-operation benefit baseline begins: beneficiaries, reliability, quality or the time the project was designed to improve. “100% completion” thus does not end monitoring before outcomes begin.

After operation begins, major projects need a benefits review over a period appropriate to their nature. The review does not automatically reopen contracts; it asks whether the intended output was delivered and whether the outcome justifying investment changed. If not, analysis distinguishes design defects, operational shortages, changed circumstances and misuse. This memory prevents repetition of projects that succeed in construction but fail in service.

This leads to an important distinction between project and portfolio management. Project managers protect their project's scope, time, cost and quality; government also needs a portfolio view. Are all projects still priorities? Are some unready? Is operating finance available for those nearing completion? Should one project stop or another be rescheduled instead of spreading resources across more projects than the state can execute? These decisions are politically harder, but central to the shift from announcing projects to managing outcomes.

Table 9-B: The Gate from Completion to Operation

Source: Project management, handover and operation section in Evidence File V1-D02-C04; no uniform trial-operation period is assumed across sectors.

15. The Centre of Government and the Delivery Function: Focused Priorities, Clear Data and Early Escalation

Cross-ministerial priorities need a central point that sees deviations without managing everything. Comparative experience compiled in the evidence file indicates that delivery units succeed when close to leadership, monitoring a limited set of priorities, receiving regular data and able to escalate obstacles to those authorised to resolve them. They fail when they become report factories, ministries above ministries, or centres requesting data from everyone without returning useful decisions.⁷

For Iraq, this version's preferred decision is not automatically to create another independent agency, but to strengthen monitoring and performance functions within the centre of government — the General Secretariat of the Council of Ministers, close to the Prime Minister's Office — with the Ministries of Planning and Finance participating within their mandates. The function tracks limited priorities, establishes outcome owners, standardises data definitions, receives exception reports and closes corrective actions. It does not sign contracts for ministries, manage directorates or replace oversight.

Escalation needs rules. Not every delay goes to the prime minister, or centralisation itself becomes a bottleneck. Each programme defines a deviation threshold for time, cost or quality and levels of resolution: project unit, ministry leadership, joint coordination, then the centre of government. Decisions are documented so the state knows why it made an exception or changed a deadline. The aim is to move a problem to the level authorised to solve it, not always the highest level.

15.1 The Annual Implementation Cycle and Decision Memory

To prevent performance management from becoming an early-government campaign that then fades, priorities need a stable implementation rhythm. After approval of the programme and budget, the cycle fixes outcomes, owners and annual milestones, followed by monthly or quarterly reviews according to indicator type and exception reports when deviation exceeds the agreed limit. Reviews do not merely recount events; they end with a corrective decision, owner and closure date.

At year-end, reporting goes beyond comparing values with targets. It explains changes in assumptions, financing, law and implementation, which measures worked or failed, and what must carry into the following year. The annual plan thereby becomes a learning cycle rather than a new document disconnected from its predecessor. This record informs the next budget so stalled programmes do not automatically continue or expand without explanation.

When ministers or directors-general change, government needs an “institutional transition package” preserving continuity: legal obligations, open decisions, critical projects, risks, indicators and definitions, contracts and deadlines, and unfinished corrective actions. The aim is not to constrain new leaders' right to change policy, but to prevent facts and memory from disappearing or problems being rediscovered from scratch.

Decision memory also protects administration from learning the wrong lesson. If a project is delayed by unready land but only financing is addressed, the system will repeat the error. The cause as established at the time, the decision, its maker and its success must therefore be recorded. As data accumulate, government can identify recurring patterns — such as design, financial-transfer or data-exchange delays — and correct the common cause rather than treating cases individually.

Table 9-C: The Government Priority Implementation Cycle

Source: Implementation chain, periodic reviews and institutional continuity in Evidence File V1-D02-C04; the cycle is an implementation formulation for Iraq Vision 2045.

16. Turning Administration from a Burden into a Driver of Growth and Trust

Administration is not a small resource-consuming sector; it is the infrastructure through which every sector passes. A business waits for a licence, a hospital for financing or procurement, a road project for land or a contract, a citizen for a document, and a governorate for approval or a transfer. Reducing obstruction and improving predictability therefore releases time, capital and human capacity for production and services. This does not mean every administrative minute converts directly into economic growth; effects operate through intermediate channels and require measurement.

When procedures are known, timeframes predictable and decisions reasoned, transaction costs fall for individuals and businesses. When ministries have data and can correct deviations early, delayed-project costs fall. When professional competence survives government changes, contracts and plans become more predictable. These mechanisms improve investment conditions, services and trust, but do not replace sectoral policies themselves. Excellent administration cannot compensate for poor economic design, though it is necessary to implement good design.

Administration becomes a “driver” when it reduces friction in obtaining rights or services, improves decision quality, speeds the conversion of public investment into working assets, and provides early warnings rather than late surprises. This chapter therefore builds shared implementation machinery; sectoral parts define what that machinery delivers in health, education, energy, water, transport and the economy.

17. International Comparisons: Transfer the Mechanism, Not the State

Iraq does not need to clone another country's government. Federal scale, allocation of powers, legal systems and political resources differ. Comparison is valuable for isolating a transferable mechanism: how was a priority set, who owned the outcome, how were data linked to decisions, how was service simplified, and what failed or caused side effects? The evidence file offers several cases; this chapter selects only five mechanisms.

Source: Comparisons established in Evidence File V1-D02-C04 and earlier project files. The rule: “transfer the mechanism, not the state”.

17.1 Lessons from Failure: Technology, Centralisation and Indicators Cannot Reform Institutions Alone

Comparative cases also show what does not work. A delivery unit without authority or data becomes an office demanding additional ministry reports. A digital platform built over old procedures may move the queue from the counter to an electronic waiting list. A data centre without access and quality rules may concentrate risks rather than improve service. Reform seriousness is therefore measured not by entities or technology contracts, but by the mechanism's ability to resolve a specific bottleneck.

Rapid reform can also impose institutional costs if it fails to distinguish unnecessary procedures from legitimate safeguards. Licence-abolition experiences demonstrate the value of simplification, but do not mean Iraq should eliminate regulatory oversight in an environment with different risks and capacities. Every removed step must answer: what risk did it address, and who will address it after the change? Without an answer, “simplification” transfers risk rather than removes burden.

18. The Vision for Effective Iraqi Government in 2045

By 2045, effective government is defined not by a digital interface or fewer employees, but by observable working practices. Every major national priority has an outcome owner, baseline and milestones communicated within the apparatus. Every ministry knows its strategic outcomes, while the centre of government has a focused, clear view of priorities rather than thousands of indicators. High-volume services have standards for time, quality, eligibility and redress, and users know their transaction's status and the reason for any rejection.

Major projects become a visible portfolio from readiness to operation, with deviations apparent before becoming years of delay. Administrative data use standard definitions, and every indicator has a source, owner and update frequency. Suitable services are completed digitally from end to end, and the once-only principle operates where lawful, with non-digital alternatives and privacy protection. The professional apparatus continues functioning through political leadership changes without denying elected leaders their right to change policy.

The most important test is correction capability. High-performing government is not error-free; it sees errors early, knows who owns them, changes plans, resources or procedures, and retains the lesson. When this behaviour becomes normal, administration turns from a chain of approvals into an outcomes system, allowing the long-term Vision to endure across governments.

Source: Iraq Vision 2045, drawing on Evidence File V1-D02-C04; the end-state formulation focuses on observable standards, not slogans.

18.1 Three Possible Pathways to 2045

The Vision does not assume linear reform. Iraq may adopt modern tools without changing its operating model, achieve partial reform in some ministries that remains unstable across governments, or turn tools into institutional rules. The following scenarios are not predictions, but tests of what design must protect.

Table 11-A: Effective Government Scenarios

Source: Prepared by the Iraq Vision 2045 team, drawing on the chapter's argument and evidence file; scenarios are design tools, not probability estimates.

19. Transformation Phases, 2027–2045

A direct leap to proactive government and deep operational intelligence is impossible before service times, project counts and job definitions are known. The Vision therefore adopts four phases, each with conditions for progression. This prevents “technological leapfrogging” or hundreds of initiatives launched before a foundation exists for measuring them.

Source: Evidence File V1-D02-C04; numerical targets described as approximate or low-confidence are not elevated to firm commitments before the 2027 baseline.

20. Indicator and Target Dashboard: Measurement Before Numerical Ambition

The Vision does not create a composite “Iraqi Government Effectiveness” index combining incompatible figures. It uses separate indicators because better digital services do not compensate for delayed projects, faster services do not prove decision quality, and a higher WGI score remains an external perception-based indicator rather than direct administrative measurement. The first phase builds baselines; targets then follow from Iraq's baseline, service standards, capacity and appropriate comparative measures.

Some targets can concern “design coverage” without waiting for a baseline: all top government priorities should have an outcome owner, and all priority services should appear in an official inventory with an owner, timeframe and definition. Service times, project completion rates and user satisfaction must receive numerical targets after 2027 measurement, because an ambitious number set before understanding distributions and service types creates a merely formal objective. A target is not a forecast; it is a proposed commitment whose realism is reviewed periodically.

Source: Evidence File V1-D02-C04. All values lacking a unified national baseline are established in 2027 before a final numerical target is set; there is no automatic progression from 50% to 100%.

21. Implementation Programmes: Six High-Impact National Functions

The Vision turns dozens of individual proposals in the evidence file into six manageable, memorable packages. The governing principle is not to create a new institution for every programme: functions first sit within existing institutions where mandates permit, and organisational or legislative changes are sought only when process analysis shows that the rule itself prevents reform.

Source: Regrouping of the programme package in Evidence File V1-D02-C04; no new agency is created where an existing function can be developed.

22. Implementation Matrix: From Programme to Responsible Body, Deadline and Verification

Source: Evidence File V1-D02-C04; legislative amendment is not assumed in advance but identified after testing “law or implementation?” for each pathway.

Source: Evidence File V1-D02-C04; the service or project owner remains the implementing body, and the delivery function does not implement in its place.

23. Cost and Financing: Transformation Costs More Than Buying a System

The final version does not adopt the approximate financial figures appearing in parts of the evidence file because they were not based on a consistent technical scope. There is no single sum called “government reform”. Costs range from changing a procedure that needs only expertise and a decision to building national digital integration, security and maintenance operations. The Vision therefore uses cost categories and requires feasibility and whole-life costing before any major technology programme.

Costs are separated into establishment and operation. Establishment includes service redesign, systems, interfaces and integration, data migration, equipment where needed and launch training. Operation includes software maintenance, information security, support centres, skills updates, surveys, data quality and contract renewals. A programme funded for establishment but without OPEX becomes an outdated, unreliable system after several years.

Core financing is the public budget's responsibility because government capability is an enduring sovereign function. Grants, technical support and concessional development finance can accelerate capacity-building or digitisation, but core functions should not depend on temporary external funding. Private-sector partnerships are used only where contract structure, data protection, service continuity and the state's interest are defensible; the Vision does not equate PPPs with digital government.

Source: Evidence File V1-D02-C04; no dollar figures are adopted before scope design and detailed costing.

24. Risks: Administrative Reform Can Create New Bureaucracy

Every administrative reform risks reproducing the problem in a new form. A delivery unit may become another reporting layer. A performance system may turn ministries into number-chasing organisations. Data centralisation may increase privacy risks. Digital services may exclude people unable to use a phone. This chapter aims not to expand the centre's tools, but to build responsibility, information and correction loops with clear safeguards.

Source: Risk register in Evidence File V1-D02-C04, with vendor lock-in, data and politicisation risks expanded as required by the final design.

25. Constitutional and Rights Safeguards: Faster Government Under the Law, Not Outside It

The conclusion inherited from “The Rule of Law and Institutional Justice” is that effective administration remains constrained by law and open to challenge and review. Safeguards are therefore design requirements, not a list appended after system construction. If a procedure requires redress rights, these must appear in the service. If a decision affects a fundamental right, it must not end in an unreviewable automated outcome. A digital service must not close access to those unable to use digital channels.

Source: Iraqi Constitution; Chapter V1-D02-C03; Evidence File V1-D02-C04. These safeguards are administrative design constraints, not a repetition of the rule-of-law chapter.

26. Chapter Boundaries: What Remains Outside Its Scope

This chapter builds government's implementation capacity. It does not repeat the theory of the state from “The State First”, the monopoly of force and external decisions from “Sovereignty and the Monopoly of Decision-Making”, or judicial structures, trials and judgment enforcement from “The Rule of Law and Institutional Justice”. It takes one conclusion from them: government operates within a constitutional federal state whose sovereignty and power are constrained by law.

Nor does it turn administrative complexity into an anti-corruption strategy. Numerous points of friction may create corruption opportunities, and unprofessional recruitment may reflect patronage. Analysis of contract and procurement corruption, illicit enrichment, disclosure, whistleblower protection and asset recovery belongs in V1-D02-C05. Digital government here likewise does not become a discussion of digital sovereignty, computing, artificial intelligence or national cybersecurity; these belong in the technology parts.

Finally, this chapter provides no health, education, electricity, water or transport plans. A sector may illustrate the implementation or service chain, but its decisions, indicators and costs remain in the relevant parts. What is built here is shared machinery: responsibility, performance, procedures, employees, data, projects and correction.

27. Conclusion: Effective Government Knows What Happens After a Decision

Part Two's argument now comprises four links. “The State First” defined the enduring framework of public authority. “Sovereignty and the Monopoly of Decision-Making” identified the source of public decision-making and force. “The Rule of Law and Institutional Justice” subjected authority itself to rules and review. This chapter adds implementation: can government turn what the state decides, law permits and budgets allocate into actual outcomes that can be measured and corrected?

Effective government does not issue more decisions; it knows what it wants, who owns the outcome, what resources it needs, which milestones must be met, how deviations are detected and who can correct them. It does not minimise procedures at any cost: it retains those protecting rights, money and safety, and removes those adding no value. Nor is it digital merely because it has a platform; it becomes digital when it redesigns services, lawfully uses data across institutions and makes the experience simpler and more dependable.

Real transformation begins by acknowledging that many baselines are missing. The Vision therefore invents no numbers. It builds measurement in 2027, selects limited priorities, expands what proves successful and protects the professional apparatus from reconstruction after every political change. Administration then becomes a national asset: reducing transaction costs, improving investment implementation, increasing service reliability and giving the state the capacity to learn rather than repeat errors.

Yet greater implementation capacity alone does not ensure that capacity serves the public interest. The more capable the state becomes at spending, contracting, hiring and deciding, the greater the cost of those capabilities being captured by private interests. The next question is therefore: how do we prevent corruption from turning effective government into a more efficient machine serving networks of influence rather than the state and citizens?

Consolidated References

1. Iraq Vision 2045: approved Operational Guide, 2026; and the latest official Vision index.

2. Evidence, Analysis, Sources and Proposed Targets File V1-D02-C04, “Effective Government”, 2026 — the principal research reference for this chapter.

3. Chapter V1-D02-C03 “The Rule of Law and Institutional Justice”, final version 1.0, and its evidence file; particularly the conclusion and context-handover block defining the transition question to effective government.

4. Chapters V1-D02-C01 “The State First” and V1-D02-C02 “Sovereignty and the Monopoly of Decision-Making”, final versions 1.0 and their evidence files; used for the definition of capacity, implementation gaps and the limits of public authority.

5. Constitution of the Republic of Iraq, 2005, particularly provisions governing executive authority and the powers of the prime minister and Council of Ministers, within the limits established by the evidence file.

6. Iraqi Ministry of Planning: official data, platforms and materials concerning planning, project monitoring and stalled projects, as compiled and established in the project's evidence files.

7. Final results of the 2024 General Population and Housing Census and related official materials; used here as a case of national coordination, implementation and data capacity.

8. Government performance reform and Takamul / IGPA programme materials adopted by the evidence file concerning re-engineering of 99 service processes; used as an implementation case, not a comprehensive government measure.

9. World Bank, Worldwide Governance Indicators (Government Effectiveness), as cited in the evidence file; used as an external perception-based indicator, not a replacement for Iraqi administrative measurement.

10. OECD literature on administrative burdens, process simplification and one-stop shops, according to references established by the evidence file.

11. Delivery and performance unit references compiled in the evidence file: UK Prime Minister's Delivery Unit, Malaysia PEMANDU and relevant Chatham House reviews concerning Iraq; used to extract mechanisms, not ready-made prescriptions.

12. Digital and administrative comparisons adopted by the project files: Estonia, the once-only principle and interoperability; Singapore, Georgia and selected regional experiences, under the rule “transfer the mechanism, not the state”.

13. Ur Portal and the National Centre for Digital Transformation, as documented by project files through 2026; conflicting coverage figures are not adopted without a common service definition.