Private beta
RAID, the schedule and the critical path on one project record. When a risk lands, the activities it threatens are already attached to it.
What it does
Most tools keep the risk log in one place and the plan in another, so the register turns into a document nobody opens between steering meetings. Here they sit on the same project record.
The same plan, five ways
Five views over the same activities, not five copies of them. Which one you want depends on the question: a board for what is moving this week, a timeline for what a slip does to the end date.
Finish to start, start to start, finish to finish and start to finish, each with lead or lag in days. Most tools give you the first one and leave you to fake the rest. Dates are computed on the project's own working week and its holidays, so a task that cannot run at the weekend does not quietly run at the weekend.
Move a bar and the work downstream of it moves in preview first: you see what the change does to every dependent date before you commit it, and you can undo it afterwards.
Projects can be shared, with owner, member and guest roles, invitations by email, and one screen that shows who can reach what. Projects import and export, so the plan you put in is a plan you can take out again.
Anyone accountable for a date. It assumes you already know what a risk register is and what critical path means, and it does not spend your time explaining them back to you.
Where the project management app is
Private beta, 249 days to launch
Private beta, building in the open
Follow the build as it happens, including the parts that do not go to plan, and be first in the day it opens.
Occasional progress notes, and one email at launch. Unsubscribe in one click.