> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/import-requirements-from-excel.md).

# Import Requirements from Excel

Import requirements, tests, and evidence using an Excel file.

Use the **Import Requirements from Excel** module to:

* Upload requirements, tests, and evidence in bulk from an Excel file, with relationships automatically established between them.
* Update existing requirements, tests, and evidence, whether previously imported or manually created
  * All fields can be updated except for the item name.

{% hint style="info" %}
This streamlined approach eliminates the need to configure items individually in the [**Requirement Management**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements.md) and [**Testing Management**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing.md) modules, providing a faster and more efficient workflow.
{% endhint %}

***

## Importing Requirements, Tests, and Evidence

Follow the steps below to prepare and import your data.

{% stepper %}
{% step %}

### Download Template

Select and download the appropriate Excel template.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* **1 Sheet Template:** A single worksheet containing all required columns for requirements, tests, and evidence.
* **3 Sheet Template:** Three separate worksheets (for requirements, tests, and evidence), each with its own set of columns.

{% hint style="success" icon="lightbulb" %}
**Tip:** For a quick and simple approach, use the **1 Sheet Template**. For a comparably cleaner and more organized approach, use the **3 Sheet Template**.
{% endhint %}

To download a template, select your preferred option and save the file locally.

{% hint style="success" %}
For guidelines and considerations on completing the template, see **Data Import – Guidelines and Considerations**.
{% endhint %}

***

{% endstep %}

{% step %}

### Import File

Upload the completed Excel file and initiate the import process.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* **Attach the Excel File:** Upload the Excel file containing the reqWheuired information.
* **Import Excel File:** Click to import the data into the appropriate modules.

{% hint style="info" %}

#### Where to Find Imported Data

* Imported **requirements** appear in the [**Manage Requirements**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/manage-requirements.md) module.
  * If linked to a test, they also appear in the corresponding test record.
* Imported **tests** appear in the [**All Tests**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/all-tests.md) module.
  * If linked to a requirement, they also appear in the corresponding requirement record.
* Imported **evidence** appears in the [**Test Evidence Management**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/test-evidence-management.md) module.
  * If linked to a test, it also appears in the corresponding test record.
    {% endhint %}

After the import is complete, the **Output** field displays a summary of the results, including:

* The number of requirements, tests, and/or evidence records added
* Any errors encountered during the import process

***

{% endstep %}

{% step %}

### Review Imported Data

Verify that all records and relationships were imported correctly.

* **For the 1 Sheet Template:**

  Imported items appear in the **Imported Data** grid within this module for quick review.
* **For the 3 Sheet Template:**

  Imported items do not appear in this grid. Instead, navigate to the relevant modules ([**Manage Requirements**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/manage-requirements.md), [**All Tests**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/all-tests.md), or [**Test Evidence Management**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/test-evidence-management.md)) to review the records.

If needed, open individual records to confirm that all fields and relationships have been correctly applied.

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Manage Requirements</strong></td><td>Browse, filter, and maintain all existing requirements.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FNZOvD3ldHJ3i1zsvDksS%2FCR-V16-Icons-1.png?alt=media&amp;token=7c420cc4-9abf-4601-8fc3-8e9769771b27">App-V16-Icons-1.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/manage-requirements.md">Manage Requirements</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/import-requirements-from-excel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.