> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/release-notes/april-2025/rich-text-fields-in-checklist.md).
# Rich Text Fields in Checklist
We’ve introduced **rich text field** to the list of checklist fields in Unifize, giving you greater control over formatting, clarity, and communication within your records.
***
**What’s New:**
* Add **bold**, *italic*, and underline text
* Create **ordered and unordered lists**
* Insert clickable **links**
* Use **headings**, separators, and inline formatting for better readability
* Maintain **structure and formatting** across multi-line content
***
**Where it works:**
* Checklist fields of type ‘Rich Text’
***
**Why it matters:**
* Improve clarity and emphasis within checklists
* Fields that require detailed notes or instructions
* Add structured formatting to SOPs, deviations, and validations
* Reduce confusion and misinterpretation by making key points stand out
***
**Availability:**
Rich text is now available in the list of all checklist fields across all processes.
> 🔗 [Learn how to use rich text in checklist fields](/user-guide/data-and-process-management/rich-text-in-checklist.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 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://docs.unifize.com/release-notes/april-2025/rich-text-fields-in-checklist.md?ask=&goal=
```
`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.
