WRTG 393 is a 3-credit upper-level course at the University of Maryland Global Campus (UMGC). UMGC describes it as a comprehensive, project-based study of applied technical writing and lists WRTG 112 as the prerequisite.
The aim is to design and develop technical documents using strategies and technologies suited to a variety of audiences. Students often find it unlike essay writing: technical documents are judged on whether users can complete a task correctly.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus |
| Code and title | WRTG 393 Advanced Technical Writing |
| Level | Undergraduate (upper level), 3 credits |
| Prerequisite | WRTG 112 |
| Requirement | General education: upper-level advanced writing |
| Format | Project-based |
| Credit note | Credit is allowed for only one of COMM 393 or 393X, ENGL 393 or 393X, or WRTG 393 or 393X |
What WRTG 393 Covers
| Topic from the catalog | What it means in practice |
|---|---|
| Applied technical writing | Producing documents that explain how to do or understand something technical |
| Design and development of documents | Planning, drafting, testing and revising |
| Strategies and technologies | Using appropriate methods and software tools |
| Variety of audiences | Writing for experts, novices and mixed readers |
Key Concepts Explained
Know the User and the Task
Technical writing begins with the user: who they are, what they know, what they need to do and in what setting. A document for a new user needs more explanation and visuals than one for a specialist.
Illustration (invented task, method only): Instructions for resetting a device should state the goal, list needed items, give one action per numbered step, and say what the user should see after each step. A warning goes before the step it applies to.
Document Design
Layout is part of the message. Use headings, white space, lists, tables and visuals to help readers find what they need. Keep design consistent.
Testing and Revising
A strong technical document is tested with a real or realistic user. Ask someone to follow it without help and note where they hesitate; those places need revision.
Typical Assignments and How to Approach Them
UMGC describes the course as project-based. Exact projects are set in each section; the table is general guidance.
| Assignment type | What it tests | How to approach it |
|---|---|---|
| Audience and task analysis | Knowing users | Describe users, tasks and context before drafting |
| Steps or procedure | Clarity and sequence | One action per step, with expected results |
| Report or proposal | Structure and evidence | Use headings, data and advice |
| Usability test and revision | Testing and improving | Record problems and show what you changed |
A Process for Technical Projects
| Phase | Output |
|---|---|
| Analyze | User profile and task list |
| Plan | Outline and design sketch |
| Draft | First version with visuals |
| Test | Notes on where users struggle |
| Revise | Improved final document |
Technical Style Basics
Use plain words, short sentences and consistent terms. Prefer active voice and commands for steps. Put warnings before the action they relate to. Use tables and lists where readers compare or follow sequences.
What a Strong WRTG 393 Submission Looks Like
A strong technical document can be used by its intended reader to complete a task. It states its audience, uses clear steps and consistent terms, and has a layout that supports scanning. Visuals have a purpose and are labeled.
It also shows evidence of testing and revision, for example a short note on what a test user struggled with and what you changed.
Questions to Ask Your Instructor
Ask which projects are required, which software tools are expected, whether you need access to a real user for testing, and how visual design will be graded. Technical projects often depend on tool choices made at the start.
Where Students Get Stuck
- Writing for yourself. You know the subject; the reader may not.
- Steps with several actions. Split them.
- Design as decoration. Every visual should serve a purpose.
- Skipping testing. A short test finds most problems.
Study Tips for WRTG 393
- Write a user profile and task list before you write anything else.
- Use consistent terms for each object or action.
- Number steps and keep sentences short and in the command form.
- Ask a friend to follow your document and watch where they stop.
How We Help with WRTG 393
Send the project brief, rubric, subject materials and any draft. A writing tutor can explain technical writing practice, prepare a model for a comparable project, or review your draft for clarity, structure and design. For wider support see our white paper writing guide.
GradeEssays is independent and not affiliated with UMGC. Our work is a study and reference aid; submit your own work under UMGC's academic integrity policy. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.
Make Your WRTG 393 Document Usable
Share the brief and draft. We review clarity, structure and design, or prepare a model to study.
Start My WRTG 393 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
UMGC lists WRTG 112.
Three credits.
Yes. UMGC describes it as a comprehensive, project-based study.
The general education requirement in upper-level advanced writing.
No. The focus is on designing documents for users and tasks.
Yes. We can review clarity, structure and design, while you submit your own final work.