A project is the unit of delivery. It belongs to a client, holds milestones and tasks, collects files and feedback, and drives what the portal shows on the Overview page.
Create a project
From the client record or the portal, choose New project. Set the dates and fee model up front — both feed the milestone schedule and invoice drafts.
- One project per deliverable keeps reporting readable
- Retainers work better as a rolling project per month
- Projects can be moved between clients if the engagement changes
Milestones drive the story
Milestones are what the client actually tracks. Keep them few, dated, and named after outcomes rather than internal phases.
Tasks, owners, and dependencies
Break each milestone into tasks with a single owner and a due date. Mark a task as blocked by another so a slipped date shifts everything downstream.
- One owner per task — shared ownership means nobody owns it
- Waiting on client tasks surface at the top of the portal Overview
- Subtasks are internal by default
What the client sees
Clients get a clean read of the board: milestone progress, what's in flight, and any item that needs their input. Internal tasks never appear.
Status, closing, and handoff
Close a project when the final milestone lands. Closed projects stay readable in the portal, which gives the client a permanent record of what was delivered.
Visible in the portal, counted in workload and progress reporting.
Dates freeze and reminders pause; the client sees a hold notice.
Read-only. Files and history remain available to the client.
Hidden from the portal but retained in your workspace.
- Resolve open feedback threads before closing
- Send the final invoice from the project so line items carry over
- Duplicate a completed project as the starting point for the next one