cvlift.ai logo
Toggle menu

Examples & writing guide

Programme manager CV examples

Updated 16 November 2026

Build your Programme Manager CV around decisions and contributions you can explain: what you supported, what you owned and what changed. These two worked examples cover a first Programme Manager application and a senior candidate with sustained delivery responsibility; use them to select comparable evidence from your own background.

Examples by experience level

01

First Programme Manager role - Programme support

Riley Sample
Programme Support Officer
Email: 
riley.sample@example.com
Location: 
Belfast, United Kingdom
Phone: 
07700 900101
LinkedIn: 
https://www.linkedin.com/in/riley-sample
SUMMARY
Programme Support Officer with two years of experience supporting a service-improvement programme across three community centres. Built a shared milestone tracker and helped reduce overdue actions from 18 to 7 over eight weeks; now seeking a first Programme Manager role.
SKILLS
​
•
Milestone tracking
•
Action-log maintenance
•
Progress reporting
•
Meeting coordination
•
Stakeholder updates
•
Issue escalation
•
Dependency tracking
•
Document control
•
Workshop preparation
•
Data checking
 
 
EXPERIENCE
​
Programme Support Officer
Harbour Community Services
Sep. 2024
 - 
Present
•
Support a Programme Manager on service improvements across three community centres; consolidated separate schedules into a shared milestone tracker so workstream leads could identify missed dates and linked activities.
•
Found that meeting actions lacked clear owners, introduced owner and due-date fields, and followed up weekly; helped the team reduce overdue actions from 18 to 7 over eight weeks.
•
Checked weekly updates against workstream records and flagged a training dependency before a planned launch; the Programme Manager approved a revised sequence that kept the pilot date unchanged.
•
Prepare fortnightly progress summaries that separate decisions needed from routine updates, then record agreed actions so centre managers can brief their teams consistently.
Project Administration Assistant
Northbank Learning Partnership
Jun. 2023
 - 
Aug. 2024
•
Coordinated bookings and checked attendance records for 12 community workshops, giving the project lead a reliable record for the final delivery report.
•
Compared venue capacity with registrations and proposed moving an oversubscribed session; the project lead approved the change and all registered participants received a place.
•
Grouped participant feedback into recurring themes and presented examples to the project lead; the team revised joining instructions to answer repeated questions about access.
EDUCATION
​
Bachelor of Arts with Honours
Northbank Metropolitan University

,

Business Management
Sep. 2020
 - 
Jun. 2023
•
Final-year group project: coordinated a four-person team reviewing a community organisation's booking process; divided the research tasks, maintained the schedule and brought the team's findings together for its final presentation.

TemplateNavy Atlas4 / 5

Why this works

Clear attribution connects Riley's supporting contributions with a first Programme Manager application; the profile, employers, history and achievement figures are fictional and illustrative.

Continue writing your CV
02

Senior Programme Manager - Government digital delivery

Jordan Sample
Senior Programme Manager
07700 900102

·

jordan.sample@example.com

·

https://www.linkedin.com/in/jordan-sample
SUMMARY
Senior Programme Manager with eight years in Programme Manager roles within government digital delivery. Leads a £6.4 million programme spanning five workstreams and 24 staff, with responsibility for delivery sequencing, budget decisions and supplier performance.
EXPERIENCE
​
Senior Programme Manager
Regional Public Services Agency
Apr. 2022
 - 
Present
•
Lead a government digital-services programme with a £6.4 million approved budget, five workstreams and 24 staff, including four direct reports; introduced a shared dependency review so workstream leads could agree priorities and escalate delivery risks.
•
Resolved competing demands for a specialist integration team by comparing service deadlines and testing capacity, then agreeing staged releases with the sponsor; all three pilot launches met their revised approval dates.
•
Challenged a supplier's proposed change after comparing it with agreed deliverables, negotiated phased acceptance with commercial colleagues and avoided £180,000 of additional charges.
•
Reallocated £240,000 within the approved programme budget after reviewing delivery risks, forecasts and remaining commitments with finance; funded additional accessibility testing and completed the first service transition within its approved allocation.
Programme Manager
Public Access Digital Directorate
Apr. 2018
 - 
Mar. 2022
•
Managed a programme with a £2.8 million approved budget to replace paper-based application processes across three public-service teams; agreed workstream milestones and reported delivery decisions to the programme sponsor.
•
Mapped dependencies between data migration, staff training and service readiness; delayed one migration rehearsal so the team could resolve a data-quality issue before transferring live records.
•
Agreed named operational owners and acceptance checks with service managers, then tracked unresolved issues through a phased handover; all three teams accepted their services with documented support arrangements.
•
Introduced monthly forecast reviews with finance and workstream leads; closed the programme with actual expenditure of £2.72 million against its £2.8 million approved budget and documented the remaining operational costs separately.
Project Manager
Public Access Digital Directorate
Sep. 2015
 - 
Mar. 2018
•
Managed a six-person team introducing an online appointment service, with responsibility for the project schedule, issue log and release recommendations.
•
Identified a conflict between testing and operational training, negotiated a revised sequence with both leads and completed the pilot before the agreed service review.
•
Compared pilot feedback with support records and prioritised changes to appointment confirmations; repeat enquiries about booking status fell from 46 to 29 in comparable four-week periods.
SKILLS
​
Programme planning
Dependency management
Risk management
Budget forecasting
Supplier performance management
Commercial negotiation
Resource allocation
Sponsor reporting
Stakeholder communication
Team leadership
Service transition planning
 
EDUCATION
​
Bachelor of Science with Honours
Westbridge University

,

Business Information Systems
Sep. 2012
 - 
Jun. 2015

TemplateBlue Horizon3 / 5

Why this works

Jordan's progression links delivery decisions with financial, commercial and team responsibility; the profile, employers, history and achievement figures are fictional and illustrative.

Continue writing your CV
Junior vs senior: what changes
AspectJuniorSenior
Evidence sourcesRiley: programme support, project administration and a university group project demonstrate relevant contributions before a first Programme Manager title.Jordan: successive Programme Manager roles demonstrate sustained government digital-delivery responsibility, supported by earlier project management.
ResponsibilityRiley: checks records, prepares updates and flags dependencies; the Programme Manager or project lead approves changes.Jordan: agrees delivery sequencing, reallocates budget and negotiates supplier changes with commercial colleagues.
AchievementsRiley: explains an individual tracking improvement and the team's reduction in overdue actions from 18 to 7 over eight weeks.Jordan: explains £180,000 of avoided supplier charges, alongside delivery and allocation decisions within a £6.4 million approved programme budget.
ProgressionRiley: moves from workshop administration into support across three community centres, with clear escalation and approval boundaries.Jordan: progresses from a six-person project team to programme ownership and then five workstreams, 24 staff and four direct reports.
Section emphasisRiley: give programme-support achievements prominence and retain the academic project to explain additional coordination experience.Jordan: give recent delivery, commercial and financial decisions the most space, with a brief education record.

How to write a programme manager CV

Read the target application's instructions, select relevant evidence, then draft concise sections and choose their order. Use the shortest readable length that covers useful evidence; remove repetition before reducing text size.

Use reverse-chronological order within experience and education. Both examples put experience first because their work provides the strongest evidence. Riley's academic project adds detail; Jordan's recent delivery decisions deserve more space.

SectionDrafting focus
Contact detailsGive your name and usable contact details.
Personal statementConnect your background and intended role when useful.
ExperienceExplain contributions, decisions and outcomes.
SkillsSelect capabilities demonstrated elsewhere.
Education and trainingRecord awards and completion status accurately.
ExtrasKeep material that adds relevant evidence.

For UK CVs prepared for applicant tracking system (ATS) screening, Careers Wales recommends simple formatting and standard headings such as Employment, Work Experience and Skills, and advises avoiding tables because software might misunderstand them. For that screening context, it also recommends advert keywords in skills, experience and the personal statement only where you can demonstrate the corresponding capabilities. The table above is a drafting aid for this guide.

Finally, check dates, contact details and wording against your records. Inspect the exported document for awkward breaks and readability, and check it against the application instructions.

Personal statement examples

Stronger example

Connect your current background, a relevant example and the role you want. These versions use the two fictional candidates above. Entry, Riley Sample: Programme Support Officer with two years of experience supporting a service-improvement programme across three community centres. Built a shared milestone tracker and helped reduce overdue actions from 18 to 7 over eight weeks; now seeking a first Programme Manager role. Senior, Jordan Sample: Senior Programme Manager with eight years in Programme Manager roles within government digital delivery. Leads a £6.4 million programme spanning five workstreams and 24 staff, with responsibility for delivery sequencing, budget decisions and supplier performance. Riley's version distinguishes a supporting contribution from programme ownership. Jordan's establishes sustained responsibility and scale, with details developed in the experience section. Use the same test for your own statement: can each detail be traced to a specific example further down the CV?

Too generic

Hard-working and highly motivated professional with excellent leadership and communication skills. Passionate about successful programmes and looking for an exciting opportunity to make a difference. This could describe either candidate. It gives no current background, specific contribution or account of responsibility. Replace the adjectives with an example that explains what you offer and the role you are seeking.

Writing your experience

Record the organisation, role and dates, starting with your most recent experience. Select relevant contributions from paid work, placements or volunteering. A brief situation, task, action and result account can help explain a decision; you don't need to turn every bullet into a long narrative.

In the UK Civil Service Government Digital and Data framework, programme delivery managers, most often at grades G7 or G6, manage dependencies of varying complexity, potentially planning and feeding into larger programmes and portfolios. Within this framework, they must remove blockers and manage risks, commercial matters, budgets and people. This is a specific Civil Service role profile, rather than a requirement for every Programme Manager job.

The fictional CVs show how to replace vague duties with useful detail:

  • Before: "Updated trackers." After, Riley: "Found that meeting actions lacked clear owners, introduced owner and due-date fields, and followed up weekly; helped the team reduce overdue actions from 18 to 7 over eight weeks." This explains what Riley changed and keeps the result attributed to the team.
  • Before: "Managed suppliers." After, Jordan: "Challenged a supplier's proposed change after comparing it with agreed deliverables, negotiated phased acceptance with commercial colleagues and avoided £180,000 of additional charges." The example explains the commercial decision. The figure measures avoided charges, so it should not be described as expenditure or a budget reduction.
  • Before: "Responsible for handover." After, Jordan: "Agreed named operational owners and acceptance checks with service managers, then tracked unresolved issues through a phased handover; all three teams accepted their services with documented support arrangements." Named owners, acceptance checks and support arrangements give the reader a concrete account of the handover and its outcome.

Match verbs to what you had authority to do. Use checked, prepared, tracked or escalated for supporting contributions where those words fit. Use agreed, allocated or negotiated for decisions you actually made. For senior experience, choose examples that show how your responsibility grew.

Key skills & ATS keywords

Hard skills

Milestone trackingAction-log maintenanceProgramme schedulingProgress reportingDependency mappingRisk assessmentBudget forecastingExpenditure monitoringResource allocationSupplier performance reviewService transition planningAcceptance planning

Soft skills

Clear written communicationActive listeningTeam coordinationConstructive challengeNegotiationProblem solvingPrioritisationAttention to detailCollaborative workingInterpersonal communicationTeam leadershipSound judgement

ATS keywords

Programme planningProgress monitoringMilestonesAction trackingDependency managementRisk managementIssue escalationBudget managementCost forecastingResource planningStakeholder communicationSupplier managementCommercial negotiationDelivery sequencingProgramme reportingService transitionTeam leadershipAcceptance criteria

Education & certifications

Use exact qualification and training names, providers, dates and completion status. Separate completed awards from study in progress, and distinguish completing a course from receiving a qualification. Choose detail relevant to your application. Riley's group project shows coordination experience before a first Programme Manager title; Jordan's shorter education record leaves more room for substantial delivery evidence.

Read the target vacancy carefully before choosing what to emphasise. Distinguish required experience, alternative credentials and preferred training, and keep those categories separate in your application notes.

For a historical employer-specific example, the Met Office's UK Programme Manager (Level 2) vacancy leading the Aviation Services Programme in Exeter had an essential qualifications-and-experience criterion that required experience in a programme environment or as a Programme Manager and listed alternative relevant credentials: Managing Successful Programmes (MSP) Practitioner, APM Chartered Project Professional or Project Leadership Programme. Applications closed on 19 November 2025. The appointment was temporary for up to 18 months, with potential to become permanent.

Read that example as a criterion for that particular closed vacancy. When writing your own CV, include only credentials you hold or describe study in progress accurately. Check the wording against your award or training record so you don't present a completed course as an awarded qualification. The fictional degrees in these CVs show how to present a completed education record; they do not establish entry requirements.

Common mistakes to avoid

  • AvoidUsing generic claims that hide your programme contribution.

    InsteadReplace broad claims with a specific example. In England, the National Careers Service recommends tailoring a CV to the job and organisation, using the advert's description and essential criteria to select relevant skills.

  • AvoidListing skills without showing where you used them.

    InsteadConnect each selected capability to an experience example. Riley's milestone tracking has a clear purpose: helping workstream leads identify missed dates and linked activities.

  • AvoidInflating supporting work into programme ownership.

    InsteadName your contribution and identify who approved the decision. Riley flags the training dependency; the Programme Manager approves the revised sequence. Keep that boundary visible.

  • AvoidUsing figures without explaining their basis.

    InsteadDistinguish approved budget, actual expenditure, forecast and avoided charges. Give a measurement period for comparisons, and remove figures you cannot defend from your own records.

  • AvoidLeaving inconsistent dates or proofreading errors.

    InsteadCheck dates and figures against personal records, read the wording aloud and ask another reader to check it. Make sure the personal statement agrees with the detailed history.

  • AvoidBurying delivery decisions in dense descriptions.

    InsteadUse consistent headings and spacing, remove repeated duties and inspect the exported document. Give each selected decision enough context for the reader to understand its outcome.

Frequently asked questions

From example to application

Turn this programme manager example into a CV that sounds like you.

Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.