D360 is the HRM Capstone, printed in the WGU catalog with the banner number HRM 3100 and worth 3 competency units. It is the culminating course, and the catalog describes it as evaluating HR strategies and organizational effectiveness. One catalog quirk to know before you start searching: HRM 3100 is also the banner printed beside the legacy course C233 Employment Law, so a search on the number alone can return an entirely different subject. Match on the title, D360 HRM Capstone, not on the number.
What a capstone is actually for
A capstone is not a bigger assignment. It is a demonstration that the separate competencies you collected across a degree can be used together on one problem, by you, without prompting. That difference explains almost everything about how these courses are scored.
Earlier courses hand you a scenario and ask you to apply one framework. A capstone hands you an organization and expects you to decide which frameworks apply, in what order, and why. The scored aspects usually reward the decisions: choosing the right analysis for this problem, gathering evidence proportionate to the claim, connecting an HR recommendation to organizational effectiveness rather than to HR tidiness, and being explicit about what you could not determine.
The practical consequence is that scope control is the capstone skill. Nearly every returned capstone in every discipline has the same underlying cause: the writer took on a question too large to evidence in the space available, then filled the gap with assertion. A narrower question, thoroughly evidenced, outscores a sweeping one every time.
WGU records the result as Competent or Not Competent, without letter grades and without an ordinary grade point average, and performance assessment work can be revised and resubmitted with no penalty attached to the result. Capstones do tend to take longer through the evaluation queue than ordinary tasks, so the cost of a return is calendar time. That is the argument for planning carefully rather than for hesitating.
Turning scored aspects into a capstone plan
If your course is assessed by a performance assessment, the aspects your evaluator scores are the entire project plan, not just the document outline. Each needs a score of 2 on its own, and in a capstone the aspects usually stretch across research, analysis, recommendation and reflection.
Here is the arithmetic at capstone scale. Suppose the rubric shows sixteen scored aspects and the deliverable runs to something like 5,000 words. Reserve 300 for an executive summary, 300 for the organizational background and 200 for a close, leaving 4,200 across sixteen aspects, or roughly 262 words each.
Now convert words into evenings, because that is the number that actually governs a capstone. At a realistic drafting rate of 400 finished words in a working evening, 4,200 words is about eleven evenings of writing, before any research. Add four evenings for evidence gathering and two for revision and you have a seventeen evening project. Put those on a calendar with dates. Students who miss capstone deadlines almost never miss them because the work was too hard; they miss them because seventeen evenings were never scheduled.
A structure for an HR capstone deliverable
Capstone deliverables in this discipline usually take the form of an organizational analysis with recommendations, sometimes accompanied by a presentation artefact. The sequence below is the one that survives evaluation.
| Component | Its job in the argument | Depth expected | Capstone level failure |
|---|---|---|---|
| Executive summary | The problem, the finding and the recommendation in one page | Written last, read first | A summary that previews the structure instead of the conclusions |
| Organizational profile | The employer, its strategy and the workforce that delivers it | Specific and sourced | Pages of background that never bear on the analysis |
| Problem definition | The single HR issue affecting organizational effectiveness | One sentence, narrow enough to evidence | Three problems in a trench coat |
| Evidence gathering | What data you used and how you got it | Method stated, limitations named | Method left implicit, so findings cannot be trusted |
| Analysis | What the evidence shows, using named frameworks | Frameworks chosen and justified | A framework applied because it was memorable |
| Recommendations | Two or three changes with cost, owner and sequence | Costed and prioritised | Recommendations disconnected from the analysis |
| Implementation and measurement | How it happens and how success is judged | Timeline with measures and baselines | Measures with no baseline |
| Reflection | What you learned and what you would do differently | Honest and specific | A gratitude paragraph, which scores nothing |
Evidence at capstone standard
The evidence bar rises in a capstone, and it rises in a particular direction: away from textbooks and towards material specific to the organization and the problem. Course readings are background. What the aspects want is analysis built on something an evaluator could not have written without you.
Three sources carry most HR capstones. Organizational material, meaning whatever your scenario supplies or what a real employer publishes, gives you the facts of the case. Public workforce and industry data gives you the comparison that turns a fact into a finding, since turnover of eighteen percent means nothing until it sits beside an industry figure. Peer reviewed HR and management research gives you the mechanism connecting a proposed change to an outcome, which is what makes a recommendation more than a preference.
Two capstone specific cautions. If your project involves collecting information from real people, follow whatever approval and consent process your programme requires, and never include identifiable personal data in an academic submission. And be scrupulous about the limitations paragraph: saying what your evidence cannot support is a mark of the standard being assessed, not an admission of weakness, and it frequently earns its own aspect.
What separates a Competent capstone from a returned one
Capstones pass when the whole document answers one question. The problem statement names it, the evidence bears on it, the analysis interprets that evidence, the recommendations respond to that interpretation, and the measures would show whether the response worked. Nothing in the document exists because it was interesting.
Capstones come back for scope, for evidence and for connection. Scope failures take on more than can be evidenced. Evidence failures assert findings the data does not carry, or use only course materials at a level where original sourcing is expected. Connection failures produce a good analysis and a good set of recommendations that are not related to each other, which is easy to do when the two sections were written weeks apart.
The other frequent return is formatting compliance. Capstone tasks tend to specify templates, section headings, appendices and file formats, and those specifications are usually attached to aspects. A brilliant document in the wrong template is a returned document.
Six mistakes that cost time in a capstone
Choosing a problem too big to evidence. Narrow it until you can prove what you claim, then narrow it once more.
Starting to write before gathering evidence. The analysis section cannot be drafted around data you have not collected.
Treating the reflection as a formality. It is a scored aspect. Name a specific decision, what it cost, and what you would change.
Ignoring the template. Where a form is specified, the form is part of the requirement.
Recommendations without cost. An organizational effectiveness argument needs to survive contact with a budget.
Leaving the executive summary to the end of the last evening. It is the first thing read and the most compressed writing in the document. Give it its own session.
What we do on a capstone, and what we will not do
We work on structure and drafting: mapping the rubric to a project plan, sizing the work in evenings, drafting model sections you can study and rewrite in your own voice, pressure testing the problem statement before you commit weeks to it, and reading a returned evaluation to name the edits that will clear it. We do not gather data from real people on your behalf and we do not contact any organization for you. If your capstone carries an objective assessment component, that exam is proctored and our role is preparation only. We are never present during an assessment, never take one for a student, and never ask for or handle WGU portal credentials.
Planning the HRM capstone?
Send the task instructions, the rubric and any template. We come back with the aspect map, the evening count and a straight read on whether your problem statement is narrow enough to prove.
Three questions students ask about D360
Why does HRM 3100 show two different courses?
Can I use my own employer as the capstone organization?
How long does a capstone realistically take?
Where D360 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.