16, February 2026

Stefan Lauber

4-minute read

Every year it’s the same story: the deadline creeps up, inputs are late, spreadsheets multiply, and the WSP becomes a last-minute rush. For companies with a large heardcount, this problem gets worse because you’re collecting input across teams, sites, and managers, and you still need a plan that fits budget, BBBEE/EE priorities, and critical skills.

The good news is that the WSP creation doesn’t have to be stressful. With a clear workflow and the right tools, you can move from chasing people to automating the whole process.

The 3 reasons WSP becomes a fire drill in large companies

Inputs are hard to gather at scale
The bigger the organisation, the more time you spend following up. People don’t respond because they’re busy and managers delay approvals.

The plan gets built manually (often in spreadsheets)
Manual compilation means version control problems, errors, and rework every time leadership gives feedback.

Budget and transformation priorities arrive late
WSP planning often starts before priorities are finalised. Then you have to rebuild the plan to match budget limits and BBBEE/EE objectives.

The “fast-track” workflow (simple 4 steps)

A better approach is:

1) Collect — gather input from employees and managers
2) Build — generate the plan from the data
3) Optimise — prioritise for budget + BBBEE/EE + critical skills
4) Report — dashboards and exports for review and submission

What changes when you do it this way

A better approach is:

• You stop chasing inputs with endless emails
• You reduce admin and rework
• You can produce versions quickly until stakeholders are aligned
• You get to a submission-ready output earlier