C720 Operations and Supply Chain Management is MGMT 4100 in the WGU catalog and carries 3 competency units, covering how organizations produce goods and services, how supply chain strategy is set, and how performance is measured. It is an undergraduate course with a graduate-level habit requirement: claims need evidence, and evidence here often means arithmetic. Each rubric aspect needs its own score of 2. Whether your Degree Plan lists C720 or MGMT 4100, this is the same course.
What C720 builds toward
Operations is where a business promise becomes a physical constraint. A company can market anything; it can only deliver what its capacity, suppliers and quality system allow. This course builds the vocabulary for that reality, then extends it outward into the supply chain, where the same reasoning applies but the levers belong to other companies.
Performance measurement is the third leg and the one most likely to appear in a rubric aspect. Operations without measurement is opinion, so the course keeps pushing you toward indicators: throughput, lead time, defect rate, inventory turns, fill rate, cost per unit. The graduate version of the same territory is C215 Operations Management, and the specialized courses that branch off it are D470 Transportation, Logistics, and Distribution and D471 Global Supply Chain Management.
Planning around mixed aspects
The catalog does not state which instrument any course uses, and task requirements live in your portal's Course of Study. If yours is a performance assessment, the planning wrinkle in operations courses is that aspects come in two species, prose and computation, and they consume time differently. A 150 word calculation aspect can take longer than a 400 word analytical one.
A worked example. Seven aspects, of which two require computation, targeting 1,900 words. Reserve 150 for the operating context and 100 for the close, leaving 1,650. The two quantitative aspects need setup, working and interpretation, roughly 190 words each including a compact table, so 380. Of the remaining five, three are analytical at 270 each, giving 810, and two are descriptive at 230 each, giving 460. Check the sum: 380 plus 810 plus 460 equals 1,650. Then add the schedule note that word budgets hide: those two computations will take a working session of their own, so plan a day for 380 words and half a day for the other 1,270.
Laying out an operations analysis
| Section | Contents | Common gap |
|---|---|---|
| Process or network description | Steps, flows, capacities, and where the work waits | Describing the product instead of the process that makes it |
| Current performance | Baseline measures with units and a period | Adjectives where numbers belong |
| Bottleneck identification | The constraint, evidenced rather than assumed | Naming the busiest station rather than the slowest one |
| Supply chain view | Suppliers, lead times, and what happens when one slips | Treating suppliers as reliable by default |
| Improvement options | Two or three interventions with costs | Options without price tags, which cannot be compared |
| Quantified impact | Expected change to the baseline measures | Improvement claimed but never sized |
| Measurement plan | Indicators, owners, review cadence | Measures nobody is scheduled to look at |
Evidence in an operations submission
Three streams matter. The first is your own arithmetic, and it is only evidence when the working is visible: formula, substitution, result, units. The second is the case or organization your task supplies, whose given figures should be quoted exactly rather than rounded into approximations that no longer reconcile. The third is external benchmarking, cited in APA, which lets an evaluative aspect say what good looks like rather than only describing what is.
A habit worth adopting early: keep an assumptions list as a labeled block in the document. Operations analysis is impossible without assumptions about demand, downtime or lead time, and an assumption stated openly is a strength while the same assumption buried inside a calculation is a hole. WGU scans submitted files through its Similarity Checker, so worked solutions found elsewhere cannot be adapted; build your computation from the data your task gives you.
What passes here
WGU records Competent or Not Competent, has no letter grades and no GPA, and requires a 2 in each aspect. Operations submissions that pass on the first attempt share a plain quality: every number in them can be traced. The reader can see where a figure came from, what was done to it, and what it means. Submissions that return usually contain a correct answer with no visible path to it, or an improvement recommendation with no estimate of its effect.
The second differentiator is scope honesty. An undergraduate operations task does not need a complete network redesign; it needs one constraint identified correctly and one intervention sized properly. Students who attempt everything produce a wide document with shallow aspects, and shallowness is what returns. When a task does come back, the comments name the aspects, revision carries no penalty, and supported work is revised until the evaluation reads Competent.
Six mistakes that cost time in C720
- Bottleneck by intuition. The station that looks busiest is often not the constraint. Compare capacities and show the comparison.
- Units left off. Units per hour, days of supply and dollars per unit are different quantities, and a bare number cannot be checked.
- Improvements without cost. An intervention with no price cannot be evaluated, and evaluative aspects then have nothing to weigh.
- Ignoring variability. Averages hide the problem. Lead time varying between three and eleven days is a different supply chain from one that always takes seven.
- Supplier risk as a sentence. Aspects on supply chain risk want a specific exposure and a specific mitigation, not a general acknowledgment.
- No baseline. Without current performance stated in numbers, no improvement can be demonstrated and the measurement aspects fail.
Operations task with numbers in it
Send the rubric and any data your task provides. The model draft shows every calculation with its working and ties each result to a decision.
Three questions C720 students ask
I have never worked in operations. Is that a problem?
Do I need a spreadsheet for this course?
What if this course is assessed by an exam for me?
Where the numbers come from when nobody gives you any
Some operations tasks hand you a dataset. Others hand you a situation and expect quantification anyway, and that is where undergraduate submissions go vague. There are three legitimate sources of numbers when none are supplied, and all three are defensible if you label them.
The first is direct observation. If the process is one you can watch, count it: how many units cross a station in ten minutes, how long a queue is at three points in a day, how often a step is repeated. A small sample honestly described is real data, and stating the sample size and conditions turns it into evidence rather than anecdote. The second is documented industry figures, cited properly, used to establish a plausible range rather than a precise value. The third is a stated assumption, which is not cheating as long as it is visible: assume demand of a given level, say why that level is reasonable, and then show what happens if it is twenty percent higher.
What fails is the fourth option, which is writing around the absence of numbers with comparative adjectives. Significantly faster, much lower cost and greatly improved are the phrases evaluators read as unsupported, because they are. A sentence that says the step took an observed average of four minutes against a target of two, based on ten observations across two shifts, will satisfy an aspect that a paragraph of confident description will not.
Three CUs and the flat-rate term
Because a WGU term costs the same regardless of how many courses you close in it, the courses worth attacking early are the ones whose work is bounded, and operations tasks are unusually bounded once the data is in hand. Front-load the calculation work while attention is fresh, then let the writing run alongside another course. The pacing page covers the cadence, and D469 Quality, Continuous Improvement, and Lean Six Sigma is the natural follow-on for students in the operations concentration.
Where C720 sits in WGU's programs
The July 2026 catalog places this code in 4 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.