> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/contract-admin/internal-comments.md).

# Internal comments

Discuss an RFI, submittal, change order or transmittal with your team in internal comments, and @mention a colleague to bring them in.

Comments let your team talk about an RFI, submittal, change order or transmittal next to its correspondence. A comment is never sent. Only people in your organization who can see the record can read it.

## Write a comment

1. Open the RFI, submittal or change order.
2. In the **Internal notes** section, click **Add note**.
3. Type your comment. To bring in a colleague, type **@** and pick their name.
4. Click **Add note**, or press Cmd+Enter (Ctrl+Enter on Windows). Enter starts a new line.

The comment appears under **Internal notes**. It is also listed in the record's history: open **Details** in the sidebar and click **History**.

## See the record's history

Click **History** under **Details** in the sidebar to open the full history of the record in a side panel, oldest first: status changes, assignments, review requests and removals, views and receipts, messages, notes and edits. Each row shows who did it and the exact time. Use **All**, **Status**, **Reviews**, **Messages** and **Views** to filter the list.

On the page itself, each event shows next to what it is about:

* A reviewer's card shows **Viewed** and when, or **Not opened yet** once the request is a day old. Only requests sent through Cogram record a view.
* A message shows **Opened by** and the reader's name when the recipient opened it in Cogram. Hover for the exact time.
* The official response shows when it was sent and, when known, when it was opened.
* In **Ball in court**, hover over or focus a stage to see who moved the record there and when.

## Write a new email from a card

Each card on the page has **New email** in its header. It folds the card's conversation to one line and opens the composer with the card's party in **To**. **Cancel** or **Send** puts the conversation back the way it was. To remove a reviewer who has not responded, open the **...** menu on their card and click **Remove reviewer**.

On a transmittal, use the comment box at the end of the thread and click **Comment**. The comment appears in the thread under a tinted header with a lock and an **Internal** label.

## Respond from the Official response card

The **Official response** card holds the whole response: who it goes to, the response of record where the record has one, your message and attachments. The **Respond** button at the top of the page opens the card and puts the cursor in the message.

| Record type  | Sent by email          | Linked to Procore |
| ------------ | ---------------------- | ----------------- |
| RFI          | Send official response | Send to Procore   |
| Submittal    | Send official response | Send to Procore   |
| Change order | Send official response | Not available     |

### Check what goes out

There is no separate review step. Everything that goes out is in the card:

* **To** shows the recipient. Point at it to see the sender.
* **Cc** opens a field to copy other people on the email.
* **Subject** starts with what the email would normally say. When the subject has the record's number, the part up to the number stays, so replies find the record. You can edit the text after it. If the subject has no number, you can add text to the end.
* **Files** shows the attachments in the order they are sent. The record's cover sheet comes first, built from what you entered. Click a file to open it. Click its **X** to leave it out. **Add cover sheet** puts the cover sheet back.

A record linked to Procore shows **Posts to Procore as** *your name* instead of To and Subject.

If Cogram's review has checks that need attention, the send button asks you to confirm in the card. Click **Send anyway** to send, or **Cancel** to go back. With no checks to look at, the response goes when you click the send button. If it can't be sent, the card says so and keeps everything you entered. A cover sheet you send is kept on the thread message with the other files.

## Who sees comments

* People in your organization who are on the project can read the comments.
* Comments never leave your organization. They are not in the emails Cogram sends, the external reviewer portal, the copy a consultant or contractor receives, cover sheets, filled templates, record downloads or Procore.
* Comments are part of your organization's [data export](https://docs.cogram.com/organization-administration/data-exports.md).

## Who can comment

Project owners, leads and members can comment. Project viewers can read comments but not write them.

## Mention a colleague

Type **@** to see the people you can mention: everyone in your organization on the project. A mentioned colleague gets a notification in the bell and a short email. The email says who mentioned them and links to the record. It does not include the comment.

## Edit or delete a comment

Only the person who wrote a comment can change it.

1. Open the **...** menu on the comment.
2. Select **Edit** to change the text, or **Delete** to remove it.

An edited comment shows "edited" before its date. A deleted comment leaves the thread for everyone and cannot be restored. When you add a mention while editing, only the newly mentioned colleague is notified.


---

# 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.cogram.com/contract-admin/internal-comments.md?ask=<question>&goal=<user_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.
