> For the complete documentation index, see [llms.txt](https://docs.growthfactor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growthfactor.ai/deals/deal-activity.md). # Deal Activity Every deal has an activity feed. It logs stage moves, field edits, file changes, and comments, each with who made it and when. *** ### Opening the Activity Feed Open any deal. The **Deal Activity** panel sits on the right side of the deal page. Use **Hide Activity** or **Show Activity** in the deal page's menu to close or reopen it. On a phone, it opens as a panel that slides over the deal. The header shows how many entries the deal has. The footer shows when the last one was added. *** ### What's Tracked | Activity | What the entry says | | --------------------- | ------------------------------------------------------------------------------------------------ | | **Stage moves** | `Moved from Searched to Qualification` | | **Deal lead changes** | `Updated lead from "Sarah Chen" to "Mike Rodriguez"` | | **Field edits** | The field, its old value, and its new value, like `Updated square footage from "1200" to "1500"` | | **Custom fields** | The field's name, its old value, and its new value | | **Notes** | The old and new notes text | | **Files** | `Updated site overview` or `Updated loi` | | **Comments** | The full comment text | Changes to a deal's score aren't logged. File entries don't name the file, and uploading, replacing, or removing a file all read the same way. To see a file's name and who uploaded it, check its card in the **Files** section. Disqualifying a deal is a stage move, so it shows as `Moved from … to Disqualified`. *** ### Reading the Feed Entries are listed newest first. Each one shows: * The team member who made the change * An icon for the type of activity * How long ago it happened, like "2 hours ago" * What changed A deal with no entries yet shows **No activity yet**. The feed keeps every entry for the life of the deal. Permanently deleting a deal also deletes its activity feed. *** ### Comments #### Adding a Comment 1. Open the deal 2. Click **Write a comment...** in the **Deal Activity** panel 3. Type your comment 4. Press `⌘Enter` (`Ctrl+Enter` on Windows) or click the arrow button to send it Press `ESC` to cancel. Comments can't be edited or deleted once they're sent. #### Who Can See and Add Comments Anyone who can view the deal's workspace can read its comments. Adding a comment requires edit access to the workspace. Without it, the comment box doesn't appear. #### Comment Best Practices **Be specific:** "Landlord countered at $32 PSF NNN, reviewing with finance" is more useful than "Negotiating." **Tag next steps:** "Awaiting phase 1 environmental report, expected Thursday" helps the team know what's pending. **Capture decisions:** "Committee approved moving forward contingent on 10-year lease term" documents critical decision points. **Note external communications:** "Called broker, left voicemail" creates a record of outreach attempts. #### Comments vs. Notes | Comments | Notes | | ----------------------------------- | ---------------------------------------- | | A running list of entries | A single editable field | | Entries from different team members | One current-state summary | | Can't be edited once sent | Each edit is logged in the activity feed | Use **comments** for ongoing updates and discussion. Use **notes** for current-state summary information. *** ### Best Practices **Comment liberally.** When in doubt, add a comment. Documented context is worth far more than the moment it takes. **Update as things happen.** Log activity when it happens, not in weekly batches. It keeps the whole team informed and prevents forgotten details. **Document decisions and rationale.** Don't just log *what* happened. Explain *why* when it's not obvious. "Moving to Disqualified—cannibalization too high at 35%" is more valuable than just changing the stage. **Use activity history in handoffs.** When you take over a deal, read its activity feed for context. **Review activity before meetings.** Before committee reviews or check-ins, scan recent activity to refresh your memory on deal status. *** ### Related Features * [Deal Dashboard](/deals/deal-dashboard.md) — pipeline views showing deal status * [Creating and Managing Deals](/deals/creating-and-managing-deals.md) — the actions that add entries to the feed --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.growthfactor.ai/deals/deal-activity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.