Know the launch is slipping before anyone asks
Status reports go stale the day they are written. Keel works out launch health from the plan and the activity around it, and tells you in plain words what is slipping and why.
What is slipping, and why
Auth service is 4 days late, which uses all the slack before the Nov 18 launch1. Payments API has had no commits for 6 days2.
- Auth service At risk
- Payments API Drift: no commits in 6 days
- Pricing screens On track
What it does
- Launch healthOn track, At risk, or Off track, with a confidence figure from critical-path slack, open risks, and overdue work.
- RepeatableThe formula is documented and tested; the same inputs always give the same result.
- Drift detectionRules catch mismatches like a task in progress with no commits for days, or done work with blocked dependents.
- Risk badgesEach badge gives the reason in one line and links to the message or commit behind it.
- Weekly summaryA digest for leads and stakeholders, written from computed numbers, with every claim cited.
- Deadline warningsWarnings before due dates, and overdue work flagged.
How it works
Every flow in Keel follows one loop: a signal becomes a risk, a risk becomes a proposal, and only an approval changes the plan.
- Keel reads the plan and the activity around it.
- It computes slack, risks, and overdue work.
- Launch health and confidence update.
- Drift and risk badges explain the reason.
- Leads get a cited weekly summary.
Launch health and drift questions
How is launch health calculated?
From critical-path slack, open risks, and overdue tasks, using documented and tested weights, so the same inputs always give the same result.
What is plan drift?
A mismatch between the plan and reality, such as a task marked in progress with no commits for six days.
Does every alert have evidence?
Yes. Each risk badge links to the message or commit it is based on.
Try it on your own launch
Keel is in early access. Join the waitlist and we will write once, when your workspace is ready.