Monitoring and controlling is not a phase you start when someone is nervous. It runs beside execution: compare performance to the baseline, decide whether the gap is noise or a decision, and change the plan only on purpose. If the register and the baseline only move during a crisis, you are doing incident management with extra columns.
Monitor is seeing. Control is acting.
Monitor and control project work means collecting performance data, comparing it to the plan, and recommending corrective or preventive action. Seeing a slip and writing 'noted' is monitoring. Changing resource, sequence, or scope through the proper path is control. One without the other is a weather report.
Control processes exist for scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement because each baseline and plan can drift independently. A green schedule next to a bleeding cost line is not 'mostly fine.' It is two stories, and someone will pick the cheerful one.
Validate scope is acceptance of deliverables, not a vibe in a demo. Control scope is keeping the approved scope the approved scope. Teams that skip formal acceptance discover at close that 'everyone liked it' is not a signature.
Integrated change control is the spine
Perform integrated change control is where requests are reviewed against the whole baseline — scope, schedule, cost, quality, risk — and approved, deferred, or rejected by the right authority. A change approved in a corridor is how you get two baselines and one argument.
Configuration and version matter. If nobody can say which specification the team is building, control is already lost. The change log is the audit trail for the inevitable 'why did this take longer?' conversation. Memory is not a configuration system.
Thresholds should be set in planning: what the PM can approve, what the sponsor must see, what needs the steering group. Inventing the threshold when the request arrives is how seniority becomes the process. That process always approves the last person who spoke.
Intervene on a trigger, not a feeling
Decide in advance what 'off' means: a variance threshold, a missed leading indicator, a risk trigger. Then look on a cadence that matches the project's pulse. Weekly for short, high-change work. Fortnightly if you can honestly claim calm. Monthly is how surprises mature into press releases.
Corrective action repairs a deviation that has already happened. Preventive action reduces the chance of one that has not. Both are changes to how you work and should be treated as such. 'We will try harder' is neither. It is a slogan with a burn-down chart.
Escalate residual performance that no longer fits your authority. A forecast that now threatens the business case belongs with the sponsor, with options, before the milestone is already missed. Late honesty is still a status surprise. Early honesty with a recommendation is the job.
Summary & next steps
Monitoring compares work to the baseline. Control acts — including integrated change control with a named authority. Use triggers and a standing cadence. 'Noted' is not a control action.
Next: Closing processes — formal acceptance, handover, and the lessons that do not die in a folder called Final_v3.