The most advanced tier of HR analytics that goes beyond predicting outcomes to recommending specific actions, using optimization algorithms, simulation models, and decision science to tell HR leaders what to do, not just what might happen.
Key Takeaways
Prescriptive analytics is the final step in the analytics maturity journey. Descriptive tells you what happened. Diagnostic tells you why. Predictive tells you what will happen. Prescriptive tells you what to do about it. In HR, this means the system doesn't just flag that 15 engineers are at high attrition risk. It recommends: adjust compensation for these 8 (with specific dollar amounts), offer a lateral move to these 3, assign a new manager to these 2, and accept the departure of these 2 (because the cost of retention exceeds their replacement cost). It factors in budget constraints, internal equity, market data, and organizational priorities to produce recommendations that are feasible, not just theoretically optimal. This is where HR analytics becomes a decision engine rather than a reporting tool.
The jump from predictive to prescriptive isn't primarily technical. It's organizational. Prescriptive analytics requires leaders to trust the system's recommendations enough to act on them. That trust only builds when descriptive, diagnostic, and predictive analytics have been accurate and useful over time.
| Tier | Type | HR Question | Output | Maturity Required |
|---|---|---|---|---|
| 1 | Descriptive | What happened? | Reports and dashboards | Basic data infrastructure |
| 2 | Diagnostic | Why did it happen? | Root cause analysis | Clean data + analytical skills |
| 3 | Predictive | What will happen? | Forecasts and risk scores | Statistical modeling + data science |
| 4 | Prescriptive | What should we do? | Specific action recommendations with expected ROI | Optimization + decision science + organizational trust |
These are the areas where prescriptive analytics delivers the most measurable impact.
After the predictive model identifies at-risk employees, the prescriptive layer determines the optimal intervention for each person. It considers the employee's predicted reason for leaving (compensation, career growth, manager issues, workload), the cost of each possible intervention, the probability that each intervention will succeed, and the employee's value to the organization. The output might be: "For Employee A, a 12% raise has a 78% probability of retention and costs $14,400. For Employee B, a promotion to senior role has an 85% probability of retention and costs $8,000 in salary adjustment. For Employee C, no intervention is cost-effective; prepare succession plan."
In industries with shift-based workers (healthcare, retail, manufacturing), prescriptive analytics creates optimal schedules that balance labor cost, employee preferences, skill coverage, overtime limits, and service level requirements. The system considers hundreds of constraints simultaneously. A nurse scheduling optimizer might balance patient-to-nurse ratios across units, minimize overtime while meeting minimum staffing requirements, honor seniority-based shift preferences, and ensure adequate skill mix on every shift. Manual schedulers can't optimize across this many variables.
Given a budget of X dollars for merit increases, prescriptive analytics allocates those dollars to maximize retention, pay equity, and performance incentives simultaneously. Instead of spreading a 3% increase evenly, the system might recommend 5% for high-risk top performers, 3% for solid performers at market rate, 1% for lower-impact roles with low attrition risk, and off-cycle adjustments for the worst pay equity gaps. This turns the annual compensation cycle from a political negotiation into a data-driven optimization exercise.
Determines the optimal allocation of recruiting budget across channels (job boards, employee referrals, agencies, social media, campus recruiting) based on historical cost-per-hire, quality-of-hire, and time-to-fill by channel and role type. Instead of spending equally across channels, the system might recommend: "For software engineers, shift 40% of your Indeed budget to employee referrals, which produce hires that perform 15% better and stay 2x longer at 60% lower cost."
Prescriptive analytics uses different techniques than descriptive or predictive analytics. Here's what powers the recommendations.
Linear programming, integer programming, and constraint satisfaction algorithms find the best solution given a set of constraints. For workforce scheduling: maximize coverage while minimizing cost, subject to labor law constraints, skill requirements, and employee availability. These are the same optimization methods used in supply chain management and logistics, applied to workforce problems.
Monte Carlo simulations and agent-based models test thousands of possible scenarios to identify the most likely outcomes and the best strategies for each. What happens if we raise the minimum wage by $2? What if attrition spikes to 25%? What if we open two new locations? Simulation lets you test decisions before you make them, without risking real-world consequences.
For simpler prescriptive use cases, decision trees codify organizational rules into automated recommendation logic. If an employee's flight risk score exceeds 0.75 AND their performance rating is 4+ AND their compa-ratio is below 0.90, recommend a salary adjustment of X%. These are less sophisticated than optimization models but easier to build, explain, and maintain.
The most advanced approach, still emerging in HR. The system learns from the outcomes of past recommendations to improve future ones. If a compensation adjustment was recommended for 50 at-risk employees and 35 stayed, the model adjusts its recommendations for similar future scenarios. Over time, it gets better at recommending interventions that actually work. This requires a feedback loop: tracking which recommendations were implemented and what happened afterward.
Prescriptive analytics isn't a tool you buy. It's a capability you build over time, layering on top of solid descriptive, diagnostic, and predictive foundations.
Data reflecting the current state and business impact of prescriptive analytics in HR.
There are real reasons why only 3% of HR organizations have reached this level. Understanding the barriers helps you plan realistically.
Unlike supply chain optimization (where widgets behave predictably), people are unpredictable. An employee might receive a perfectly targeted retention offer and still leave because their spouse got a job in another city. No model accounts for every variable in human decision-making. Prescriptive analytics in HR will always operate with higher uncertainty than in operations or logistics. Accept that and plan for it.
When a system recommends giving Employee A a 10% raise and Employee B only 2%, it needs to do so without encoding discriminatory patterns. Prescriptive models must be audited for disparate impact across protected characteristics. The recommendations also need to pass the "newspaper test": if your optimization logic was published in a news article, would it seem fair and reasonable?
Many HR leaders and line managers resist data-driven recommendations because they feel it diminishes their judgment and experience. Getting to prescriptive analytics requires a cultural shift where data-informed decisions are valued alongside experience-based decisions. This takes years, not months. Start by showing that simpler analytics (descriptive and predictive) produce good outcomes, then gradually introduce recommendations.