How do I set up workforce planning software for skills-based assignment and weekly capacity forecasting?

Here’s a practical way to set up workforce planning software for skills-based assignment and weekly capacity forecasting.

1) Define the planning model

Start by deciding what the software should optimize.

Common goals

• Assign work to the best-fit employee based on skills
• Forecast weekly capacity vs. demand
• Identify shortages, overloads, and skill gaps
• Support prioritization rules, e.g.:
  • certified staff first
  • seniority rules
  • workload balancing
  • location/shift constraints

Key units to plan in

• Work items: cases, tickets, projects, shifts, orders, etc.
• Capacity: hours, points, cases, or weighted effort
• Skills: required competencies, certifications, language, tools, geography
• Time buckets: usually weekly for forecasting, daily for assignment if needed

---

2) Clean and structure your data

Most setups fail because the underlying data is messy.

Employee master data

For each employee, capture:

• Employee ID
• Team / manager / location
• Employment type, FTE, working hours
• Availability by week
• Skills and proficiency levels
• Certifications and expiry dates
• Cost rate, if relevant
• Absence / PTO / leave

Skill taxonomy

Create a controlled list of skills:

• Skill name
• Category
• Level scale, e.g. 1–5
• Required certification if applicable
• Skill validity / recertification rules

Example:

• Excel: 1–5
• Customer Support Tier 2: 1–3
• SAP Billing: 1–5
• Spanish: fluent/intermediate/basic

Work demand data

For each demand item or forecast:

• Work type
• Required skill(s)
• Required level
• Estimated effort
• Due date / week
• Priority
• Location or time zone constraints

---

3) Build the assignment rules

Define how the software should match work to people.

Matching logic

A common rule order is:

1. Must-have constraints
   • certified
   • available
   • correct location/time zone
2. Skill fit
   • required skill matches
   • required level met or exceeded
3. Secondary optimization
   • lowest workload
   • highest proficiency
   • shortest queue time
   • lowest cost

Example assignment rule

Assign a task only if:

• employee has skill = “Claims Processing”
• skill level >= 3
• availability >= 4 hours this week
• no PTO overlap
• capacity remaining after current assignments

Then rank eligible people by:

• highest skill level
• lowest current utilization
• least overtime

---

4) Define capacity forecasting logic

Weekly capacity forecasting compares expected demand to available labor.

Capacity calculation

For each employee, weekly capacity can be:

Scheduled hours

• minus PTO
• minus holidays
• minus training
• minus meetings/admin time
• minus non-productive time

Then apply utilization assumptions:

• 100% available hours is usually unrealistic
• use a productive capacity factor, e.g. 80–85%

Example:

• Contracted hours: 40
• PTO: 8
• Meetings: 4
• Productive factor: 85%

Forecast capacity:

• (40 - 8 - 4) × 85% = 23.8 productive hours

Demand forecasting

Forecast weekly demand by:

• historical workload trends
• seasonality
• pipeline/orders/tickets
• planned projects
• backlog carryover

Then convert demand into the same unit as capacity:

• hours
• case handling time
• weighted points

---

5) Set up the data model in the software

Most workforce planning tools need a few core tables or objects.

Suggested core entities

• Employees
• Skills
• EmployeeSkills
• Availability
• WorkItems
• DemandForecast
• Assignments
• CapacityCalendar
• Absences
• Rules / Constraints

If the software supports custom fields, use them for:

• skill proficiency
• certification expiry
• work item effort
• priority score
• capacity weight

---

6) Configure weekly planning views

Create dashboards for both planning and operations.

Weekly capacity dashboard

Show by:

• team
• manager
• location
• skill group
• employee

Key metrics:

• planned capacity
• forecast demand
• net surplus/shortage
• utilization %
• overtime risk
• skill coverage %

Weekly assignment view

Show:

• open work items
• recommended assignee
• required skills
• current utilization
• SLA / due date
• assignment confidence

---

7) Use scoring or optimization

If the software supports optimization, define objective weights.

Typical scoring formula

You can score each employee for a task using something like:

• +50 if required skill present
• +20 if skill level exceeds requirement
• +15 if availability > threshold
• +10 if same location/time zone
• -20 if utilization > 90%
• -30 if overtime likely

The highest score gets the assignment.

If it supports linear optimization, define:

• minimize skill mismatch
• minimize overtime
• balance load
• maximize SLA adherence

---

8) Set exceptions and overrides

Automated assignment always needs manual control.

Common exception handling

• urgent escalations
• key account assignments
• temporary cross-training
• coverage during absences
• special project staffing

Add an approval workflow for:

• assignments outside skill rules
• assignments that exceed capacity
• reassignment of high-priority work

---

9) Test with real scenarios

Before go-live, test against real historical weeks.

Validation checks

• Did the forecast match actual capacity?
• Were assignments made to truly qualified staff?
• Did any employee exceed reasonable utilization?
• Were low-volume skills still covered?
• Did certifications or expirations affect eligibility correctly?

Use at least:

• one normal week
• one peak week
• one holiday/absence-heavy week
• one change-heavy week

---

10) Establish governance

Keep the model accurate over time.

Ongoing maintenance

• update skill profiles monthly or quarterly
• refresh forecasting assumptions weekly
• review assignment exceptions
• audit utilization and overtime
• retire obsolete skills
• validate forecast bias against actuals

Ownership

Assign responsibility for:

• HR data maintenance
• manager approval of skills
• operations forecasting
• system administration
• reporting and analytics

---

11) Recommended rollout approach

A simple implementation path:

Phase 1: Basic visibility

• load employee data
• load skills
• track availability
• forecast weekly capacity

Phase 2: Skills-based assignment

• add work item skill requirements
• enable matching rules
• pilot with one team or work type

Phase 3: Optimization

• add scoring
• load balancing
• overtime controls
• SLA prioritization

Phase 4: Advanced forecasting

• historical demand trends
• seasonality
• what-if planning
• scenario modeling

---

12) Example setup in practice

Imagine a support team.

Employee data

• 20 agents
• skills: Tier 1, Tier 2, Spanish, Billing, Technical
• weekly availability: 32–40 hours

Work demand

• 500 tickets/week
• each ticket tagged with:
  • required skill
  • expected handling time
  • priority

Rules

• Tier 2 tickets require Tier 2 skill level 3+
• Spanish tickets must go to bilingual agents
• billing issues require Billing skill
• no agent above 85% utilization unless urgent

Outputs

• weekly shortage in Tier 2 by 24 hours
• surplus in Tier 1 by 40 hours
• 3 agents flagged for cross-training
• 12 tickets auto-assigned, 5 held for manual review

---

13) Best practices

• Use a consistent skill scale across the organization
• Separate “can do” skills from “licensed/certified” skills
• Forecast in the same unit used for demand
• Keep rules simple at first
• Review forecast accuracy regularly
• Avoid overloading the model with too many constraints too early

---

If you want, I can also give you:

1. a sample data schema for Excel/SQL/HRIS,
2. a step-by-step setup for a specific tool like Workday, UKG, Anaplan, or Smartsheet, or
3. a template for weekly capacity forecasting and skills assignment rules.