Resource loading: spot the overloaded team before it happens
A schedule says when work happens. It does not say whether anyone can do it. Resource loading adds the people.
These are the eight planning threads the Krong course is built around. The highlighted ones are covered here. What are the planning threads?
The hidden failure
Three tasks start in the same week. On paper that is fine, because they have no link between them. But they all need the same team of two. In week nine that team has six people's worth of work. Nobody planned it. Everybody feels it.
How Sen builds the picture
Sen reads your RACI. Every team marked R on a task works on it for its whole duration, at the effort you set (one person by default). Sen adds this up for each team and each week.
| Colour | Meaning |
|---|---|
| Grey | Work is planned, within capacity |
| Amber | Above 80 per cent of capacity |
| Red | Over capacity |
On Caldera Freight
The Data Engineering Team has two people. In weeks 9 to 12 three tasks overlap and the team needs three. Sen flags it in red and names the tasks. You can move a task that has float, add a person, or accept the delay.
Cost from rates
Enter a day or week rate per team. Sen multiplies it by the effort and shows labour cost beside each task's budget. If the two disagree, you find out before the money is spent.
What it does not do
Sen shows overload. It does not move work for you. Levelling is a decision with trade-offs, so it stays with the planner.
Questions people ask
Where does the demand come from?
From the RACI. A team marked R on a task works on it for its whole duration.
Can I set part-time people?
Yes. Set a capacity per team and the people needed per task.
Does it handle individuals?
Sen plans by team or role. Add a team per person if you need that detail.
See it in a real plan
Open Sen and explore the Caldera Freight example. Every figure on this page comes from it. Copy it, change a task, and watch the plan move together.
Open Sen, free About the course