Set up a project and hand it over
Take a job from the very first setup right through to handover. Create it, price the work,…
Walk the risk register on a regular cadence, score likelihood and impact honestly, and assign a mitigation owner before a risk turns into a real problem.
3 steps across the platform - what you do at each one, and why it matters.
Go through every open risk on the register, re-score its likelihood and impact against what you now know, and retire anything that has genuinely passed.
Why: A risk register nobody revisits just accumulates stale entries and hides the two or three that actually matter this month.
For every risk still live, name the mitigation action, its owner and a date, rather than leaving it as a description with nobody accountable for it.
Why: A risk with no owner and no date is a risk that sits there until it happens. Assigning both is what actually reduces the chance it does.
Report how the register has moved since the last review, new risks in, old ones retired or realised, so the wider team sees the trend, not just a snapshot.
Why: A single risk review tells you where you stand today. The trend across several is what tells you whether the project is getting safer or more exposed.
2 / 184 platform modules
Take a job from the very first setup right through to handover. Create it, price the work,…
Plan the programme, freeze a baseline to measure against, feed real progress back from site…
See where the job truly stands against the plan and the budget: bring the programme current…