> 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/using-specifications.md).

# Using Specifications

Every Bank will contain at least ONE Specification. Specifications provide the rules that determine which questions will be contained on an exam Form.

Every Bank will contain at least ONE Specification. Specifications provide the rules that determine which questions will be contained on an exam Form. The same Specification may be used for multiple Forms, or there may be a different specification for each Form.

![specification.png](https://e02.insite.com/files/sites/global/using-specifications/specification.png)

![specification-2.png](https://e02.insite.com/files/sites/global/9844/specification-2.png)

**Important Note when using Filter Type in Specifications:** The **Set Weight** stores the value entered by an administrator in **GAC %** column on **Workshop** page and helps calculate the values for the **Pivot Table Filter**, and then the **Pivot Table Filter** will determine the set number of questions on the form. In other words, the **Set Weight** only makes sense when the **Filter Type** in the Specification is set to **Filter with Pivot Table**.

The **Set Weight** is not used in question filtering, even when **Filter Type** is **Filter with Pivot Table**. The **Pivot Table Filter** only applies to the questions filter while the **Set Weight** is only used to store the value that was used to calculate the **Pivot Table Filter** values.

The value in the **Question Limit** only affects the set of form questions when the **Filter Type** is set to **Include All Questions**. **Set Weight** is not applicable and has no effect on the creation, delivery, or marking of the form if the **Filter Type** is set to **Include All Questions**.


---

# 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/using-specifications.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.