Civil Service Programme Manager and Senior Project Manager Applications

Personal statements, behaviours, CVs and interviews for SEO and Grade 7 programme and senior project delivery roles

Civil Service Programme Managers lead groups of connected projects and the business change needed to deliver a wider outcome. Senior Project Managers usually lead a substantial project with significant complexity, risk and stakeholder exposure. The titles overlap in vacancies, so the responsibilities matter more than the label.

This hub explains the SEO and Grade 7 level, the evidence recruiters usually need and where to find complete examples for each part of the application.

Programme Manager and Senior Project Manager application guides

Use the guide that matches the part of the application you are working on.

What does a Civil Service Programme Manager do?

The Government Project Delivery Capability Framework describes a Programme Manager as leading a defined set of interdependent projects and the associated business change. The role owns successful delivery of the required outcomes, including governance, assurance, progress, risks, issues and readiness for change.

The current Project Delivery Capability Framework provides Programme Manager profiles at SEO and Grade 7, as well as more senior levels. This hub focuses on SEO and Grade 7. Programme complexity increases with grade, while departments can use different vacancy titles according to the scope of the role.

What about Senior Project Manager roles?

Senior Project Manager is a common vacancy title rather than a single fixed Civil Service framework level. In the Project Delivery Capability Framework, Project Manager roles progress through HEO, SEO, Grade 7 and Grade 6 as project complexity increases. A vacancy called Senior Project Manager may therefore sit at SEO or Grade 7, depending on the organisation and project.

Read the responsibilities before deciding which examples to use. A substantial single-project role can require evidence that is just as senior as a programme role, even though the delivery structure is different.

Typical responsibilities

• Programme or project performance: defining delivery objectives, maintaining an integrated plan and ensuring governance has a reliable view of progress.
• Governance and assurance: establishing decision routes, tolerances, reporting and assurance activity that fit the scale and risk of the work.
• Risk, issues and dependencies: identifying cross-project or cross-workstream dependencies, resolving problems and escalating decisions at the right level.
• Business case and benefits: keeping delivery aligned to the case for change, tracking benefits and making sure investment decisions remain evidence-based.
• Resources and budgets: working with finance, commercial and delivery leads to understand costs, capacity, capability and supplier constraints.
• Business change and readiness: ensuring operational teams, users and stakeholders are ready for implementation rather than treating technical delivery as the end point.
• Stakeholder leadership: influencing senior leaders, sponsors, delivery partners and specialists who may have competing priorities.
• Leadership through others: setting direction for project managers, workstream leads and professional specialists while remaining accountable for the overall outcome.

What recruiters usually look for

Strong applications normally make the scale of responsibility easy to see. Useful evidence often covers:

• leading complex delivery with several linked workstreams or projects
• making decisions when time, cost, scope, quality or benefits are in tension
• creating or improving governance and controls
• managing significant risks, issues and dependencies
• influencing senior stakeholders and sponsors
• leading delivery through project managers, workstream leads or specialists
• maintaining business readiness and benefits, not just completing outputs
• using evidence to reset plans when assumptions change
• working with finance, commercial, digital, policy, operations or external suppliers

Professional qualifications can be useful where the advert requests them. They do not replace evidence that you can lead difficult delivery and make sound decisions.

How applications can be assessed

Civil Service campaigns use different combinations of Success Profiles. You may be assessed through a CV, Previous Skills and Experience, a personal statement, behaviour examples, technical criteria, an interview, a presentation or a scenario exercise.

Project Delivery vacancies may also refer to capability framework areas such as governance, risk and issue management, business cases, benefits, planning, assurance, commercial management or stakeholder engagement. Follow the advert and attachments rather than assuming every programme role uses the same selection process.

How expectations change between SEO and Grade 7

SEO Programme Manager or Senior Project Manager

SEO evidence should show control of a low to moderate complexity programme or a substantial project. You should be able to integrate plans, manage delivery through workstream leads, resolve cross-team problems, advise governance and keep outcomes, risks and business readiness visible.

A strong SEO example shows that you are shaping delivery, not simply reporting what other people have done.

Grade 7 Programme Manager or Senior Project Manager

Grade 7 evidence should show wider authority, complexity and organisational impact. You may lead several project managers, manage significant investment or supplier dependencies, advise Directors or an SRO, establish governance, challenge strategic assumptions and make difficult recommendations about scope, sequencing or benefits.

A strong Grade 7 example shows that you can protect the intended outcome when individual projects, stakeholders or constraints pull the programme in different directions.

Can you apply from outside formal programme management?

Yes, if your experience genuinely demonstrates the required scale. The strongest transferable backgrounds usually involve complex change rather than routine management alone.

• Transformation and change leadership: coordinating several workstreams, readiness, stakeholders, risks and implementation across an organisation.
• Digital delivery: leading multidisciplinary teams, dependencies, suppliers, releases and service transition across several products or systems.
• Operations: leading major service change across multiple locations or functions, with measurable readiness and performance outcomes.
• Commercial or procurement: coordinating complex procurements, supplier transitions, governance, budgets and dependencies with wider business change.
• Policy implementation: turning a policy decision into coordinated delivery across digital, operational, legal, finance and stakeholder workstreams.

Translate the experience accurately. A large operational responsibility is not automatically a programme. Show the connected change, dependencies, governance and outcome you actually led.

Common application mistakes

• Describing a collection of projects without explaining the common outcome or dependencies between them.
• Focusing on schedules, RAID logs and reporting while leaving leadership and decision-making weak.
• Claiming programme ownership when the applicant actually managed one workstream and escalated all material decisions.
• Giving senior stakeholder examples that show updates and meetings rather than advice, challenge or negotiated decisions.
• Treating go-live as success without showing business readiness, adoption or benefits.
• Using a Grade 7 example where the applicant personally completes tasks that should be owned by project managers or specialist leads.
• Using impressive project values or team sizes as a substitute for explaining what was difficult about the delivery.
• Presenting every problem as resolved cleanly. Strong senior evidence can include compromise, residual risk and decisions to stop, delay or reduce scope.