E004 Introduction to IT sits under banner number ITEC 2012 and is worth 3 competency units. It is the current entry point to the College of IT, covering fundamental concepts, organizational structures and the roles inside them, with networking, database management, cybersecurity, artificial intelligence and software development each getting a pass. E004 is the replacement for the older 4 CU D322, which carries the same title under banner ITEC 2002; if your Degree Plan shows the older code, work from the D322 page instead.
A shorter course with a wider brief
E004 covers more ground than its predecessor in fewer competency units, and that compression is the whole personality of the course. Artificial intelligence and software development now appear beside the traditional networking, database and security material, which means the same reading week has to carry more distinct vocabulary. Students who fail to finish quickly are almost never blocked by difficulty. They are blocked by treating a 3 CU course as a small course and giving it small attention until the first assessment shows how many separate ideas it expects them to hold.
The second half of the course brief is easy to underrate: structures and roles. WGU wants you to know who does what in an IT organization, because every later course assumes you can tell a systems administrator's problem from a security analyst's problem from a data engineer's problem. If a scenario in your assessment names a job title, that title is doing work in the question and is not decoration.
The database strand deserves its own warning. It arrives early, looks like vocabulary, and is the piece students most often carry forward broken. Knowing that a relational database stores rows in tables is not the same as understanding why a table is split, what a key guarantees, or why a report that joins two sources can produce more rows than either one contained. Later data courses in the plan do not reteach that intuition; they assume it. Ninety minutes spent drawing two related tables by hand pays back across three subsequent courses.
Assessment at WGU returns Competent or Not Competent. There are no letter grades, no ordinary grade point average, and the 3 CUs describe the size of the course rather than a score. Terms run six months at a flat rate, so a course like this one, closed early, quietly lowers what every other course in the term costs you.
Reading the aspects as a blueprint
If your section of E004 is assessed by a performance assessment, treat the scored aspects as the table of contents you were not given. The prompt reads as a story about an organization; the aspects tell you how many separately judged answers the story is hiding. WGU requires a score of 2 in every aspect for a task to pass, and no aspect can be carried by a neighbouring one, so an unaddressed aspect is a returned task no matter how strong the rest reads.
Try the arithmetic on a five aspect task with a 1,500 word target. Take 120 words for the opening that names the organization and the question, and 90 for the close. That leaves 1,290 for the body, or about 258 words per aspect at a flat split. Then adjust for verb weight: an aspect that says "explain" or "recommend" needs about 350 words to carry a claim plus support plus a reason, while an aspect that says "identify" or "describe" is usually complete in 170. Two heavy aspects at 350 and three lighter ones at 197 comes to 1,291, which is the plan. Write each block to its number and stop when you hit it.
The discipline this creates matters most in the AI and software development material, where students either write far too little because the topic is unfamiliar or far too much because they have opinions. A word target attached to a heading removes both failure modes before the draft exists.
Shape for a roles-and-systems brief
Introductory College of IT tasks usually produce a short applied brief written for a named audience inside a scenario organization. The proportions below work when the task asks you to survey an organization's technology and say something useful about it. Swap the block names for your own aspect names and keep the ratios.
| Block | Job it does | Target share |
|---|---|---|
| Audience and purpose | Who reads this brief, what decision it supports, and the single question it answers. | 8 percent |
| Current state | The organization's systems as they are, described concretely enough that a reader could picture the rack or the tenant. | 15 percent |
| Roles and ownership | Which function owns each system and where the ownership gaps sit. This is the block students skip. | 14 percent |
| Domain analysis | Networking, data, and security read against the current state, one short pass each rather than three essays. | 26 percent |
| Emerging technology | Where AI or automation changes the picture, with one specific use case rather than a general claim. | 15 percent |
| Recommendation | What to do, who owns it, and what it costs in effort. Written so a manager could act on it. | 14 percent |
| Close | One paragraph. Restate the decision, name the first step, stop. | 8 percent |
Sourcing a course that spans six subjects
Breadth makes sourcing harder, not easier, because each domain has its own authority. Take definitions from the course materials, technical behaviour from vendor or standards documentation, and workforce or role claims from published occupational data rather than from a careers article. For AI material specifically, prefer primary documentation of a service or model over commentary about it; commentary in this field goes stale inside a semester and evaluators notice when a claim is dated.
There is a particular sourcing trap in an introductory course, and it is worth naming. Definitions of common terms are freely available in a hundred places, so students grab whichever wording reads best and cite a general reference site. That choice is not wrong so much as weak: it tells the evaluator you found a definition rather than that you understood which authority owns it. Preferring the standards document, the vendor glossary or the assigned course text costs no extra effort at the moment of writing and changes how the whole submission reads.
Keep citations inside the aspect block that uses them so the evaluator never has to hunt for support. Use the citation style your task specifies and be consistent about it. The single most useful habit is separating what you sourced from what you concluded. A sentence like "the documentation describes three storage tiers" is sourced; a sentence like "for this organization the middle tier is the right default" is yours, and marking that boundary in plain words is one of the cheapest ways to look like a professional writer to someone reading twenty submissions a day.
The line between Competent and returned
A submission earns Competent when every aspect has a visible, self-contained answer that a reader could locate in under five seconds. It gets returned when the writing is good but structurally invisible, or when a domain is described in general terms that would fit any organization on earth. The single most common return in an introductory survey is a brief that never mentions the scenario after its opening paragraph.
Returns are not punishment. Performance assessment work can be revised and resubmitted without a grade penalty, so a complete draft submitted early is worth more than a perfect draft submitted late. Where E004 uses an objective assessment, that exam is proctored and the boundary is fixed. We prepare students for it with structured study plans, practice questions and a read on whether a preassessment score means go or wait, and we take no part during any assessment. We never ask for portal credentials and would not accept them.
Three CUs, six subjects, one deadline?
Send your E004 rubric or preassessment report and we will turn it into a headed section plan with word targets attached.
Five errors that stall students here
- Sizing effort by competency units. Three CUs describes course weight, not workload. E004 asks about six subject areas and rewards a study plan built around that number instead.
- Working the wrong code. E004 is ITEC 2012 at 3 CUs; D322 is ITEC 2002 at 4 CUs. They share a title and most of a syllabus, but only the code on your Degree Plan closes your requirement.
- Skipping the roles material. Structures and roles feel like background reading and then appear inside a scenario as the thing being tested. Learn the ownership boundaries.
- Treating AI as an opinion section. The aspects want a use case with a mechanism, not a view on whether AI is good. Name a task, name what the technique does to it, move on.
- Writing one long undifferentiated essay. Without headings that mirror the aspects, an evaluator has to reconstruct your plan while scoring you, and reconstruction failures read as missing content.
- Letting the database strand stay abstract. Terms without a drawn example do not survive to the next course, and the next course will not slow down for you.
- Waiting for confidence before submitting. Confidence is not a submission criterion. Coverage of every aspect is, and coverage is checkable in twenty minutes with the rubric open beside the draft.
Three questions students ask about E004
What is ITEC 2012 and how does it relate to E004?
I already took D322. Do I have to take E004 as well?
How much programming does the software development part expect?
Where E004 sits in WGU's programs
The July 2026 catalog places this code in 6 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.