Coming soon: customisable project statuses

Customisable project statuses are finally coming to Operating. Estimated launch date: Monday, October 19th.
⚠️ This may require action from your end. ⚠️
Soon, project status can be
any shade of Tentative: for example “Waiting for Staffing”, “Pending signature”, …
different kinds of Confirmed: for example “Ongoing”, “Paused”, “Pending final paperwork”…
Completed
Cancelled
We will share more info on the customisable statuses later on. This heads-up changelog focuses on the changes in workflows that might be unexpected:
Projects get explicit end states.
Today a project ends by being archived, whether it was delivered or never happened.
With the new statuses, the outcome is recorded first, and archiving is a separate, optional step.
What changes in the project lifecycle
Archiving via the API
Only projects with status Completed or Canceled can be archived.
For existing Operating customers, the old archiving behaviour stays supported until the end of January 2027.
If you archive tentative projects using the API, the status will also change to Canceled
If you archive confirmed projects using the API, the status will also change to Completed
⚠️ Action needed if you pull data from Operating ⚠️
If you filter data with "tentative, archived" or "confirmed, archived", update those filters to Canceled and Completed.
This may break on Monday, October 19th:
CSV exports
Integrations using the Operating API
Your MCP use
Reports API is unchanged
The Reports API works as before. Canceled projects are excluded, the same way "tentative, archived" projects are today. Completed projects are included in confirmed numbers.