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

# Common Project Workflows

> Create a project, update scope from a call, send a status update, attach signals, run close-the-loop after release

These are the common day-to-day flows in Projects.

## Create a Project

Most projects start in [Triage](../Triage/overview) and get promoted, but you can also create one directly.

<Steps>
  <Step title="Click 'New project'">
    The sparkles-icon button in the top-right of `/projects`.
  </Step>

  <Step title="Fill in the form">
    Title (required), description, type (auto-selected, required), optional start/end dates.
  </Step>

  <Step title="Submit">
    Creates a tracked item, promotes it immediately (so it skips triage), and navigates to `/projects/{id}`.
  </Step>
</Steps>

## Promote from Triage

The more common path. In Triage's Signals tab:

<Steps>
  <Step title="Open a tracked item">
    Selecting a row in the Signals tab opens its detail in the right pane.
  </Step>

  <Step title="Click 'Promote to project'">
    The action button in the detail footer.
  </Step>

  <Step title="Item appears in /projects">
    Status flips to `in_progress`, `in_triage` flips to `false`, and the item disappears from the Triage list.
  </Step>
</Steps>

You can also bulk-promote — select multiple rows in the Signals tab, then click **Promote N**. See [Promote & Merge](../Triage/promote-and-merge).

## Link a Call

Calls bring in real customer context fast.

<Steps>
  <Step title="Open the Link a Call modal">
    From the project's right rail, click **Link a call** (phone icon).
  </Step>

  <Step title="Search or browse">
    Search by title, or leave the field blank to see recent calls.
  </Step>

  <Step title="Pick a call">
    Click any row. All signals from that call auto-attach to the project, and you'll see a toast: *"Linked 'Call title' — attached N signals."*
  </Step>
</Steps>

## Find & Attach Signals

When you want to attach signals that match the project's theme:

<Steps>
  <Step title="Click 'Find related signals'">
    From the People & Signals card on the detail page.
  </Step>

  <Step title="Search and filter">
    Type a query; filter by boundary (external / internal / all) and interaction type (call, message, feedback).
  </Step>

  <Step title="Multi-select and add">
    Check the signals you want, click **Add N to review**. They attach in the "suggested" review state — they don't feed the AI rollup until you approve them.
  </Step>
</Steps>

<Tip>
  The [Suggested Signals](./ai-features#suggested-signals-banner) banner does this automatically when a project has fewer than 5 signals — use it for a head start, then refine with **Find related signals**.
</Tip>

## Update Scope from a Call

When a call surfaces a scope change, BuildBetter spots it and surfaces a diff.

<Steps>
  <Step title="Open the Update Scope modal">
    Triggered automatically when a linked call's transcript suggests a scope change.
  </Step>

  <Step title="Review the evidence">
    Left side: the quoted transcript segment with speaker and timestamp. Right side: a draft diff of the scope doc (removed bullets vs. added bullets, grouped under section headings).
  </Step>

  <Step title="Approve">
    Writes the change into the project's scoping doc.
  </Step>
</Steps>

## Send a Status Update

Generate a shareable status snapshot for the team, an exec, or release comms.

<Steps>
  <Step title="Click 'Status update'">
    The send-icon button in the list page header.
  </Step>

  <Step title="Pick a scope">
    My projects / All projects / Specific initiative.
  </Step>

  <Step title="Pick a window">
    Default is 7 days; change as needed.
  </Step>

  <Step title="Pick an output type">
    Team status / Exec rollup / Release comms draft.
  </Step>

  <Step title="Generate and copy">
    The output is markdown you can click to copy and paste straight into Slack, email, or a doc.
  </Step>
</Steps>

## Close the Loop After Release

When a project ships, you owe a follow-up to the people who asked for it.

<Steps>
  <Step title="Open the Close the Loop card">
    On the detail page, right rail.
  </Step>

  <Step title="Review the checklist">
    One row per linked contact: person name, company, current reply state.
  </Step>

  <Step title="Draft the update">
    Use the composer to write a short message. The same body can be sent across recipients, or you can tailor per-person.
  </Step>

  <Step title="Send via Slack or email">
    One-click per contact. A contact gets auto-marked "replied" once the assignee responds in the designated channel or thread — no manual checkboxes needed.
  </Step>
</Steps>

## Merge Duplicates

If the [Similar Projects](./ai-features#similar-projects-banner) banner appears with candidates:

<Steps>
  <Step title="Review the match">
    Each candidate shows a match % and title.
  </Step>

  <Step title="Click 'Merge'">
    Collapses the candidate into the current project: moves every attached signal, archives the duplicate, and logs a merge event in the timeline.
  </Step>
</Steps>

## Update Metadata Inline

The rail dropdowns update fields without leaving the page:

* **Status** — change the substatus chip
* **Type** — re-categorize the project
* **Assignee** — assign or reassign the DRI
* **Priority** — P0–P3
* **Area** — taxonomy area path

Every change is timestamped and visible in the Timeline tab.