E057 Risk Management and Contingency Planning, catalog number PJMG 2110, is the three-competency-unit course where WGU asks you to be specific about what could go wrong. The scored work is a risk register with categorized entries, each rated for likelihood and impact, prioritized against the others, and answered with a response that somebody could actually execute. The discipline is harder than it looks because most students write risks that are too vague to rate. A risk you cannot score is a risk you cannot prioritize, and a risk you cannot prioritize produces a contingency plan with nothing behind it.
What PJMG 2110 is actually testing
A usable risk statement has three parts: a cause that exists today, an uncertain event, and a consequence for the project's objectives. Write only the middle part and you get entries like "delays" or "budget overrun", which describe an outcome rather than a risk and cannot be rated. Write all three and the same idea becomes something like: because the vendor's contract has not been signed, delivery of the server hardware may slip past week nine, which would push the integration activities and delay the go-live milestone. That version can be rated, owned and answered.
The rating half tests judgment under uncertainty. Likelihood and impact are both estimates, and the course rewards students who define their own scale in writing before they use it. A five-point scale where a 4 means "more likely than not within this project's timeframe" is defensible. The same 4 with no definition is a number an evaluator cannot check. The scale itself is usually worth writing out in a small table before the register begins.
The response half tests whether you can match strategy to situation. Avoiding, transferring, mitigating and accepting are not interchangeable, and each carries a cost. Accepting a risk is a legitimate choice when the cost of response exceeds the exposure, but the acceptance has to be stated as a decision with a trigger for reconsidering it, not implied by silence. Submissions that mitigate every single entry read as students following a formula rather than exercising judgment.
Turning scored aspects into a register plan
Scoring detail for E057 sits in your Course of Study, not in the public catalog. Read it before you write a single risk. Each aspect is scored independently on a three-point scale, a 2 in each aspect passes the task, and nothing averages across them. In a register-based deliverable this often means the artifact and its accompanying analysis are separate aspects, and it is entirely possible to build a strong register that fails on an unwritten justification.
Where your course is assessed by performance assessment, treat the aspect list as the section list. Risk deliverables tempt students to organize by risk category, which buries the scored reasoning inside a table and leaves the analytical aspects looking unanswered.
The word budget, worked. Take a rubric with five scored aspects and directions asking for roughly 1,800 words alongside the register itself. Spend 140 words defining your rating scales, because that pays for itself in two later aspects, and hold 120 for a closing statement about monitoring. The remaining 1,540 across five aspects is about 300 words each. Then shift weight: the aspect on prioritization reasoning usually deserves 400, and the aspect that simply asks you to categorize risks rarely needs more than 200.
Watch the register length separately. Twenty-five thinly written risks score worse than ten written properly, because each entry has to carry cause, event, consequence, rating, owner and response. If your register would run to forty rows, you are cataloguing the world rather than analyzing this project.
A structure that fits a risk deliverable
Risk work almost always pairs a table with a written analysis. Your task directions rule wherever they specify a format. Where they do not, this arrangement keeps the scored reasoning outside the table where an evaluator can find it.
| Section | What belongs in it | How it tends to be scored |
|---|---|---|
| Scope of the assessment | The project, the phase you are assessing and what you excluded | Frames the register; without it the entry set looks arbitrary |
| Rating scales | Defined likelihood and impact levels, in words, before any rating happens | Underpins two or three later aspects at once |
| Identification method | How the risks were surfaced: breakdown structure review, checklist, stakeholder input | Scored for method rather than volume |
| Risk register | Cause, event, consequence, category, likelihood, impact, score, owner, response | Checked for completeness of each row, not the number of rows |
| Prioritization | Why the top entries are the top entries, with the scoring made visible | The reasoning aspect; a sorted table is not an argument |
| Response plans | Chosen strategy per priority risk, with the action, owner and cost | Scored for executability by someone other than you |
| Contingency and triggers | What is held in reserve, and the observable signal that releases it | Scored for having a trigger at all; most drafts omit it |
Triggers are the cheapest points in the course and the most frequently missing. A contingency plan without a trigger is a document nobody will ever act on, because no one knows when to start.
Evidence craft in a risk deliverable
Risk analysis is built on estimates about events that have not happened, which makes the sourcing question sharper than in a costing course, not softer.
- Ground causes in the scenario. Every risk should trace to something stated or reasonably inferable from the brief, and the trace should be visible.
- Justify the ratings you assign to the top few risks in prose. A number in a cell is a claim; the sentence beside it is the evidence.
- Quantify impact where the scenario permits. Days of delay or a cost figure beats the word "high" in almost every case.
- Cite any framework or category taxonomy you adopt, in APA, where the rubric asks for citation.
- Separate risk from issue. Something already happening is an issue and belongs in a different conversation; putting issues in the register signals a definitional gap.
- Name secondary risks. A response that introduces a new exposure, such as transferring work to a subcontractor, should say so.
The strongest risk submissions include at least one positive risk. Opportunity handling sits inside serious risk practice, and a register composed entirely of threats reads as a partial understanding of the discipline.
What separates Competent from a returned risk task
Everything at WGU resolves to Competent or Not Competent, with no letter grades and no ordinary grade point average. Performance assessment work can be revised and resubmitted without a grade penalty, so a return costs days rather than standing.
Risk deliverables that pass on the first read share a short list of traits:
- Every register row states a cause, an event and a consequence rather than a one-word hazard.
- Likelihood and impact scales are defined before they are used, and the definitions are applied consistently.
- Each priority risk has a named owner who is a role in the scenario, not the project manager for all of them.
- Response strategies vary, and at least one acceptance is defended rather than defaulted to.
- Contingency amounts and triggers connect to specific register entries rather than sitting as a lump.
- The analysis reaches conclusions about this project instead of restating general risk theory.
Where a proctored objective assessment forms part of your plan for this course, the rule does not bend. Proctored exams are yours to sit. We build the study plan, drill definitions and scoring methods, work practice problems and give an honest readiness verdict. We do not sit assessments and we never ask for portal credentials.
Six mistakes that send E057 tasks back
- Writing consequences as risks. Delay and overrun are effects. Without a cause and an uncertain event in front of them, they cannot be rated.
- Rating without a scale. Numbers in cells that no one defined are unverifiable, and every downstream prioritization inherits the problem.
- Mitigating everything. Uniform response strategy is the clearest sign that judgment was replaced by pattern.
- Assigning every owner to the project manager. Ownership means the person who can actually act on the cause.
- Omitting triggers. Contingency with no release condition is theatre, and it is a fast, avoidable loss.
- Padding the register. Forty shallow rows take longer to write and score worse than twelve complete ones.
How support works on this course
Risk tasks fail on entry quality more than on anything else, and entry quality is fixable in an afternoon. Send the rubric from your Course of Study, the task directions and your draft register. The work comes back with each entry rewritten into cause, event and consequence form, rating scales defined and applied consistently, ownership pushed onto the roles that can act, and triggers written for every contingency you hold.
What transfers is the register habit itself. E057 feeds the capstone directly, and a register written properly here can be extended rather than rebuilt when the later courses ask for one.
Questions students ask about E057
Is E057 the same course as PJMG 2110?
How many risks should a register contain?
Is a qualitative rating scale acceptable?
Register entries too vague to rate?
Send the rubric, the task directions and your draft. Entries come back in cause, event and consequence form, with defined scales, real owners and a trigger behind every contingency.
Where E057 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.