E056 Budgeting and Cost Control, catalog number PJMG 2365, is the three-competency-unit course where WGU turns a work breakdown structure into money and then asks what you do when the money stops behaving. Two skills are in play and they are not the same skill. Building a budget is bottom-up arithmetic driven by resource requirements. Controlling cost is a monitoring discipline that compares planned against actual and decides whether the difference means anything. Most returns in this course come from students who did the first well and treated the second as a footnote.
What PJMG 2365 is actually testing
The estimating half of E056 rests on a single principle: cost is derived, not chosen. You start from the work packages, identify what each one consumes in labour hours, materials, equipment and services, apply a rate to each quantity, and let the total emerge. A budget that starts from a number the sponsor mentioned and works backwards to fill it is the classic failure here, and it is visible immediately because the component figures come out suspiciously round.
The control half tests whether you can read a variance. A project that has spent more than planned might be in trouble or might simply be ahead of schedule and therefore ahead of spend. A project under budget might be efficient or might be behind and not yet incurring the cost it will. This is why cost control in any serious treatment brings schedule into the picture rather than comparing spend to plan in isolation. Assessment work in E056 rewards students who show they know the difference between spending differently and performing differently.
Underneath both halves sits a vocabulary that has to stay stable: direct against indirect cost, fixed against variable, estimate against budget against baseline, contingency reserve against management reserve. Evaluators notice when a submission uses budget and estimate interchangeably, because the two words describe different stages of commitment and the slip usually predicts a control section that has nothing to measure against.
Turning the rubric into a costing plan
WGU publishes scoring detail inside your Course of Study rather than in the catalog, so open it first and count the aspects. Each is scored on its own against a three-point scale, a 2 in each passes the task, and no aspect compensates for another. In a numeric course this cuts both ways. A flawless spreadsheet does not rescue a missing narrative aspect, and a persuasive narrative does not rescue a total that does not add up.
Where your course uses a performance assessment, build the outline directly from the aspect list and give each aspect a heading in the rubric's own vocabulary. Costing deliverables are easy to organize by category, which is exactly the trap: category headings hide which aspect each paragraph is answering.
The word budget, worked. Assume six scored aspects and directions calling for roughly 2,000 words of written material alongside any workbook. Take 150 for an opening that names the project and the basis of estimate, and 130 for a closing statement on how cost will be controlled after the plan is approved. That leaves 1,720 for six aspects, or roughly 285 words apiece. Then rebalance: the aspect asking you to interpret variance almost always deserves 400 or more, because it is where reasoning is scored rather than reporting, and the aspect asking you to list cost categories rarely needs more than 180.
Any aspect running past 500 words in this course has usually absorbed a neighbour. If your variance section has started explaining your estimating method again, that content belongs upstream and its absence there will cost you the estimating aspect.
A structure that fits a project budget deliverable
Costing deliverables carry a workbook or table plus a written argument. Your task directions decide the format wherever they speak to it. Where they are silent, this order keeps the arithmetic and the reasoning in step.
| Section | What belongs in it | How it tends to be scored |
|---|---|---|
| Basis of estimate | Where your rates and quantities came from and what you assumed | Protects every number downstream; without it the budget looks invented |
| Resource requirements | Labour, materials, equipment and services mapped to work packages | Scored for traceability back to the breakdown structure |
| Cost estimate | Quantity times rate for each line, subtotalled by package and phase | Checked for arithmetic and for consistent units |
| Reserves | Contingency for known risks, with the reasoning that sized it | Scored for justification; a flat percentage with no rationale scores thin |
| Budget baseline | The time-phased total the project will be measured against | Scored for being a baseline rather than a grand total |
| Control approach | What gets measured, how often, by whom, and the threshold that triggers action | Scored for being operable by someone else |
| Variance interpretation | What the supplied or projected variances mean and what you would do | The reasoning aspect; restating the numbers earns nothing |
Time-phasing is the step students skip. A budget that exists only as a single total cannot be compared against actuals partway through, and a control section built on an unphased budget has nothing to control. Spreading the baseline across periods takes fifteen minutes and makes the last two sections possible.
Evidence craft when your evidence is a rate and a quantity
Cost work needs sourcing in a way that surprises students arriving from writing courses. Nearly every figure is a claim about the world, and claims about the world need a stated origin.
- Attach a source to every rate. A scenario document, a published wage figure, a vendor quotation or a stated assumption. Unsourced rates are the single most common weakness in project budgets.
- Show the arithmetic path, not just the result. Quantity, rate, extension and subtotal. An evaluator who cannot reproduce a line cannot award accuracy for it.
- Keep units consistent and say what they are once. Hours against days and thousands against units are the errors that quietly wreck a total.
- Distinguish estimate ranges from point figures. If your basis is analogous rather than parametric, say so and give the range you are confident in.
- Cite external references in APA where the rubric asks for citation. Industry cost data and professional standards both count as sources.
- Never present a placeholder as a finding. If the scenario withholds a rate, state the assumption in the basis of estimate and use it consistently thereafter.
The mark of a strong cost submission is that it says out loud what would make it wrong. One sentence naming the assumption most likely to break, and what the budget would do if it did, reads as control thinking rather than as spreadsheet work.
What separates Competent from a returned budget task
Assessment outcomes here are 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 the price of a return is time inside a six-month flat-rate term rather than a permanent mark.
Budget deliverables that pass on the first read tend to look like this:
- Every line in the estimate traces to a work package in the breakdown structure, and no package is missing a cost.
- The stated total equals the sum of the parts, verified by hand rather than trusted to a formula.
- Reserves are justified by named risks rather than set at a round percentage of everything.
- The baseline is phased across time, so a variance at any point in the project is computable.
- The control section names a measurement frequency, a responsible role and a threshold that triggers escalation.
- Variance discussion reaches a decision. Reporting that cost exceeded plan is not analysis until you say what should happen.
If an objective assessment appears in your plan for this course, the boundary is fixed. Proctored exams are yours alone to sit. Support here means drilled formulas, practice variance problems and a candid readiness call. We do not sit assessments and we never ask for portal credentials.
Six mistakes that cost time in E056
- Working backwards from a target number. Budgets built to hit a figure show it, because the components come out round and the basis of estimate goes vague.
- Leaving the budget unphased. A single grand total makes the entire control half of the course unanswerable.
- Setting contingency by habit. Ten percent of everything is not a reserve, it is a reflex. Size it against the risks you actually named.
- Comparing spend to plan without schedule. Under budget and behind schedule looks identical to under budget and efficient until you bring progress into the comparison.
- Reporting variance without deciding anything. The reasoning aspect asks what you would do, and describing the gap is not deciding.
- Mixing direct and indirect cost silently. Overhead folded into labour lines without a note makes every unit rate unverifiable.
How support works on this course
Cost tasks are the easiest in the sequence to check objectively and the easiest to lose on a small arithmetic slip. Send the rubric from your Course of Study, the task directions, your breakdown structure and any workbook you have started. The work comes back with every line traced to a package, the totals recomputed independently, reserves argued against named risks, and the variance section rewritten so it reaches a decision instead of stopping at a number.
The transferable part is the basis of estimate discipline. Once you write one properly, every later costing artifact in the sequence and in your working life gets faster and harder to argue with.
Questions students ask about E056
Is E056 the same course as PJMG 2365?
Do I need accounting background for E056?
Can you do the budget spreadsheet for me?
Budget not tying back to your work breakdown?
Send the rubric, the task directions and your workbook. Every line gets traced to a package, totals recomputed by hand, and the variance section rewritten to reach a decision.
Where E056 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.