C210 Management and Leadership Capstone is MGMT 6910 in the WGU catalog and carries 4 competency units as the culminating assessment of the M.S. Management and Leadership curriculum. Capstones at WGU are not harder than the courses that precede them; they are longer, and length is what exposes weak planning. If a performance assessment carries your version, the document has to satisfy every scored aspect at a 2, across a scope wide enough that most students lose track of at least one. C210 and MGMT 6910 are the same course.
What a graduate capstone is actually testing
The word culminating is doing real work in the catalog description. A capstone asks you to demonstrate the program's competencies together, on a single problem, in a way that no individual course required. That means the skill under examination is integration: taking a leadership diagnosis, an organizational analysis, a change or strategy argument and a measurement plan, and making them one coherent piece of reasoning rather than four chapters that happen to be stapled together.
It also means the capstone is where earlier shortcuts come due. A student who wrote a vague development plan in C203 and a vague team plan in C205 now has to produce a document where vagueness has nowhere to hide, because the sections have to connect and connections require specifics. The undergraduate equivalents run through the capstone hub, and the MBA version is C216.
Turning a long rubric into a working schedule
WGU does not publish task detail in its catalog; the Course of Study in your portal is where the requirements for your version live. Assuming a performance assessment, the capstone planning problem is different from a normal course because the aspect list is long enough that word budgeting alone is insufficient. You need a calendar as well as an outline.
A worked example. Take a rubric with sixteen scored aspects and a 6,000 word document. Reserve 400 words for front matter and 300 for the conclusion, leaving 5,300 across sixteen aspects, or an average of 331. Now weight them: six descriptive or contextual aspects at 220 gives 1,320; six analytical aspects at 380 gives 2,280; three design or recommendation aspects at 450 gives 1,350; one measurement aspect takes 350. Sum: 1,320 plus 2,280 plus 1,350 plus 350 equals 5,300. Then convert to a schedule at a realistic 700 finished words a day, which is eight working days of drafting plus two for revision and formatting. Ten working days is a very different plan from the weekend most students imagine, and knowing that in week one is the single most valuable output of the exercise.
Holding a long document together
The structure below is built around one rule: every section must be traceable to the problem stated on page one. Capstones drift, and drift is what makes a strong section fail an aspect it should have satisfied.
| Component | Its job in a capstone | Drift risk it controls |
|---|---|---|
| Problem statement | One paragraph naming the organization, the issue, and why it matters now | The document that answers a different question by the middle |
| Scope and boundaries | What is deliberately excluded | Endless expansion, the main cause of capstone overruns |
| Evidence base | Data gathered, method used, limitations acknowledged | Conclusions that outrun what the evidence can support |
| Analysis | Frameworks applied to the specific case, findings stated plainly | Theory sections that describe rather than apply |
| Leadership dimension | What the findings demand of the leaders involved | A management report with the leadership competency missing |
| Recommendation and plan | The proposal, sequenced, resourced, owned | A conclusion that is a summary rather than a decision |
| Evaluation design | How anyone would know it worked, and when | The aspect most often left until the writer is exhausted |
Evidence at capstone scale
Capstone evidence has to be both broader and more disciplined than a course paper. Broader, because a culminating assessment expects you to draw on the program's range rather than one topic's literature. More disciplined, because at 6,000 words it is genuinely easy to lose track of which claim rests on which source. Build the reference list as you write and keep a working note of what each source is doing in the argument, since a source list assembled at the end usually contains two entries nobody can find in the text.
Where the capstone uses organizational data, state the method by which you obtained it and its limitations in plain language. A short paragraph saying that figures came from internal reports for a two-year window, that one quarter is incomplete, and that the analysis therefore treats trend rather than level, does more for credibility than any amount of confident phrasing. Submitted files pass through WGU's Similarity Checker, and at capstone length the risk of unintentional close paraphrase rises simply because you are handling more source material; write from notes rather than from open documents.
Where capstones pass and where they return
Work at WGU is Competent or Not Competent, with no letter grades and no GPA, and every aspect needs its own 2. Capstones almost never return for weak thinking. They return for coverage gaps: an aspect somewhere in the middle of a long rubric that received two sentences because the writer was tired, or a required element such as an evaluation plan that arrived as a paragraph when the aspect wanted a design.
Two mechanical habits prevent nearly all of it. Keep a coverage checklist beside the draft and tick each aspect only when its section is finished, never when it is planned. And do a final pass where you read the rubric aloud and point at the paragraph that answers each aspect; anything you cannot point to is not there, whatever your memory says. Because performance assessment work can be revised and resubmitted without penalty, a returned capstone costs time rather than standing, and the revision guide covers how to close it in one pass.
Six mistakes that cost weeks in a capstone
- Choosing a topic before reading the rubric. A topic that cannot generate evidence for four of the aspects will not survive, and discovering that in week three is expensive.
- Scope with no stated boundary. Without an explicit exclusion paragraph, capstones grow until the deadline stops them.
- Writing sequentially from page one. Front sections get polished, back sections get rushed, and the back sections usually hold the design and evaluation aspects.
- Leaving the measurement plan last. It is the aspect most often written at 2am and most often returned.
- Relying on memory for organizational facts. At this length, unsourced specifics accumulate and one of them will be wrong.
- Ignoring the queue. A capstone submitted in the final fortnight of a term with no revision window is a gamble against a queue you do not control.
Capstone planned, not improvised
Send the rubric and your topic. You get a scope read, a section plan with a schedule, and a model draft built aspect by aspect with a walkthrough.
Three questions C210 students ask
How do I pick a capstone topic that will not collapse?
Should I write about my own workplace?
How early should I start relative to the term end?
Gathering capstone evidence before you need it
The most common capstone delay has nothing to do with writing. It is waiting on information: a report someone has to pull, a figure only one department holds, a permission that takes a week to arrive. Because a capstone runs long, that delay lands in the middle of drafting rather than at the start, and it stops everything.
The fix is to open every evidence request in the first week, before the outline is finished and before you are certain you need all of it. List what the analysis might require, ask for all of it at once, and accept that some of it will turn out to be unnecessary. Requesting five things and using three costs nothing; discovering in week five that the fourth would have taken ten days costs a term boundary. While you wait, write the sections that need no external input: the problem statement, the scope, the literature-backed portions of the analysis. Capstone drafts written in that order almost never stall, because the writer always has something available to work on. Keep a short log of what was requested, from whom, and when, since the limitations paragraph in your methodology section can be written directly from it, and a limitations paragraph grounded in what you actually could not obtain reads far better than one improvised at the end.
Four CUs and the end of a program
The capstone is the one course where flat-rate term math cuts against you. Everywhere else, closing courses quickly lowers the effective cost of a six month term; here, a capstone that misses a term boundary can force an entire additional term for a single course. That asymmetry is the reason capstone scheduling deserves more planning than anything else in the plan, and the reason we push for early submission rather than early perfection. The capstone help page covers the staged method, and queue timing covers the wait you have to design around.
Where C210 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.