PM FPX 4060 Assessment 2 Risk Register example

Reviewed by Rupert Danvers, MBA Risk Management in Project Management Capella University Free custom sample in 24 to 48h

This PM FPX 4060 Assessment 2 sample paper is a risk register for the veterinary hospital relocation that defines its probability and impact scales before giving any risk a score. It belongs to Capella PM FPX 4060, Risk Management in Project Management, which students in the BS in Business, Project Management take as PM-FPX4060. The paper expresses impact in project terms such as days of delay and dollars, and puts an owner on every row. It explains the ranking rather than just listing it and handles low-probability, high-severity risks deliberately. It covers how scores will change, who scored the risks, the limits of a qualitative assessment and a review date on each entry.

CoursePM FPX 4060 Risk Management in Project Management
AssessmentAssessment 2
Paper typeRisk register
LengthAbout 1,110 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramBS in Business, Project Management
UpdatedSeptember 2026

Free sample paper for PM FPX 4060 Assessment 2

1

Assessing Risks on a Veterinary Hospital Relocation: Scales Defined Before Any Score, Impact in Project Terms, an Owner on Every Row, Ranking Explained, Low-Probability High-Severity Risks Handled, and a Review Date on Each Entry

Student Name

Capella University

PM FPX 4060: Risk Management in Project Management

Instructor Name

Month Day, Year

What this part is doingThe title names the assessment and its features. Risk assessments are judged on whether scores mean something, so the scales lead.
2

The Scale Defined Before Any Score

Probability is scored from 1 to 5: 1, under 10%; 2, 10% to 30%; 3, 30% to 50%; 4, 50% to 70%; 5, over 70%. Impact is scored from 1 to 5 on whichever of three dimensions is worst. Schedule: 1, less than one week; 2, one to two weeks; 3, two to three weeks, using the buffer; 4, more than three weeks but opening still by June 1 with lease extension; 5, opening after June 1. Cost: 1, under 5,000 dollars; 2, 5,000 to 15,000; 3, 15,000 to 40,000; 4, 40,000 to 85,000, exceeding contingency; 5, over 85,000, requiring management reserve. Patient care: 1, no effect; 2, minor inconvenience to clients; 3, some appointments rescheduled; 4, surgeries canceled or services unavailable for days; 5, practice unable to see patients. Risk score is probability times impact, from 1 to 25. The Project Management Institute (2017) describes probability and impact matrices with defined scales as the basis for qualitative prioritization; defining the scales first makes scores comparable. A score of 4 means nothing until someone says 4 of what.

What this part is doingProbability and impact scales are defined with thresholds. Scorers reward assessments that fix scales before scoring.
3

Impact Expressed in Project Terms

Each risk's impact is stated in the scale's terms. R1, hidden conditions in the rear area: cost 20,000 to 35,000 dollars, impact 3; schedule one to two weeks, impact 2; overall impact 3. R4, lease extension refused: patient care impact 5 if the move is late. R5, associate veterinarian resigns: patient care impact 3, with appointments reduced for several weeks. R3, X-ray detector delayed: schedule impact 1 at current float; patient care impact 2 if training is shortened.

The Register With Scores

R1, hidden conditions: probability 4, impact 3, score 12. Owner: general contractor's superintendent, reporting to the project manager. Review: every site meeting until the rear area is opened. R4, lease extension refused: probability 2, impact 5, score 10. Owner: project manager. Review: January 23, when the sponsor decides on the extension offer. R2, late final inspection: probability 3, impact 3, score 9. Owner: architect. Review: March 15. R5, veterinarian resigns: probability 2, impact 3, score 6. Owner: practice owner. Review: monthly. R11, physicist scheduling conflict: probability 2, impact 3, score 6. Owner: project manager. Review: February 1, after the physicist is booked. R7, neighbor complaint: probability 2, impact 2, score 4. Owner: practice owner. Review: closed if no complaint by construction start. R3, X-ray detector delay: probability 3, impact 1, score 3. Owner: project manager. Review: when the vendor confirms the ship date. R9, clients not informed: probability 3, impact 1, score 3. Owner: client service supervisor. Review: after the 30-day notice. R10, equipment price rise: probability 1, impact 2, score 2. Owner: project manager. Review: closed once all orders are confirmed. R6, project manager absence: probability 1, impact 3, score 3. Owner: practice owner. Review: monthly. R8, controlled substance discrepancy: probability 1, impact 4, score 4. Owner: practice owner. Review: two weeks before the move.

Ranking Explained, Not Just Listed

The ranking puts R1, hidden conditions, first because it is likely and would consume most of the remaining contingency. R4, the lease, is second despite a probability of 2 because its impact is the most severe on the scale: no place to see patients. R2, the inspection, is third because it sits on the critical path. R3, the X-ray delay, ranks low because float absorbs it; if the delay grows beyond seven weeks, its impact rises and the score will change.

What this part is doingThe reasons behind the top-ranked risks are stated. Scorers reward rankings that are explained.
4

Low Probability, High Severity Handled

Two risks score low on the product but carry severe consequences, and they are not left at the bottom. R4, the lease, has impact 5 and is treated as a top-three risk regardless of its score. R8, a controlled substance discrepancy during the move, has probability 1 but could trigger a regulatory report and investigation. Both are flagged for response planning even though their scores are moderate. A rule is set: any risk with impact 5 on any dimension receives a planned response regardless of probability. Multiplying probability by impact hides the risks that are rare but ruinous.

How Scores Will Change

Scores are expected to change as the project moves. R1 will fall sharply once the rear area is opened and inspected, whatever is found, because uncertainty will turn into known cost. R4 will fall to near zero if the landlord signs the option. R9 will rise in April as the notices go out and the practice learns how many clients have outdated contact details. Updating scores at each review keeps the ranking tied to the current state of the project rather than to what was known in January.

Who Scored the Risks

Scores were set in a 45-minute session with the project manager, owner, architect, and contractor's superintendent. Each person scored independently first, and differences of more than one point were discussed. The largest disagreement was on R1: the superintendent scored probability 4 based on the building's age, while the owner scored 2, trusting the pre-purchase inspection. After the superintendent explained that the inspection did not open walls, the group agreed on 4.

Limits of a Qualitative Assessment

Qualitative scores rank risks but do not estimate the total exposure precisely. For the top risk, R1, the contractor's range of 20,000 to 35,000 dollars provides a rough quantitative estimate; comparing it with the remaining contingency of 43,300 dollars shows that one large finding could use most of it. A full quantitative analysis is not warranted for a project of this size, but the top risks' cost ranges are recorded so the sponsor can see the dollars behind the scores.

A Review Date on Each Entry

Each risk has a review date or a trigger for review. Risks tied to events, such as the rear area being opened or the physicist being booked, are reviewed at that event; others are reviewed monthly. Closed risks are marked closed with the date and reason, and they stay in the register so that the closeout review can see which risks occurred, which did not, and how accurate the scores were.

Conclusion

With scales defined first and impact expressed in schedule, cost, and patient care terms, the register scores eleven risks, gives each an owner and review date, ranks hidden conditions, the lease, and the final inspection highest, and handles low-probability, high-severity risks with a rule that any impact 5 risk receives a response.

5

References

Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th ed.). Project Management Institute.

PM FPX 4060 Assessment 2 instructions, in plain terms

Assessment 2 in PM FPX 4060 has you analyze and record the risks identified in Assessment 1. You define probability and impact scales in terms another person could apply, score each risk, calculate a priority, rank the risks and explain the ranking, assign an owner and set a review date for each entry. Risks with low probability but severe impact need separate attention, since a simple score can hide them. The register should say who scored the risks and what the limits of the method are. Risk management texts and the PMBOK Guide on qualitative risk analysis support the work.

Inside the PM FPX 4060 Assessment 2 example

The example puts the scales before the scores, which is the ordering decision that carries the deliverable. The opening block states the project and the source of the entries, briefly, then the legend defines each level of probability and each level of impact in language a second person could apply to the same list and reach similar numbers. The register follows, sorted by score rather than by the order the risks were found. Rows near the top get a paragraph each in the analysis section underneath, where the reasoning behind the two numbers is made explicit. A separate block handles entries that scored low but would be severe if they landed, since rank alone hides them. The document ends with tolerance: what level of exposure the project accepts without action and what level forces a response. Every column heading is defined somewhere.

Where the marks sit in the PM FPX 4060 Assessment 2 scoring guide

Marks in this assessment go to the scales, the scores, the ranking, the owners, the treatment of severe risks and the review. Scales reach Distinguished when each level is defined in project terms before use, such as "high impact means more than two weeks of delay or more than ten thousand dollars." Scores score higher when consistent with the definitions. The ranking earns credit when explained, not just sorted. Owners are judged on whether each is a role that can act. Low-probability, high-severity risks should be flagged. Review dates should be set. Distinguished registers can be scored the same way by a second person.

PM FPX 4060 Assessment 2 help from the desk

Risk registers often use high, medium and low without defining them, so two people would score the same risk differently. Another weakness is expressing impact in general terms rather than days or dollars. The ranking is a sorted list with no explanation. Owners are missing or assigned to the project manager for everything. Rare but catastrophic risks sink to the bottom because their score is low. Review dates are absent, so the register goes stale. A legend defining each scale level, followed by the register with score, rank, owner and review date, makes the analysis repeatable and prepares for the response plan in Assessment 3.

Get a PM FPX 4060 Assessment 2 example written to your instructions

Send the Assessment 2 instructions and the scoring guide from your PM FPX 4060 courseroom, plus the risks you identified earlier and any register template your section provides. We build a custom example to those criteria, with defined scales and scores that survive checking, and return it in 24 to 48 hours. First one at no charge. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.

More PM FPX 4060 papers and BS in Business, Project Management samples

PM FPX 4060 Assessment 2 questions, answered

Do I need a numeric scale or will qualitative ratings do?

Either can work if the levels are defined. A five point numeric scale is common because it multiplies cleanly into a score, but a qualitative scale is acceptable when each band states what it means in weeks, dollars or scope. What fails is an undefined label. Read your instructions, since some sections specify the scale and the matrix shape.

Where do the probability numbers actually come from?

From something you can name: comparable projects, vendor performance history, the experience of the people interviewed, or a stated assumption when nothing better exists. Faculty are not checking whether a figure is correct, since nobody can know that in advance. They are checking whether the number has reasoning behind it and whether the register says what that reasoning was.

Should responses appear in the register at this stage?

A response column is normal in a live register, but in this course the response work usually belongs to the next assessment, where each strategy gets argued rather than named. Follow your own instructions. If a response column is required here, keep the entries short and save the justification, the trigger and the residual exposure for the deliverable built to carry them.

Where can I find a free PM FPX 4060 Assessment 2 sample paper?

This page presents the scored register for the hospital move, with scales defined before any score, impact in project terms, an owner on every row, the ranking explained and a review date on each entry.

Why define scales before scoring in PM FPX 4060 Assessment 2?

Without definitions, "high" means different things to different people and scores cannot be compared. Defining each level in days or dollars makes the ratings consistent.