Monash University · FACULTY OF PROJECT MANAGEMENT

FIT5057 Chap.4 Risk and Governance

- one subject, every graph, every model, every mark
6 Chapters3-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 4 of 7 · FIT5057

Risk and Governance

Risk and Governance explains how uncertainty becomes owned action inside a clear authority structure. You will write cause-event-effect risk statements, rate probability and impact consistently, choose responses that change exposure, and record residual risk.

Governance distinguishes direction and oversight from daily management, sets tolerances and escalation paths, and supports systems auditing when a visible variance may have several connected causes. A rating helps order attention, but an owner, trigger and treatment are what make a register operational. The chapter therefore asks whether a proposed response changes probability or impact and what exposure remains afterward.

Governance examples show how a project manager verifies evidence and recommends an option before escalating a tolerance breach to the role with authority. The audit section follows a symptom across scope, schedule, resources, risk and quality rather than blaming the nearest person. Original scenarios require a corrective control that addresses the demonstrated weakness and a reviewable condition for closing the finding.

This joined approach supports project auditing and professional judgement because it makes decisions, accountability and residual uncertainty visible. Every escalation still needs a recommendation, not only a notification.

In this chapter

What this chapter covers

  • 01

    Cause-event-effect risk statements

  • 02

    Probability, impact and priority ratings

  • 03

    Threat and opportunity responses

  • 04

    Risk ownership, triggers and residual exposure

  • 05

    Governance authority and escalation tolerances

  • 06

    Systems auditing and corrective controls

Worked example · free

Escalate a schedule tolerance breach

Q [5 marks]. The marks used here are not a published University assessment scheme. A supplier delay is forecast to add nine working days. The project manager may approve up to four days of schedule variance. What should happen next?
Probability rises upward and impact rises to the right; the plotted letters show how multiplying the two ratings moves attention toward the red zone.Probability rises upward and impact rises to the right; the plotted letters show how multiplying the two ratings moves attention toward the red zone.1234526810361215481216510152025ABCImpact increasesProbability increases
Probability rises upward and impact rises to the right; the plotted letters show how multiplying the two ratings moves attention toward the red zone.
  • +1Verify the nine-day forecast, affected milestones, assumptions and current response options.
  • +2Document consequences for cost, scope, quality, stakeholders and risk, then recommend an option.
  • +1Escalate to the authority named for a tolerance breach because nine days exceeds the delegated four-day limit.
  • +1Update the schedule and register after the authorised decision is recorded.
The project manager should present verified evidence and a recommendation to the appropriate sponsor or governance body. The baseline changes only after the decision is authorised.
Sia tip — Escalation is not forwarding a problem. Bring evidence, options and a recommendation to the role with the necessary authority.
Glossary

Key terms

Risk Trigger
An observable condition that signals a risk response or escalation should begin.
Residual Risk
The exposure that remains after the planned response has been applied.
Governance
The system of decision rights, accountability, direction, oversight and escalation for project work.
Tolerance
A delegated limit within which a project role may act without escalating for higher authority.
FAQ

Risk and Governance FAQ

What makes a risk response specific enough?

It names the action, owner, timing or trigger and the exposure it is intended to change. A statement such as monitor closely is incomplete unless monitoring leads to a defined decision or response.

How is governance different from project management?

Governance establishes direction, decision authority, accountability and oversight. Project management plans and coordinates work inside that structure. A manager can recommend a change but cannot approve beyond the authority delegated to the role.

Why should an audit follow more than one artefact?

A visible problem such as delay can originate in scope, estimates, dependencies, resources, risk ownership or late decisions. Following the evidence across connected artefacts helps identify a control gap rather than treating one symptom.

What should accompany an escalation?

Bring the verified condition, affected tolerance or baseline, consequences, feasible options and a recommendation. The purpose is to place a decision with the role holding authority, not to transfer an unexplained problem upward.

Study strategy

Assessment move

Rewrite vague risks into cause, event and effect, then add probability, impact, owner, trigger, response and residual exposure. For governance scenarios, identify the decision, delegated tolerance and role with authority before recommending escalation. Practise systems audits by starting with a variance and tracing upstream assumptions and downstream consequences.

End with a corrective control that would actually detect or reduce the stated weakness, plus a named follow-up owner and review point. Build a small risk register containing one schedule threat, one quality threat and one opportunity. Score all three on the same scales, but also note urgency, proximity and whether a trigger is visible.

Replace generic treatments such as monitor with an action that changes exposure, and recalculate the residual rating after the response. Then create a governance map for one change decision: show who recommends, who approves, who provides evidence and who must be informed. Introduce a tolerance breach and write an escalation brief that includes verified condition, affected baseline, options and a recommendation.

For audit practice, choose a symptom such as a missed quality gate. Trace it backward through resources, dependencies, estimates and ownership, then forward into benefits and stakeholder commitments. Ask whether the proposed control would have detected the actual weakness. This prevents meetings, registers and extra reporting from being offered as solutions without a causal link.

Working through Risk and Governance in FIT5057? Sia is AskSia’s AI Project Management tutor — ask any FIT5057 Risk and Governance question and get a clear, step-by-step explanation grounded in how FIT5057 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 171 of your subjects at Monash University, plus 1,000+ more Bibles across the AskSia library.
Sia - your FIT5057 tutor, unlimited, worked the way the exam marks it
The full 3-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works