BSBPMG536 Assessment Help: Manage Project Risk Guide
Quick answer: BSBPMG536 Manage project risk is a BSB Business Services Training Package unit and a core unit of the BSB50820 Diploma of Project Management. You identify, analyse, treat, monitor and review project risks on at least two occasions, usually through a risk management plan, a risk register, stakeholder records and a lessons-learned report. The register and evidence of monitoring carry the most weight.
BSBPMG536 at a glance
| Item | Detail |
|---|---|
| Unit code and title | BSBPMG536 Manage project risk (Release 1) |
| Training package | BSB Business Services Training Package, nationally recognised in Australia |
| Where it appears | Core unit in BSB50820 Diploma of Project Management and CPC50320 Diploma of Building and Construction (Management); elective in diplomas such as ICT50220 Diploma of Information Technology |
| Elements | 1. Identify project risks. 2. Analyse project risks. 3. Establish risk treatments and controls. 4. Monitor and control project risks. 5. Assess risk management outcomes. |
| Performance evidence | Manage project risk on at least two occasions, using risk management techniques, strategies and tools on a project of sufficient complexity |
| Knowledge evidence | Risk categories, components of a risk management plan, risk controls, risk frameworks, and qualitative and quantitative risk techniques |
| Supersedes | BSBPMG517 Manage project risk (equivalent) |
BSBPMG536 follows the full risk management life cycle on a project: identify, analyse, treat, monitor and review. Most RTOs give you a case-study project (for example an office fit-out, event or software roll-out) and ask for a risk management plan, a risk register, stakeholder communication and a lessons-learned review. Because the performance evidence asks for two occasions, expect either two projects or two distinct risk cycles.
Stuck on BSBPMG536 Assessment Help: Manage Project Risk Guide?
Send us your brief. A Australian tutor will explain what the marking criteria are asking for and help you plan your answer. Your first consultation is free.
How to approach each part of BSBPMG536
1. Identify project risks (Element 1)
Set the risk objectives and standards with stakeholder input (PC 1.1), describe the project risk context (PC 1.2), then use valid identification methods (PC 1.3). Name the methods you used, such as a brainstorming workshop, document review of the scope and schedule, checklists from past projects, assumption analysis or expert interviews. Referencing a recognised framework such as AS ISO 31000 Risk management guidelines shows the assessor that your process is structured.
2. Analyse and prioritise risks (Element 2)
Agree a classification and ranking system (PC 2.1), analyse threats and opportunities within your delegated authority (PC 2.2), and confirm priorities with the client and stakeholders (PC 2.3). A five-by-five likelihood and consequence matrix is the most common qualitative tool. Many briefs also ask for one quantitative technique, such as expected monetary value.
| Likelihood (1 to 5) | Consequence (1 to 5) | Score | Rating used in the register |
|---|---|---|---|
| Rare = 1 | Insignificant = 1 | 1 to 4 | Low |
| Unlikely = 2 or Possible = 3 | Minor = 2 or Moderate = 3 | 5 to 9 | Medium |
| Likely = 4 | Major = 4 | 10 to 16 | High |
| Almost certain = 5 | Severe = 5 | 20 to 25 | Extreme |
Use the bands your RTO or case-study organisation specifies, as these vary between templates.
Worked method example (not an answer): In an invented office move project, the risk is "furniture supplier delivers two weeks late". Likelihood is possible (3) and consequence is major (4), so the score is 12 (High). For expected monetary value, if the probability is 30% and the impact is 20,000 Australian dollars in temporary hire costs, EMV = 0.3 multiplied by 20,000 = 6,000 Australian dollars. That figure helps justify spending up to a similar amount on treatment, such as a backup supplier deposit. Apply the method to the risks in your own brief.
3. Treatments, controls and the risk register (Element 3)
Document existing controls (PC 3.1), analyse treatment options with stakeholders (PC 3.2), record and implement agreed treatments (PC 3.3), and update the plan with named owners (PC 3.4). Use the standard four treatment strategies: avoid, reduce, transfer and accept, and for opportunities, exploit or enhance.
| Register column | What to write |
|---|---|
| Risk ID and description | Cause, event and effect in one sentence |
| Category | For example schedule, cost, quality, safety, supplier, stakeholder |
| Existing controls | What is already in place |
| Likelihood, consequence, score | From your agreed matrix |
| Treatment and strategy | Specific action and whether it avoids, reduces, transfers or accepts |
| Owner and due date | A named role, not "the team" |
| Residual rating | Expected score after treatment |
| Review date and status | When it will be checked again |
4. Monitor, control and review (Elements 4 and 5)
Set a review process such as weekly risk reviews in team meetings (PC 4.1), show how a changed circumstance altered a risk (PC 4.2, 4.3) and how you modified the plan (PC 4.4). Then review outcomes at project close (PC 5.1), recommend improvements (PC 5.2) and document lessons learned for future projects (PC 5.3).
Common mistake: Submitting a risk register that never changes. Elements 4 and 5 need evidence that risks were monitored, that at least one change in the environment led to an updated rating or response, and that you reviewed how well risk management worked. Include a version history or meeting minutes to prove it.
How assessors judge BSBPMG536
| What the assessor checks | Satisfactory looks like | Not yet satisfactory looks like |
|---|---|---|
| Context and objectives (PC 1.1, 1.2) | Risk objectives agreed with stakeholders and context described | Jumping straight into a list of risks |
| Identification (PC 1.3) | Named, valid methods and a range of risk categories | Only obvious risks with no method |
| Analysis (PC 2.1 to 2.3) | Agreed matrix applied consistently, threats and opportunities, priorities confirmed | Ratings with no explanation |
| Treatment (PC 3.1 to 3.4) | Specific treatments with owners and residual ratings | Vague actions like "monitor closely" |
| Monitoring (PC 4.1 to 4.4) | Review process and evidence of updates after change | Static register |
| Review (PC 5.1 to 5.3) | Lessons learned and recommended improvements documented | No closing review |
Want a tutor to check your draft first?
Get clear written feedback on your own work before the deadline: structure, criteria coverage and referencing. Your first 15-minute consultation is free.
Pre-submission checklist
- Risk management plan states objectives, context, methods, matrix and roles
- Risks span several categories and include at least one opportunity
- Every risk has an owner, treatment, residual rating and review date
- One qualitative and, if required, one quantitative technique is shown
- Stakeholder input and agreement are evidenced (emails, minutes)
- Register updates show at least one changed circumstance
- Lessons-learned review with improvement recommendations is included
- Evidence covers two occasions or two risk cycles if your brief requires it
Stuck on BSBPMG536? Get a free BSBPMG536 planning template
Our Australian tutors can explain the performance criteria, check your draft against the assessor checklist and give feedback before you submit. You keep full ownership of your work.
BSBPMG536 answer hints and sample structure
There is no answer to copy here, and BSBPMG536 is assessed as competent or not yet competent. This structure shows a sensible effort split for a typical risk management plan and portfolio. Follow your RTO's templates first.
| Section | Suggested share | Linked elements |
|---|---|---|
| Risk management plan (objectives, context, methods, matrix) | About 25% | Element 1, 2.1 |
| Risk register with analysis and treatments | About 35% | Elements 2 and 3 |
| Monitoring evidence and updated register | About 20% | Element 4 |
| Lessons-learned and improvement report | About 15% | Element 5 |
| Stakeholder communication records | About 5% | PC 1.1, 2.3, 3.2 |
Deadline coming up?
Book a 1-to-1 online session today. Tutors are available 7 days a week, 8am–11pm, and usually reply within 2 hours.
Frequently asked questions
What is BSBPMG536?
BSBPMG536 Manage project risk is a nationally recognised unit in the Australian BSB Business Services Training Package. It covers identifying, analysing, treating, monitoring and reviewing risks that may affect project objectives.
Which qualifications include BSBPMG536?
training.gov.au lists it as a core unit in BSB50820 Diploma of Project Management and CPC50320 Diploma of Building and Construction (Management), and as an elective in other diplomas.
How many times must I manage project risk?
The performance evidence requires you to manage project risk on at least two occasions.
What did BSBPMG536 replace?
It supersedes and is equivalent to BSBPMG517 Manage project risk.
What goes in a project risk register?
Risk description, category, existing controls, likelihood, consequence and rating, treatment, owner, residual rating and review date and status.
What is the difference between qualitative and quantitative risk analysis?
Qualitative analysis rates likelihood and consequence on a scale, such as a 5 by 5 matrix. Quantitative analysis uses numbers, such as expected monetary value, to estimate cost or time impact.
Can a tutor check my risk register?
Yes. A tutor can review whether your ratings, treatments and owners are clear and consistent and give feedback, while the register remains your own work.