D361 Business Simulation is BUS 2111 in the WGU catalog and carries 4 competency units, applying skills from across the business core inside a simulated business environment. It is unusual in the plan because part of the work is an activity rather than a document, and that creates a specific trap: students optimize the simulation and neglect the writing that is actually scored. Results are inputs to the assessment, not the assessment. Each rubric aspect needs its own 2. D361 and BUS 2111 are the same course.
What D361 builds toward
A business simulation compresses years of decisions into hours, and the compression is the point. Pricing, capacity, marketing spend, hiring and financing all interact, and the interaction is invisible in a course that teaches each separately. The simulation makes it visible by punishing inconsistency: a price cut with no capacity to serve the demand, or a marketing push with no cash to fund it, produces a result you can see rather than a comment on a paper.
Because it applies the business core, D361 assumes vocabulary from across the plan, including D076 Finance Skills for Managers, D077 Concepts in Marketing, Sales, and Customer Contact and D464 Managing Operations. Students who take it after those courses spend less time confused by the decision screens and more time reasoning about them.
Aspects that score reasoning, not results
WGU does not publish assessment types or task requirements in its catalog; the Course of Study inside your portal holds them, including how your version of the simulation is set up. If a performance assessment carries the written component, the important planning insight is that aspects almost always ask why you decided something, what you expected, and what you learned. Winning the simulation is not itself an aspect.
A worked example. Say ten aspects and a 2,400 word written component alongside the simulation activity. Reserve 180 for the business context and 100 for the close, leaving 2,120. Three aspects on decision rationale take 260 each, giving 780. Three on analysis of results take 250 each, giving 750. Two on adjustments made take 180 each, giving 360. Two on reflection and lessons take 115 each, giving 230. Sum: 780 plus 750 plus 360 plus 230 equals 2,120. Keep a decision log while you play, because writing 780 words of rationale from memory two weeks later produces vague sentences that no aspect can score.
Documenting simulation decisions
| For each decision round | Record this | Why the rubric wants it |
|---|---|---|
| Position entering the round | Cash, capacity, share, and the constraint you faced | Establishes what the decision was responding to |
| Options considered | At least one alternative you rejected | Shows the decision was chosen rather than defaulted to |
| Decision made | The specific settings and quantities | Makes the reasoning checkable against the outcome |
| Expected outcome | What you predicted, with a number where possible | The single most scoreable thing in simulation writing |
| Actual outcome | What the results showed | Supplies the comparison the analysis aspects need |
| Explanation of the gap | Why prediction and result differed | Where genuine learning is demonstrated |
| Adjustment | What you changed next round as a result | Closes the loop that reflection aspects look for |
Evidence produced by the simulation itself
The simulation generates your data, and it is legitimate evidence provided you report it precisely. Quote the actual figures rather than describing them, name the round, and keep units consistent. Where the results contradict what you expected, say so plainly, since a document in which every prediction came true reads as reconstructed after the fact.
Business concepts should be cited in APA where you use them to justify a decision, and this is where the course earns its place in the plan: saying that you cut price because a competitor did is a description, while saying you cut price because demand in this segment appeared elastic, supported by the round-over-round volume response you observed, is analysis. Anything you submit passes through WGU's Similarity Checker, and simulation strategy guides circulate widely online, so the reasoning must be your own writing about your own rounds.
What passes in a simulation course
WGU records Competent or Not Competent, with no letter grades and no GPA, and each aspect requires its own 2. D361 submissions return most often when the writing reports outcomes without reasoning. A student describes what happened round by round, accurately, and never states what they expected or why they chose what they chose, leaving the rationale aspects unanswered.
Passing documents are frequently written by students whose simulated business performed poorly, which surprises people. A business that struggled produces gaps between expectation and result, and those gaps are exactly what the analysis and reflection aspects are scored on. A run that went smoothly gives you less to explain. Write honestly about the rounds that went wrong, name the cause, and describe the adjustment, and the weak performance becomes the strongest material in the document. If it returns, the comments identify the aspects, and there is no penalty for sending it again.
Six mistakes that cost time in D361
- Playing first, writing later. Decision rationale reconstructed from memory is vague, and vagueness is what returns these tasks.
- Reporting results as narrative. A chronology of what happened satisfies no aspect asking why you decided something.
- Hiding the bad rounds. The gaps between expectation and outcome are the most scoreable material you have.
- Decisions with no stated alternative. Without a rejected option, there is no visible decision to evaluate.
- Ignoring the interactions. The point of the simulation is that marketing, capacity and cash constrain each other, and a document treating them separately misses the course.
- Predictions omitted. Without an expectation recorded, the comparison that drives the analysis aspects cannot be made.
Simulation done, write-up due
Send the rubric and your round results. The model write-up turns decisions and outcomes into scored reasoning, with an aspect map and a walkthrough.
The decision log that makes the write-up easy
Nearly all of the difficulty students report in this course comes from one avoidable choice: playing the whole simulation and then trying to write about it. The alternative costs about five minutes per round and turns the written component into transcription rather than reconstruction.
Before submitting each round's decisions, write four short lines. What is my constraint right now, meaning cash, capacity, demand or something else. What am I choosing to do about it. What do I expect to happen, stated as a number or a direction. What would tell me I was wrong. Then after results are published, add one line recording what actually happened and one explaining the difference.
Six lines per round, across however many rounds your simulation runs, produces a complete record of exactly the material the rubric asks for. It also improves your play, because writing a prediction forces you to have a model of how the simulated market works rather than adjusting settings by feel. Students who keep this log typically write the final document in an evening, and the resulting analysis is specific in a way that memory cannot reproduce. If you have already played several rounds without one, start now anyway, since the last rounds documented properly are worth more than all of them recalled vaguely.
Three questions D361 students ask
Does my simulated company have to be profitable to pass?
Should I look up strategy guides for the simulation?
What can you help with on a simulation course?
Four CUs and the flat-rate term
Simulations run on a schedule set by rounds rather than by your calendar, which makes D361 the one business course you cannot compress at will. Plan around that: start it early in a six month term so the round schedule finishes with time to spare, and treat the written component as a task that begins with round one rather than after the last one. Because WGU charges one flat rate per term, a course with a fixed pace should be started first and run in parallel with everything else. See the progress guide.
Where D361 sits in WGU's programs
The July 2026 catalog places this code in 9 current WGU programs. 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.