> 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/creating-records-manually.md).

# Creating records manually

Enter an RFI, a submittal or a change order that reached you outside email or Procore, so it is tracked and answered like any other.

Not every RFI arrives by email. A contractor asks a question on a call, hands over a printed submittal, or raises a change in a site meeting. You can enter these records yourself so they sit in the same log, with the same thread, as the ones Cogram files for you.

## Creating a record

1. Open the [RFIs](https://app.cogram.com/dashboard/correspondence/rfis), [Submittals](https://app.cogram.com/dashboard/correspondence/submittals) or [Change orders](https://app.cogram.com/dashboard/correspondence/change-orders) page under Contract admin.
2. Click **Create** at the right of the toolbar.
3. Choose the **Project**. When the page is scoped to a project, it is chosen for you.
4. Check the **Number**. Cogram suggests the next number in the project's log, for example `RFI-015` after `RFI-014`. You can change it. If the number is already used in the project, Cogram tells you, and you can still create the record.
5. Enter the **Subject** (RFIs) or **Title** (submittals and change orders).
6. In **From**, pick the contractor contact who sent it, or type their email address to add them as a new contact.
7. Add the question or description, and attach the files they sent. Drop files or folders, choose them, or click **Add from project** to attach documents already in the project.
8. Open the details to set the rest:
   * RFIs: assignee, due date, spec section and drawing.
   * Submittals: assignee, due date, spec section, drawing and package.
   * Change orders: cost impact and currency, schedule impact in days, date received and response due date. The type (PCO, CO or CCD) sits next to the number.
9. Click **Create RFI**, **Create submittal** or **Create change order**. Cogram opens the new record.

An RFI or submittal is received today unless you set **Date received**. Leave **Due date** empty and Cogram sets it from the project's review period. See [Received and due dates](https://docs.cogram.com/contract-admin/due-dates.md).

## What Cogram does with it

The record is filed as received from the contact you chose. Its thread starts with their question or description and the files they sent, as if it had arrived by email. Everything works as it does for a record filed from email: you can reply, run a review, draft a response, forward it to a consultant, and assign it. Your response is emailed to the contact. The record's **Source** reads **Added manually**.

A new record is assigned to you unless you pick someone else in **Assignee**. A record that Cogram files from email is assigned to the person whose mailbox it came in through. You can reassign or unassign either one on the record.

Automations that start when an RFI or submittal is created run for these records too. In an automation's trigger, the source filter calls them **Manual**.

## Projects connected to Procore

When a project syncs RFIs and submittals from Procore, Procore stays the source of truth for them. You can't create an RFI or a submittal in Cogram on that project: the project is grayed out in the picker, and the **Create** button is disabled while the page is scoped to it. Create the record in Procore and it syncs to Cogram.

Change orders don't sync with Procore, so you can create them on any project.

## Who can create records

You need an **RFI / Submittals** seat (see [Licensing](https://docs.cogram.com/organization-administration/licensing.md)), which also covers change orders, and you need to be an owner or member of the project. Project viewers can read records but can't create them.


---

# 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/creating-records-manually.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.
