Skills & Workload: Staffing Decisions Backed by a Real Capacity Signal
On this page
The problem: staffing by gut feeling
Every manager has been in this situation: a new project lands, and someone needs to be assigned to it. The manager runs through a mental list — who's good at this, who worked on something similar last time — and then picks someone. What almost never happens is a real check on whether that person actually has room for more work right now.
The result is predictable. The same two or three "reliable" people get stacked with everything, quietly burn out, and the rest of the team's capacity goes underused because nobody has an accurate picture of who's actually free. Staffing decisions get made on memory and reputation, not on data.
Skills & Workload exists to fix both halves of that problem at once: knowing who can do the work, and knowing who has time to do it.
What Skills & Workload actually does
The module has two connected parts.
1. A skills graph
This is a structured record of what each employee can do — their skills, proficiency, and relevant experience, tied directly to their profile. Instead of relying on a manager's memory of "I think Priya knows Python," the skills graph gives you a searchable, organization-wide map of capability. When you need someone who can do a specific thing, you can look it up instead of guessing.
2. A real 7-day workload signal
This is the part that makes the module genuinely different from a static skills directory. The workload signal isn't a survey, a self-reported "how busy are you" rating, or a manager's estimate. It's derived from real time-log data — specifically, activity logged through Timeline over the trailing seven days.
That means when you look at an employee's workload, you're looking at an honest reflection of their actual recent activity, not a number someone typed into a form once and forgot to update. It's a rolling window, so it stays current: someone who was slammed two weeks ago but has since wrapped a project will show up with real, current capacity — not a stale reputation.
How it works
- Skills are recorded on employee profiles. These can be added by the employee, by a manager, or populated over time as courses are completed in Learning — skills and training naturally feed each other.
- Time logs accumulate through normal work. As employees log time against tasks and projects (through Projects and Timeline), that activity becomes the raw material for the workload signal.
- The system calculates a 7-day workload signal. This rolls up recent logged activity into a real, current picture of how loaded each employee actually is.
- Managers cross-reference skills and workload together. Instead of two separate questions — "who can do this" and "who has time" — Skills & Workload lets you ask both at once, against the same employee.
A simple way to think about it
| Without Skills & Workload | With Skills & Workload |
|---|---|
| "I think Sam knows this area" | Skills graph confirms Sam's recorded experience |
| "Sam seems busy, but so is everyone" | 7-day workload signal shows Sam's actual recent logged hours |
| Assignment based on memory and habit | Assignment based on real, current data on both dimensions |
Who uses this
- People managers — deciding who to staff on new work without overloading their most reliable performers.
- Project leads — finding someone with the right skill set who also has real bandwidth this week, not just the "usual" person.
- HR / resourcing teams — spotting organization-wide capacity trends, like a department where workload is consistently concentrated on too few people.
Common mistakes and misconceptions
The most important thing to understand about the workload signal is what it's measuring: logged activity over the last seven days, not a prediction, not an opinion, and not a productivity score. It answers "how loaded has this person actually been recently," not "is this person a hard worker" or "is this person good." Conflating the two is a mistake — and it's a mistake SAVHN deliberately avoids inviting, unlike tools that try to synthesize a single "performance" number out of activity data. See Workforce Intelligence for more on why SAVHN treats that distinction as a hard line.
A second common mistake is treating the skills graph as a one-time setup task. Skills go stale just like any other record — if nobody updates it as people grow into new capabilities, the graph slowly becomes less useful than the manager's memory it was meant to replace. Tie it into regular check-ins or course completions in Learning so it stays alive.
Third, don't use the 7-day window as a substitute for a longer-term view. It's intentionally short and recent — great for "who can take this on this week," not for annual capacity planning. For that, you'd look at trends over time rather than a single rolling window.
Where it fits in SAVHN
Skills & Workload sits at the intersection of HRMS, Projects, and Timeline — pulling real structural and behavioral data from across the platform instead of asking anyone to maintain a separate spreadsheet of who's good at what. It's a natural companion to Manager Copilot, which uses a similar principle — real recent activity data, not assumptions — to filter idle alerts.
The underlying philosophy is the same one that runs through SAVHN more broadly: decisions should be backed by real, current data pulled from work that's already happening, not by separate surveys, guesses, or stale records. You can read more about how the modules work together in the Knowledge Center.