# Case: the launch risk register > Take the team's raw forty-line list, sort out the issues, assumptions and dependencies, score the real risks in days or money, add the missing ones, and send Leo the top five with owners, responses and triggers. - Course: [Project Management Without the Bureaucracy: Run One Project from Brief to Closure](https://productovi.com/courses/project-management-without-bureaucracy.md) - Module: Risk and quality - Lesson 24/32, ~36 min - Source: https://productovi.com/courses/project-management-without-bureaucracy/launch-risk-register-case ## Forty lines and no names **Alex Tutor:** Monday, 7 December. You've learned to sort, score and respond. Now do it for real on the list the team wrote last week. **Leo:** Before the holidays I want one page: the five risks that could stop us, who watches each, and what we do. Not forty lines. **Hanna:** And if something costs money, give it in UAH. I can't plan a reserve from "high". **Alex Tutor:** Here are the scales the team agreed, and the raw list exactly as it was written. > **The written scales** > > - **Probability:** rare = 5%, unlikely = 20%, possible = 50%, likely = 80%. "Certain" is not on the scale: a certain event is an issue. > - **Impact in days:** working days of schedule lost if nothing is done. > - **Impact in money:** extra UAH spent against the 600,000 UAH ceiling. > - **Exposure** = probability × impact, compared only within one unit. **Dataset (CSV):** [Physics launch: the team's raw risk list, 1–4 December 2026](https://productovi.com/datasets/project-management-without-bureaucracy/launch-risk-register-case/physics-risk-register-raw.csv) Forty lines collected from Vira, Danylo, Roman, Hanna, Leo and marketing, unedited. Probability and impact are as each author logged them. - `item_id`: Line number in the list - `raised_by`: Who wrote the line - `raised_on`: Date the line was added - `item`: The line as written - `probability`: Probability as logged: rare, unlikely, possible, likely, certain or blank - `impact_days`: Working days of schedule lost, if given - `impact_uah`: Extra spend in UAH, if given - `owner`: Who watches the item (empty everywhere) **Sofia:** Not one line has an owner. And most of these are already happening. **Alex Tutor:** Start there. Sort before you score: which lines are issues, assumptions or dependencies? > **Exercise:** Which of these lines are **issues**, not risks? Select all that apply. ## Score what is left **Danylo:** Nine risks left. Mine first: the contractor, R35, possible, ten days. **Alex Tutor:** Six risks have an impact in days and two in UAH. R34, "something may go wrong with the platform", has no event at all: rewrite it or drop it. **Alex Tutor:** One line has no event at all. What do you do with it? > **Exercise:** R34 reads "Something may go wrong with the platform." What should happen to it? **Hanna:** Score the day ones together and the money ones together. Don't hand me a single number that mixes them. **Sofia:** So the contractor is 0.5 × 10, and Vira's review 0.5 × 7. I'll do all six. > **Exercise:** Add up the exposure of the **six risks scored in days** (R01, R14, R19, R22, R35, R37). In working days. **Alex Tutor:** And the two money risks, scored separately. > **Exercise:** Two risks have an impact in money: R28, ad prices rise (likely, 30,000 UAH) and R21, the test places learners at the wrong level (possible, 24,000 UAH). What is their total exposure, in UAH? ## The bottom of the list **Sofia:** By exposure, R37 comes last: 1.5 days. Five slots, nine risks. I'd cut it. **Hanna:** Read the line again. If the provider holds the account, nobody pays for anything, physics or English, for weeks. In February. **Alex Tutor:** Ask the second question: if it happens, can we still open, or still reach 120 learners? For R37 the answer is no. It stays. **Leo:** Agreed. I'd rather spend an hour now on a second payment route than lose February to one email from the provider. > **Exercise:** R37 says the payment provider may hold Klasna's account while it reviews a new product line: rare, 30 days, exposure 1.5 days, the lowest of the nine risks. If it happens, nobody can pay for any package, physics or English, for weeks in February. Leo's page has room for five risks. What should happen to R37? ## What the list forgot **Vira:** Read it as a tutor on a February evening. What isn't here? **Sofia:** Nothing about outages or alerts during live lessons. Nothing about evening slots filling up, though Roman warned us tutors are free only in the evenings. **Alex Tutor:** The most dangerous risks are often the ones that feel like normal life. Add both as full rows: cause, event, consequence, scored on the same scales. **Danylo:** Outages I can't fix in code. But a lesson cut by an alert can be moved, if the booking rule says so. > **Exercise:** Which real risks are **missing** from the raw list? Select all that apply. ## Quality in the register **Danylo:** R21 is mine too: the test may place learners at the wrong level. 24,000 UAH of refunds and tutor switches if it happens. **Vira:** And R10 says the test still has 40 questions instead of 60. That issue feeds this risk. **Alex Tutor:** Then the response is quality built in, not a refund budget. Fix R10 this week, and check the test on a few real learners before families see it. **Sofia:** So R10 goes to the issue list with Danylo as owner, and R21 stays in the register with a quality response. > **Exercise:** R21: the diagnostic test may place learners at the wrong level, costing 24,000 UAH of refunds and tutor switches. The list also has an issue, R10: the test still has 40 questions, while the agreed spec says 60. Which response to R21 builds quality into the work? **Alex Tutor:** Last: what does the page say about the other lines? > **Exercise:** Leo's page shows the top five risks. What should it say about the other thirty-five lines of the raw list? ## One page for Leo **Leo:** Now the page. Five risks, each with who, what we do and what tells us it's starting. I'll read it on my phone. **Alex Tutor:** Say in one line what you did with the other thirty-five lines, then the five rows. Scales on the page, units on every number. **Vira:** And one line on how we keep it alive after the holidays. **Sofia:** Fifteen minutes in every Wednesday status. Close what's passed, add what's new. > **Exercise:** Write the one-page risk summary Leo asked for: the top five risks with owners, responses and triggers. > **Key points** > > - Sort before you score: in the raw list only 9 of 40 lines (22.5%) were risks; the rest were issues, assumptions and dependencies, and nobody owned anything. > - Score on written scales and keep units apart: 17.0 days of exposure across six day risks, 36,000 UAH across two money risks. > - Rank by exposure, then keep anything that would stop the opening or the result, like the provider hold at 1.5 days. > - Add what the list forgot: outages, alerts and evening slots are ordinary inputs for evening lessons. > - Each top risk: one owner, one concrete response, one trigger with a date and a number, reviewed every Wednesday. **Alex Tutor:** Risk and quality stage done. In January the work runs at full speed, and one of these triggers is going to fire. - Previous lesson: [Risk responses, the pre-mortem and built-in quality](https://productovi.com/courses/project-management-without-bureaucracy/responses-premortem-quality.md) - Next lesson: [Changes without a committee, and a decision log](https://productovi.com/courses/project-management-without-bureaucracy/changes-without-a-committee.md) --- Productovi Learning. Free, no sign-up needed to read.