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.
Set the dates #
- 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.
- 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.
What a due date changes #
- The Project paces to its due date, so 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.
Was this page helpful?
Related
- Create a project
Add a project to track delivery work, with an optional start date and due date.
- Expected progress
What Expected today means on a goal, how Brev works it out from the time period and milestones, and where it shows.
- Goal status: On Track, Behind and At Risk
What each goal status means, why a goal reads Behind or At Risk, and how to set the status yourself.
- Goals: the complete guide
Every rule for goals in one place: progress, status, tracking, roll-up, weights, alignment, scoring, closing a period, and editing or deleting goals.