C218 is the MBA, Information Technology Management Capstone, listed in the WGU catalog under the CCN ITM 6900 and worth four competency units. The catalog calls it the culminating integrative course of the MBA Information Technology Management program. What makes this capstone distinct from a general business capstone is the audience problem. A technology proposal has to be credible to someone who will never read an architecture diagram and credible to someone who will, and student submissions usually collapse toward one of those readers. The method below keeps both in the room by building a traceability chain from business objective all the way to measurement, so that every technical statement has a business reason above it and every business claim has a technical mechanism below it.
The traceability chain, and why it decides the score
Write your capstone as a chain with five links. A business objective with a measure attached. A capability the organization needs in order to hit that objective. A technical approach that provides the capability. A cost and effort to obtain the approach. And a measure that will show, after implementation, whether the objective moved.
Every paragraph in the document should be traceable to a link in that chain. The test is simple: pick any technical sentence and walk upward, asking why it is here. If the answer arrives within two steps at a business objective, the sentence belongs. If it does not, it is a specification masquerading as an argument.
The chain also fixes the audience problem without stylistic gymnastics. Executive readers move down the chain until they are satisfied and stop. Technical readers start further down and check that it holds. You do not need two documents, you need one document whose reasoning runs in a direction both readers can travel.
Working from the scored aspects: budget along the chain
If your capstone is assessed by a performance assessment, the aspects your evaluator scores are the specification. Map each one to a link in the chain, then size accordingly.
Here is the arithmetic on a plausible shape. Say the capstone carries eleven scored aspects and you plan around 4,400 words of substance. Sort the aspects by chain position: two on objective and context, two on capability and requirements, three on technical approach, two on cost and risk, and two on implementation and measurement. Now weight by how contested each link is. Objective and context are rarely argued with, so 250 words each, which is 500. Capability and requirements are where scope is set, so 400 each, which is 800. Technical approach is the heart, so 550 each, which is 1,650. Cost and risk get 500 each, which is 1,000, because unpriced proposals are the classic return. Implementation and measurement get 225 each, which is 450. Total 4,400, and the two heaviest sections are exactly the two an experienced reviewer would attack first.
Keep 150 words in reserve for a decision summary at the front. Executives read the first page; put the recommendation, the cost, the timeframe and the measure there and let the rest of the document defend it.
The chain, link by link
| Link | What must be nailed down | How it usually fails |
|---|---|---|
| Business objective | A stated outcome with a number and a deadline, owned by a named function | An objective phrased as adopting a technology |
| Capability required | What the organization must be able to do that it currently cannot | Skipping straight from problem to product |
| Current state | Systems, data, integrations, skills and processes as they are now | An assumed blank slate, which makes every cost wrong |
| Technical approach | The chosen option, the alternatives, the integration points, the data implications | One option presented with no comparison |
| Security and compliance | What data is touched, what protections apply, what obligations attach | A single paragraph appended at the end |
| Cost and effort | Acquisition, implementation, integration, training, ongoing support, and internal time | Licence cost quoted as total cost |
| Risk | Technical, organizational and vendor risks, each with a response and an owner | Risks listed with no mitigation attached |
| Measurement | The metric, its baseline, its target and when it is read | Success defined as successful implementation |
Evidence craft for a technology proposal
Technology proposals have an evidence hazard that other business documents avoid: nearly all the accessible material is produced by people selling something. Vendor documentation is authoritative about what a product does and unreliable about what it achieves. Analyst material carries useful market structure and should be attributed rather than treated as neutral fact. Peer-reviewed and practitioner research is the right source for adoption effects and failure rates.
Cost claims need composition rather than a total. Build a figure from parts a reader can question: licences by seat or capacity, implementation days at a stated rate, integration effort, training hours, and the internal staff time the project consumes, which is the line students omit most often and the one an executive will ask about first.
Where the capstone touches data, say what data, where it moves, who can see it and what obligations attach. A capstone that proposes moving information between systems without addressing that has left out the part that would stop the project in a real organization. Use APA unless the task names another style, cite at the point of claim, and label every estimate as an estimate with its basis in the same sentence.
What separates Competent from a return
WGU requires at least a 2 in every scored aspect for a performance assessment task to pass, and technology capstones lose most often on two aspects. The first is the alternatives aspect: a single recommended approach with no comparison, which cannot satisfy any rubric wording that includes evaluate or justify. Two credible alternatives, each with the reason it lost, converts it.
The second is the measurement aspect, where students define success as delivery rather than as effect. If the metric in your closing section is not the same metric that appeared in your objective, the chain is broken and the evaluator will see the break.
Revision at WGU costs no grade penalty, so a returned capstone is a defect list. Repair the named aspects, then walk the chain again from objective to measurement, because a change to the technical approach usually invalidates a cost line or a risk somewhere else.
Six mistakes that cost time in C218
- Leading with the technology. If the product is named before the objective, the whole document reads as a solution looking for a problem.
- No current state. Costs and integration effort are meaningless without knowing what already exists.
- One option, no comparison. The fastest way to lose an evaluation aspect you had the material to pass.
- Security as an afterthought. In a technology capstone this reads as a professional gap, not just a missing section.
- Total cost of ownership reduced to licence cost. Implementation, integration, training and internal time are usually the larger half.
- Leaving the capstone until the term is nearly gone. Terms run six months at a flat rate, and a capstone that slides into another term is the most expensive delay in the program.
How we work this course with you
Send the course code and your capstone instructions and you get back the chain built for your proposal, an aspect map with the weighting applied, a cost structure with every line itemized, and drafting support document by document so the reasoning stays visible while you rewrite it in your own voice. If your plan carries an objective assessment anywhere, our work there is preparation only. Objective assessments at WGU are proctored, so our involvement ends before one starts. We do not sit, take or assist during any assessment, and we never ask for or store portal credentials.
Questions C218 students ask
How technical should this capstone actually get?
What if my proposal involves technology I have never worked with?
I have no security background. How do I write that section credibly?
Landing the C218 capstone?
Send the ITM 6900 instructions and your term end date. A staged plan and a chain map come back.
Where C218 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.