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.
These are the common day-to-day flows in Projects.
Create a Project
Most projects start in Triage and get promoted, but you can also create one directly.
Click 'New project'
The sparkles-icon button in the top-right of /projects.
Fill in the form
Title (required), description, type (auto-selected, required), optional start/end dates.
Submit
Creates a tracked item, promotes it immediately (so it skips triage), and navigates to /projects/{id}.
Open a tracked item
Selecting a row in the Signals tab opens its detail in the right pane.
Click 'Promote to project'
The action button in the detail footer.
Item appears in /projects
Status flips to in_progress, in_triage flips to false, and the item disappears from the Triage list.
Link a Call
Calls bring in real customer context fast.
Open the Link a Call modal
From the project’s right rail, click Link a call (phone icon).
Search or browse
Search by title, or leave the field blank to see recent calls.
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.”
Find & Attach Signals
When you want to attach signals that match the project’s theme:
Click 'Find related signals'
From the People & Signals card on the detail page.
Search and filter
Type a query; filter by boundary (external / internal / all) and interaction type (call, message, feedback).
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.
The Suggested Signals banner does this automatically when a project has fewer than 5 signals — use it for a head start, then refine with Find related signals. Update Scope from a Call
When a call surfaces a scope change, BuildBetter spots it and surfaces a diff.
Open the Update Scope modal
Triggered automatically when a linked call’s transcript suggests a scope change.
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).
Approve
Writes the change into the project’s scoping doc.
Send a Status Update
Generate a shareable status snapshot for the team, an exec, or release comms.
Click 'Status update'
The send-icon button in the list page header.
Pick a scope
My projects / All projects / Specific initiative.
Pick a window
Default is 7 days; change as needed.
Pick an output type
Team status / Exec rollup / Release comms draft.
Generate and copy
The output is markdown you can click to copy and paste straight into Slack, email, or a doc.
Close the Loop After Release
When a project ships, you owe a follow-up to the people who asked for it.
Open the Close the Loop card
On the detail page, right rail.
Review the checklist
One row per linked contact: person name, company, current reply state.
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.
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.
Merge Duplicates
If the Similar Projects banner appears with candidates:
Review the match
Each candidate shows a match % and 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.
- 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.
