Written by our assessment team: what the criteria mean in practice, the evidence that works, and where learners get caught out.
What this unit is really about
Unit 509 is the biggest Level 5 unit at 6 credits, and unlike the Level 3 equivalent (306, which asks you to contribute to a project) this one asks you to plan and manage one. Four outcomes: lifecycle and governance knowledge, planning and evaluation knowledge, then planning projects and managing projects in practice.
The spec is explicit that the unit establishes the key differences between Business As Usual (BAU) and a project, so get that right early: a project is temporary, has a defined start and end, delivers a unique output, and closes. BAU is continuous and repeatable. Improving the monthly report every month is BAU; replacing the reporting system is a project. Choosing a piece of BAU as your project is the most common way to fail this unit.
The evidence that works
| Learning outcome | Evidence that works well |
|---|
| LO1 — lifecycle, governance, teams | The stages, different lifecycle approaches (waterfall, agile, hybrid, stage-gate), the roles, and your organisation's governance requirements |
| LO2 — plan, manage, evaluate | How to create a plan, an evaluation of tools, an assessment of collaboration tools, an examination of change impacts, reporting methods, success measures, and why closure and evaluation matter |
| LO3 — plan projects | The plan itself, produced with real tools, and evidence that stakeholders agreed it |
| LO4 — manage projects | Resource allocation, briefing records, monitoring against milestones, adjustments made, stakeholder updates, and a review of your own ability |
Criterion 3.2 — agree project plans with relevant stakeholders — needs an artefact: a sign-off email, minuted approval, or a signed plan. Keep it, because it is the criterion learners most often have no evidence for.
Choosing a project that will finish
The practical constraint is time. LO4 needs implementation, monitoring, adjustment and a review, so your project must reach a reportable stage within your enrolment. Safe choices: a system or process implementation in one department, an office or site move, a new service launch to one customer group, a compliance or accreditation exercise, a recruitment and onboarding programme for a cohort.
If your project is genuinely long, evidence a defined phase with its own start, end and deliverable, and say so explicitly. Assessors accept a clearly bounded phase; they cannot accept a plan with no outcome.
Where Level 5 depth shows
2.2 evaluate project management tools. Evaluation means judgement with trade-offs, not a list. A Gantt chart communicates dependencies to stakeholders but rots the moment reality diverges and nobody updates it; a Kanban board reflects real flow but hides the deadline; critical path analysis exposes what actually matters but demands duration estimates you may not have. Say which you used and why it suited your project.
2.4 examine potential impacts of project changes. This is change control — scope, cost, time, quality and risk moving together, and the governance route for approving a change. Iron triangle thinking is fine here, provided you apply it to a real change request you handled.
4.6 review own ability to manage projects. A frank reflection, ideally with feedback from your sponsor or team, and a development action. Vagueness here is visible.
Useful reading
