> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assuric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Procedures and records

> How a procedure is a document behind a policy task, where controlled documents fit, and the records that prove you follow your procedures.

<Note>
  **Quick summary**

  * A procedure is the real document behind a policy task, and a record is the proof you followed it.
  * Approving a procedure's document updates the task's status.
  * You send an approved procedure to staff yourself, by adding it to a checklist or the staff portal.
</Note>

## Procedures are documents

A procedure task is a policy task: a *Document* task in the *Policies* group, like *Quality Manual & Policy maintained*. It names the document that answers it, a standard operating procedure (SOP) when the requirement is for a written procedure.

<Frame>
  <img src="https://mintcdn.com/assuric-docs/_QF9-JQr52Or9WhB/images/quality/procedures-filtered.png?fit=max&auto=format&n=_QF9-JQr52Or9WhB&q=85&s=c9caf2e849a7855365057201dea9704d" alt="The ISO 9001 Tasks tab filtered to &#x22;SOP&#x22;, showing the Policies group narrowed to Document-type tasks" width="3200" height="2000" data-path="images/quality/procedures-filtered.png" />
</Frame>

*Filtering a task list to "SOP" (1) narrows it to policy tasks, one written procedure each (2).*

That document is [versioned](/documents/versions-and-version-history) and approved like any other, so approving it updates the task's status.

## Controlled documents

Tick **Controlled** on the procedures your quality management system (QMS) is built on. They get a Document ID and a formal review and approval cycle, and are locked while the cycle runs and once approved.

## Give staff the procedures to read

Staff only get procedures you send. Once it's approved, add the document to either of these:

* **A checklist:** Add it as a [*Resources* item](/people/checklists#resources-items-signing-off-a-policy). Staff open the document and click **I have read and understood the above resources**, and each person's **History** keeps the version and date they confirmed, which you show an auditor.
* **The staff portal:** Add it to the **Resources** tab of your [staff portal](/people/staff-portal), assigned to the groups who need it.

When you approve a new version, [Republish options](/documents/versions-and-version-history#republish-options) lets you move each checklist item and staff portal resource using the document to the new version.

## Records

Record tasks ask for dated proof, not a document. Each has an owner from People, and most sit in the *Organisation* group, shared between ISO 9001 and ISO 13485.

<Frame>
  <img src="https://mintcdn.com/assuric-docs/_QF9-JQr52Or9WhB/images/quality/records-filtered.png?fit=max&auto=format&n=_QF9-JQr52Or9WhB&q=85&s=09d0867f2bf8947e4422ebb207ddccdb" alt="The ISO 9001 Tasks tab filtered to &#x22;record&#x22;, showing the Organisation group with a Record-type task highlighted" width="3200" height="1935" data-path="images/quality/records-filtered.png" />
</Frame>

*Filtering to "record" (1) surfaces the operational records, like CAPA records maintained (2), rather than the policies behind them.*

## Related articles

<Columns cols={2}>
  <Card title="Controlled documents" icon="file-check" href="/quality/controlled-documents">
    The review and approval cycle for your procedures.
  </Card>

  <Card title="Checklists: Overview" icon="circle-check" href="/people/checklists">
    Have staff read and sign off a procedure, and keep the proof.
  </Card>

  <Card title="Audit and review records" icon="notebook-pen" href="/quality/audit-and-review-records">
    Where your procedures and records get examined.
  </Card>

  <Card title="Quality FAQ" icon="circle-question-mark" href="/quality/faqs">
    Quick answers to the things customers ask us most.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.