> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/documents/documents-overview-paperwork-that-gets-signed.md).
# Documents Overview: Paperwork That Gets Signed
Some jobs need more than an estimate and an invoice — a service agreement, a contract, a liability waiver, a job-completion sign-off. Documents is where you send that paperwork to the customer, collect a legally-binding e-signature, and keep everything on file. This guide explains what documents are, how they're different from your notes and invoices, and where to find them on web and mobile.
### What a Document Is
A document is a file you send the customer to **read and sign** — built from your own PDF or a saved template. You choose whether it needs a signature, send it by text or email, and the customer signs from a secure link on their phone or computer.
Documents sit alongside two things people sometimes confuse them with:
* **Notes & photos** live on the job and are **internal** — the customer never sees them.
* **Estimates & invoices** are about **money** — options and the bill.
* **Documents** are the **paperwork the customer signs** — agreements, contracts, completion forms.
> 💡 **Key idea:** If it needs the customer's signature and isn't a bill, it's a Document.
### Where Documents Live
**On the web**, you'll find documents in three places:
* The **Documents** page — your full list, split into **Active**, **Drafts**, and **Deleted**.
* On any **job** — the Documents card, for paperwork tied to that work.
* On any **contact** — the Documents tab, for everything that customer has ever signed.
The web is also where you can **upload other files** to a job — permits, spec sheets, Word or Excel docs — even when they don't need a signature.
**On mobile**, techs work from the job's **Docs** tab. Tap **New document** to build and send one for signature right from the field — no laptop needed.
`[insert screenshot: split image — the web Documents page (Active/Drafts/Deleted) on the left, the mobile job "Docs" tab on the right.]`` ``*still needs mobile`
### The Document Lifecycle
Every document moves through the same simple path, and you can see exactly where it stands at any time:
**Draft → Sent → Viewed → Signed**
* **Draft** — built but not sent yet. Only your team can see it.
* **Sent** — delivered to the customer by text or email.
* **Viewed** — the customer opened it.
* **Signed** — done. The signed copy is saved and stamped with who signed and when.
*(You may also see **Expired** or **Cancelled** for documents that were never completed.)*
### What's in This Section
* **Send a Document for Signature** — build from a template or PDF and get it signed.
* **Create & Reuse Templates** — set up your standard agreements once.
* **Upload & Attach Files to a Job** — store permits, spec sheets, and other files.
* **Track Status & Signatures** — see what's signed, resend, and share links.
* **Manage Documents: Edit, Download, Delete & Restore** — keep your list tidy.
> 💡 **Tip — Set up templates first.** If you send the same agreement on most jobs, save it as a template once. After that, sending it is a few taps instead of a rebuild every time.
### FAQ
* **How is a document different from a note?** Notes are internal; documents are sent to the customer to sign.
* **Do all documents need a signature?** No — you can send one as read-only, or require a signature.
* **Can I send a document from my phone?** Yes — from the job's **Docs** tab.
* **Where do signed documents go?** They stay on the job and the contact, and on the Documents page, with the signed copy saved.
* **Can I attach a file that isn't for signing?** Yes — upload it to the job on the web.
---
# 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.bluepro.ai/documents/documents-overview-paperwork-that-gets-signed.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.