Loading
Because leave is approved in one place and capacity planned in another. Somebody approves a fortnight in July and the plan still shows that person at full availability.
Add freelancers, part-time patterns and a couple of people shared across accounts, and the capacity number becomes a guess everyone treats as fact.
Working patterns, approved leave and cost rates live on the personnel record, and Loop reads them directly. Contractors sit on the same record with a different employment type.
So capacity reflects who is actually available, and project cost reflects what people actually cost.
It will not refuse leave to protect a deadline. It shows the consequence and leaves the decision with the manager.
It also will not manage freelancer contracts — they are personnel records, not a procurement system.
Dates are promised against hours that exist. The collision between a booked holiday and a client deadline shows while it is still a proposal.
Margin includes real people cost rather than a blended average that flatters the profitable accounts and hides the rest.
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, as personnel with a different employment type, visible without being on payroll.
Cost is; individual rates follow permissions.
No. Availability affects dates; reasons stay in Nest.
Half an hour on your own numbers is usually enough to say whether Nest is the right place to start.