SKIL90004 Chap.7 Execution, Monitoring and Control
Execution, Monitoring and Control
Execution produces deliverables, monitoring gathers actual evidence and control compares that evidence with the authorised plan. This chapter builds exception reports from condition, cause, consequence, options and decision authority. It distinguishes corrective action from formal change, risks from realised issues, and sponsor, project-manager and team responsibilities inside one feedback loop.
Monitoring cadence must leave time to act and each indicator needs a source, cut-off and owner. Control does not mean restoring every variance automatically: the team diagnoses the condition, compares responses and escalates commitments that require approval. After a decision, linked schedule, budget, risk and quality records must agree, while superseded forecasts remain available for learning and later effectiveness review.
What this chapter covers
- 01
Execution coordination
- 02
Monitoring evidence
- 03
Baseline comparison
- 04
Exception reporting
- 05
Corrective action
- 06
Change control
- 07
Issue management
- 08
Roles and decision rights
Worked example · free
Control a slipping validation milestone
- 1State the five-day forecast variance against the baseline.
- 1Identify instrument access as the evidenced cause.
- 1Trace effects on the critical path and presentation evidence.
- 1Compare alternative equipment, resequencing and a revised milestone.
- 1Name the approval owner and decision deadline.
Key terms
- Project baseline
- A Project baseline is the authorised reference used to compare current scope, schedule or cost evidence.
- Corrective action
- Corrective action seeks to return performance toward the approved plan without hiding the variance.
- Exception report
- An Exception report states a threshold breach, cause, forecast consequence, options and decision required.
- Project issue
- A Project issue is a condition that has occurred and requires present management rather than probability assessment.
- Decision right
- A Decision right defines who has authority to approve a particular project choice.
- Responsibility matrix
- A Responsibility matrix clarifies delivery, accountability, consultation and information roles for work or decisions.
Execution, Monitoring and Control FAQ
What is the difference between monitoring and control?
Monitoring gathers evidence about current and forecast performance. Control compares that evidence with the authorised plan and decides whether corrective action, escalation or formal change is needed.
When should a problem be escalated?
Escalate when a defined threshold is breached or the required action exceeds delegated authority. State the condition, cause, consequence, options, recommendation, owner and decision deadline.
How does a risk become an issue?
A risk describes an uncertain event. Once the event occurs, manage the immediate condition as an issue while updating related risk exposure, responses and lessons.
Exam move
Turn each status scenario into a short exception brief. Preserve the baseline, separate the evidenced cause from symptoms, identify who can decide and state the trade-off in every recovery option. Practise distinguishing actions that restore the plan from changes that alter the commitment and need formal approval.
Use a six-part template only as a completeness check: current condition, evidence and cause, forecast consequence, options, recommendation and decision owner. Populate it with different scientific situations so the reasoning does not become mechanical. For a late critical task, state the baseline and forecast difference, then trace the effect to a milestone and stakeholder decision.
For a quality exception, preserve acceptance evidence rather than accelerating by omission. For a resource conflict, compare resequencing, added capability and a changed commitment. Quantify what the scenario supports and state assumptions where confidence is limited. Match monitoring frequency to the time available to act. A temperature condition may need rapid evidence, while a stable procurement can use a slower cadence.
Name the source, cut-off and owner of each indicator. Distinguish corrective action, which seeks to return performance toward the approved plan, from a change that alters scope, budget, timing or another controlled commitment. Route the second through the stated authority and update linked schedule, budget, risk and quality records after approval. Practise converting a risk into an issue once the event occurs.
Manage immediate recovery and update continuing exposure separately. Review roles using a responsibility matrix, keeping final accountability clear while assigning responsible work, consultation before decisions and information after them. Include deputies for time-critical approvals. Write sponsor reports as decisions, not activity diaries.
State what the team has tried, what options remain and what happens if no choice arrives by the deadline. After a response is selected, assign the effectiveness check and preserve the superseded forecast for later learning. This final step proves whether control changed the condition rather than merely producing another meeting. Review one completed scenario from the recipient's perspective.
Ask whether the named owner has authority, whether the deadline leaves time to act and whether the options are genuinely different. Remove operational history that does not change the decision, but retain assumptions and trade-offs. Then write the return message to the team explaining the decision, controlled-plan update and first review point.
Working through Execution, Monitoring and Control in SKIL90004? Sia is AskSia’s AI Project Management tutor — ask any SKIL90004 Execution, Monitoring and Control question and get a clear, step-by-step explanation grounded in how SKIL90004 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
