This manual is for PM-FPX4060 Assessment 1, start to submission. The first thing graded here is the distinction most drafts blur, which is that a risk has not happened and an issue has. The assessment usually asks you to state how much variation the organization will accept on each objective, identify risks by more than one method, and write each entry so it contains a cause, an uncertain event and a consequence somebody could price. Your scoring guide decides whether that arrives as a risk management plan, a register with commentary, or an identification memo for a sponsor. Below: the method, a structure that answers the criteria one by one, and a sample excerpt with notes. Prefer to hand it off? A premium original sample is delivered inside 24 to 48 hours, revised free until nothing sits below the top column. Your courseroom may print this as PM FPX 4060 Assessment 1 or PM4060 Assessment 1; it is the same deliverable, and PM-FPX4060 Assessment 1 is what this manual walks through.
One honesty note before the manual: Capella revises courses and scoring guides over time, so always write to the exact scoring guide attached to your assessment in the courseroom. The course identity above is verified on capella.edu; the method and structure below are our tutors' approach to it, not Capella's official rubric text.
How PM-FPX4060 Assessment 1 is scored
Criteria are graded separately, and on an identification deliverable the four levels turn on whether the entries are entries at all:
| Level | What it means on a risk identification and register |
|---|---|
| Distinguished | Tolerance is stated per objective, every entry carries a cause that is true today, an uncertain event and a priced consequence, and the identification draws on assumptions, dependencies and comparable past projects rather than one brainstorm. |
| Proficient | A complete register of well-formed entries. Each one names an uncertain event, and nothing in the document says how much variation the organization would accept. |
| Basic | A list of one-word categories: weather, staffing, vendor. Accurate as a set of headings and impossible to own, price or monitor. |
| Non-performance | A required element is absent, or the register contains events that have already happened, which is a status report and gets marked as one. |
Read every entry aloud with the word may inside it. If the sentence still makes sense it is a risk. If it sounds absurd because the thing already occurred, it belongs in an issue log with an owner and a resolution date, and if it matters you can add the separate risk that the issue is not resolved in time.
The PM-FPX4060 Assessment 1 method, step by step
-
Write the tolerance down before the first entry
The same event deserves mitigation in one organization and acceptance in another, so say how much variation the sponsor will take on cost, on schedule and on service. Without that line no response decision in the document has anything to be measured against, and the criteria notice.
-
Identify by four routes, not by one sitting
Test your own assumptions, look through the schedule for activities with one qualified person and no slack, read what went wrong on comparable projects, and ask the people doing the work rather than the people planning it. A register produced by a single brainstorm has the shape of one afternoon's thinking.
-
Build each entry in three parts
Cause is something true today, event is the uncertain thing, consequence is what it does to cost, schedule, quality or reputation. That structure does immediate work: the cause tells you where a preventive response goes, the event tells you what a trigger should watch for, and the consequence tells you what figure belongs in the impact column.
-
Test each entry for a second reader
Ask whether somebody else reading only your sentence would estimate roughly the same probability and the same cost. If they would not, the entry is still a category with a longer name. This test takes seconds and removes most of the weak lines in a first draft.
-
Separate the register from the issue log in the document
Two artifacts, two purposes. Risks carry probability and a trigger, issues carry an owner and a resolution date. Mixing them costs marks twice, because the risk criterion sees entries that are not risks and the monitoring criterion sees no evidence anything is being tracked forward.
-
Include the opportunities, then submit
Uncertainty runs both ways and most guides ask for both, so write down the favourable events too: a supplier with spare capacity, a module another team has already built, a quiet fortnight in the receiving department. Then mark yourself against every descriptor and submit while a second attempt still fits.
A structure that maps to the criteria
Ranges our tutors use for an identification deliverable with a tolerance section; where the guide asks for a full plan, the process and roles sections take some of these words.
| Section | What it must do | Guide |
|---|---|---|
| Project and objectives | What the project delivers and the objectives that any risk will be measured against. | ~200 words |
| Risk tolerance | How much variation the organization accepts on each objective, stated in figures or days. | ~200 words |
| Identification methods | The four routes used, what each produced, and what the method could still have missed. | ~250 words |
| The register | Entries in cause, event and consequence form, with an initial impact figure against each. | ~400 words |
| Opportunities | Favourable uncertainties written in the same three-part form, with the value each would release. | ~200 words |
| Issue log and references | What has already happened, separated out with owners and dates, plus current APA both ways. | ~200 words |
Annotated sample excerpt
Two register entries and one tolerance line from an original model our team wrote, printed as they would appear in the artifact.
Tolerance: the board will accept up to two weeks of schedule variance on the move and no interruption at all to next-day order despatch, which makes despatch continuity the objective every response in this register is judged against.1 Entry 4: because the mezzanine racking permit was lodged on the twelfth of June and the authority's published turnaround is 30 working days, the racking install may not be permitted before the current lease ends on the eighth of August, which would force a third-party overflow store at about 9,400 dollars a month.2 Entry 9, an opportunity: because the outbound carrier has two unused bays at the new site until October, the pick line may be commissioned a fortnight early, which would release roughly 6,300 dollars of double-running cost and is worth a call to the carrier this week rather than a note in the register.3
- 1Tolerance stated per objective, with one objective named as the binding one. Every later response decision now has something to be weighed against.
- 2Cause, event and consequence in one sentence, with dates that are true today and a monthly figure a second reader could check.
- 3An opportunity written in the same three-part form with a value and an action. Registers that carry only threats answer half of what most guides ask for.
The full premium sample for your exact assessment, written fresh to your scoring guide and issue, is free to request. Study it, revise it into your own voice, and submit work you understand.
The five mistakes that cost Distinguished
- Risks written as one-word labels. Weather, haulage or permits names a family of risks rather than one of them, and a family cannot be owned, priced or watched.
- Issues filed as risks. An event that has already happened has a probability of one, and putting it in the register makes the register a status report.
- No tolerance anywhere. Without a stated appetite there is no basis for deciding which risks deserve money, which is the decision the rest of the course is about.
- Identification by one brainstorm. Assumptions, dependencies and comparable projects each surface risks a single meeting does not, and most guides ask which methods you used.
- Threats only. Uncertainty runs in both directions, and a register with no opportunities has left the favourable half of the criterion unanswered.
Pre-submission checklist
- Tolerance stated for each objective in figures or days
- At least four identification methods used and named
- Every entry carrying a cause true today, an uncertain event and a priced consequence
- Each entry tested against the second-reader question before it stayed in
- Issues separated into their own log with owners and resolution dates
- Opportunities recorded in the same form, self-scored against the descriptors, submitted early in the week
Risk register or identification section due?
Send the scenario and the criteria. We state the tolerance, work four identification routes, and return a premium original sample inside 24 to 48 hours with entries a second reader could price.