C234 is printed in the WGU catalog as HRM 3200 Workforce Planning: Recruitment and Selection, 3 competency units. It teaches how an organization anticipates the staffing it will need and then designs the recruitment and selection process that fills the gap. It is the legacy entry for this material. The current course is D354 Talent Acquisition, so check your Degree Plan and build from whichever code it lists. This page is a planning manual for the deliverable, not a summary of the reading.
The two halves of the course, and which one gets underwritten
The course title names two activities that students treat as one. Workforce planning is forecasting: how many people, with which capabilities, by when, given turnover, growth and the work the organization has committed to. Recruitment and selection is execution: where those people come from, how they are assessed and how the choice is defended.
The forecasting half is where submissions come back thin. Recruitment is intuitive because everyone has applied for a job, so students write confidently about sourcing channels and interview questions and then produce two vague sentences about demand analysis. Rubrics in this subject usually put real weight on the planning half, because that is the part a working manager cannot do by instinct.
Fix it by starting every draft with the numbers. Current headcount in the role, expected departures, expected growth, and time to fill. Even estimated, those four figures turn the plan section from opinion into arithmetic, and the recruitment section that follows suddenly has a target it is trying to hit.
Everything in this course is recorded as Competent or Not Competent. WGU does not issue letter grades and does not calculate an ordinary grade point average from them, and performance assessment work can be revised and resubmitted without a penalty attached to the result. Use that. Submit a complete attempt with your best forecast rather than sitting on a draft while you look for a perfect data source.
Turning scored aspects into a staffing plan document
If your course is assessed by a performance assessment, the aspects the evaluator scores are the section list. Each is judged separately and needs a score of 2, so an aspect buried inside another aspect's paragraph is an aspect that may be read as unaddressed.
Here is the arithmetic on a mid sized rubric. Suppose there are seven scored aspects and you plan a document of about 2,100 words. Staffing plans need a scenario recap the later sections lean on, so hold back 200 words for that, and 100 for the closing summary. That leaves 1,800 words across seven aspects, or roughly 257 each. Round to 250 and keep 50 in reserve for the aspect that turns out to need a table.
Then adjust for the fact that not all aspects are equal work. An aspect asking you to identify a sourcing channel is a 150 word aspect. An aspect asking you to design a selection process and justify each stage is a 400 word aspect. Move the difference between them explicitly and write the number beside each heading in your outline. Deciding proportions before drafting is what stops the recruitment section from eating the planning section, which is the most common structural failure in this course.
One more habit that saves a return. Where an aspect asks for a specific count, three sourcing strategies, two selection methods, put the count in your heading. It looks blunt on the page and it makes an evaluator's judgement immediate.
A structure for a workforce planning deliverable
The typical deliverable here is a staffing plan or a recruitment and selection proposal addressed to a hiring manager or an executive. Below is a layout built for that document.
| Component | What goes in it | Form | What an evaluator looks for |
|---|---|---|---|
| Demand picture | Roles needed, count, timing, and the business reason behind them | Short prose plus a small table | A number, not an adjective |
| Supply picture | Internal candidates, expected attrition, external availability of the skill | Prose with sourced labour market data | External data actually cited rather than assumed |
| Gap statement | Demand minus supply, expressed as positions and timeline | One paragraph | Arithmetic that follows from the two sections above it |
| Job analysis | The duties and the qualifications that genuinely predict performance | Structured list | Requirements tied to the work, not to preference |
| Sourcing strategy | Named channels, why each fits this role, and cost or reach implications | One paragraph per channel | A reason per channel, not a list of job boards |
| Selection process | Each stage in order, what it measures, who runs it | Sequenced list or table | Each stage measuring something the job analysis named |
| Fairness and legal check | Consistency, documentation, and the obligations selection triggers | Short section | Present at all, which is often the difference |
| Metrics | Time to fill, quality of hire, yield by stage | Table | Measures that match the plan's own goals |
Evidence that supports staffing claims
Recruitment writing drifts into folklore faster than almost any other HR topic, so the sourcing layer does a lot of work here. Three source families carry most of it.
Public labour market data gives you occupation level wages, employment levels and projected change, which is how a claim about candidate scarcity stops being a feeling. Occupational information databases give you standardised task and skill statements for a role, which is the fastest legitimate way to build a job analysis that is not just your own job description rewritten. Peer reviewed selection research gives you the comparative validity of interview formats, work samples and structured assessments, and citing it is how a selection design becomes defensible instead of merely sensible.
Two more rules. Attach the citation to the sentence that carries the claim, because aspects are scored claim by claim. And treat any vendor whitepaper as marketing until proven otherwise; a recruitment platform's own report on how well its product works is not independent evidence, and evaluators notice.
What earns Competent in this course
A passing staffing plan is arithmetically honest and operationally specific. The gap number follows from the demand and supply sections. Every selection stage measures something the job analysis identified. The metrics at the end would tell you whether the plan worked. Nothing in it depends on the reader's goodwill.
Work gets sent back for a small number of repeat reasons. The plan asserts a shortage it never evidenced. The selection process is a list of steps with no stated purpose per step, so the aspect asking for justification has nothing to score. The fairness section is missing, or is present but generic enough to belong to any plan. Or the whole document describes recruitment in general rather than recruitment for the specific role the prompt named, which quietly fails the applied half of several aspects at once.
Six mistakes that cost time in C234
Writing the recruitment half first. The plan should determine the recruiting, and drafting in that order almost always produces a forecast reverse engineered to match the channels you already liked.
Inflating qualifications. Requiring a degree or a decade of experience for a role that does not need it weakens both the sourcing and the fairness sections, and an evaluator can see the mismatch against your own job analysis.
Naming channels without reasons. A list of five places to post is not a sourcing strategy. Each channel needs a sentence saying why this role and this labour market.
Designing interviews you never justify. Structured formats and work samples have research behind them. Say so, and the justification aspect writes itself.
Skipping the documentation question. How decisions get recorded matters as much as how they get made, and rubrics frequently ask about it in the fairness aspect.
Building from the wrong code. If your plan shows D354 Talent Acquisition, use its requirements. The subjects overlap heavily and the assessments are separate.
Where our help starts and where it stops
We work on the written deliverable: reading the rubric with you, building the aspect plan, drafting a model staffing plan you can study and rewrite in your own voice, and turning a returned evaluation into a short list of edits. If C234 carries an objective assessment on your plan, that exam is proctored and our role is preparation only, meaning study plans, practice questions and an honest read on readiness. We are never present during an assessment, never take one for a student, and never ask for or handle WGU portal credentials.
Building a staffing plan for C234?
Send the scenario, the task instructions and the rubric. We come back with the aspect plan, the data sources worth citing and a straight read on where the forecast is thin.
Three questions students ask about C234
Is HRM 3200 a different course from C234?
What do I do if the prompt gives me no real numbers to forecast with?
Should I use my own employer as the organization?
Where C234 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.