WGU C948: Technical Communication

C948 Technical Communication: what this course really asks of you

WGU's C948, Technical Communication, sits in the School of Technology and shows up on many IT and information-technology-management degree plans. Despite the "technical" label, this is a writing course. Its whole premise is that people who work in technology spend an enormous amount of their day explaining complicated things to audiences who do not share their expertise: a CIO who wants the bottom line, a project team that needs step-by-step instructions, a client who is nervous about cost, a vendor who needs precise specifications. C948 asks you to prove you can shift your message, format, and tone to fit each of those readers without losing accuracy.

Direct answer: C948 is passed through a performance assessment, not a proctored multiple-choice exam, so you "study" by learning to write clearly for a stated audience and purpose and then following the task rubric line by line. Read every prompt carefully, match each deliverable to the audience it names, and revise against the aspect-by-aspect requirements before you submit.

Because the deliverable is a document you build rather than a test you sit, this course rewards care over cramming. Many students find it a welcome break from heavier technical or math-based classes, but "lighter" is not the same as "automatic." The most common reason a submission comes back is not bad writing; it is a missed requirement or an audience mismatch. If you treat the rubric as a checklist and the audience as a real person, you are most of the way there.

What the performance assessment covers

C948 is assessed by performance assessment (PA) work broken into several components, and each component changes the purpose and the audience, which is exactly the skill the course is testing. Based on public course descriptions, the work centers on the following areas:

• Choosing the right genre (type): deciding whether a message belongs in an email, a memo, a formal report, a proposal, or another format for the audience you are given.
• Audience analysis: identifying what a specific reader already knows, what they need, and how much technical detail is appropriate.
• Design principles: using headings, layout, white space, and visuals so a document is easy to scan and understand, not just grammatically correct.
• Accuracy and ethics: communicating truthfully and clearly, without exaggeration or misleading framing.
• Adapting tone and formality: writing to leadership differently than you would write to a peer team or an outside client.
• Clear, organized prose: logical structure, concise sentences, and correct mechanics across every deliverable.

The exact prompts are set by WGU and can change, so always work from the task instructions and rubric in your current course of study rather than any example you find online.

How hard it is and how long it takes

Many students report that C948 is one of the more approachable courses on an IT plan, precisely because it does not involve an unpredictable objective exam. If you already write reasonably well, the main challenge is patience and attention to instructions. If writing is not your strength, budget more time for revision, but know the material is learnable.

Completion times vary widely with your writing background and how many other courses you are juggling. Some students move through it in a matter of days of focused effort; others spread it over a couple of weeks. Rather than chasing anyone else's timeline, plan for at least one full draft plus a dedicated revision-and-proofread pass per deliverable, and give yourself a day between writing and editing so you can see your own work with fresh eyes.

A study plan built around the task, not a test

Because there is no question bank to drill, your "studying" is really structured practice at writing on demand. A plan that works well for this course:

• Map the rubric first. Before writing a word, list every aspect the evaluator will score and turn each into a requirement you can check off. This is the single highest-value habit in C948.
• Read the course material on genre and audience. Use the provided learning resources to get concrete on when a memo beats an email, and what "design" means for a document. Take short notes in your own words (active recall) rather than highlighting.
• Draft one deliverable at a time. Write for the specific audience the prompt names. Say out loud who the reader is and what they need before you start each section.
• Revise in passes. First pass for content and requirements, second for organization and design, third for grammar and tone. Reading your draft aloud catches clunky sentences fast.
• Self-test against the rubric. Score your own draft as if you were the evaluator. Anything you cannot clearly point to in your document is a gap to fix.

Spacing this work over several sessions instead of one marathon almost always produces cleaner writing, because revision benefits from distance. If you want to see how communication skills carry across the rest of the tech program, it helps to look at neighboring courses like D075 Information Technology Management Essentials and more build-heavy courses such as D288 Back-End Programming, where documenting your work clearly matters just as much as the code.

Mistakes that send C948 submissions back

Most revisions in this course come from a handful of avoidable problems:

• Missing a required component. The task has multiple parts; skip or thin out one and the whole submission is marked incomplete. Check every part against the rubric.
• Writing to the wrong audience. Sending an executive a wall of technical detail, or giving a technical team a vague summary, misses the core skill being tested.
• Ignoring design. A correct but dense block of text loses points because C948 grades whether a reader can actually use the document.
• Copying a template too literally. Sample documents online are for shape and tone only. Reusing someone else's wording risks an integrity violation and rarely fits your exact prompt.
• Submitting your first draft. Small errors in grammar, formatting, and consistency add up. A dedicated proofreading pass is not optional here.

C948 Readiness Checklist

Before you submit, confirm that you can honestly answer yes to each of these:

• Can you name the audience and purpose for every deliverable in the task?
• Can you point to where in your document each rubric requirement is satisfied?
• Can you explain why you chose each genre (email vs. memo vs. report vs. proposal)?
• Can you show design choices, such as headings and layout, that make each document easy to scan?
• Can you confirm your tone shifts appropriately between leadership, peers, and external readers?
• Can you verify every claim in your writing is accurate and stated ethically?
• Have you read each deliverable aloud to catch awkward or unclear sentences?
• Have you proofread for grammar, spelling, and formatting consistency in a separate pass?
• Is all of the writing genuinely your own, in your own words?

C948 FAQ

Is C948 an objective assessment or a performance assessment?

C948 is assessed by a performance assessment. You complete a task made up of several written deliverables rather than sitting a proctored multiple-choice exam. Always follow the task instructions and rubric in your current course of study.

How many competency units is C948?

WGU sets the competency-unit value for each course, and it can differ by program version. Check the official course details in your degree plan or the WGU institutional catalog for the current number rather than relying on a figure from a study site.

How long does it take to finish C948?

It depends heavily on your writing background and workload. Many students complete it faster than their technical courses because there is no unpredictable exam, but plan for at least a full draft plus a separate revision and proofreading pass for each deliverable.

Is C948 hard?

Many students describe it as one of the more manageable courses on an IT plan, especially if they already write comfortably. The difficulty is less about writing talent and more about following instructions precisely and matching each message to its audience.

What is the best way to prepare?

Turn the rubric into a checklist, learn the course material on genre and audience, then draft one deliverable at a time and revise in focused passes. Self-scoring your draft against the rubric before submitting catches most issues.

Can I use example papers I find online?

Use them only to understand structure and tone. Copying wording risks an academic-integrity violation and usually will not fit your specific prompt. Your submission must be original and written for the exact audience each task section names.

For more study guides across this program, see the School of Technology hub, related courses like C792 Data Modeling and Database Management Systems, or browse the full guide index. You can confirm official course facts on the WGU IT degrees page.