> 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/create-requirement.md).

# Create Requirement

Create new requirements and optionally link them to tests.

Use the **Create Requirement** form to define and configure a new requirement.

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

{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}

***

## Completing the Form

Follow the steps below to complete the form.

{% stepper %}
{% step %}

### Define Core Attributes

Provide the core details needed to define the requirement.

* **Requirement Name:\*** Enter a brief, descriptive title for the requirement.
* **Requirement Type:\*** Select the category that best reflects the requirement’s purpose or scope (e.g., Audit, Inspection)
* [**Linked Test(s):**](#user-content-fn-1)[^1] Select one or more tests that validate or support the requirement.
* **Description:** Provide a detailed description of the requirement, including its purpose, scope, and any relevant context.

<p align="center">━━━━━━━━━━━━━━━━━━━━━━━━━━━</p>

**Read-Only Fields** (🔒)

* **Requirement ID:** A system-generated, unique identifier used for tracking and reference.

***

{% endstep %}

{% step %}

### Define Checklist (Optional)

Create a checklist to specify how the requirement will be evaluated and validated.

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

Click **Add** to create a new checklist item.

<details>

<summary><mark style="color:blue;"><strong>Define New Requirement Check Item</strong></mark></summary>

The **Define New Requirement Check Item** form allows you to create individual checklist items.

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

1. **Define Details**

Complete the relevant fields to configure the item:

* **Checklist No.:\*** Enter the position of the item within the checklist.

{% hint style="info" %}
This field defaults to the system-assigned order based on when the item is added; modify it to change the sequence.
{% endhint %}

* **Question:\*** Enter the question or statement to be presented in the checklist.
* **Answer Type:\*** Select the response format (e.g., True / False, Multiple Choice, Text Value).

{% hint style="warning" %}
If **Multiple Choice** is selected, additional fields will appear to define the answer options.
{% endhint %}

* **Will This Check Be Evaluated?:** Indicate whether the item will be validated.
  * If <mark style="color:blue;">**Yes**</mark>, provide the correct answer based on the selected answer format.

***

2. **Save Changes**

When ready to save, choose one of the following options:

* **Save and New:** Click to save the item and open a new form to add another.
* **Save and Close:** Click to save the item and close the form.

</details>

Added entries appear in the grid with the following options:

* **Edit** ( <i class="fa-pen">:pen:</i> ): Click to modify an item.
* **Delete** ( <i class="fa-trash-can">:trash-can:</i> ): Click to remove an item.

{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undo** ( <i class="fa-rotate-left">:rotate-left:</i> ).
{% endhint %}

***

{% endstep %}

{% step %}

### Submit Requirement

Click **Submit** to finalize and create the requirement, making it available for use in the system.

***

{% 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>Import &#x26; Sync Requirements with EPC Repository</strong></td><td>Import requirements from the repository and synchronize them with source updates.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F2i3jq5QEcqQ6QnibX7kq%2FIMS-V16-NAV-Library-Icons-122.png?alt=media&amp;token=280e6366-561f-4b86-9804-191223e45d1a">IMS-V16-NAV-Library-Icons-122.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/import-and-sync-requirements-with-epc-repository.md">Import &amp; Sync Requirements with EPC Repository</a></td></tr><tr><td><strong>Import Requirements from Excel</strong></td><td>Import and update requirements, tests, and evidence in bulk using an Excel file.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F8EURtbR8olEYsY7knlFB%2FIMS-V16-NAV-Library-Icons-106.png?alt=media&amp;token=7664c54c-4826-48e4-8ca0-d042582c2f2d">IMS-V16-NAV-Library-Icons-106.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/managing-requirements/import-requirements-from-excel.md">Import Requirements from Excel</a></td></tr><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>

[^1]: 💡 **For Administrators:**

    * The list of tests is sourced from the [**All Tests**](/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/all-tests.md) module, under **Testing Management**.


---

# 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/create-requirement.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.