Features/Timelines
The road to launch, visible to your client.
Every project gets an ordered, dated timeline: what is done, what is in progress, and what is waiting on the client. Your client reads it at a glance instead of asking, and the one that is stuck on them chases itself.
60 days with everything on. No card.
Timeline · Website redesign
2 of 5 doneKickoff and sitemap
Done Feb 6
Design approved
Done Feb 20 · logged in the thread
Build and internal review
In progress · due Mar 6
Content in from you
Waiting on youDue Mar 3
Waiting on you · homepage copy and team photos
Launch
Mar 17
Your client sees this exact list · the reminder handles the chasing
How it works
The mechanics, plainly.
01
Milestones in plain words, in order
Design approved, content in, launch. You lay out the milestones with or without dates, drag them into order, and the timeline holds that order even when a date moves. The client sees where things stand without a status call, and so does everyone on your side.
02
A stuck milestone joins the waiting list
When a milestone is blocked on the client, you mark it and say what you need. It joins the same waiting-on-client list as approvals and signatures, and the same 48-hour reminder nudges them under your name. No second reminder system, no chasing by hand.
03
Your checklist stays yours
Under each milestone your team keeps a private checklist of what is left. Clients never see it: it is not hidden by the screen, it is withheld by the database. The client sees the milestone; the mess behind it stays backstage.
04
Quiet by design
Completing a milestone posts one small line into the project's thread, which reaches clients who live in email through the thread they already have. Adding, editing, and reordering notify nobody. A plan being sketched should not ping anyone.
Dates optional
A sequence without dates is a valid timeline. Add dates when they are real.
The reminder does the chasing
A milestone waiting on the client inherits the 48-hour reminder automatically.
Status cannot drift
Done, current, waiting, and upcoming are read from the facts, never set by hand.
Common questions
Can my client edit the timeline?
No. Clients read it; your team writes it. The only way a client acts on the timeline is answering the thing a milestone says is waiting on them.
Who can see the checklist under a milestone?
Only your team. Checklist items are never sent to a client's browser at all, so there is nothing to accidentally reveal.
Do milestones need dates?
No. An ordered list without dates is a valid timeline, and you can add dates when they become real. Ordering is by your sequence, not by date, so a moved date never reshuffles the plan.
Does every change email my client?
No. Completing a milestone posts one line into the project's thread. Marking one as waiting on the client sends the same notification the waiting list already uses. Everything else is silent.
Try it with one client this week.
Move one project in and see. If it doesn't help within two weeks, export it and walk away.
60 days with everything on. No card.