> 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/user-guide/definitions/record.md).

# Record

### Definition

A Record in Unifize is a structured entity that acts as the central hub for all information, actions, and conversations related to a specific process instance. It ensures visibility, traceability, and accountability across teams by capturing data, discussions, approvals, and status updates in a single location.

Records are used to standardize workflows, maintain compliance, and drive collaboration by embedding real-time conversations directly within the process.

{% hint style="info" %}
Check out [Developer Documentation for Records](broken://spaces/cZhAoxKwpBioghRXCQLi/pages/lWZ2yThffyLFHwprqMVa)
{% endhint %}

### Key Features

* **Single Source of Truth** – Combines structured data, checklists, and conversations in one place.
* **Real-time Collaboration** – Enables team discussions through an embedded Conversation Thread.
* **Traceability & Auditability** – Captures all changes, actions, and approvals chronologically.
* **Customizable Checklist Structure** – Supports file uploads, linked fields, attachments, and metadata fields.
* **Automated Updates** – Notifies stakeholders of status changes and task completions.

### What constitutes a Record?

Every **Record** in Unifize consists of the following key elements:

1. **Header**
   1. **Title & Unique ID** – Provides a clear identifier for the record.
   2. **Status** – Displays the current progress (e.g., Open, In Progress, Completed).
   3. **Owner & Participants** – Identifies who is responsible and who can collaborate.
   4. **Due Date & Priority** – Helps define the urgency and deadlines for a record.
   5. **Record Options** – Options to share a record, and access Process Builder for making changes to the underlying process.
2. **Conversation**
   1. Real-time chat-based collaboration embedded within the record.
   2. Allows @mentions, file sharing, and decision logging for context.
   3. Uploads and links files directly within the record for reference.
   4. Tracks every change, comment, and status update in chronological order.
   5. Ensures compliance by maintaining an immutable history of actions.
3. **Checklist**
   1. A structured list of required actions and approvals within the process.
   2. Supports sections, linked fields, and automation for better organization.
   3. Supports connections to other related records or processes (Parent/Child Records).
   4. Enables cross-functional visibility and dependency tracking.
   5. Supports version control to track document history.

<figure><img src="/files/GvdTAKOusOR2QPEy6B3Y" alt=""><figcaption><p>A Sample Record, with Header, Conversations and Checklist</p></figcaption></figure>

Records in Unifize serve as the foundation of process execution and collaboration, enabling teams to centralize data, track actions, and maintain full traceability in one unified workspace. By embedding real-time conversations, structured checklists, and automated updates, records eliminate the silos that traditionally slow down workflows.

With their customizable structure, and audit-ready history, records empower teams to enhance collaboration, improve compliance, and drive operational efficiency across all business processes.


---

# 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/user-guide/definitions/record.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.