> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/features/assessments.md).
# Assessments
Write questionnaires, ask people or teams to answer them about a record, and run campaigns across many records.
Assessments let you ask structured questions and see who still owes an answer. You write a questionnaire once, then ask a person or a team to answer it about a record, or send it to the owners of many records in a campaign. Answers are stored with the record in your ServiceNow instance, so other features such as reviews and scores can use them.
## What it is
A full-page view called **Assessments**, with the subtitle **Questionnaires and who still owes an answer**. It has three tabs: **Overview**, **Questionnaires** and **Campaigns**.
The Assessments Overview
There are two kinds of questionnaire:
| Kind | Asked about | Typical use |
| -------------- | -------------------------------- | ----------------------------------------- |
| **Assessment** | A record, such as an application | Maturity, architecture review, risk check |
| **Survey** | A person | Satisfaction, readiness, pulse checks |
The **Overview** cards each switch the list below them:
| Card | Shows |
| ----------------------- | --------------------------------------------------------------------------------------------------- |
| **In use** | Published questionnaires, how often they were asked and answered, with **Ask someone** on each row. |
| **Asked of me** | What you, or a team you belong to, still have to answer. |
| **Late** | Requests past their due date and who they are waiting on. |
| **Still being written** | Questionnaires not ready to send. |
| **Who is using it** | Teams and programmes using questionnaires. |
| **Campaigns** | Rounds in flight. |
## When to use it
* You need the same questions answered consistently about many records.
* A review gate in [Architecture Governance](/command/features/architecture-governance.md) expects an assessment as evidence.
* You want to know who has not answered yet, and what is late.
## How to
### Open the view
1. Click **Assessments** in the activity rail.
### Write a questionnaire
1. Open **Questionnaires** and create a new questionnaire.
2. Enter a **Name**, choose the **Kind** (assessment about a record, or survey asked of a person) and, for an assessment, which records it is about.
3. Add sections and questions. Answer types include **Scale**, **Number**, **Single choice**, **Multiple choice**, **Yes / No**, **Short text**, **Long text**, **Date**, **Record reference** and **Attestation**.
4. Click **Check**, then **Publish**. To change a published questionnaire later, create a **New revision**.
### Ask someone about a record
1. On **Overview**, open **In use** and click **Ask someone** on the questionnaire.
2. Under **About**, search for the record.
3. Under **Who**, choose **A person** or **A team** and search for them.
4. Set a **Due** date, then click **Ask**.
The request lands in the person's, or the team's, **My Tasks**. For a team, everyone in it is told and anyone in it can answer.
{% hint style="info" %}
Without a due date a request can never show as late.
{% endhint %}
### Run a campaign
1. Open **Campaigns** and create a campaign.
2. Enter a **Name** and choose a published **Questionnaire**.
3. Under **Which records to include**, set a filter, or leave it empty for all records.
4. Under **Who should answer**, choose the field that names each record's owner.
5. Check the preview: **Records**, **People**, **Teams** and **Missing an owner**.
6. Click **Create campaign**, then **Start**, then **Send**. Click **Finish** when the round is over.
The campaign form and its preview
### Answer an assessment
1. Open it from **Asked of me** with **Open**, from the task in **My Tasks**, or from **Open the assessment** in a review.
2. Answer the questions. Required ones are marked with an asterisk. Use **Add a comment** to explain an answer.
3. Click **Save** to continue later, or **Submit** when you are done.
## Good to know
* Requests notify people in Command. They do not send email.
* An anonymous survey does not create a task, and your name is not stored with the answers once you submit.
* A campaign reports records that have no owner instead of skipping them silently.
* Administrators choose which questionnaire Command asks for in which situation in **Global Settings > Assessments**.
{% hint style="warning" %}
You may occasionally receive the same request notification twice. This is a known issue and does not create a second request.
{% endhint %}
## Related
* [Tasks, Notifications and Approvals](/command/the-portal/tasks-and-notifications.md)
* [Architecture Governance](/command/features/architecture-governance.md)
* [Ideation Portal](/command/features/ideation-portal.md)
* [Personas](/command/the-portal/personas.md)
---
# 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.ins-pi.com/command/features/assessments.md?ask=&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.
