> For the complete documentation index, see [llms.txt](https://nationgraph.gitbook.io/nationgraph/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nationgraph.gitbook.io/nationgraph/help-center/readme/automations-overview/foia-automations.md).

# FOIA Automations

Request, track, and parse signed vendor contracts at scale through FOIA.

Click here to watch [video](https://screen.studio/share/w9ufzf9f).

{% embed url="<https://screen.studio/share/w9ufzf9f>" %}
Submitting a mass FOIA / vendor-contract automation
{% endembed %}

### What it does

Request signed vendor contracts across one territory or your full coverage map.

You can now:

* Submit FOIA requests at scale through one automation
* Target one vendor or several vendors in the same run
* Narrow requests to the products you actually compete with
* Filter results by status, vendor, product, and date range
* Review parsed contract fields and the raw contract document
* Push completed results into your CRM once it is connected

This gives your team direct visibility into vendor relationships, ACV, and renewal timing.

### When to use this

* You need competitor intel at scale.
* You want renewal timelines and contract values.
* You want proof of incumbent usage before outreach.

### Create a FOIA automation

{% stepper %}
{% step %}

#### Start the automation

Go to **Automations → New Automation → Request Vendor Contracts**.

Select one territory or all territories.

These are the institutions you are requesting from.
{% endstep %}

{% step %}

#### Select vendors and products

Choose the competitors or vendors you want to request.

Then choose the specific products you compete with.

For a broad reseller like **CDWG**, pick only the relevant SKUs.

For a direct competitor, select the full product set.
{% endstep %}

{% step %}

#### Set the renewal window

Choose a date range that matches the renewal window you want to map.

In the demo, the range starts in **January 2023** and extends several years out.

Use the range to see where each competitor sits over time.
{% endstep %}

{% step %}

#### Name and generate the batch

Name the automation and create it.

Generating the request batch usually takes a minute or two.
{% endstep %}
{% endstepper %}

### What to expect

NationGraph fans the run out for you.

It submits web forms and sends emails to FOIA officers where needed.

In the demo, the run covers about **53,000 institutions** and about **161,000 total requests** across three vendor requests per institution.

{% hint style="warning" %}
FOIA timing varies by agency. Plan for **4–6 weeks** before many requests start returning.

In the demo, fewer than **5%** of existing contracts return within three months. About **45%** return in months three through six. Overall success lands around **60–70%** for contracts that exist.

Small districts often miss the six-month SLA because they do not have a dedicated FOIA officer.
{% endhint %}

### Use the results

Open the results table to review and filter the contracts that come back.

When new contract results are ready, NationGraph sends a notification to the in-app notification inbox. If you subscribe to real-time email or Slack alerts, the notification is also sent there.

You can filter by:

* status, such as **Completed**
* vendor
* product
* date range

Each record can include:

* annual **ACV**
* total **ACV**
* contract end date
* contract metadata
* the raw contract document, including signer and payment terms

Once your CRM is connected, you can push selected records into it from the results table.

See [Sync automation results to your CRM](/nationgraph/help-center/readme/automations-overview/sync-automation-results-to-your-crm.md).

### Related pages

* [Competitor Contracts](/nationgraph/help-center/readme/workspaces/competitor-contracts.md)
* [Sync automation results to your CRM](/nationgraph/help-center/readme/automations-overview/sync-automation-results-to-your-crm.md)
* [Notifications](/nationgraph/help-center/readme/notifications.md)


---

# 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://nationgraph.gitbook.io/nationgraph/help-center/readme/automations-overview/foia-automations.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.