Cost Control
You can open, copy, reorder, sync and delete sets from one place.
**Cost Control Sets** lists every set in the project. Open it from **Manage Cost Control Sets** in the set dropdown.
| Column | Why you look at it | | -------------------- | ----------------------------------------------------- | | **Name** | what you called it | | **Comment** | why this one exists | | **Linked to budget** | which budget it tracks — and therefore which it locks | | **Lock** | the padlock state | | **Modified** | when it last changed | | **Server** | its sync state | | **Shared** | who it has been shared with |
The dropdown separates **In Budget *name*** from **In Other Budgets**, so a project with several budgets does not present one undifferentiated list.
- **Open** a set. - **Copy** one — see [copy a cost control set](/kb/article/copy-a-cost-control-set). - **Drag** to reorder — presentation only, no effect on any figure. - **Sync** one set, or **Update All** to bring every dataset in line at once. - **Delete** one, which asks *Are you sure you want to delete this cost control set?*
Worth knowing, because it is sometimes the reason to delete one. A budget is locked *for as long as a set exists on it* — remove the last set and the budget becomes editable again.
That is a legitimate route when a set was created prematurely. It is not the route for a budget that genuinely needs restructuring mid-production: there, copy the budget and leave the set with the original, so what you were measuring against is preserved.
The **Server** column reads in sentences rather than codes. All nine states, and what each one means, are listed once in [how your work is saved and synced](/kb/article/how-your-work-is-saved-and-synced) — this article does not repeat them.
The two to act on are **Version conflict**, meaning the same set changed in two places, and **Upload failed**, meaning a period's bookings exist only on your machine.
Markdown