Across every WGU technology program we split the work the honest way: proctored OAs and embedded industry certifications get blueprint-based preparation, while performance-assessment projects, like C949 Data Structures and Algorithms write-ups, D522 Python for IT Automation deliverables, and D282 Cloud Foundations work, get drafts and documentation built by writers who ship code for a living, in 24 to 48 hours, revised free until Passed. Dual-coded courses are drafted to your generation's rubric, C-series or D-series.
The two workloads inside every tech plan
Exam courses dominate the early plan: foundations, networking, security basics, many finishing in industry certifications that count for course credit and job interviews at once. These pace the degree, and they respond to exactly one thing, structured preparation against the published blueprint, practiced until the preassessment clears the bar. Project courses take over later: coding tasks with written justifications, automation scripts with documentation, data analyses with reports, architecture proposals. These grade on the write-up as much as the artifact, which surprises engineers every time; a working script with a thin narrative bounces, because the rubric's aspects live mostly in the prose.
What working-engineer drafting means
- Code-adjacent tasks arrive with the technical choices defensible: why this structure, why this library, what breaks under load
- Documentation written like documentation, requirements, design rationale, test evidence, not padded essay
- Data-analytics tasks include the actual analysis artifacts, notebooks and outputs consistent with the narrative
- Diagrams that match the prose: network topologies, architecture sketches, data flows, checked as part of QA
- Legacy C-code or current D-code rubrics respected per the code guide
Pacing the ladder
The proven tech-term shape alternates lanes: an exam course in study while a project course drafts, two closes a month as the steady state, more in sprint months. Front-load the certification-bearing courses, their double value decays if the degree stalls, and never leave the capstone alone at the end of a term; run it on the staged method with margin. At about $4,030 per undergraduate term, the gap between a four-term and an eight-term finish is a workstation and a vacation; the expedite desk maps your version free.
Ship the degree like a project
Send your program and Degree Plan. Exam plan plus first project draft, moving within 24 hours.
Sorting the Degree Plan before the term opens
Stop reading your Degree Plan as a list of subjects and read it as three piles sorted by instrument. Pile one is the courses your portal shows as objective assessment only. Pile two is performance assessment only. Pile three is both. The portal is the only place that says which pile a course belongs in, and the sort is worth twenty minutes with a spreadsheet, because the piles behave nothing alike.
Add the CU column next. Forty two CUs left in front of you might split into twenty one CUs of exam-only work, twelve CUs of task-only work, and nine CUs of both. That split is your term stated honestly. The twenty one exam CUs are study hours nobody can take off your hands, and nobody should offer to. The twelve task CUs are drafting weeks that run beside study rather than instead of it. The nine dual CUs are the ones that surprise people, because they want both kinds of effort and get budgeted as though they were one course each.
The sort also sets the order. Exam courses carry no evaluator queue inside them, so they close the hour you pass, which makes them the CUs to bank first when a term needs momentum against the pace minimum. Task courses spend days in evaluation no matter how fast the draft moves, so they want to be open early and stay open, with the next task already drafting while the last one sits with an evaluator.
A term budgeted in hours you actually have
Term maps fail because they count courses instead of hours. Run the other arithmetic once, on paper, before the term opens.
Start with the honest number. Twenty hours a week across a twenty six week term is 520 hours. Subtract the weeks you already know you will lose to a holiday stretch, a release at work, a family event: four lost weeks at twenty hours is eighty hours gone, leaving 440.
Now price the piles. Give an exam course a planning figure of fifteen study hours per CU, so a 3 CU exam course is a 45 hour project and a 4 CU one is 60. Six exam courses averaging 3 CUs comes to 270 hours. A task course you draft entirely yourself lands somewhere between 25 and 40 hours depending on the artifact. A task course where the draft arrives from us costs you closer to 8 to 12, which is what it takes to read the draft properly, rebuild it in your own voice, check it line by line against your task instructions, and submit. Four of those is about 40 hours.
270 plus 40 is 310 hours against 440 available. Resist the urge to fill the 130 hour gap. That gap is what absorbs the course that fights back, the first attempt that does not go your way, and the fortnight your life takes back without asking. A term plan with no gap in it has already failed and is only waiting for the evidence.
Then calibrate, because fifteen hours per CU is a planning assumption rather than a fact about you. Track your first exam course honestly. If it cost 70 hours instead of 45, multiply every remaining exam estimate by 1.5 and rebuild the map in week three, while fixing it still costs a conversation with your Program Mentor instead of a term.
Artifact first or write-up first, and when each is wrong
Every technical task is two deliverables wearing one name: the thing you built and the prose that explains it. Which one you make first is a real decision with a real cost on both sides, and engineers tend to pick by instinct rather than by task.
Building first
Writing the code, the model, or the diagram first is faster while it lasts, and it buys one genuine advantage: the prose you write afterward is true. Documentation written against a working artifact describes what the artifact does rather than what you hoped it would do, and specifics are what an evaluator can actually score. The cost is scope. Built to your own taste, an artifact answers questions your task instructions never asked and quietly skips ones the aspects your evaluator scores do ask. Finding that out afterward means rework in the expensive direction, because every change to the artifact drags the paragraphs that described it.
Skeleton first
Writing the narrative skeleton first, one heading per requirement in your task instructions, then building to fill it, guarantees that nothing gets built that nothing scores. The cost is that prose written before the artifact exists is usually wrong in its details, so you pay a reconciliation pass at the end. On genuinely exploratory work, an analysis whose result you cannot know in advance, writing the conclusions first is fiction, and it reads like fiction to somebody who has read a hundred of these.
The rule that settles it
Ask whether the outcome is knowable before you build. Deterministic work, a script with defined inputs and outputs, a topology that satisfies stated requirements, an implementation of a structure you already understand, goes skeleton first every time. Exploratory work goes artifact first, but you still write the headings first, because headings are scope control rather than prose. That is the order our task drafts follow, and when a task is the exploratory kind we say so at the start instead of pretending the answer was known in advance.
The five course shapes in a technology plan
| Course shape | What a normal week holds | Where it stalls | What closing it depends on |
|---|---|---|---|
| Exam only | Study blocks, practice, one appointment | Weeks of circling because the booking never gets made | Your own readiness evidence, then a slot |
| Certification bearing | Study against published exam objectives, plus scheduling logistics | Waiting to feel ready, then discovering lead time | Objectives coverage and whatever your program sets for further attempts |
| Single deliverable | Drafting, then a queue | Idle days with nothing else in motion | Every aspect answered, then evaluator turnaround |
| Multi task project | Overlapping tasks with dependencies between them | Task two waiting on task one's feedback | Sequencing, and the queue counted once per task |
| Capstone | A staged project with approvals inside it | Opening it in the last six weeks of a term | Approval gates that run on somebody else's calendar |
Read the third column as the list of ways this college takes time from you, and notice that only one entry is about difficulty. The rest are scheduling. That is the argument for holding a task course and an exam course open together, and the argument for putting the capstone on a calendar before it officially becomes your problem.
What actually costs technology students weeks
- Absolute paths and machine-specific assumptions in submitted code: the script runs because a folder exists on your laptop, and fails the first time anyone else opens it
- Screenshots cropped past the evidence: an aspect that asks you to show a result wants the command, the output, and whatever identifies the work as yours
- Diagram labels that disagree with the prose, which hands an evaluator a contradiction between two documents you wrote yourself
- Features nobody asked for: every extra capability is more surface to defend in writing and more that can be wrong, and the aspects are the scope
- Booking a proctored appointment as though it were a same-day action, and reading your program's rules on further attempts only after the first one
- Saving the heaviest CU course for last, when the term boundary is the only deadline at this university that can actually hurt you
Three questions from technology students
My code works but the task came back. Can you fix only the write-up?
I have eight years in the field. Can I skip preparation and sit the exam?
Can I use code I wrote at work as my task artifact?
The technology programs, one by one
Every technology program grid in WGU's July 2026 catalog now has a full standard-path page: 34 programs and 241 unique nonzero course codes, each linked to its own course guide. Open the program shown on your Degree Plan, then work class by class.