Skip to main content
A project is one piece of client work. It has a client, a team, a delivery status, and dates.

​
Status vs. state

Two separate things, deliberately:
  • Status — the delivery lifecycle you report on: On going, On hold, Completed, Cancelled.
  • State — whether the record is in play at all: active or archived.
A completed project stays active until you archive it, so it keeps appearing in reports for the period it ran.

​
Setting one up

1

Name and client

Link a client if you have the Clients module on — that’s what makes client-level rollups and invoicing possible later.
2

Dates and engagement

Start and end dates, engagement type, and a monthly hours cap where relevant.
3

Add the team

Each person gets a project role. See Workspaces and people.

​
The project workspace

Board and list

The same tasks, two views. Columns follow your status order.

Sprints and milestones

Timeboxes and delivery checkpoints.

Files and notes

Attachments and shared writing, scoped to the project.

Reports

Delivery confidence, budget, and SLA compliance for this project.

​
Settings worth knowing

Override the workspace default for this project, or leave it to inherit. See SLA Management.
With the Budgets module on, set hours or value and get alerts as thresholds are crossed. Owners and admins see budget warnings in their digest.
Give the project an address so replies and forwarded mail land as work.

​
Archiving

Archiving takes a project out of day-to-day views while keeping its history for reporting. Prefer it to deleting.