> 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/organization-administration/contract-admin-settings.md).

# Contract admin settings

Organization-wide settings for RFIs, submittals and change orders: filing from project email, AI drafts for Procore records, the Cogram Automatic Review prompts, submittal response statuses, and what

Org Admins manage organization-wide settings for RFIs, submittals and change orders under [Organization Settings > Contract admin](https://app.cogram.com/dashboard/settings/admin/contract-admin). The tab has five sections: **Filing**, **AI drafts**, **Automatic review**, **Submittal responses** and **Cover sheets**.

> **Availability**: The **Contract admin** tab appears for Org Admins when your organization has Contract admin. You do not need a Contract admin license yourself to change these settings. See [Licensing](https://docs.cogram.com/organization-administration/licensing.md).

## Filing

Cogram can file RFIs, submittals and change orders from project email. The **Filing** section has one switch for each, and each switch applies to the whole organization:

* **RFI filing** files a qualifying email as an RFI and drafts a response for review.
* **Submittal filing** files a qualifying email as a submittal and drafts a review.
* **Change order filing** files a qualifying email as a change order and fills in its details for review.

Turn a switch off to pause that filing on every project. Projects keep their own settings, so turning the switch back on restores them.

A record is filed for a project only when all of these are true:

1. The switch is on here.
2. **Email filing** is on for the project.
3. The matching switch is on for the project, under **Overview > Automations**.

Cogram turns the three project switches on when someone turns on **Email filing** for a project. See [RFI, submittal and change order filing](https://docs.cogram.com/agent/automations.md#rfi-submittal-and-change-order-filing).

**Expected result**: on a project's **Automations** tab, a row you paused here is locked and reads "Paused for your organization."

**A switch reads "Not set up yet"**

Cogram sets up the three filing Automations when someone in your organization gets an Agent license. Assign an Agent license to one person under [Organization Settings > Licenses](https://app.cogram.com/dashboard/settings/admin/licenses), then reload this page. Contact Cogram support only if your organization does not have Agent.

## AI drafts

**Draft responses for Procore records** controls the drafts Cogram starts by itself in connected Procore projects. It is off until an Org Admin turns it on.

When it is on, Cogram drafts a response each time an RFI or submittal in a connected Procore project lands in your court. It applies only to Procore projects where **RFI filing** or **Submittal filing** is on. Items already in your court when you turn it on are skipped.

Pausing **RFI filing** or **Submittal filing** for the organization in the **Filing** section also stops these drafts for that record type, on every project.

The switch does not change two other drafts. The **Draft response** action on a record always works, and a record filed from an email always gets its draft.

Review every draft before you send it. Check names, dates, quantities, and specification and contract references against the source.

## Automatic review

The Cogram Automatic Review is the review card at the end of an RFI, submittal or change order page. Click **Run review** on the card, or **Rerun** in its menu, and Cogram writes one review of the record: what needs action first, each finding with a link to the file page or record it comes from, and a suggested next step. The card shows a verdict: **Looks good**, **Comments** or **Action needed**.

When the review finds that a consultant from the project directory should review the record next, it offers to send it to them: the firm's name in the review becomes a link, and **Suggested actions** under the review has a **Send to** button for each. Clicking opens **Send for review** with that person and a short note filled in. You can change anything before you send. A consultant who is already reviewing the record shows **Already reviewing** instead.

The **Automatic review** section holds the reviewing instructions Cogram follows, one prompt per record type: **RFI**, **Submittal** and **Change order**.

### Change a prompt (Org Admins)

1. Open the **Automatic review** section of [Organization Settings > Contract admin](https://app.cogram.com/dashboard/settings/admin/contract-admin#automatic-review).
2. Edit the prompt of a record type. For example, add what your firm checks first on every submittal.
3. Click **Save**.

The line above each prompt says **Cogram default**, or who changed it last and when. **Reset to default** returns that record type to Cogram's prompt. A record type you have not changed follows Cogram's default, including later improvements to it.

The prompt holds the reviewing instructions only. The record's details, the output format, the verdicts, the links and the safety rules are fixed by Cogram.

**Expected result**: rerun the review on a record of that type. The new review follows your prompt. Reviews that ran before keep their text until they are rerun.

## Submittal responses

Set the response statuses your team picks from when responding to a submittal, such as Approved or Revise and Resubmit. Org Admins do this under the **Submittal responses** section of [Organization Settings > Contract admin](https://app.cogram.com/dashboard/settings/admin/contract-admin#submittal-responses).

**Where the statuses apply**

* Submittals that are not linked to Procore: those created from an email, and those recorded in Cogram only.
* The label you set is the one your team picks, the one shown on the submittal (thread, board, list, and cover sheet), and the one printed in the email to the contractor.

**Where they do not apply**

* Procore-linked submittals. They keep the standard statuses, which Cogram maps to the response types of the Procore project.
* RFIs. An RFI response is an answer and has no status.

### Change the statuses (Org Admins)

1. Open the **Submittal responses** section of [Organization Settings > Contract admin](https://app.cogram.com/dashboard/settings/admin/contract-admin#submittal-responses).
2. Edit a label. A label can have up to 60 characters.
3. Drag a status by its handle to change the order.
4. Turn a status off to stop offering it. At least one status stays on. **Not Applicable** is off until you turn it on.
5. Click **Save changes**.

There are six statuses. You can rename, reorder, and turn them off, but you cannot add new ones.

### Expected result

Open a submittal that is not linked to Procore in [Contract Admin > Submittals](https://app.cogram.com/dashboard/correspondence/submittals) and respond. The statuses offered are the ones you left on, under your labels, in your order.

Renaming a status also renames it on submittals already responded to in Cogram. Emails already sent do not change.

### Start over

**Reset to defaults** puts the labels, the order, and the switches back to how Cogram ships them. You are asked to confirm first.

## Cover sheets

Cogram puts a cover sheet in front of every RFI, submittal, change order and transmittal your firm downloads or sends. The **Cover sheets** section of [Organization Settings > Contract admin](https://app.cogram.com/dashboard/settings/admin/contract-admin#cover-sheets) sets what your firm prints on it.

Every field is optional. An empty field prints nothing: no heading, no blank line.

### Limitation wording

Two texts, each in your firm's own words:

* The **RFI** text prints under the official response on an RFI your firm has answered. An RFI with no response prints none.
* The **submittal** text prints in the review stamp on a submittal your firm has returned. A submittal still under review prints none.

**Use suggested wording** fills the editor with a starting point. It is a draft, not a default: read it, edit it to match your agreements, and save. Cogram prints nothing until you do. Each text can have up to 1,000 characters.

### Letterhead

Your firm's address, phone and website print under your firm name or logo in the sheet header, small and secondary.

These three fields are your firm identity, the same one under [Organization Settings > General](https://app.cogram.com/dashboard/settings/admin/overview). Change the address here and it changes there too, so your firm has one address of record.

Your firm's role on a job ("Architect of record", "Design architect") is set per project, not here. See [Firm role](#firm-role) below.

### Preview

**Sample RFI cover** and **Sample submittal cover** download a sheet that carries your saved settings on obviously-sample content, so you read your own wording on a sheet before a consultant does. Save first: the sample shows what is saved, not what is in the editor.

### Firm role

Set your firm's role for one project on that project's **Overview > Settings** tab, in the **Firm role** section. It prints with your firm identity on that project's cover sheets. Project owners and Org Admins can change it. Left blank, nothing prints.

One firm is the architect of record on one job and the design architect on the next, which is why the role is per project and the letterhead is not.


---

# 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/organization-administration/contract-admin-settings.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.
