Loading
Because the request arrives by email with a date on it and nothing else. Whether two other people are already off that week, whether the person has the balance, whether it clashes with a delivery date — none of it is in the message.
So approval becomes a reflex, and the clash is discovered by whoever is short-staffed on the day.
A leave request arrives with the team calendar beside it: who else is off, the remaining balance, and any delivery commitment in Loop that overlaps. The decision is made with the context rather than after it.
Approvals route by reporting line, and delegation is set on the record, so cover during your own leave is a rota rather than an exception.
It will not decide for you, and it will not stop you approving something that causes a clash. It shows the clash first.
And it does not measure your team's performance from activity. Reviews and goals are things people write, not things inferred.
The team calendar is current because it is the same record people book against. Probation dates, review dates and fixed-term ends surface before they pass rather than after.
What you can see stops at what you need: approving time does not show you what that time costs.
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.
Not unless you are given that field. Approving time does not require it and does not grant it.
Yes — the team calendar and any overlapping delivery commitment.
Delegation is set on the record, so approvals route to your cover automatically.
Half an hour on your own numbers is usually enough to say whether Nest is the right place to start.