A steering committee needs the real project status, not a version that sounds better than what is happening on the ground.

The vendor runs their delivery. The PMO runs the project on your behalf, which is a different job. It holds the vendor to the RFP commitments and contract, tracks value against the business case, coordinates your internal teams, and escalates problems while they are still small. Without it, the client side of an implementation often falls to a finance director doing a second full-time job.

What the PMO controls

Scope runs through a formal change process, so every addition is priced, approved and sequenced instead of being absorbed quietly into a slipping timeline. Schedule runs through an integrated plan that includes your internal tasks, data cleansing, testing and training, not only the vendor's configuration milestones.

Budget is tracked against the full investment picture, including internal costs. Risks and issues are logged, owned and reviewed weekly, so they do not surface at the steering committee after they have become crises.

Saudi-specific project governance

Implementations in the Kingdom carry dependencies that a generic PMO plan can overlook. These include ZATCA Phase 2 onboarding and certification timing, and GOSI and WPS payroll cutover windows that cannot slip past a pay date.

They also include year-end reporting where both Hijri and Gregorian calendars matter, and Arabic-language testing and training that must run in parallel with English. The PMO builds these into the critical path rather than discovering them late.

Managing the vendor relationship

Weekly status meetings run to your agenda, not the vendor's. Deliverables are accepted against written criteria. Invoices are released only when milestones are met. Disputes are documented while the facts are fresh.

This is not adversarial. Good vendors welcome a competent client-side PMO because it removes ambiguity, and it shifts the balance of information toward the client.

A hypothetical example

A Riyadh industrial group is partway through an ERP implementation, and the vendor's reports show green status. The PMO's integrated plan shows that data migration for some entities has not started, that the payroll cutover falls in a salary run week, and that the e-invoicing integration partner has not yet been engaged. The PMO takes these points to the steering committee with the evidence behind them.

What you receive

An integrated project plan, a change control process, weekly status reporting in a format leadership can read quickly, a risk and issue register with owners, steering committee preparation and facilitation, and vendor deliverable acceptance. A benefits tracking framework continues past go-live into operation.

Keeping the business case alive after go-live

The PMO's job does not end at cutover. The benefits promised in the business case continue to be tracked after go-live, with the same rigor applied to realized savings as to projected ones.

Where a benefit is not materializing, the PMO identifies why, such as an unused feature, a process that reverted to the old way, or a workflow that needs redesign, and drives the fix.