C723 Quantitative Analysis For Business is BUS 3100 in the WGU catalog and carries 3 competency units, covering decision-making models including expected value, linear programming and inventory models. The title prints with a capitalized For in the catalog, which is why searches for it look inconsistent. This is the undergraduate business course where partial understanding is most visible, because a model either produces a defensible number or it does not. Each rubric aspect needs a 2. C723 and BUS 3100 are the same course.
What C723 builds toward
Quantitative analysis is the practice of turning a business question into a structure that can be solved, then turning the solution back into a decision. Three model families dominate the course and they answer different questions. Expected value handles decisions under uncertainty, where outcomes have probabilities and you need a rational basis for choosing. Linear programming handles allocation, where limited resources must be split among competing uses to maximize or minimize something. Inventory models handle timing and quantity, balancing the cost of holding against the cost of ordering or running out.
The skill that transfers beyond the course is recognition: reading a messy business situation and knowing which structure fits. That recognition reappears in C720 Operations and Supply Chain Management and in the graduate treatment at C215 Operations Management, and the statistical groundwork sits in C955 Applied Probability and Statistics.
Planning when the aspects are calculations
The WGU catalog carries no assessment-type field and does not publish task requirements; your Course of Study does. If a performance assessment carries your version, quantitative aspects require a different planning unit than prose aspects. Each model has a fixed anatomy, and budgeting by that anatomy is more useful than budgeting by word count alone.
A worked example. Suppose six scored aspects, four of them computational, with a 1,700 word target. Each computational aspect needs five parts: the decision stated, the model chosen with a justification, the inputs listed with units, the working shown, and the result interpreted. At roughly 220 words each including a compact table, four of those consume 880. The two remaining aspects, typically a comparison of methods and a recommendation, take 320 and 350, giving 670. Plus 150 for framing, the document lands at 1,700. Then apply the time rule that word counts conceal: each model will take between forty minutes and two hours to build and check, so four models is a full working day before a single explanatory sentence is written.
Presenting a model so it can be verified
| Step | What to show | Why evaluators want it |
|---|---|---|
| Decision | The choice being made, in one sentence | Anchors the model to a business question rather than an exercise |
| Model choice | The technique and one sentence on why it fits | Aspects often score method selection separately from execution |
| Inputs | Every value with its unit and where it came from | Makes the result reproducible and exposes hidden assumptions |
| Assumptions | Anything estimated, stated as a labeled list | An unstated assumption reads as an error |
| Working | Formula, substitution, arithmetic, result | A result with no path to it cannot earn its aspect |
| Interpretation | What the number means for the decision | The step that converts arithmetic into analysis |
| Sensitivity | What input would change the answer, and at what value | Demonstrates understanding rather than execution |
Evidence when the evidence is arithmetic
In quantitative work the calculation is the citation, and its standard is reproducibility. Someone reading your document should be able to recompute every figure from what you have shown. That means formulas written out, substitutions visible, units carried through, and rounding applied at the end rather than at each step, with a note saying what you rounded to.
Where inputs come from outside the task, cite them in APA like any other source. Where they are estimates, say so and give the basis. Linear programming deserves a specific note: the formulation is the scored part more often than the solution. Writing out the decision variables, the objective function and each constraint in algebraic form, with a sentence saying what each constraint represents in the business, satisfies aspects that a solver's output alone cannot. Submitted work goes through WGU's Similarity Checker, so textbook worked examples cannot be adapted; run the models on the data your task provides.
Where quantitative submissions pass and fail
Work at WGU is recorded as Competent or Not Competent, with no letter grades and no GPA, and every aspect needs a 2 on its own. The failure list in this course is short and mechanical: a result with no working, a unit mismatch, an assumption used but never stated, a model applied to a problem it does not fit, or a correct calculation with no interpretation attached.
The single most effective habit is to write the interpretation sentence immediately after each result, before starting the next model. It forces you to notice when a number is implausible, and it guarantees the analytical half of each aspect exists. The second habit is a units audit: read the document once looking only at units, ignoring everything else. That pass takes ten minutes and catches the error type that most reliably returns quantitative tasks. Where work does come back, comments name the aspects and resubmission carries no penalty.
Six mistakes that cost time in C723
- Answer without working. The most common return in the course, and entirely preventable.
- Probabilities that do not sum correctly. An expected value built on a distribution that does not add to one is wrong before the arithmetic starts.
- Constraints missing from a formulation. A linear program that omits a real limit produces an optimum the business could never implement.
- Mixed time bases. Annual holding cost against weekly demand is the classic inventory error and it produces a confident, wrong answer.
- Rounding early. Rounding at each step compounds, and a reader who recomputes will land somewhere else and mark the aspect unmet.
- No interpretation. An optimal quantity with no sentence about what the business should therefore do leaves the analytical half of the aspect empty.
Models due, working has to be visible
Send the rubric and the data. Every model comes back with its formulation, working, units and interpretation, mapped to the aspect it satisfies.
Recognizing which model a problem wants
Most of the difficulty students report in this course is not computation. It is standing in front of a paragraph of business narrative and not knowing which structure it is asking for. Three diagnostic questions settle it almost every time.
First, does the problem contain uncertainty with named or estimable probabilities? If several futures are possible and you are choosing before knowing which one arrives, you are in expected value territory, and the giveaway phrases are chances, likelihood, and scenarios such as strong demand or weak demand. Second, does the problem contain a limited resource shared between competing uses, along with something to maximize or minimize? Machine hours, labor hours, material, budget or floor space split across products or routes points to linear programming, and the giveaway is the word per: hours per unit, cost per mile, capacity per week. Third, does the problem involve something held over time with a cost for holding it and a cost for replenishing it? That is an inventory question, and the giveaway is any mention of ordering cost, carrying cost, or demand across a period.
Problems that seem to fit two structures usually do fit two, at different layers. A firm might use expected value to choose a demand scenario and then a linear program to allocate resources under it. Saying that explicitly in the document, rather than picking one and hoping, tends to satisfy method-selection aspects outright, because it demonstrates exactly the recognition skill the course exists to build.
Three questions C723 students ask
My math is weak. Is this course going to be a problem?
Should I use a spreadsheet solver?
What if a proctored exam carries this course for me?
Three CUs, one flat term
Quantitative courses reward concentration, so they suit the front of a six month term rather than the exhausted end of one. Errors in arithmetic behave differently from errors in prose: they compound quietly and take longer to find. Schedule this course when you have clear working sessions available, and pair it with a reading-heavy course rather than another calculation-heavy one. Because a WGU term costs the same regardless of how many courses close in it, the aim is always to bank quantitative courses early. See the pacing page.
Where C723 sits in WGU's programs
The July 2026 catalog places this code in 7 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.