> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-5.md).

# Checklists tables

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/viewpoint-5.md).
{% endhint %}

## Description

Checklist templates, libraries and folders with their permissions and tags, the checklist log, and the checklists filled in on tasks.

## Tables

| Name                                                                                                                                             | Columns | Comment                                                                                                                                                                                           | Type       |
| ------------------------------------------------------------------------------------------------------------------------------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| [tPri\_CL](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl.md)                                                                  | 18      | A checklist (UI: checklist), with its order, priority, visibility and lock flags; its items are in tPri\_CL\_Item. Every library entry and site or multi-site template points at one checklist.   | BASE TABLE |
| [tPri\_CL\_Item](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_item.md)                                                       | 39      | One line of a checklist: an item to tick or answer, or a section heading, with its answer options such as yes or no, star rating, radio or NFC. A task gets its own copy in tPri\_JobTodo.        | BASE TABLE |
| [tPri\_CL\_ItemMedia](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_itemmedia.md)                                             | 13      | A photo or video on a checklist item (tPri\_CL\_Item); tasks use tPri\_JobTodoMedia. Empty on staging, though php-apis still saves it and sends it in the app sync.                               | BASE TABLE |
| [tPri\_CL\_Item\_Notes](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_item_notes.md)                                          | 12      | A note line on a checklist item (tPri\_CL\_Item); a task's copy is in tPri\_JobTodo\_Notes.                                                                                                       | BASE TABLE |
| [tPri\_CL\_Library](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_library.md)                                                 | 24      | One checklist in the Snapfix checklist library, with its description, note and version; it points at its checklist in tPri\_CL.                                                                   | BASE TABLE |
| [tPri\_CL\_LibraryAttachTag](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_libraryattachtag.md)                               | 14      | Attaches a checklist tag (tPri\_CL\_Tag) to a library checklist (tPri\_CL\_Library); the library's tag filter matches through it.                                                                 | BASE TABLE |
| [tPri\_CL\_LibraryPermissions](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_librarypermissions.md)                           | 14      | Links a library checklist to a row of tPri\_CL\_Permissions. Empty on staging, though the Laravel API's checklist code still uses it.                                                             | BASE TABLE |
| [tPri\_CL\_LibraryVirtualFolders](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_libraryvirtualfolders.md)                     | 15      | A folder of the checklist library; library checklists list their folders in uuid\_tCL\_LibraryVirtualFolder\_CSV. Empty on staging, though the Laravel API's checklist folder code still uses it. | BASE TABLE |
| [tPri\_CL\_MultiSiteTemplate](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_multisitetemplate.md)                             | 27      | A checklist template of a multi-site, pointing at its checklist in tPri\_CL and at the library entry it came from, if any; it is shared through tPri\_CL\_MultiSiteTemplatePermissions.           | BASE TABLE |
| [tPri\_CL\_MultiSiteTemplatePermissions](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_multisitetemplatepermissions.md)       | 14      | Shares one multi-site checklist template with one target in tPri\_CL\_Permissions.                                                                                                                | BASE TABLE |
| [tPri\_CL\_MultiSiteTemplateVirtualFolders](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_multisitetemplatevirtualfolders.md) | 16      | A folder of one multi-site's checklist templates.                                                                                                                                                 | BASE TABLE |
| [tPri\_CL\_Permissions](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_permissions.md)                                         | 17      | One target a checklist template is shared with: a multi-site, a site or a group, as the uuid columns say. New rows default to hidden (fVisible 0).                                                | BASE TABLE |
| [tPri\_CL\_SiteTemplate](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_sitetemplate.md)                                       | 28      | A checklist template of one site, pointing at its checklist in tPri\_CL and at the library entry or multi-site template it came from, if any; no staging row has either link.                     | BASE TABLE |
| [tPri\_CL\_SiteTemplatePermissions](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_sitetemplatepermissions.md)                 | 14      | Shares one site checklist template with one target in tPri\_CL\_Permissions.                                                                                                                      | BASE TABLE |
| [tPri\_CL\_SiteTemplateVirtualFolders](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_sitetemplatevirtualfolders.md)           | 16      | A folder of one site's (uuid\_tParent) checklist templates.                                                                                                                                       | BASE TABLE |
| [tPri\_CL\_Tag](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_tag.md)                                                         | 13      | A checklist tag in a checklist tag folder (tPri\_CL\_TagHeader); library checklists get it through tPri\_CL\_LibraryAttachTag.                                                                    | BASE TABLE |
| [tPri\_CL\_TagHeader](https://docs.snapfix.com/engineering-reference/db/tables/tpri_cl_tagheader.md)                                             | 12      | A folder of checklist tags (tPri\_CL\_Tag); the newest row is from 2025-09.                                                                                                                       | BASE TABLE |
| [tPri\_ChecklistLog](https://docs.snapfix.com/engineering-reference/db/tables/tpri_checklistlog.md)                                              | 16      | One activity line for a checklist template of a site or a multi-site, with its text and the request JSON.                                                                                         | BASE TABLE |
| [tPri\_JobTodo](https://docs.snapfix.com/engineering-reference/db/tables/tpri_jobtodo.md)                                                        | 45      | One checklist item on a task, the task's own copy of a checklist item (tPri\_CL\_Item), with its answer settings, done state and answer.                                                          | BASE TABLE |
| [tPri\_JobTodoMedia](https://docs.snapfix.com/engineering-reference/db/tables/tpri_jobtodomedia.md)                                              | 17      | A photo or video on a task's checklist item (tPri\_JobTodo).                                                                                                                                      | BASE TABLE |
| [tPri\_JobTodo\_Notes](https://docs.snapfix.com/engineering-reference/db/tables/tpri_jobtodo_notes.md)                                           | 14      | A note line on a task's checklist item (tPri\_JobTodo).                                                                                                                                           | BASE TABLE |
| [tPri\_Job\_CL\_Template](https://docs.snapfix.com/engineering-reference/db/tables/tpri_job_cl_template.md)                                      | 13      | Links a task to the site or multi-site checklist template its checklist came from.                                                                                                                | BASE TABLE |
| [tPri\_MultiSiteChecklistTemplate](https://docs.snapfix.com/engineering-reference/db/tables/tpri_multisitechecklisttemplate.md)                  | 10      | Unused; empty, and no in-scope code names it \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                            | BASE TABLE |

## Relations

```mermaid
erDiagram

"tPri_JobTodoMedia" }o--o| "tPri_JobTodo" : "FOREIGN KEY (uuid_tJobTodo) REFERENCES tPri_JobTodo (uuid)"

"tPri_CL" {
}
"tPri_CL_Item" {
}
"tPri_CL_ItemMedia" {
}
"tPri_CL_Item_Notes" {
}
"tPri_CL_Library" {
}
"tPri_CL_LibraryAttachTag" {
}
"tPri_CL_LibraryPermissions" {
}
"tPri_CL_LibraryVirtualFolders" {
}
"tPri_CL_MultiSiteTemplate" {
}
"tPri_CL_MultiSiteTemplatePermissions" {
}
"tPri_CL_MultiSiteTemplateVirtualFolders" {
}
"tPri_CL_Permissions" {
}
"tPri_CL_SiteTemplate" {
}
"tPri_CL_SiteTemplatePermissions" {
}
"tPri_CL_SiteTemplateVirtualFolders" {
}
"tPri_CL_Tag" {
}
"tPri_CL_TagHeader" {
}
"tPri_ChecklistLog" {
}
"tPri_JobTodo" {
  varchar_255_ uuid
}
"tPri_JobTodoMedia" {
  varchar_255_ uuid_tJobTodo
}
"tPri_JobTodo_Notes" {
}
"tPri_Job_CL_Template" {
}
"tPri_MultiSiteChecklistTemplate" {
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# 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.snapfix.com/engineering-reference/db/tables/viewpoint-5.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.
