Loading
Because the plan and the truth are separate. The plan is a document; the truth is spread across four people, and the report is the weekly act of joining them by hand.
By the time it is written it describes Tuesday, and the decisions it supports are being made on Thursday.
The plan is the record the team works in, so the report is a view rather than an assembly job. Delivery risk is derived from ageing tasks, stalled dependencies and capacity that never existed — evidence rather than the loudest voice in the standup.
The AI standup digest summarises what actually changed and cites the tasks it read, so it can be checked.
It will not manage stakeholders and it will not tell you which risk actually matters. It surfaces the ones with evidence behind them; judgement stays yours.
And it will not fix a plan built on optimistic estimates. It will show you how the last six went, which is the more useful input.
Because capacity comes from Nest and cost from logged time, a plan that cannot be staffed is visible before it is committed to rather than in week three.
Margin and schedule sit on one record, so the trade-off conversation happens with both numbers present.
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.
It is a live view of the work, so there is nothing to assemble. The digest summarises what changed.
From the work itself — ageing, dependencies, capacity — with the reasons shown.
Yes, capacity comes from Nest including leave and working patterns.
Half an hour on your own numbers is usually enough to say whether Loop is the right place to start.