> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/assessments/specifications-forms/creating-a-form.md).

# Creating a Form

Each Specification can have one or more Forms. Forms are used to deliver the actual questions during the exam and control the availability of the exam.

**Each Specification can have one or more Forms. Forms are used to deliver the actual questions during the exam and control the availability of the exam.**

* Under the **Specification** tab select the **Specification** that you want to create the Form for.
* Click on the **Add** button and select **Form**
* Add a **Form Name** (This is the internal name used to uniquely identify this exam form for filing purposes)
* Add a **Code** (This is the form's catalog code. It defaults to N/A. Can be left as is unless a specific identifier is desired)
* Add a **Source** (Reference to the source of the content and/or configuration for this form. Can enter one if available.) - *Optional*
* Add **Origin** (Identifies the originating platform and/or record for this form. When this property is used, it should ideally contain a fully qualified URL or API path.) - *Optional*
* Add a **Time Limit** (This is the number of minutes allowed for each attempt on the exam. Enter time limit in minutes)
* Select the **Criteria** (Sets) you want included in the Form.
* Under **Like Item Groups**, select if you want the questions to be **Mutually Exclusive** or **Not Mutually Exclusive** to the Form you are creating.
* Click the **Next** button.
* All the questions that will be included in the form will be listed under **Preview Questions**.
* Click the **Save** button to create the Form.


---

# 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.shiftiq.com/help/assessments/specifications-forms/creating-a-form.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.