A risk review is a short meeting whose output is a change to next week's work. For teams delivering across Pretoria, Johannesburg, and Midrand, the review has to end with an owner and a date, or the risk sits in a spreadsheet while the work moves on without it. Most registers fail quietly. Someone updates them before a steering committee. They grow. The next week's plan looks the same when people leave the room. The review felt responsible. Delivery did not get safer.

The point of the review is a decision. If the plan looks the same at the end, you held a reading group. The people on the call from another city will have given up an hour and gained a longer list.

Twenty-five minutes, and a change to the plan

Keep the top risks only: the ones that can move the date, the cost, or adoption. Each one has an owner who is in the room or on the call, including an owner who is in a different city from the meeting. The output is one of three things. A task on the board. A decision the sponsor must make. Or a conscious choice to carry the risk, written down so it is not rediscovered next month.

  • Open with what changed since last time, not the full list.
  • Give each live risk one owner, a person who can act this week in Pretoria, Johannesburg, or Midrand.
  • Leave with fewer open items than you started, or a written reason you did not.
  • Put the action where the team already looks, before the call ends.

Twenty-five minutes is long enough if the list is short. It is too short if the register still holds every theoretical worry from the kickoff. Archive the items nobody is willing to act on. A carried risk with no owner is a sentence. A carried risk with an owner and a review date is a decision.

Name risks the way this corridor delivers

Some risks are universal. A key person leaves. A vendor slips. Scope grows because a stakeholder arrived late. Some show up more often when the work runs between Pretoria, Johannesburg, and Midrand. Put those on the register when they are real for this project. Leave off the generic list inherited from a template. A register full of theoretical risks hides the two that can slip the go-live.

Access to a Midrand site that is only practical on certain days can move a date if the work needs that building. A month-end freeze with a finance team in Johannesburg can move a date if the next release needs their sign-off in that window. A workshop you only booked once, in a Pretoria boardroom at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157 or in Centurion, can disappear because a diary or a power cut moved, and the Midrand and Johannesburg people had no second slot.

A blocker can also sit unseen when the person who sees it is in Johannesburg and the person who can remove it is in Pretoria. Put both names on the card, and write the early sign that would move the risk onto the board.

Separate what you are watching from what is already late

A risk is something that might happen. An issue is something that has. Teams mix them and then debate labels while the week slips. If it has happened, it belongs on the board as work, with a date. The register keeps the things you are still trying to prevent, and the early signs that prevention is failing.

That split keeps the review short. Issues get done. Risks get watched, with a trigger that would move them onto the board. "Vendor has not confirmed by Wednesday" is a trigger. "Vendor risk" is a mood. The trigger should be checkable by someone specific, whether they are at a desk in Pretoria or on a site in Midrand.

A trigger you can test on Wednesday

Write the trigger as a fact a person can check without a meeting. A confirmation email by Wednesday. A training seat booked for the Johannesburg group. An access window confirmed for the Midrand building. If Wednesday comes and the fact is missing, the item moves onto the board the same day. Waiting for the next monthly risk review is how a trigger becomes a surprise at steerco.

An issue that belongs on the board

Once the trigger has fired, stop calling it a risk. Give it an owner and a date, and let the next delivery cycle absorb it. A Pretoria register that still lists a problem the Midrand team is already living with will teach both cities to ignore the register.

Keep the review where the team already looks

A register in a folder nobody opens will rot, especially when the folder lives on a drive that the Johannesburg and Midrand people do not open. Link each live risk to a line on the sponsor dashboard the team sees in the week. The sponsor sees the few items that need them, whether the steerco is in Johannesburg, Midrand, or on a call back to Pretoria. Everyone else sees the action.

That is how a risk review keeps delivery moving. It changes the plan for next week, in every city that has to carry the work. It does not pause delivery for an hour of archaeology through a spreadsheet that grew because nobody was allowed to close a line.

MetaServ's risk work runs these reviews with the people who own the work, in the office or on a call, and leaves the register smaller than we found it. The approach is to tie each live risk to an owner, a date, and the plan. We are based at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157. We facilitate reviews on-site with teams in Pretoria, Johannesburg, and Midrand, and remotely when the owner of the risk is on the line from another city.

If the register is longer than last month and the plan is unchanged, talk to MetaServ about the review. Bring the top five lines. That is the meeting.

Frequently asked questions

What should Midrand keep in view for risk reviews that keep delivery moving?

A risk register that only grows is a diary. A short review with an owner and a date is what keeps delivery honest for teams in Pretoria, Johannesburg, and Midrand.

What else should a Midrand reader take from risk reviews that keep delivery moving?

A short review with an owner and a date is what keeps delivery honest for teams in Pretoria, Johannesburg, and Midrand.

Does risk reviews that keep delivery moving need a trip to the Centurion office every time?

No. Risk management for this note runs from 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157, on-site or on a call, for teams in Pretoria, Midrand, and Johannesburg.