Loading
Because they are planned as though the people involved were available. They are not: teaching, marking and term dates take most of the year, and the project assumes the remainder without ever writing it down.
So a six-week piece takes two terms, and nobody can point to the week it went wrong.
Capacity comes from Nest, so leave, working patterns and contracted hours are already in the picture rather than assumed away. A phase can be planned against what is genuinely free.
Approvals route to the reporting line and are recorded with a date, so a committee decision is a record rather than a line in minutes somebody has to find.
It is not a timetabling system and it is not a student information system. It manages projects and the staff time that goes into them.
And it will not resolve the tension between teaching and project work. It makes the trade-off explicit before the project is committed to.
Work that crosses departments sits on one record with one owner, rather than in two systems with two versions of the deadline. Recurring annual work — validation, audits, open days — is a template rather than a rebuild.
Books tracks spend against the budget line during the project, not after it.
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.
Nest — leave, working patterns and contracted hours.
They follow the reporting line you configure, with a dated record of the decision.
Yes, with phases, tasks and dependencies carried forward.
Half an hour on your own numbers is usually enough to say whether Loop is the right place to start.