WGU PA task rubrics, explained

The anatomy of a WGU rubric

Open any task and you will find three linked parts. The prompt lists lettered requirements (A, B, B1, C, and so on). The rubric restates each requirement as an aspect and gives it a scoring row. Most rows show at least two columns: what a Not Yet Competent response looks like and what a Competent one looks like, sometimes with a middle tier the evaluator will not pass. The Competent column is the only one that matters, because it is the literal definition of done for that aspect.

Read across a single row and you have that aspect's acceptance criteria in the university's own words. Read down the whole table and you have the exact checklist an evaluator walks. The strongest submissions turn that table into their own structure: one heading per lettered requirement, in the same order, so nothing can be forgotten and nothing is left for the evaluator to hunt.

Reading the aspect verbs

The difference between Competent and Not Yet Competent usually lives in a single verb. An aspect that says describe wants a clear account; one that says analyze wants causes and consequences weighed; one that says justify wants reasons given against alternatives; one that says evaluate wants a judgment defended with criteria. Answering a justify aspect with a describe response is the most common way a thorough, well-written task still comes back. Match the verb's depth and you have met the aspect; miss it and length will not save you.

The misreads that bounce tasks

• The implicit answer. The information is somewhere in the document but never appears as a direct, labeled response to the aspect. This is the single most common return.
• The generic answer to a scenario. Many tasks supply a company, patient, or classroom; an aspect that ignores those given names and numbers reads as unmet even when the content is correct.
• The wrong artifact. Some aspects require a supplied template, a spreadsheet, or a recorded presentation; correct content in the wrong container does not pass.
• The sourcing slip. Aspects that ask for evidence want current, real sources cited in APA unless the task says otherwise, and formatting errors can trip a professional-communication aspect on their own.

The returned-task loop is a feature

A task that misses an aspect is not a failure on your record. It comes back with evaluator comments naming exactly which aspects sat at Not Yet Competent, you fix only those, and you resubmit as many times as it takes with no penalty and nothing recorded on your transcript. The discipline that ends the loop is literal: answer each comment as its own labeled passage rather than lightly editing the paragraph the evaluator already rejected. Our full method for this lives in the task-writing manual, and how these marks roll up into a Passed course is in the grading guide.

Where tutoring fits

Reading a rubric well is a learnable craft, and it is also the exact thing we do for you when a task is due faster than the craft can be practiced. Send the code, the task number, and the rubric, and a draft comes back built on the aspect skeleton, every aspect answered at its verb's depth, with an aspect map showing where each row is satisfied so you can defend every line and rework it into your own voice.

Sources and verification

Every claim here is checked against official WGU sources, and the primary documents reward a look of your own:

• wgu.edu/about/institutional-catalog.html: WGU's Institutional Catalog, the primary source for assessment, term, and transfer policy
• wgu.edu/blog/who-evaluates-wgu-performance-assessments1712.html: WGU on its evaluation faculty and the under-72-hour service level
• apastyle.apa.org: APA Style, the authority behind the formatting most tasks require
• nwccu.org: Northwest Commission on Colleges and Universities, WGU's institutional accreditor

Keep going