Timelines for client launches
Move one date.See what it does to the launch.
One late deliverable quietly pushes go-live, and nobody sees it until the client does. Fluidwork draws the chain: link the work, move a date, and watch everything downstream follow.
Launch · Halden Bank website
Thursday, November 26
Drag any bar. Pull its right end to change its length.
Tab to a task, ← → to move, Shift to resize
One late deliverable quietly pushes go-live, and nobody sees it until the client does. Fluidwork draws the chain: link the work, move a date, and watch everything downstream follow.
01 · Dependencies & milestones
Every date knows what it is waiting on.
Link work finish-to-start and pin the moments that matter, like Client sign-off and Launch. When design runs long, Fluidwork moves everything that waits on it, and leaves alone everything that does not.
02 · Baselines & snapshots
A baseline you can explain.
Snapshot the plan the client agreed to. When dates drift, the original stays on the timeline as a ghost with the variance beside it, so “why did launch move?” takes two minutes to answer, not an afternoon.
Design system
Design review ran long
Page templates
Waits on design
CMS build
On baseline
Content migration
Waits on sign-off
Launch vs. Oct 9 baselineNov 26 → Dec 1 · +3 working days
04 · Linear sync
Linear keeps the dates honest.
Engineering stays in Linear. Fluidwork keeps issue context in sync both ways, so the timeline reflects the work as it is, not as it was at kickoff. Not on Linear? Import a CSV or plan with local issues.
Linear · HAL-142
CMS content types
Fluidwork · Halden Bank relaunch
CMS build
Built for the way agencies deliver