Loading
Because the denominator is wrong. Capacity is calculated from headcount times a standard week, and leave, training, notice periods and part-time patterns are all quietly ignored.
The result is a number that looks acceptable while the people in it are working weekends, and no one can point at which assumption caused it.
The personnel record holds contracted hours, working pattern, leave taken and leave booked. Loop's capacity planning reads it directly rather than assuming a standard week.
So a plan that requires somebody who is on leave in week three is visible before the plan is committed to.
It will not resource projects. It supplies availability and cost; who is right for a piece of work is a judgement about skills.
And it holds only the skills you record. There is no automatic capability inference from what somebody has worked on.
Cost rates on the personnel record feed project margin in Loop, so a delivery that is profitable at blended rates and unprofitable at real ones stops being a surprise.
Offboarding closes access across every product in one action rather than six and a forgotten seventh, which matters when your business is other people's systems.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, including leave, working patterns and contracted hours.
Yes, per person, on the project record.
Yes, across every product, in one action.
Half an hour on your own numbers is usually enough to say whether Nest is the right place to start.