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

# Signing packages: what they are and how they work

> Discover how signing packages bundle documents and signers together, move through a defined lifecycle, and capture a legally defensible e-signature record.

A **signing package** (also called a *signing*) is a collection of documents sent to one or more signers at a specific location. It is the central unit of work in Safeclose — the thing your organization creates, tracks, and retains as a compliance artifact after everyone has signed.

Managers create signing packages, assign documents and signers, and monitor progress. Signers receive access to their assigned package and complete their documents through the Safeclose signing interface.

## Key entities

Three objects make up every signing package:

| Entity        | What it represents                                                                                                                                    |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Signing**   | The package itself — ties together a location, an optional flow, a status, and an optional note.                                                      |
| **Documents** | The individual items that signers must review and sign. Each document in a signing comes from the document library and is classified by chattel type. |
| **Signers**   | The people assigned to complete the package. Each signer is linked to specific documents within the signing.                                          |

## Lifecycle

Every signing package moves through the following states:

```
draft → active → complete
                ↘ cancelled
```

| Status        | Meaning                                                                                           |
| ------------- | ------------------------------------------------------------------------------------------------- |
| **Draft**     | The package has been created but not yet sent. The manager can still make changes.                |
| **Active**    | The package has been sent. Signers can now access and complete their documents.                   |
| **Complete**  | All required documents have been signed. The package is closed and the audit record is finalized. |
| **Cancelled** | The manager cancelled the package before completion. Signers can no longer act on it.             |

<Note>
  Once a signing package moves from **Draft** to **Active**, documents and signers cannot be changed. If you need to modify the package, cancel it and create a new one.
</Note>

## Flows and templates

Managers use two types of reusable building blocks to streamline package creation:

<AccordionGroup>
  <Accordion title="Flows">
    A **flow** defines the structure and sequence of a signing session — which steps signers go through, in what order, and what they must complete at each step. Think of a flow as a template for the overall signing experience. Flows are scoped to a location and can be reused across many signing packages.
  </Accordion>

  <Accordion title="Templates">
    A **template** is a reusable document that can be included in signing packages without re-uploading the source material each time. Templates are also scoped to a location. Managers with the appropriate access level can create, edit, duplicate, and deactivate templates.
  </Accordion>
</AccordionGroup>

<Tip>
  If your organization runs the same type of signing regularly — such as onboarding paperwork for new customers — create a flow and a set of templates once and reuse them. This reduces setup time and keeps the signer experience consistent.
</Tip>

## How signers complete a package

When a signing package is active, signers access it through the **Signing Packages** section of their Safeclose account (`/signing/packages`). They see only packages assigned to them.

For each document in their package, signers:

1. Review the document content.
2. Click the **Sign** button to record their signature.
3. Repeat for each assigned document until the package is complete.

### What e-signing records

When a signer clicks **Sign**, Safeclose records:

* The **timestamp** of the signature event.
* The signer's **IP address** at the time of signing.
* The document's **signed status**, marking it complete.

This information is retained as part of the audit trail for the signing package and cannot be altered after the fact.

<Warning>
  E-signatures recorded in Safeclose are intended for compliance purposes. Confirm with your legal counsel that electronic signatures meet your specific regulatory requirements before relying on them for a given document type.
</Warning>

## Monitoring and reporting

Managers can view the status of all signing packages within their scope from the signing hub. Depending on their access level, they can also cancel active packages, resend notifications to signers, and export signing lists for reporting.

<CardGroup cols={1}>
  <Card title="Signing workflow guide" icon="pen-line" href="/guides/signing-workflow">
    A step-by-step walkthrough of creating a signing package, assigning signers, and tracking completion.
  </Card>
</CardGroup>