Projects
A project is the container your work sits in. It has a scope (a supplier, a remit, a lane, or whatever you name), a workflow that says what its stages are, and a start and an end.
Open Projects from the left rail. The list opens on what is live; the control above it reaches closed and archived projects.
Where projects come from
Most of them open themselves. Each overnight engine run puts the lines worth your attention into the project for their scope:
| Workflow | One project per | Opened by |
|---|---|---|
| Supplier buy | Supplier | The daily sync |
| Price review | Remit | The daily sync |
| Transfer | Lane | The daily sync |
| Log a problem | Whatever you name | You, usually from a conversation |
A supplier project spans every buyer holding that supplier’s lines — Mattel across three remits is one project and three sets of lines. Each buyer sees their own share of it.
New lines land in the project that is already open, so a supplier you are part-way through is refreshed rather than replaced. Once it is raised, the next sync opens a fresh one.
The stages inside a project
The stage strip across the top of a project says how many lines are in each stage. A project is never “in Pending” as a whole while a line sits untriaged, so the current stage is the earliest one still holding lines.
| Stage | What is in it |
|---|---|
| Triage | Lines you have not settled yet. Opening one is the review you have always done: the grid, the evidence, your adjustments. |
| Pending | Lines you have settled, waiting on the rest of the batch. |
| Raise the order (or Done) | What has been decided, and the control that closes the batch. |
Clicking a stage opens it without leaving the project, and the URL carries it — so a link to Pending is still a link to the project.
Raising an order
Raise the order closes the batch and writes the consolidated order as a CSV file on the project, with a record of who raised it and when. Nothing is sent to the supplier: sending it is the next step, and until it exists the file is the hand-off.
Whether you can raise it while lines are still open depends on the workspace’s rule (Settings → Projects):
- Every buyer signs off — the order waits until nothing is left open.
- An owner may raise it early — an owner or admin can raise it anyway. The override is recorded, and the units still open move into a new project for the same supplier, so nothing in flight is lost.
When a project closes itself
Two cases, both recorded in the log rather than done quietly:
- It emptied out. The engine stops producing work for a scope — a supplier drops out of the recommendations, or a remit is re-partitioned so its lines move to another book. Every line in the project closes, nothing was ever committed, and after a day of that it closes itself. Nobody has to raise an empty order to clear it, and the scope is free again if the engine comes back to it.
- It went idle. Everything was committed and then left alone for the window your workspace set (Settings → Projects, off unless you set one).
Neither ever closes work you still have open.
The rail beside a project
Every project carries the same rail whatever its workflow: the gate (who has to agree, and whether it is ready), tasks out (with somebody else) and tasks back (with you), the documents attached to it, the artefacts it has produced, and its log — including every sync that added to it.
Starting one by hand
New project offers the workflows this workspace has switched on. A conversation with Twelfth can be promoted into one with Make this a project: the chat stays the record of how it started, and the project carries it from there.
Workflows that are designed but not built yet appear as dashed cards. Opening one shows what it will be and records that you want it.
Where the old links go
/app/work, /app/triage and /app/pending now open Projects. An old link to a single work item opens that item inside the project that holds it.