> 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/send-a-document-for-signature.md).

# Send a Document for Signature

This is the core of Documents: take a template or a PDF, tell BluePro who it's for, and send it out for the customer to sign. The whole thing takes a minute or two, and you can do it from the office or the field.

`[insert video: 60–90s — build a document from a template, set the contact, preview, and send by email + text. Web capture, with a quick cut to the mobile flow at the end.]`

### Start From a Template or a PDF

You've got two ways to begin:

* **Use a template** — pick one your team already set up. Fastest option; everything's ready to go.
* **Upload a PDF** — drop in your own file to send a one-off document.

**On the web:** open the **Documents** page and click **New Document**, then drag a PDF onto the upload area (or start from **Templates**).\
**On mobile:** from the job's **Docs** tab, tap **New document**, then choose **Use a template** or **Upload PDF**.

### Set It Up

Fill in a few details so the document knows who it's for and how to behave:

* **Contact** — who's signing (required).
* **Job** — tie it to the work, if it belongs to one.
* **Title** — what the customer sees it called.
* **Type** — Service Agreement, Contract, Job Completion, or Custom.
* **Require signature** — leave on if they need to sign; turn off to send read-only.

<figure><img src="/files/S2yMSW35RoqfEuheiFif" alt=""><figcaption></figcaption></figure>

### Add Signature Fields *(web)*

If your document needs the customer to sign or initial in a specific spot, drag those fields onto the page in the builder. You can also add **merge fields** that auto-fill customer and job info — name, address, date — so you're not retyping details that BluePro already knows.

> 💡 **Tip — Set fields once, reuse forever.** Place your fields, then save the document as a template. Every future send already has the signature line in the right place.

### Preview & Send

Before it goes out, check it:

* **On the web:** click **Preview as recipient** to see exactly what the customer will get.
* **On mobile:** tap **Preview document**.

Then send it. Choose **Text**, **Email**, or both, and the customer gets a secure link to open and sign. You'll see a confirmation once it's on its way.

### Approving on the Spot

If the customer is standing right there and doesn't need a signature link, some documents can be handled in person — the same way estimates can be approved in person. For paperwork that requires a real signature, send the link so it's captured and verified.

### FAQ

* **Template or PDF — which should I use?** Template for anything you send often; PDF for a one-off.
* **Does every document need a signature?** No — turn off **Require signature** to send it read-only.
* **Can the customer sign on their phone?** Yes — the link works on any phone or computer.
* **What file types can I send?** Documents are built from PDFs.
* **Can I send from the field?** Yes — the full flow works on mobile from the job's **Docs** tab.


---

# 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/send-a-document-for-signature.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.