Culminating assessment guide
WGU Capstone Guide: Planning, Evidence, Submission and Revision
A WGU capstone is a culminating demonstration of program-level competency. The exact task, artifact, approvals and submission sequence vary by program, so the active course and task instructions must control the plan.
Quick answer
A WGU capstone should demonstrate program competency through the current task
Start by identifying the exact course, program and current task sequence. Convert every rubric criterion into a deliverable, evidence source and final location. If the capstone uses a client, workplace, dataset or technical artifact, verify permission, privacy and authenticity before building around it.
Do not copy a public capstone. Its program, rubric and evidence may differ, and WGU requires original student work.
Maintain a traceability matrix connecting requirement, competency, evidence, working output, final section and quality check. Use version control for the manuscript, artifact, calculations, code, presentation and appendices so a revision does not create contradictions.
When evaluator feedback arrives, repair the earliest controlling decision first. A scope or method change can require updates across results, recommendations, visuals and the executive summary.
A decision-first method
Build the capstone from competencies outward
The project should remain traceable from the task and rubric to the final evidence.
Verify the exact capstone task
Use the active program, course and task version rather than a public sample.
Map competencies and criteria
Give every scoring requirement an evidence source and final location.
Plan authentic inputs
Confirm data, client, workplace, research, code or artifact access and permissions.
Build and test the product
Create working outputs, record methods and evaluate against explicit criteria.
Revise from evaluator feedback
Log comments, changes, locations and dependent sections before resubmission.
Working decisions
WGU capstone traceability matrix
| Layer | Planning record | Final evidence |
|---|---|---|
| Requirement | Exact task and rubric language | Clearly located response |
| Competency | Knowledge or skill demonstrated | Reasoning, artifact or analysis |
| Input | Approved source, data or case | Traceable citation or project record |
| Quality | Acceptance or evaluation criterion | Test result, rubric audit or limitation |
Use the current program, course or project requirements as the controlling source. The table is a planning aid, not an institutional ruling.
Original worked example
A technical capstone narrows from solution idea to testable artifact
A learner proposes a broad cybersecurity platform. The course window and available environment make that infeasible. The project is narrowed to a bounded access-control prototype with defined user stories, threat assumptions, test cases, expected outcomes and limitations. The report shows what was built, how it was tested and what the evidence does not establish.
Feasibility and traceability produce a stronger capstone than an ambitious claim without inspectable evidence.
Common problems and repairs
Common WGU capstone repairs
Using a public task as the current task
Repair: verify the active course-room version.
Building before defining acceptance criteria
Repair: state what each test or evaluator should be able to observe.
Reporting an artifact without method evidence
Repair: preserve requirements, decisions, tests and results.
Revising one section in isolation
Repair: audit all dependent claims and outputs after a controlling change.
Final control
Before WGU capstone submission
- Current task and rubric confirmed.
- Every criterion maps to evidence and a location.
- Inputs, permissions and project records are authentic.
- Methods and tests are reproducible.
- Claims stay within the observed evidence.
- Evaluator feedback and dependent revisions are reconciled.
Keep the record authentic
Do not use another student’s task, artifact, code, data or submission. Do not invent clients, approvals, tests or results.
Capstone control file
Keep one evidence file for the entire WGU capstone
Build a working control file with the current task directions, rubric language, approved topic boundary, source notes, calculations, draft decisions and evaluator feedback. For every rubric criterion, record the section where it is addressed and the evidence that makes the response verifiable. This prevents a revision to one section from silently creating a contradiction elsewhere.
Use version names that show the task and revision stage. After feedback, create a comment-to-change table with the evaluator statement, your interpretation, the exact revision, the location and the final check. If a comment is ambiguous, ask for clarification instead of guessing what a competent response requires.
Before resubmission, read only for consistency. Check that names, dates, populations, methods, numerical results and recommendations agree across the narrative, tables, appendices and presentation. The final pass should also confirm that every source is represented accurately and every citation has a matching reference.
Sources and version check
Sources used for this guide
- WGU CBE implementation guide, for program-level competency and capstone principles
- WGU Assessments, for assessment formats and competency demonstration
- WGU Performance Assessment guidance, for current PA preparation and feedback practices
Verify the active requirements
Transfer, assessment, dissertation and exam requirements can change. Confirm the current rule with the institution before acting.
Frequently asked questions
WGU Capstone Guide: Planning, Evidence, Submission and Revision questions
What should I verify first for wgu capstone?
Verify the current institution, program, course or project requirements and identify the exact decision you need to make. Public examples do not override your active requirements.
Can Bright Writers help me plan wgu capstone?
Yes. Help can include requirement breakdown, planning, concept explanation, evidence organization, rubric review, feedback on your own draft and a prioritized revision plan.
Can I use the example on this page in my submission?
Use it to understand the reasoning moves, then create your own work from your assignment, approved evidence and authentic project record. Do not submit the sample as your answer.
What should I send when requesting help?
Send the current instructions, rubric or policy, your own attempt, relevant feedback, the exact point of difficulty and the deadline. Remove passwords and protected personal information.
Will Bright Writers complete or submit the work for me?
No. Support is educational and review-based. You remain the learner, author and person responsible for every submission and institutional decision.