D322 Introduction to IT carries the WGU banner number ITEC 2002 and is worth 4 competency units. It is the survey that maps the whole discipline in one course: systems and services, networking and security, scripting and programming, data management, and the business of IT. Search either D322 or ITEC 2002 and you are looking at one course with one entry on your Degree Plan. Newer degree plans replace it with the 3 CU E004, which carries the same title under banner ITEC 2012; if your plan lists E004 instead, the E004 page is the one you want.
What a five-domain survey actually demands
The trap in D322 is its own breadth. Five domains sit side by side and none of them goes deep, so students read the material once, feel comfortable, and then discover that comfort with vocabulary is not the same as being able to place a term in the right layer of a system. The course wants you to hold a mental map: which problems belong to hardware and operating systems, which belong to the network, which belong to the data layer, and which are governance questions that no technical fix resolves. Every later course in the plan assumes that map exists.
Because WGU is competency based, the course closes when you demonstrate that map, not when you accumulate seat time. Work returns Competent or Not Competent, there are no letter grades and no ordinary grade point average, and the four competency units are simply the size tag on the course. The practical consequence is that D322 is one of the fastest courses in the plan for a student who already works in IT and one of the slowest for a student who tries to memorize five domains of terminology in isolation.
Turning scored aspects into a section plan
If your version of D322 is assessed by a performance assessment, the useful move is to stop treating the prompt as the plan. The prompt tells you the story; the aspects your evaluator scores tell you the shape. Open the rubric before you write anything, list every scored aspect down the left of a page, and give each one its own heading in the draft. WGU requires a score of 2 in each aspect to pass a task, and each aspect is judged on its own, so an essay that is brilliant across three aspects and silent on a fourth comes back untouched by the brilliance.
Here is the arithmetic that keeps a survey submission honest. Say the rubric lists seven scored aspects and the whole task is meant to run about 2,100 words. Reserve roughly 150 words for an orienting opening and 100 for a close, which leaves 1,850 for the body. Divide by seven and you get about 265 words per aspect. Now weight it: aspects that ask you to compare or justify need more room than aspects that ask you to identify, so push two of them to 350 and pull two of the identification aspects down to 190. The plan is now a set of seven headed blocks with a target word count each, and you write to the block rather than to the page.
The reason this matters more in a survey course than anywhere else is that breadth invites drift. With five domains available, a paragraph about network segmentation can slide into a paragraph about firewall vendors and then into a paragraph about compliance, and the aspect that asked about segmentation never receives its evidence. A word budget attached to a heading makes drift visible while you are still writing.
A working shape for a survey deliverable
Survey courses in the College of IT tend to produce short applied reports or briefs rather than research papers. The table below is a shape that holds up when the task asks you to analyze a scenario organization and recommend across domains. Rename the headings to match your own rubric aspects; the proportions are the part worth keeping.
| Block | What goes in it | Share of the word count |
|---|---|---|
| Scenario framing | The organization, its size, what it does, and the one problem the task actually asks about. No history, no filler. | 7 percent |
| Systems and services | Hardware, operating systems and the service model in play, named specifically rather than generically. | 16 percent |
| Network and security | Topology, access paths, and the exposure that follows from them. Tie each risk to something in the scenario. | 20 percent |
| Data management | Where data lives, who touches it, how it is structured, and what retention or integrity constraint applies. | 16 percent |
| Scripting or automation | The repetitive task worth automating and why a script beats a manual runbook here. | 13 percent |
| Business of IT | Cost, service management and the governance point that makes the recommendation adoptable. | 18 percent |
| Close | The recommendation restated as a decision someone could sign, plus the first implementation step. | 10 percent |
Evidence craft when the subject is everything at once
A survey course tempts students into sourcing from whatever page ranked first. Evaluators in the College of IT read a lot of that, and they can tell. Anchor technical claims to the vendor or standards body that owns the thing you are describing: an operating system claim to the vendor documentation, a protocol claim to the relevant standard, a control claim to a published framework rather than to a blog summarizing it. Where the course materials give you a text, cite the text; a survey course is one of the few places where the assigned reading is genuinely the best available source for a definition.
Use the citation style your task names and cite at the point of claim. Two habits pay for themselves here. First, never let a citation carry a claim the source does not make; a source about virtualization benefits does not support a sentence about your scenario company's budget. Second, when you make a scenario-specific claim, say it is yours: phrases like "for this organization" mark the boundary between sourced fact and applied judgment, and evaluators reward that boundary being visible.
What earns Competent, and what gets sent back
Submissions that pass D322 read like someone who can already place a problem in the right domain. They answer the aspect in its first sentence, then support it, then stop. Submissions that come back almost always share one of two shapes: they describe the technology accurately but never connect it to the scenario, or they connect enthusiastically to the scenario while leaving one aspect unaddressed. Neither is a writing problem. Both are planning problems.
The good news in competency-based assessment is that a return is not a penalty. Performance assessment work can be revised and resubmitted without any grade cost, so the sensible strategy is to submit a complete draft rather than to polish indefinitely; evaluator feedback is more precise than your own guessing. Where D322 uses an objective assessment, that exam is proctored, and the boundary there is absolute. We build preparation: domain-by-domain study plans, practice questions, and a read on whether your preassessment score says go or wait. We never sit an exam, take no part once one begins, and portal credentials are never requested or handled.
Stuck in the five-domain sprawl?
Send the D322 rubric or your preassessment report and we will map it into a section plan you can write against the same day.
Six mistakes that cost time in this course
- Studying the domains as five separate courses. The assessment asks you to move between them inside one scenario. Study the joins, not the lists.
- Writing to the prompt instead of the rubric. The prompt is prose and hides the boundaries between aspects. The rubric shows them, and the rubric is what gets scored.
- Confusing the two codes. D322 is 4 CUs under ITEC 2002; E004 is the 3 CU version under ITEC 2012. Work the one your Degree Plan lists, because the other will not close your requirement.
- Generic scenario technology. "A firewall" and "a database" score lower than a named product class with a stated reason. Specificity is the cheapest depth available in a survey course.
- Treating the business-of-IT aspect as filler. It carries real weight and it is the aspect students most often write in two sentences. Cost, service management and governance need the same evidence discipline as the technical blocks.
- Delaying the submission to keep polishing. Revision is free. Sitting on a draft for a week to fix wording burns term time that could have bought another course at the same flat rate.
Three questions students ask about D322
Is D322 the same course as ITEC 2002?
My plan shows E004, not D322. Which one do I take?
Do I need IT work experience to move through it quickly?
How support runs on this course
Confirm the code on your Degree Plan row before anything else happens, because D322 and E004 are not interchangeable and finishing the wrong one closes no requirement. Then send the rubric or your preassessment report. Written work comes back aspect-mapped: a heading for each scored aspect, a word target beside each heading, and every technical claim tied back to the scenario organization rather than left floating as general description. Preparation work comes back domain by domain, with practice questions and an honest read on whether your preassessment score says book the attempt or spend another week first. The walkthrough is the part that transfers, because the habit of placing a problem in the right domain is what the rest of the College of IT plan runs on.
The term economics favour speed in a survey course. A WGU term is six months at a flat rate, so effective cost per course falls every time you close another one inside the same term. Four competency units of breadth is among the fastest work available to anyone who already handles IT problems at work, and clearing it in weeks rather than months buys room for a harder course at no extra price.
The last pass before you submit
Most returns in a survey course are structural rather than factual, which means a short mechanical check catches them faster than another read for style. Run this list once the draft is complete, before you read a single sentence for wording.
- Every scored aspect has its own heading, worded with the rubric's noun rather than your preferred synonym.
- Every domain block names something specific from the scenario. If a paragraph would survive being pasted into a different company's report, it is too generic to score well.
- Every sourced claim is a claim the source actually makes, and every applied judgment is marked as yours.
- The business of IT block carries real evidence rather than two closing sentences.
- The close states a decision someone could sign, plus the first implementation step.
- The code on the document matches the code on your Degree Plan row.
Where D322 sits in WGU's programs
The July 2026 catalog places this code in 4 current WGU programs. 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.