> ## 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.
# Tracked Items Overview
> Track commitments, requests, problems, ideas, releases, and other business objects extracted from your conversations — with automatic routing, triage, and promotion to projects
Tracked Items capture the business objects that surface in your conversations — commitments made to customers, feature requests, problems reported, ideas proposed, releases planned. Each item carries the signals it came from, links to related Linear / GitHub work, and a lifecycle that moves from automatic detection through triage to active project work.
## Lifecycle at a Glance
The 2026-04-28 update introduced an end-to-end lifecycle for tracked items: automatic routing → triage → projects.
BuildBetter classifies signals from your conversations and creates a tracked item when one looks important enough to track (`in_triage: true`).
The item appears in the [Triage Signals tab](../Triage/signals) for human review. You can assign, change type/status, merge duplicates, correct misclassifications, push to Linear, or promote to a project.
Promoted items move to [/projects](../Projects/overview) with `in_triage: false` and `status: in_progress` — and bring their signals, calls, and Linear/GitHub links with them.
From `/projects`, the tracked item runs through stages (Scoping → In progress → In review → Shipping → Released → Stable) with rollups, integrations, and close-the-loop tracking. See [Project Detail](../Projects/project-detail).
You can also create tracked items manually — they enter triage by default and follow the same path.
## What's New (2026-04-28)
* **Automatic routing** — high-urgency signals create tracked items in triage automatically
* **AI Route** — propose attaching to an existing project or creating a new one ([details](../Triage/ai-routing))
* **Merge & correction** — duplicate detection with `MergeDuplicateModal`; misclassification feedback via `CorrectionModal` ([details](../Triage/promote-and-merge))
* **Promotion to Projects** — single and bulk promote from any Triage tab
* **Related Linear / GitHub linking** — Linear tickets, PRs, and authors carry over when items move
## What Is Tracked?
Tracked is a system for organizing and monitoring the things that matter to your business. Create object types for different categories—like commitments, requests, or releases—then populate them as these items emerge from customer conversations, internal meetings, and other data sources.
Track commitments, requests, problems, ideas, releases, use cases, objections, and more
Add properties like owner, status, priority, account, initiative, or any custom field
Connect objects to extracted signals showing where they were mentioned
View objects in table or kanban layouts, filtered and sorted your way
## What Can You Track?
Tracked is designed for business objects that emerge from conversations and need ongoing monitoring:
### Commitments & Promises
Things you've committed to customers or stakeholders:
* "We promised Acme Corp we'd have SSO by Q2"
* "Told the enterprise team we'd prioritize bulk import"
* "Committed to fixing the sync issue by next week"
### Requests & Feature Asks
What customers and users are asking for:
* Feature requests from discovery calls
* Enhancement suggestions from support tickets
* Integration requests from sales conversations
### Problems & Issues
Pain points and challenges surfaced in conversations:
* Recurring customer complaints
* Workflow blockers mentioned in calls
* Technical issues affecting multiple accounts
### Ideas & Opportunities
Concepts and possibilities worth tracking:
* Product ideas from customer conversations
* Market opportunities identified in sales calls
* Process improvements suggested by team members
### Releases & Launches
Things you're shipping or have shipped:
* Product releases and their status
* Feature launches with rollout tracking
* Updates communicated to customers
### Use Cases & Objections
Patterns from sales and success conversations:
* How customers are using (or want to use) your product
* Common objections heard in sales calls
* Competitive situations and outcomes
## Core Concepts
### Object Types
Object types define what category of things you want to track. Examples:
* **Commitments**: Promises made to customers
* **Requests**: Feature and enhancement asks
* **Problems**: Issues and pain points
* **Ideas**: Opportunities and concepts
* **Releases**: Product launches and updates
* **Use Cases**: Customer scenarios and applications
* **Objections**: Sales concerns and blockers
### Properties
Properties are the fields you add to track details about each object. Common properties include:
| Property | Type | Example Use |
| -------------- | ----------- | --------------------------------- |
| **Status** | Select | Open, In Progress, Done, Won't Do |
| **Priority** | Select | High, Medium, Low |
| **Owner** | User | Who's responsible |
| **Account** | Text/Object | Which customer it's for |
| **Due Date** | Date | When it needs to be done |
| **Initiative** | Select | Which initiative it relates to |
| **Quarter** | Select | Q1, Q2, Q3, Q4 |
| **ARR Impact** | Number | Revenue associated |
| **Source** | Select | Sales, Support, Product, Internal |
You can create any custom property to capture what matters for your tracking needs.
### Objects
Objects are the individual items you create—each commitment, request, problem, etc. Every object:
* Belongs to an object type
* Has values for defined properties
* Can link to signals from conversations where it was mentioned
* Appears in views based on its property values
## Key Features
### Extraction Links
Connect objects to your conversation intelligence:
* **Link signals**: Associate extracted signals with relevant objects
* **See context**: View the exact moments in calls where objects were discussed
* **AI suggestions**: Get recommendations for relevant extractions
* **Build evidence**: Accumulate mentions across multiple conversations
### Multiple Views
Visualize your tracked objects:
* **Table view**: Spreadsheet-style with sortable, filterable columns
* **Kanban view**: Board organized by status or other select properties
* **My Objects**: Filter to see only items assigned to you
* **Saved filters**: Create and share common filter combinations
### Import & Export
Move data in and out:
* **CSV import**: Bulk import objects from spreadsheets
* **Export data**: Download objects with all properties
* **Bulk operations**: Update multiple objects at once
## Getting Started
Go to **Settings → Features → Tracked** and click **Create Object Type**. Start with something common like "Commitments" or "Requests."
Define properties like Status, Owner, Priority, and Account. Start simple—you can add more properties later.
Navigate to **Tracked** in the sidebar and start adding objects as they surface from conversations.
Connect objects to relevant signals to maintain context and evidence.
Use views to monitor open items, track progress, and ensure nothing falls through the cracks.
## Common Object Types by Team
**Requests**
* Properties: Status, Priority, Requester Count, Account, Initiative, Effort
* Track: Feature requests, enhancements, integration asks
**Problems**
* Properties: Status, Severity, Affected Accounts, Owner, Root Cause
* Track: Customer pain points, workflow blockers, UX issues
**Ideas**
* Properties: Status, Category, Potential Impact, Source
* Track: Product concepts, improvement opportunities, innovation ideas
**Commitments**
* Properties: Status, Account, Owner, Due Date, Made By, Made To
* Track: Promises to customers, timeline commitments, feature promises
**Problems**
* Properties: Status, Account, Severity, Owner, Resolution
* Track: Account issues, escalations, at-risk situations
**Use Cases**
* Properties: Account, Category, Status, Success Metrics
* Track: How customers use your product, expansion opportunities
**Objections**
* Properties: Category, Frequency, Win Rate Impact, Response
* Track: Common concerns, competitive objections, pricing pushback
**Commitments**
* Properties: Account, Deal, Owner, Due Date, Status
* Track: Promises made during sales process
**Use Cases**
* Properties: Industry, Company Size, Category, Outcome
* Track: How prospects want to use your product
**Commitments**
* Properties: Status, Owner, Stakeholder, Quarter, Initiative
* Track: Strategic commitments, board promises, team commitments
**Releases**
* Properties: Status, Target Date, Owner, Initiative, Impact
* Track: Product launches, feature releases, major updates
**Ideas**
* Properties: Status, Category, Strategic Fit, Owner
* Track: Strategic opportunities, market ideas, expansion concepts
## Property Design Tips
### Essential Properties
Most object types benefit from these core properties:
* **Status**: Track lifecycle (Open → In Progress → Done)
* **Owner**: Who's responsible for this object
* **Priority**: How important or urgent it is
* **Source**: Where it came from (Sales, Support, Product, etc.)
### Context Properties
Add context to understand each object better:
* **Account/Customer**: Which customer it relates to
* **Initiative/Project**: What larger effort it connects to
* **Quarter/Timeline**: When it's relevant
* **Notes**: Free-form details and context
### Measurement Properties
Track impact and outcomes:
* **ARR/Revenue**: Financial impact
* **Frequency/Count**: How often it's mentioned
* **Effort/Size**: Implementation complexity
* **Outcome**: What happened (Won, Lost, Shipped, etc.)
Start with 4-6 essential properties. You can always add more as you learn what's useful. Too many properties upfront can slow down object creation.
## Integration with BuildBetter
### From Signals to Objects
Tracked objects connect to your conversation intelligence:
1. Signals are extracted from calls and data
2. Create objects for important items (commitments, requests, etc.)
3. Link relevant signals to each object
4. Build up evidence and context over time
5. Track resolution and outcomes
### With Knowledge Pages
Use Knowledge for process documentation, Tracked for the items themselves:
* **Knowledge**: "How we handle customer commitments" (the process)
* **Tracked**: Individual commitments you've made (the items)
### With Documents
Generate reports and summaries from tracked objects:
* Create documents summarizing open requests by account
* Generate commitment reports for QBRs
* Build release notes from tracked releases
Tracked is available with the appropriate feature flag enabled. Contact your workspace admin to enable object tracking.