D355 is HRM 3530 Total Rewards in the WGU catalog, worth 3 competency units, and the catalog describes it as designing compensation, benefits and recognition systems that attract and retain employees. It is the current replacement for the legacy course C236 Compensation and Benefits. The change in title is the change in scope: rewards here include everything of value an employer gives, not only what lands in a bank account. Build from whichever code appears on your Degree Plan.
What the word total is doing in the title
The legacy course was about pay and benefits. The current one is about the whole reward package, and that widening is the reason submissions written from older study material come back incomplete. A total rewards frame usually contains five families: base pay, variable pay, benefits, recognition, and development or career opportunity. Some frameworks add wellbeing as its own family.
The point of the frame is not taxonomy. It is that the families trade against each other. An employer that cannot win on base pay can sometimes win on schedule flexibility, tuition support or a genuine promotion path, and a reward strategy is the argument about where to spend the next dollar for the largest effect on attraction and retention. Coursework at this level is usually asking you to make and defend exactly that trade.
Which means the strongest submissions do something most drafts skip: they connect the reward design back to a workforce problem. Turnover in a specific role, difficulty filling a specific vacancy, low uptake of a benefit nobody wanted. A package designed against a named problem can be evaluated. A package designed in the abstract can only be described.
WGU records the result as Competent or Not Competent, without letter grades or an ordinary grade point average, and performance assessment work can be revised and resubmitted with no penalty attached to the result. Build the package on the best data you can find, state your assumptions in the text, and submit rather than polishing indefinitely.
Turning scored aspects into a rewards plan
If your course is assessed by a performance assessment, the aspects your evaluator scores are the section plan, and each must reach a score of 2 on its own. Rewards deliverables often mix prose, tables and a communication artefact, so decide which aspect each element serves before you build any of them.
Here is the conversion with a slightly different starting point. Suppose your rubric shows ten scored aspects and the prompt sets no word limit at all, which is common on design tasks. Absence of a limit is not permission to write forever; set your own budget from the aspect count. At a working rate of 220 words per aspect you get 2,200 words of body, plus roughly 250 for the scenario and 150 for a close, so plan on about 2,600 words total and treat that as a ceiling.
Then look for aspects that ask for an artefact rather than prose, for example a rewards statement, a cost table or a communication piece. Give each of those about 100 words of budget rather than 220, because the artefact carries the content, and move the saving into the aspects that ask you to justify a design decision. Justification aspects are where evaluators spend their attention, and they are almost always underfed in a first draft.
A structure for a total rewards deliverable
The typical deliverable is a rewards strategy or package recommendation for a described employer. The sequence below moves from problem to design to cost to communication, which is the order a reward decision actually gets made in.
| Section | The question it settles | Evidence to bring | Signal of a weak version |
|---|---|---|---|
| Workforce problem | What attraction or retention failure this package must fix | Turnover, vacancy duration or exit reasons | A package with no problem attached to it |
| Reward strategy | Where this employer chooses to compete and where it will not | A stated market position per reward family | Claiming to lead on everything, which nobody funds |
| Base pay design | Grades, ranges and the internal ordering behind them | Job evaluation method plus market data with dates | Ranges with no midpoint reasoning |
| Variable pay | What behaviour is being paid for and how the payout works | The formula, the trigger and the funding source | A bonus with no measurable trigger |
| Benefits and wellbeing | What is offered, what it costs and who values it | Cost per employee and any uptake evidence | A benefit list with no cost and no audience |
| Recognition | How non monetary contribution gets acknowledged | Frequency, ownership and criteria | Employee of the month with no criteria |
| Career and development | What growth the package promises and how it is delivered | A path with named steps | Development mentioned but never designed |
| Cost and communication | What the package costs and how employees learn its value | Total cost as a share of payroll, plus a communication plan | Cost omitted, which undermines every recommendation |
Evidence craft when the subject is rewards
Rewards writing fails on evidence in a particular way: the claims are about what employees want, and everybody has an opinion about that. Discipline the section with three types of source.
Wage and benefits statistics from federal statistical agencies give you employer cost data by compensation component, which is how you can say what a benefit typically costs as a share of total compensation rather than guessing. Peer reviewed research on motivation, pay satisfaction and turnover gives you the mechanism behind a design choice, and it is the right citation when you claim that recognition affects retention. Professional association survey work gives you practice prevalence, meaning how many employers actually offer a thing, which is different from whether it works.
Keep those three straight in your writing, because conflating them is a common source of returns. Prevalence is not effectiveness. Cost is not value. And a survey of employee preferences tells you what people say they want, which is worth citing as long as you do not present it as evidence of behaviour. Attach each citation to the sentence it supports, and reconcile the reference list against the body after your final edit.
What separates a Competent package from a returned one
Passing packages are affordable, coherent and connected. Affordable means a cost figure appears and the recommendation lives inside it. Coherent means the strategy section and the design sections agree, so an employer that said it would match the market does not then propose ranges well above it. Connected means every element traces back to the workforce problem named at the start.
Returns cluster around four failures. No cost dimension anywhere, so no aspect asking for feasibility can be scored. A design with no stated market position, which leaves the evaluator no standard against which to judge the numbers. Recognition and development mentioned but never designed, which is the modern equivalent of skipping benefits. And the general failure of an abstract package: correct concepts, no organization, no aspect fully applied.
Five mistakes that cost time in D355
Treating total rewards as compensation with extra words. The non cash families carry real aspect weight, and skipping them is skipping scored content.
Designing before naming the problem. Without a retention or attraction issue in front of you, there is nothing to justify a trade off against.
Leaving cost out. Every reward has a price. A package without one reads as a wish list and fails the feasibility aspect.
Confusing prevalence with effectiveness. That most employers offer something is not evidence that it works, and evaluators in this subject notice the substitution.
Reusing C236 requirements. The legacy compensation and benefits course covers overlapping ground under a narrower title, and its assessment is not this one.
How we work here, and the boundary we hold
We support the written work: rubric mapping, budgeting the aspects, drafting a model rewards plan you can study and rewrite in your own voice, and turning a returned evaluation into a specific list of edits. We are a coursework support studio rather than a rewards consultancy, so nothing we produce is advice for a real employer to implement. If D355 carries an objective assessment on your plan, that exam is proctored, and our role is preparation only: study plans, practice questions and an honest readiness call. We are never present during an assessment, never take one for a student, and never ask for or handle WGU portal credentials.
Designing a package for D355?
Send the scenario, the task instructions and the rubric. We come back with the aspect budget, the cost sources worth citing and a straight read on whether the package holds together.
Three questions students ask about D355
What changed between C236 and D355?
Do I need real cost figures for the employer in my scenario?
How specific should the recognition section be?
Where D355 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. 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.