QGT1 Business Management Capstone Written Project is BUS 4840 in the WGU catalog and carries 4 competency units, a written capstone integrating competencies from across the Business Management degree. The four-character code is one of WGU's older formats and appears that way in Degree Plans, so QGT1 and BUS 4840 point at one course. Capstones are not conceptually harder than the courses before them; they are longer, and length exposes planning. Each aspect is scored independently, with a 2 required in every one.
What a written capstone is testing
Individual courses test competencies one at a time. A capstone tests whether they hold together on a single problem, which is a different skill and one nobody has practiced. The document has to identify a real business issue, analyze it using methods from across the degree, and produce a recommendation that survives the analysis, all while remaining one argument rather than a sequence of chapters.
The written framing matters too. This is a document a business reader should be able to follow, which means a summary that states conclusions rather than previewing them, headings that let a reader navigate, and evidence they can check. The other capstones in the school approach the same challenge from different majors, including D473 Solutions Design and Visualization Capstone and D178 Marketing Strategy and Analytics, and the graduate versions are C210 and C216.
Turning a long rubric into a schedule
WGU does not publish assessment types or task requirements in its catalog; the Course of Study in your portal holds yours. If a performance assessment carries it, the capstone planning problem differs from a normal course because the aspect list is long enough that a word budget alone is insufficient. You need a calendar too.
A worked example. Fifteen aspects and a 5,000 word document. Reserve 350 for front matter and 250 for the conclusion, leaving 4,400 across fifteen aspects, an average of 293. Weight them: five contextual or descriptive aspects at 200 gives 1,000; six analytical aspects at 340 gives 2,040; three recommendation and implementation aspects at 380 gives 1,140; one evaluation aspect takes 220. Sum: 1,000 plus 2,040 plus 1,140 plus 220 equals 4,400. Then convert to days at a realistic 700 finished words a day: roughly six working days of drafting, plus two for revision and formatting, plus whatever the evidence gathering takes. Eight working days is a very different plan from the long weekend most students have in mind.
Holding a long written argument together
| Section | Its job | The drift it prevents |
|---|---|---|
| Summary | States the problem, the finding and the recommendation | A summary that promises rather than concludes |
| Organization and problem | Names the business, the issue and its cost | A problem so broad no analysis could resolve it |
| Scope | What is included and explicitly excluded | Expansion, the main cause of capstone overruns |
| Method and evidence | What was examined and how, with limitations | Conclusions that outrun the evidence gathered |
| Analysis | Frameworks applied to this case, findings stated plainly | Theory described rather than used |
| Recommendation | The proposal, sequenced, resourced and owned | A conclusion that summarizes instead of deciding |
| Implementation and evaluation | What happens first, and how success is judged | The aspects written last and most often thinly |
Evidence at capstone length
Two disciplines matter more at 5,000 words than at 1,500. The first is source tracking: build the reference list while writing and keep a working note of what each source is doing in the argument, because a bibliography assembled at the end reliably contains entries nobody can locate in the text. The second is claim auditing, since at capstone length it is genuinely easy to make a specific assertion about the organization in week one and lose track of where it came from by week three.
Where the capstone uses organizational data, state how it was obtained and what it cannot support. A short methodology paragraph saying that figures cover two years, that one quarter is incomplete, and that the analysis therefore treats trend rather than level, does more for credibility than confident phrasing ever will. Submitted work runs through WGU's Similarity Checker, and at length the risk of unintentional close paraphrase rises simply because more source material passes through your hands, so draft from notes rather than from open documents.
Where written capstones pass and fail
WGU records Competent or Not Competent, keeps 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 in the middle of a long rubric that received two sentences, or a required element such as an evaluation plan that arrived as a paragraph when the aspect wanted a design.
Two clerical habits prevent nearly all of it. Number the aspects and write the number into the draft beside the passage that answers each one, then strip the numbers out before submitting; anything still unnumbered at the end never got written. And read the document once backwards, section by section from the last to the first, which breaks the narrative pull that makes a tired writer believe a thin closing section is complete. Because performance assessment work can be revised and resubmitted without penalty, a returned capstone costs time rather than standing. The revision guide covers closing it in one pass.
Six mistakes that cost weeks here
- Topic chosen before the rubric is read. A topic that cannot generate evidence for several aspects will fail, and finding that out in week three is expensive.
- Writing straight through from page one. Front sections get polished, back sections get rushed, and the back holds the recommendation and evaluation aspects.
- No stated exclusions. Without a boundary, the document grows until the deadline stops it.
- A summary that previews. Business readers expect conclusions at the top, and a summary aspect is usually scored against that convention.
- Specifics recalled rather than checked. Across five thousand words a document accumulates dozens of factual claims, and the one that turns out to be wrong is always in the section an evaluator reads closely.
- Submitting with no revision window. A capstone sent in the final fortnight of a term is a gamble against a queue you do not control.
Capstone planned rather than improvised
Send the rubric and your topic. You get a scope read, a section plan with a working schedule, and a model draft built aspect by aspect with a walkthrough.
Testing a capstone topic before you commit to it
The single most consequential hour of this course is the one spent choosing a topic, and most students spend about ten minutes on it. A structured test takes an hour and prevents the failure mode where a promising subject collapses in week three.
Take four aspects from the middle of the rubric, not the first ones, since opening aspects are usually generic and any topic satisfies them. For each, write two sentences describing what evidence your topic would supply. If you cannot do it for two of the four, the topic is wrong regardless of how interesting it is. Then apply three practical filters. Access: can you obtain the organizational detail the analysis needs, and how long will that take. Boundedness: can the problem be stated in one sentence with a clear edge, since problems needing three sentences to define are usually two problems. And consequence: does the recommendation matter to anyone, because a capstone recommending something nobody would resist is usually addressing a symptom rather than an issue.
Topics that pass all of this share a shape. They are narrow, current, attached to a specific organization, and they involve a decision where reasonable people would disagree. A regional operator deciding whether to consolidate two facilities. A service business whose retention has slipped in one segment. A distributor choosing between adding a warehouse and outsourcing delivery. Those produce documents where every section has something to say, which is the entire difference between a capstone that writes itself and one that has to be dragged.
Three questions QGT1 students ask
Is my own employer a safe subject for this?
How long should the document actually be?
How does capstone support work?
Four CUs and the term boundary
Flat-rate terms reward speed everywhere in a WGU plan except here. A capstone that misses a term boundary can force an entire additional six month term for one course, which inverts the usual arithmetic and makes capstone scheduling the highest-stakes planning decision in the degree. Aim to submit with four to six weeks of term remaining so the evaluator queue and one revision cycle both fit. The capstone help page covers the staged method.
Where QGT1 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.