Cover photo: Rodeo Project Management Software / Unsplash. Illustrative photograph, not a client project.
Decide what the PMO is there to do
A programme management office can become very good at asking delivery teams for information and surprisingly bad at giving anything useful back.
Start with the service it should provide. Perhaps three suppliers maintain incompatible plans. Perhaps the sponsor receives conflicting cost forecasts. Perhaps decisions spend weeks waiting for a named owner. These are specific problems a PMO can help solve. “Improve governance” is too broad to staff or measure.
APM describes PMOs as support structures for projects, programmes or portfolios. It distinguishes embedded, central and hub-and-spoke arrangements. The right arrangement depends on the work being supported. A programme office serving one connected change is not automatically an enterprise portfolio function.
Write a service charter before recruiting
For each proposed service, name its user, inputs, output, frequency and boundary. Agree who supplies reliable data and who has authority to act on the result. The PMO can maintain the decision queue; it should not inherit the sponsor’s decisions by accident.
| Service | Useful output | Accountable source | Boundary |
|---|---|---|---|
| Integrated planning | Accepted milestone and dependency view | Workstream leads | PMO challenges forecasts; leads own delivery |
| Decision support | Options, deadline and decision owner | Person requesting the decision | Sponsor or delegated authority decides |
| Cost consolidation | Reconciled forecast and explanation of movement | Finance and budget owners | PMO does not approve spend |
| Evidence coordination | Traceable evidence index for reviews | Delivery and service owners | Authors do not replace independent assurance |
This is an illustrative starter charter. Remove services nobody needs. Add a service only when the programme can identify its recipient and the decision or action it enables.
Use the programme governance framework to settle decision rights. The PMO charter describes how support gets delivered within those rights.
Choose where the people sit
An embedded office can stay close to a complex programme’s daily work. A central team can share scarce planning or financial-analysis skills across smaller initiatives. A hybrid can work where local delivery needs support but common definitions matter across the organisation.
In a fictional programme with three interdependent workstreams and two suppliers, a reasonable starting point might be an embedded planning and controls role with part-time finance and change support. It is a hypothesis to test against workload, not a staffing benchmark. Price the time required to reconcile plans, prepare decisions and maintain evidence before turning it into a headcount request.
Keep separation where it matters. Someone assembling the evidence can check completeness, but an independent review should not be described as independent if the same person is reviewing their own delivery decisions. Identify the sponsor, programme manager, service owners and assurance route outside the PMO chart.
A first-90-days launch plan
Days 1–30: establish the service. Interview the people who will use the office. Inventory reports, meetings and data sources. Pick two recurring problems to solve first, agree the charter and capture a baseline. Pilot one integrated milestone view rather than migrating every workstream into a new tool.
Days 31–60: make it dependable. Run the agreed services through several reporting cycles. Reconcile inconsistent definitions with their owners. For example, “committed cost” must mean the same thing in the programme pack and the finance source. Record unresolved differences rather than hiding them in a spreadsheet adjustment. Retire a duplicate report only after its recipient agrees that the replacement meets the need.
Days 61–90: review whether it earns its time. Ask users which service changed a decision or exposed a material problem earlier. Compare reporting effort and decision delays with the baseline. Expand the service, simplify it or stop it based on that evidence. This sequence is a suggested working plan, not an APM standard or a promise that every PMO can be established in three months.
Make data ownership explicit
Every reported measure needs a source owner, definition, cut-off and correction process. A PMO analyst can consolidate the forecast without becoming accountable for a supplier’s estimate. Show stale data as stale; do not roll last month’s figures forward and call them current.
For cross-border teams, put the cut-off in a time zone and agree how local non-working days affect it. Give contributors enough time to validate their figures before the pack goes to the sponsor.
Measure the office with a few service-level questions: how long do material decisions wait, how many critical handoffs lack confirmed owners, and how much effort does reporting consume? Track context and trends. A rising number of recorded dependencies may mean better visibility rather than deteriorating delivery.
The PMO should reduce the effort needed to run the programme. If it creates a second management system that everyone has to feed, revisit its charter before buying another dashboard.
Practical questions
Do we need a PMO tool before launching the service?
Not necessarily. Start with controlled sources and agreed definitions that the team can maintain. Choose tooling when you understand the reporting, collaboration and access needs. A new platform will not settle conflicting ownership or cost definitions.
Can one person provide PMO support?
For a limited scope, possibly. Estimate the work and coverage needed rather than starting with a title or headcount ratio. One person may need access to specialist planning, finance or assurance support and a backup when unavailable.
When should a temporary programme office close?
Set its exit conditions in the charter. Before closure, transfer records, outstanding actions, reporting responsibilities and benefits follow-up to named owners. If a service must continue, fund and assign it explicitly rather than leaving a temporary team indefinitely in place.
Use the worksheet
Download the editable worksheet (CSV) ↓
Open the CSV in your spreadsheet application, replace the illustrative entries and add rows for your programme. It contains plain values, no formulas or macros. Keep evidence references in the sheet and sensitive supporting material in your own controlled systems. Nothing is submitted through this download.
Reviewed 8 November 2026. Examples, figures and working methods are illustrative editorial material, not measured client results, professional certification or a substitute for your organisation’s required approvals.

