# Set a project's start and due dates

Give a project its own delivery window, and see how a due date changes its pacing and reporting.

A Project's dates are its delivery window, separate from its time period. Both are optional.

**Who can do this:** anyone who can edit the goal. By default that is its owners, and Org Admins and Owners. Team Admins can too when their team, or a subteam, owns the goal or has one of its owners. See [Roles and permissions](https://help.brev.io/roles-and-permissions/).

## Set the dates {#steps}

1. Open the Project's ⋯ menu and choose **More fields**. On the Project's page, you can instead hover the details under its title for **Add start date** and **Add due date**.
2. Choose **Due date** or **Start date** and pick a date. To clear one, open its pill in the goal dialog and choose **Remove due date** or **Remove start date**.

![A goal page, where a Project shows its dates in the details under its title.](https://help.brev.io/doc-assets/screenshots/goal-detail-goal-page.png)

> **Tip: Success check**
>
> The row shows a "Due" chip with the date. Point at it to see the whole delivery window.

## What a due date changes {#what-a-due-date-changes}

- The Project paces to its due date, so [expected progress](https://help.brev.io/expected-progress/) and status count down to it.
- It counts in the period that holds its due date, not the one it's filed in.
- With no start date, pacing starts on the day the Project was created.
- A connected Linear or Asana project fills in a date you left empty.

---

Use Brev from Claude, ChatGPT or Cursor with the Brev MCP server, https://mcp.brev.io/mcp: [set it up](https://help.brev.io/connect-ai-assistant/).