Project Coordinator to Project Manager: What Has to Change on Your CV
Many project coordinators already do a large share of project management work, but their CV still reads like a support role. Hiring managers screening for PM roles look for ownership of scope, schedule, budget, risk and decisions. This guide shows what to change on your CV so the work you already do is read as project management.
Why coordinator CVs get filtered out for PM roles
A project manager posting asks one question of every CV: has this person owned a project, or part of one, from start to finish? Most coordinator CVs answer "no" without meaning to. They describe the work around the project instead of the project itself.
Recruiters and hiring managers who screen for PM roles tend to look for four signals:
- Ownership. Did you decide things, or only record them?
- Scale. How big was the project, the budget, the team, the stakeholder group?
- Outcomes. Was the project delivered, and what changed because of your work?
- Control. Did you manage scope, schedule, cost, risk or quality, or only report on them?
The good news is that many coordinators already have evidence for at least two or three of these. They took over a workstream when the PM was on leave, ran the supplier onboarding, rebuilt the schedule after a delay, or chased the decisions nobody else would chase. That work is project management. The CV just has to say so, accurately.
From "supported" to "owned": change the verbs
The fastest change is in the verbs. Coordinator CVs are full of words that place you one step away from the result: supported, assisted, helped, was responsible for maintaining, involved in. Each one tells the reader that someone else held the accountability.
Replace them with verbs that describe what you actually controlled, but only where it is true:
| Instead of | Use, if accurate |
|---|---|
| Supported the PM with scheduling | Built and maintained the project schedule; flagged slippage and proposed recovery options |
| Assisted with stakeholder communication | Ran weekly status updates for a group of stakeholders across several departments |
| Helped track the budget | Tracked spend against budget and raised variances before month-end reviews |
| Involved in risk management | Maintained the risk log and owned follow-up on mitigation actions |
| Took meeting minutes | Ran project meetings, recorded decisions and drove actions to closure |
A useful test: if your manager read the line, would they nod? If yes, keep it. If they would say "that was me", rewrite it. Overclaiming tends to fall apart in the first interview, when the interviewer asks what you would have done differently and you have no answer because the decision was not yours.
Before and after: rewriting coordinator bullets
Here is what the shift looks like on real-style CV lines. Each "after" line names the project, your part in it, the scale and the result.
Coordinated project meetings and updated project documentation.
Ran weekly delivery meetings for a 9-month office relocation (4 workstreams, 3 suppliers); kept the decision log current, which cut repeat discussions and kept sign-offs on schedule.
Supported the project manager in tracking project tasks and deadlines.
Owned the integrated schedule for a CRM rollout to 200 users; spotted a two-week slip in data migration early and agreed a re-sequenced plan with the vendor that protected the go-live date.
Responsible for purchase orders and invoice processing.
Managed procurement for a $350K equipment upgrade: raised and tracked 40+ purchase orders, reconciled invoices against delivery, and closed the project within budget.
Helped onboard new team members to the project.
Designed and ran onboarding for 12 contractors joining mid-project, reducing the time before they could work independently from weeks to days.
Use your own numbers. If you do not know the exact figure, use an honest approximation ("around 15 stakeholders", "a six-figure budget"). If there is no number at all, describe the consequence instead: what would have gone wrong without your work. For more on this pattern, see Project Manager CV: How to Write Achievements Instead of Tasks.
Show scale: the numbers a PM reader looks for
Coordinators often leave scale out because it feels like it belongs to the PM. It does not. You worked on that project, so you can describe it. A hiring manager wants to know what size of project you are used to, because it tells them what they could trust you with.
For each significant project, try to find:
- Budget: total project budget, or the part you tracked.
- Duration: start to finish, or the phases you covered.
- Team: number of people, internal and external, and how many you coordinated directly.
- Stakeholders: departments, sites, clients or suppliers involved.
- Deliverables: what was produced, rolled out, built or moved.
- Method: waterfall, agile, hybrid, or your organisation's own framework.
Put the scale in the first half of the bullet, where it is read. "Coordinated a multi-site ERP rollout" says less than "Coordinated a 14-month ERP rollout across 3 sites and 5 suppliers". If confidentiality is an issue, round or describe the range rather than leaving it out.
Summary and job title: be honest, be specific
Your job title is your job title. Changing "Project Coordinator" to "Project Manager" on your CV is a risk: background checks and reference calls often confirm titles, and a mismatch can end an offer. What you can change is the context around it.
Two honest options work well:
- Add a clarifying line under the title. For example: Project Coordinator (acting PM for supplier workstream, 6 months). Only if that happened.
- Lead with the projects. Under each role, open with one line describing the main project and its scale, then the bullets.
The summary at the top of the CV is where the direction changes. A coordinator summary usually describes support skills. A PM-oriented one describes delivery.
Organised and detail-oriented project coordinator with strong communication skills and experience supporting project teams.
Project coordinator with 4 years in infrastructure projects, including 6 months leading a supplier workstream. Experienced in schedule control, budget tracking and risk follow-up on projects up to $2M. Looking for a project manager role in construction or facilities.
The second version names the sector, the scale, the PM-level work and the target role. It gives the reader a reason to keep going.
Skills and tools: what to keep and what to cut
Many coordinator CVs list skills that every PM candidate has, or that signal admin work rather than delivery. A long list of soft skills ("organised", "team player", "excellent communicator") takes space and proves nothing. Show those through the bullets instead.
Keep a short, specific skills section that matches the postings you target:
- Project controls: scheduling, budget tracking, change control, risk and issue management, RAID logs.
- Methods: the delivery approaches you have actually used.
- Tools: the scheduling, ticketing, collaboration or ERP tools named in the postings you want and that you can use without training.
- Certifications: any you hold or are working towards, with dates. If you are wondering whether to pursue one, Do You Need a PMP to Become a Project Manager? covers when it helps.
Cut or shrink general office software, data entry, diary management and filing unless the posting asks for them. They are not wrong, but they pull the reader's attention back to the coordinator role you are trying to move on from.
Target the roles that fit your evidence
The CV changes above work best when they are aimed at roles your evidence can support. A coordinator with strong schedule and supplier experience is a credible candidate for some PM roles straight away and a stretch for others.
Roles that often fit a first move from coordinator:
- Junior or Associate Project Manager
- Project Manager in a smaller organisation, where projects are shorter and teams lighter
- Project Lead or Workstream Lead inside a larger programme
- Project Manager in the same sector or organisation, where your context knowledge counts
Roles that are usually a stretch at this point: Senior Project Manager, Programme Manager, or PM roles in a new sector with a large budget and no context you can bring. Applying there is not forbidden, but expect a lower response rate.
An internal move is also worth considering. Your current employer already knows your work, and an "acting PM" assignment on a small project gives you the line your CV needs for the next external application.
Checklist before you send the CV
Run through this list against one specific posting before each application:
- The summary names the type of PM role and sector you are targeting.
- Each recent role opens with the main project and its scale.
- Most bullets start with a verb that shows what you controlled, not what you supported.
- At least half of your bullets include a number or a clear result.
- Your job titles are accurate, with any acting or lead responsibility explained.
- The skills section matches the posting's language and skips generic soft skills.
- Admin tasks take up no more than a line or two.
- Every claim is one you can talk through in detail at interview.
If you can tick all eight, your CV is now reading as a project manager's CV. The remaining question is whether it fits the specific roles you want, and that depends on the posting.
Want to know where you stand?
Send your CV and one project manager posting you'd like to get. Within 48 hours you get a written report: your fit for that role, the gaps that matter, rewritten CV lines, and the roles you can target now.
Get my PM Fit Report — $39