> For the complete documentation index, see [llms.txt](https://ensis-ai.gitbook.io/ensis-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ensis-ai.gitbook.io/ensis-documentation/product-guides/proposal-management/proposal-setup/requirements-extraction.md).

# Requirements Extraction

## Select Your Requirement Page Ranges

Select the page ranges where your key requirements reside within each opportunity file.

<figure><img src="/files/6jQLC0ZAvIROOBhuXaFM" alt=""><figcaption></figcaption></figure>

**If there are no requirements in a file**, you may select "No requirements in this document". Ensis will scan the document and leverage its contents for proposal content generation, but it will not use it to build your key requirements list.&#x20;

Or, **you may ask Ensis to scan the entire document for key requirements** by selecting "All pages".

{% hint style="info" %}

#### **What Ensis Extracts for Each Requirement**

1. **Requirement Content**
   * A requirement in Ensis is defined as either:
     * A **deliverable**—the service or product the contractor must provide to fulfill the contract
     * A **guideline or instruction**—rules for the proposal and response process
2. **Requirement Identifier (If Available)**
   * If the original solicitation includes section identifiers, Ensis retains them with each requirement to help you organize your proposal.
   * For example, if a requirement comes from **Section 4.2.1** of the opportunity, Ensis stores that identifier so you can easily reference its source and structure your response accordingly.

This ensures that extracted requirements are both meaningful and traceable, making it easier to align your proposal with the solicitation's expectations.
{% endhint %}