Workforce Planning, Job Analysis and Hiring Requirements

Introduction

Personnel sourcing and recruitment become strategically valuable only when an organization can explain why a role is needed, what contribution it must make, which capabilities are required, and how evidence will be used to identify suitable candidates. Workforce planning, job analysis, competency design, job description writing, hiring requisitions, and recruitment planning are therefore not separate administrative activities. They form a connected decision system.

Workforce planning translates organizational strategy into estimates of future labor demand and supply. Job analysis converts those estimates into a defensible understanding of work. Competency frameworks and skills profiles describe the capabilities associated with effective performance. Job descriptions communicate role purpose and accountability, while hiring requisitions authorize and specify a staffing action. Finally, the recruitment plan determines how, where, and when the organization will seek candidates.

The central managerial challenge is alignment. A hiring decision should be aligned with business strategy, operating design, labor-market conditions, budget, employment law, diversity objectives, and the organization’s capacity to integrate and develop the person hired. Poor alignment produces unnecessary headcount, inflated requirements, biased selection, weak candidate experiences, and avoidable turnover.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the relationship between strategy, workforce planning, job analysis, and recruitment.
2. Distinguish workforce demand, workforce supply, and workforce gaps.
3. Apply qualitative and quantitative approaches to workforce forecasting.
4. Conduct a systematic job analysis using multiple sources of evidence.
5. Develop competency frameworks, skills profiles, job descriptions, and hiring requisitions.
6. Design evidence-based recruitment plans that reflect labor-market realities.
7. Evaluate ethical, legal, technological, and governance issues in defining hiring requirements.
8. Critically assess the limitations of forecasts, competency models, and recruitment metrics.

1. From Organizational Strategy to Workforce Requirements

Strategic workforce planning

Strategic workforce planning is the systematic process of ensuring that an organization has the quantity, quality, location, timing, and cost of labor needed to achieve its objectives. It is broader than headcount budgeting. Headcount describes how many positions exist; workforce planning considers the work that must be performed, the capabilities required, alternative ways of obtaining those capabilities, and the risks associated with shortages or surpluses.

A useful planning sequence is:

Strategy → operating model → work and capability requirements → workforce demand → workforce supply → workforce gap → action plan.

Strategic workforce planning normally addresses six dimensions:

• Quantity: How many workers or work hours are needed?
• Quality: What knowledge, skills, abilities, and other characteristics are required?
• Timing: When must capability be available?
• Location: Where must work be performed?
• Employment arrangement: Should capability be obtained through employees, contractors, partners, automation, or other arrangements?
• Cost and risk: What financial, operational, legal, and reputational constraints apply?

The process should begin with business assumptions rather than with requests from individual managers. For example, a plan to enter a new market may imply additional sales, compliance, customer support, and localization capabilities. A digital-transformation strategy may reduce some transactional work while increasing demand for data governance, cybersecurity, product management, and change leadership.

Workforce demand and supply

Workforce demand is the amount and type of labor required under a specified business scenario. Workforce supply is the labor and capability likely to be available from internal and external sources. Internal supply includes current employees, contingent workers, successors, employees who can be redeployed, and employees who can be developed. External supply includes potential applicants, professional communities, educational institutions, competitors’ employees, and specialized labor markets.

The basic workforce-gap relationship is:

where G_t is the workforce gap in period t, D_t is forecast workforce demand, and S_t is forecast workforce supply. The equation assumes that demand and supply are measured in comparable units, such as full-time-equivalent positions, productive hours, or defined capability units. A positive value indicates a shortage; a negative value indicates a surplus. The equation is descriptive rather than a complete staffing decision because it does not by itself account for productivity, quality, cost, or timing.

If demand is 120 full-time-equivalent positions and expected supply is 105, the numerical gap is 15 positions. Management must still decide whether to recruit all 15, redesign work, improve productivity, develop internal talent, automate some activities, or use contingent labor.

Forecasting methods

No single forecasting method is universally superior. Graduate-level workforce planning combines quantitative analysis with managerial judgment and scenario reasoning.

Trend analysis projects historical employment or workload patterns into the future. It is useful when the environment is relatively stable, but it can reproduce outdated assumptions.

Ratio analysis links workforce requirements to a business driver, such as employees per production unit, recruiters per annual hire volume, or service agents per customer population. If the historical ratio is stable, it can provide a transparent planning baseline. Its weakness is that ratios may conceal changes in productivity or technology.

Workload analysis begins with expected work volume and the time required per unit of work. If annual workload is 48,000 cases, each case requires 30 minutes, and one full-time employee provides 1,500 productive hours annually, the baseline requirement is:

Thus, FTE = (48,000 × 0.5) ÷ 1,500 = 16 full-time-equivalent employees. The time unit must be consistent: 30 minutes is 0.5 hours, and productive hours must exclude leave, training, meetings, and other nonproductive time. The result is a capacity estimate, not necessarily a final hiring target; service-level requirements, peak demand, absence, quality, and scheduling constraints may require adjustment.

Scenario planning develops multiple plausible futures, such as expansion, stable demand, recession, regulatory change, or technological substitution. It is particularly valuable when uncertainty is high. Scenarios should identify assumptions, early-warning indicators, workforce consequences, and contingent actions rather than merely describe optimistic and pessimistic stories.

Delphi and expert judgment use structured rounds of informed estimates. They can incorporate knowledge unavailable in historical data, but results may be influenced by dominant participants, political incentives, or shared bias.

Skills-based planning forecasts capabilities rather than only occupations or positions. It is useful when roles evolve quickly and when employees may perform work across traditional job boundaries.

A robust forecast records assumptions, confidence levels, data sources, time horizons, and sensitivity to changes. Forecasts should be reviewed as conditions change rather than treated as permanent facts.

2. Job Analysis as the Foundation of Hiring Decisions

Meaning and purpose

Job analysis is the systematic collection and evaluation of information about work, including tasks, responsibilities, outputs, context, relationships, tools, working conditions, and the capabilities associated with effective performance. It concerns the job, not the personality of the current jobholder.

Job analysis serves several purposes:

• defining recruitment and selection criteria;
• establishing training and development requirements;
• supporting performance management and job evaluation;
• identifying health, safety, and accessibility considerations;
• clarifying accountability and reporting relationships;
• supporting fair and legally defensible employment decisions;
• identifying opportunities for work redesign, automation, or job enlargement.

A job analysis should distinguish essential functions from activities that are incidental, infrequent, or capable of being reassigned. It should also distinguish minimum entry requirements from capabilities that can be learned after appointment.

Sources and methods of data collection

A high-quality analysis normally uses more than one source. Relevant sources include jobholders, supervisors, subject-matter experts, customers, process documentation, performance data, occupational databases, and observations of work.

The choice of method should reflect the work. Observation may be valuable for warehouse or laboratory roles, while interviews and critical incidents may be more appropriate for strategic, advisory, or managerial work. Analysts should compare reported work with actual workflow because formal job descriptions often lag behind operational reality.

Task, duty, responsibility, and outcome

These terms should not be used interchangeably. A task is a distinct activity, such as validating an invoice. A duty is a cluster of related tasks, such as accounts-payable administration. A responsibility is an area of accountability, such as maintaining payment accuracy. An outcome is the result expected from the work, such as timely and accurate supplier payment.

Outcome-oriented analysis helps prevent job descriptions from becoming lists of activities without explaining value. For example, “prepare monthly reports” is less informative than “produce accurate monthly workforce reports that enable managers to monitor turnover, vacancy, and labor cost.”

Work context and job design

Job analysis should document reporting relationships, decision authority, interdependence, technology, work location, scheduling, physical or psychological demands, customer exposure, travel, and regulatory obligations. It should also assess autonomy and standardization. Two jobs with similar tasks may require different competencies if one operates under close supervision and the other makes high-consequence decisions independently.

Job analysis should not assume that the current design is optimal. Analysts should ask whether activities can be simplified, combined, automated, distributed, or redesigned. Recruiting for a poorly designed job can institutionalize inefficiency.

3. Competency Frameworks and Skills Profiles

Competencies and skills

A skill is a learned capacity to perform a particular activity, such as querying a database or conducting a structured interview. A competency is a broader and observable combination of knowledge, skill, ability, behavior, judgment, and motivation that contributes to effective performance in a context. Competencies may be technical, behavioral, leadership-related, or strategic.

A competency framework organizes competencies across an organization or occupational family. A skills profile specifies the skills, proficiency levels, credentials, and experiences associated with a particular role. The two concepts overlap but are not identical: a skills profile tends to be more granular and task-oriented, while a competency framework often expresses broader patterns of effective behavior.

A useful framework distinguishes:

1. Core competencies: Expected across the organization, such as ethical conduct or collaboration.
2. Functional competencies: Associated with a profession or discipline, such as employment-law knowledge in an HR role.
3. Role-specific competencies: Required for a particular job, such as workforce forecasting.
4. Leadership competencies: Relevant to roles involving direction, influence, and stewardship.

Proficiency levels

Proficiency scales should be behaviorally anchored. Labels such as “basic,” “intermediate,” and “advanced” are ambiguous unless the organization defines what performance looks like.

Proficiency should be treated as role-relative. An advanced analyst may not be an expert architect. Frameworks should avoid requiring the highest level for every competency because excessive requirements narrow applicant pools and create unrealistic expectations.

Validity and adverse impact

Competencies should be included because there is a defensible relationship between the competency and job performance, not because it sounds desirable. Requirements should be tested for necessity, observability, trainability, and potential exclusionary effects. A degree requirement, for example, may be unnecessary if the actual work can be performed through demonstrated technical competence and relevant experience.

Competency models can also become vague cultural filters. Terms such as “executive presence,” “culture fit,” or “high potential” may conceal subjective preferences unless translated into observable, job-relevant behaviors. A more defensible alternative is to specify communication behaviors, stakeholder-management outcomes, or decision practices.

4. Writing Job Descriptions and Hiring Requirements

The job description

A job description is a formal communication and governance document. It should explain the role sufficiently for applicants, managers, HR professionals, and decision-makers to understand its purpose and boundaries. A strong job description commonly includes:

• job title and organizational unit;
• job purpose or contribution statement;
• key outcomes and responsibilities;
• reporting relationships and major interfaces;
• decision authority;
• essential functions;
• required and preferred qualifications;
• technical and behavioral competencies;
• work location, schedule, travel, and employment conditions;
• physical, safety, accessibility, or licensing requirements where relevant;
• compensation range or applicable pay information where required;
• equal-opportunity and accommodation information;
• review date and document owner.

Responsibilities should be written as meaningful outputs and accountabilities, not as inflated lists. A job description should communicate scope without pretending that every future task can be predicted.

Required versus preferred criteria

The distinction between required and preferred criteria is essential. A required criterion is necessary for competent performance at entry or is legally, operationally, or safety-critical. A preferred criterion improves readiness or reduces development time but is not essential. Inflating preferred criteria into requirements can reduce diversity, increase recruitment costs, and exclude capable candidates.

A practical test is: if a candidate lacks this criterion but possesses the other essential capabilities, could the gap be closed through reasonable training, supervision, or onboarding within an acceptable period? If yes, the criterion may be preferred rather than required.

Hiring requisition

A hiring requisition is the formal request and authorization to fill a role. It connects workforce planning to recruitment execution. In addition to the job-description content, it should include:

• reason for hiring: new position, replacement, growth, temporary demand, or risk mitigation;
• approved headcount and budget;
• employment type and duration;
• target start date and urgency;
• recruitment owner and hiring manager;
• proposed sourcing channels;
• selection stages and decision rights;
• labor-market evidence;
• diversity, accessibility, and compliance considerations;
• consequences of delay;
• approval history.

The requisition should answer the managerial question, “Why should the organization authorize this staffing action now?” A replacement request may be justified by continuity risk, while a new position may require evidence of workload, revenue opportunity, regulatory need, or strategic capability.

5. Evidence-Based Recruitment Planning

A recruitment plan explains how the organization will reach, assess, and convert an appropriate candidate population. It should be based on the labor market rather than on habit.

Market diagnosis

Recruiters should assess talent availability, geographic concentration, compensation expectations, competing employers, mobility patterns, required credentials, remote-work possibilities, and time-to-fill risk. Internal data may be supplemented by professional associations, public labor statistics, educational providers, industry research, and structured market conversations.

Market evidence should influence requirements. If a requirement is rare and not essential, the organization may redesign the job, train for the skill, hire for adjacent capability, broaden location, adjust compensation, or use a temporary solution. Simply declaring the market “difficult” does not justify lowering standards without analysis.

Sourcing strategy

Sourcing channels should correspond to the target population. Possible channels include internal mobility, employee referrals, professional networks, specialist agencies, universities, apprenticeships, public employment services, social platforms, talent communities, and direct search. Channel selection should consider reach, cost, speed, candidate quality, accessibility, and diversity of the resulting pool.

A recruitment plan should specify the candidate value proposition. This includes meaningful work, development opportunities, rewards, flexibility, leadership quality, social purpose, and employment conditions. The proposition must be credible; inaccurate promises damage trust and retention.

Selection evidence and recruitment metrics

Recruitment metrics should support decisions rather than reward activity alone. Useful measures include qualified-applicant rate, source-to-interview conversion, interview-to-offer conversion, offer acceptance, time to fill, time to productivity, cost per hire, quality of hire, early turnover, candidate experience, and representation across stages.

Metrics require careful definitions. “Time to fill” may mean days from requisition approval to acceptance, whereas “time to hire” may mean days from application to acceptance. Without standard definitions, comparisons are misleading.

For a recruitment channel, a simple conversion rate can be expressed as:

If 80 applicants produce 16 interviews, the application-to-interview conversion rate is 20%. This measure describes funnel movement; it does not establish quality or fairness. A channel with a low conversion rate may still produce excellent hires, while a high conversion rate may reflect weak screening standards.

Recruitment analytics should be disaggregated where lawful and ethically appropriate by stage, source, location, job family, and relevant demographic categories. Organizations should investigate large differences rather than infer causation from correlation. Small samples, changing labor markets, and inconsistent process administration can distort conclusions.

6. Governance, Ethics, and Regulation

Hiring requirements affect access to employment and therefore require governance. Organizations should comply with applicable laws concerning discrimination, equal employment opportunity, disability accommodation, privacy, pay transparency, working time, licensing, and record retention. Legal requirements vary by jurisdiction, so HR professionals should obtain qualified local advice rather than rely on generic templates.

Important principles include:

• Job relevance: Criteria should relate materially to work performance or legitimate operational requirements.
• Consistency: Candidates should be evaluated against defined criteria using comparable procedures.
• Transparency: Applicants should receive accurate information about role expectations and selection stages.
• Accessibility: Requirements and processes should not create avoidable barriers for people with disabilities.
• Privacy and data minimization: Collect only information necessary for a legitimate recruitment purpose and protect it appropriately.
• Accommodation: Distinguish essential outcomes from conventional ways of performing them.
• Documentation: Preserve evidence supporting requirements, approvals, and selection decisions.
• Human accountability: Managers remain responsible for employment decisions even when technology is used.

A requirement can be unintentionally discriminatory even when stated neutrally. For example, a rigid schedule may exclude qualified candidates with caregiving or disability-related constraints when the work could be performed through alternative scheduling. Analysts should examine whether the requirement is genuinely essential and whether reasonable accommodation is possible.

7. Technology and Artificial Intelligence in Requirement Design

Digital labor-market platforms, skills databases, applicant tracking systems, and generative AI can accelerate job-description drafting, skills extraction, market mapping, and requisition administration. Their usefulness depends on the quality of underlying data and the quality of human oversight.

AI-generated job descriptions may reproduce gendered language, outdated occupational assumptions, unnecessary credential requirements, or biased historical patterns. Automated skills inference may confuse association with competence. Ranking systems may disadvantage candidates whose career histories differ from the data used to train the model.

Governance should include documented purpose, data provenance, validation, human review, accessibility testing, security controls, monitoring for disparate outcomes, candidate communication where required, and a process for contesting errors. AI should assist analysis, not silently determine who is considered qualified. A human reviewer should verify that every requirement is job-related, understandable, and necessary.

8. Integrated Applied Case

Illustrative case: Northstar Health Services

Background. Northstar Health Services operates outpatient clinics and plans to expand remote patient monitoring over two years. The strategy requires nurses, patient-support specialists, data analysts, and implementation managers. The organization initially submits a requisition for ten “digital health specialists” with a bachelor’s degree, five years of healthcare experience, coding knowledge, clinical communication skills, and willingness to work evenings.

Problem. The requisition combines several types of work and imposes requirements that may be unnecessary. Managers disagree about whether the roles will interpret clinical alerts, support patients, configure software, or analyze data. The broad specification produces few applicants, high salary expectations, and inconsistent screening.

Analysis. HR conducts interviews with jobholders, supervisors, clinicians, patients, and the technology vendor. Process mapping shows four work streams:

1. triaging alerts under clinical protocols;
2. coaching patients in device use;
3. monitoring data quality and dashboards;
4. coordinating implementation and workflow change.

Critical incidents reveal that safe escalation judgment and patient communication are essential for the first work stream. Coding is not essential for patient coaching. The work also has predictable daytime peaks, so the original universal evening requirement is unnecessary.

Workload analysis estimates 18,000 annual patient-support contacts. Each contact requires an average of 12 minutes, and one employee provides 1,350 productive contact hours annually. The baseline contact capacity is:

Northstar then adds capacity for quality review, absence coverage, and peak demand through a separate scheduling analysis rather than arbitrarily rounding the result. The calculation is treated as a baseline, not as a final headcount decision.

Approach and solution. Northstar creates four job families with separate descriptions and skills profiles. It classifies competencies as required or trainable, removes the blanket coding requirement, defines clinical escalation as essential only for the triage role, and permits alternative schedules where service coverage is maintained. The recruitment plan uses internal mobility, nursing networks, community partnerships, and a paid training pathway for patient-support roles. Structured selection methods are developed from critical incidents and work samples.

Outcome. The revised requisitions produce a larger and more diverse qualified pool. Hiring managers report clearer decisions because applicants are assessed against role-specific evidence. The organization also discovers that some dashboard work can be automated and that internal patient-service employees can transition into support roles after training.

Learning points. First, workforce planning should examine work design before requesting headcount. Second, job analysis prevents unrelated activities from being combined into unrealistic roles. Third, separating essential from trainable requirements can expand access without lowering standards. Fourth, quantitative workload estimates are useful only when assumptions and capacity limits are explicit. Finally, recruitment effectiveness depends on the quality of the requirement definition that precedes sourcing.

9. Challenges and Limitations

Workforce planning is vulnerable to uncertain strategy, incomplete data, changing technology, managerial optimism, and political pressure. Forecasts may create false precision, particularly when organizations express uncertain estimates as exact headcounts. Scenario ranges and confidence statements are often more honest than a single number.

Job analysis also has limitations. Incumbents may describe preferred practices rather than actual work, supervisors may exaggerate requirements to increase status, and new roles may lack historical evidence. Analysts should triangulate sources and revisit analyses after major changes.

Competency frameworks can become bureaucratic catalogs that are too broad to guide decisions. They may also privilege dominant cultural norms or reward polished self-presentation rather than substantive performance. Frameworks should therefore be concise, observable, validated, and periodically reviewed.

Recruitment metrics can encourage dysfunctional behavior. Pressure to reduce time to fill may lead to premature hiring; pressure to reduce cost per hire may reduce candidate quality; and source metrics may reward volume rather than valid selection. Metrics must be interpreted as a balanced system connected to business outcomes, fairness, candidate experience, and retention.

Best-Practice Checklist

Before approving a requisition, HR and the hiring manager should be able to answer:

1. What strategic or operational problem does the role address?
2. What evidence supports the workload and timing assumptions?
3. Have alternatives such as redesign, development, automation, or redeployment been considered?
4. What are the essential outcomes and functions?
5. Which requirements are truly necessary at entry?
6. Which capabilities can be developed after hiring?
7. How will performance be evidenced during selection?
8. Is the job description accurate, accessible, and legally reviewed where necessary?
9. What does the labor market indicate about sourcing, compensation, and timing?
10. How will recruitment outcomes, fairness, and quality be evaluated?

Chapter Summary

Workforce planning translates organizational strategy into future requirements for labor and capability. Demand and supply should be considered in comparable units, while workforce gaps should be interpreted alongside productivity, cost, timing, risk, and alternative solutions. Forecasting methods include trend, ratio, workload, scenario, expert, and skills-based approaches; each has assumptions and limitations.

Job analysis provides the evidentiary foundation for recruitment. It examines tasks, duties, responsibilities, outcomes, context, decision authority, and essential functions using multiple data sources. Competency frameworks and skills profiles convert this evidence into observable capabilities and proficiency expectations. Effective job descriptions distinguish required from preferred criteria and communicate role purpose, outcomes, conditions, and accountability. Hiring requisitions connect these requirements to authorization, budget, urgency, and business rationale.

Evidence-based recruitment planning uses labor-market analysis, appropriate sourcing channels, credible candidate value propositions, structured selection evidence, and carefully defined metrics. Ethical and legal governance requires job relevance, consistency, accessibility, privacy, accommodation, documentation, and human accountability. Technology and AI can improve efficiency but must be validated and monitored for bias. The overall principle is integration: sound recruitment begins with sound workforce and work analysis.

Key Terms

Competency: An observable combination of knowledge, skills, abilities, behaviors, judgment, and motivation associated with effective performance.

Competency framework: An organized structure of competencies across an organization, function, or occupational family.

Essential function: A fundamental duty or outcome that a role must perform, with or without reasonable accommodation.

External labor supply: Potential workers available outside the organization, including applicants, professionals, graduates, and contingent workers.

Full-time equivalent (FTE): A standardized measure of labor capacity based on the organization’s definition of full-time work.

Hiring requisition: A formal request and authorization to fill a position.

Job analysis: Systematic study of work tasks, responsibilities, outcomes, context, and capability requirements.

Job description: A formal document describing a role’s purpose, responsibilities, requirements, and conditions.

Job redesign: Deliberate alteration of tasks, relationships, technology, or work arrangements.

Jobholder: A person currently performing the work being analyzed.

Labor-market analysis: Examination of external talent availability, competition, compensation, location, and related conditions.

Proficiency level: A defined degree of capability, preferably expressed through observable behavior.

Required criterion: A qualification or capability necessary for competent, safe, lawful, or effective entry performance.

Scenario planning: Analysis of multiple plausible futures and their implications for workforce decisions.

Skills profile: A role-specific description of skills, proficiency, credentials, and experience.

Strategic workforce planning: Alignment of future labor capacity and capability with organizational strategy.

Supply forecast: Estimate of labor and capability likely to be available in a future period.

Task: A distinct activity performed as part of a job.

Workforce demand: The quantity and type of labor or capability required under defined assumptions.

Workforce gap: The difference between forecast workforce demand and forecast workforce supply.

Review Questions

Short Answer Questions

1. What is the difference between workforce demand and workforce supply?
2. Why should job analysis distinguish essential functions from incidental activities?
3. How does a competency differ from a skill?
4. What information should a hiring requisition contain beyond a job title?
5. Why must recruitment metrics be defined consistently?

Long Answer Questions

1. Explain how organizational strategy is translated into a workforce plan and then into a recruitment requirement.
2. Compare workload analysis, ratio analysis, and scenario planning, including the assumptions and limitations of each.
3. Design a job-analysis process for a newly created professional role using at least three data-collection methods.
4. Discuss how required and preferred criteria influence validity, diversity, and recruitment outcomes.
5. Evaluate the ethical and governance risks of using AI to draft job descriptions or screen candidates.

Analytical / Application Questions

1. An organization forecasts demand for 75 FTEs and internal supply of 62 FTEs. Analyze at least four possible responses besides immediately hiring 13 employees, and identify the additional evidence required before choosing among them.
2. A manager requires a master’s degree, ten years of experience, and “executive presence” for a role whose documented outcomes involve dashboard production and stakeholder reporting. Critique the requirement and propose a more defensible skills profile.
3. Using the Northstar case, explain how job analysis changed the recruitment strategy and assess which assumptions in the workload calculation should be tested before finalizing staffing levels.

Multiple Choice Questions with Answers

Question 1

Which sequence best represents the relationship among the major activities in this chapter?

A. Recruitment channels → strategy → job analysis → workforce forecast

B. Strategy → workforce requirements → job analysis → requisition and recruitment plan

C. Job description → organizational strategy → labor supply → competency framework

D. Hiring requisition → workforce surplus → business strategy → job analysis

Correct Answer: B. Strategy → workforce requirements → job analysis → requisition and recruitment plan

Question 2

If forecast workforce demand is 120 FTEs and forecast supply is 105 FTEs, what is the workforce gap?

A. 15 FTE shortage

B. 15 FTE surplus

C. 225 FTE total capacity

D. 87.5 FTE shortage

Correct Answer: A. 15 FTE shortage

Question 3

Which method begins with expected work volume and the time required per unit of work?

A. Trend analysis

B. Delphi analysis

C. Workload analysis

D. Succession analysis

Correct Answer: C. Workload analysis

Question 4

Which statement best distinguishes a competency from a skill?

A. A competency is always a formal credential, while a skill is informal

B. A skill is broader than a competency in every situation

C. A competency combines capabilities and behaviors in a performance context

D. A competency applies only to managers

Correct Answer: C. A competency combines capabilities and behaviors in a performance context

Question 5

What is the primary purpose of separating required from preferred criteria?

A. To eliminate the need for job analysis

B. To identify what is essential at entry and avoid unnecessary exclusion

C. To ensure every applicant has identical experience

D. To increase the number of credentials in the job description

Correct Answer: B. To identify what is essential at entry and avoid unnecessary exclusion

Question 6

A recruitment channel produces 16 interviews from 80 applicants. What is the application-to-interview conversion rate?

A. 5%

B. 16%

C. 20%

D. 80%

Correct Answer: C. 20%

Question 7

Which is the strongest reason to use multiple sources in job analysis?

A. It guarantees that all employees will agree

B. It reduces the need to document assumptions

C. It helps triangulate reported work, actual work, and contextual evidence

D. It replaces the need for managerial judgment

Correct Answer: C. It helps triangulate reported work, actual work, and contextual evidence

Question 8

Which criterion is most defensible in a job description?

A. A vague requirement for cultural fit

B. A credential included only because competitors use it

C. An observable capability materially related to essential job outcomes

D. A preference for applicants from a particular institution

Correct Answer: C. An observable capability materially related to essential job outcomes

Question 9

What is a major governance risk when AI is used to screen applicants?

A. It always eliminates human judgment

B. It may reproduce bias in historical data or proxy variables

C. It makes job analysis unnecessary in all cases

D. It prevents organizations from collecting any recruitment data

Correct Answer: B. It may reproduce bias in historical data or proxy variables

Question 10

In the Northstar case, what did job analysis reveal?

A. All digital health work required identical qualifications

B. Coding was essential for every role

C. The proposed role combined several distinct work streams

D. Workload estimates were irrelevant to staffing decisions

Correct Answer: C. The proposed role combined several distinct work streams