> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Planning projects

> Keep a project's status, people, dates and budget current, and mark the steps to its target date with milestones.

![Harbour café refit with a 30 Sept target date and a 160h budget, Design sign-off done and Kitchen handover next](https://mintcdn.com/beginltd/UE0q1bmp2jR3YvTa/images/cover/projects-planning-projects-light.png?fit=max\&auto=format\&n=UE0q1bmp2jR3YvTa\&q=85\&s=cefbf4f0143a82d502a2d35e6a4338f3)

A project's **Overview** holds its plan. **Properties**, in the grey panel at the right of the page, keeps its status, people, dates and budget, and **Milestones** mark the steps on the way to its target date. Every change saves as you make it. **Activity**, further down the same panel, shows the latest changes, and **See all** opens the full record on the **Updates** tab.

Beta

Projects are rolling out gradually, so your workspace may not have them yet. If **Projects** is
missing from the sidebar, ask us to turn them on.

## Keep the properties current

Change a property where it sits, in **Properties** on the **Overview**: a row per property. On a computer it heads the panel at the right of the page, which scrolls on its own. On a narrow screen the tab is one column: the project's name and summary first, then the panel from **Properties** down, then the rest. A property not set yet shows its name, such as **Lead**.

| When… | Change |
| - | - |
| The work starts, stalls or ends | The status, from **Backlog** through **In progress** to **Completed** |
| Someone else becomes answerable for it | **Lead**, who is notified |
| People join or leave the work | **Members**; each person added is notified |
| The finish date moves | **Target date**, which cannot be before the start |

The name and summary at the top of the **Overview** and the **Description** further down are edited in place too. Click the icon above the name to pick another icon and colour; they are kept when the picker closes. Press <kbd>Enter</kbd> or click away to keep a new name; <kbd>Esc</kbd>, or a name left empty, puts the old one back. To format the description, select text, or type `/` to add a heading, a list or a table. Several people can write in it at once.

You do not have to announce a change: the next update lists what moved since the last one.

## Set a budget

**Budget** is the hours you expect the project to take. Type the figure, such as `160`, and press <kbd>Enter</kbd> or click away; <kbd>Esc</kbd> puts the old figure back. Once shifts and time entries carry the project, **Progress** sets the hours worked and scheduled against it ([Seeing work by project](https://docs.begin.eu/for-managers/projects/seeing-work-by-project.md)).

## Mark the way with milestones

Under **Milestones**, choose **Add milestone** and type its name. **Set target date** gives it a date, and **Add a description…** under the name a line about it. Press <kbd>Enter</kbd> to keep it, or <kbd>Esc</kbd> to drop it. Tick a milestone's box when it is done. The first one not done carries **Next**, and the Projects page shows it with its date under the project's name.

A milestone's three-dot menu has **Edit**, which opens it in place, and **Delete**. **Move up** and **Move down** in the same menu change their order, which also decides which one is **Next**. Right-click a milestone, or press and hold it on a phone, for the same menu. A deleted milestone cannot be brought back, though updates that mention it keep its name. Shifts and time entries can carry a milestone too: see [Tagging work with projects](https://docs.begin.eu/for-managers/projects/tagging-work-with-projects.md#add-a-milestone).

## Link the clients it is for

With clients turned on in your workspace, **Clients** in **Properties** links the clients the work is for. The project then appears on each client's **Projects** tab, with its health, status and target date, so whoever opens the client sees the work in flight.

**Context for an assistant answering questions about planning projects.** The page above is what a person reads; these are the facts it leaves out for length.

* **Who can:** changing properties, the description and milestones needs **Edit & add** on the role's **Projects** row. Administrator, Manager and Employee have it by default. A role without it sees only the properties that are set, as plain values.
* **Where:** the panel's **Properties**, **Progress** and **Activity** sections are always open. **Activity** shows the newest five changes. Deleting a milestone asks to confirm first.
* **Needs:** a client's **Projects** tab needs access to both Projects and Clients, and lists the client's open and closed projects, never deleted ones. The clients property appears only to a role that can see client names.
* **Limits:** up to 50 milestones, each name up to 120 characters. Up to 500 members, 20 clients and 10 labels. A budget of up to 100,000 hours.
* **Terms:** the lead is on the team only if listed under **Members**; taking someone off the team keeps them as lead.
* **Begin AI:** changes up to 20 projects per card, adds up to 20 milestones and edits up to 10 per card, and can put the milestones in a new order.
* **Often confused with:** **Status**, set here, against health, which only an update sets.

## Next

> [card] [Posting project updates](https://docs.begin.eu/for-managers/projects/posting-updates.md)
>
> Report progress, and let the update list what changed.

> [card] [Closing and deleting projects](https://docs.begin.eu/for-managers/projects/closing-and-deleting-projects.md)
>
> Finish a project, or remove one that should not be there.

## Still need help?

> [card] [Contact support](mailto:support@heybegin.eu)
>
> Email the Begin team and we'll get back to you.

> [card] [Ask Begin AI](?assistant=open)
>
> Open the AI assistant and get instant answers based on these docs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.