Timeline with the chain that matters
Harold follows the dependencies and tells you how much slack is really left.
38 days of work on the chain that matters, and 48 days until 15 Nov.
Harold turns a few sentences into phases, tasks, dependencies and dates. Then Harold rewrites the plan as reality changes, with your approval every time.
Proposed plan · nothing saved yet
4 phases · 27 tasks · target 15 Nov · built from your description
Harold can do anything you can do in a project: close tasks, create them, move dates, shift budget, reorder the plan. Say it in a sentence. Harold works out the knock-on effects and shows you every change before it happens. Open it from any page with Ctrl+J, or ⌘J on a Mac.
It works: try a command, a question, or send the update.
Drag through eight weeks of one project. The spreadsheet drifts with every note; the Harold plan absorbs each one.
Agency can’t start the templates until 6 Oct.
No forty-field project charter. A few questions at most, each one saying why it's being asked. “Not sure” is always an answer.
Yes, it's a hard ceiling Change
Why: approvals add tasks, and fix the order of the last phase.
Why: outside dependencies are the usual reason a launch date slips.
Harold follows the dependencies and tells you how much slack is really left.
38 days of work on the chain that matters, and 48 days until 15 Nov.
Late work rises to the top. Everything else keeps its place.
They rise to the top of your list, and everything else keeps its place.
Required, recommended, optional and conditional work never blur together.
Costs you mention in a note are recorded against the ceiling.
One live, read-only page per project. No account needed to open it, and you can revoke it any time.
Harold reads the note against the whole project and proposes what changes. You accept, reject, or undo.
You tick off a task and add a line
Nothing changes until you accept.
RejectAccept