Signatures

Signatures sends documents out for e-signature: upload a document, place the fields each signer must complete, send it, and track who has signed. Signers complete it from the client portal, a shared link, or an emailed signing link. They don't need a Bitment account to sign.

Your team uses it for engagement letters, authorizations, and anything else that needs a real signature and a record of who provided it and when.

Where to find it

Open Signatures from the dock, or Data › Signatures from inside a client. A signature request isn't required to start scoped to one client. You attach signers as you build it, and they can span several clients or types of recipient.

Key concepts

client contact, a colleague, a referral partner, or someone added ad hoc by name and email.

assigned to a signer.

requests, without re-placing every field each time.

open and sign the document.

Send a document for signature

  1. Open Signatures and start a new request, either by uploading a PDF or starting

from a template. There's no mandatory client picker; you can scope it to a client later or leave it unscoped.

  1. Add the signers using the recipient picker: search across your firm's people

(colleagues, client contacts, and client-as-a-whole groups), or use Add by name / email… for someone not yet on the roster.

  1. Place the fields on the document, dragging them where they belong on the page and

sizing them. On a phone you drag with your finger, and nudge/resize steppers give you precision. Fields can be placed before you've assigned a signer; they show as (unassigned) until you do.

  1. If you operate more than one firm, choose which firm an unrecognized signer

should be filed under.

  1. Publish (send). Publishing is blocked while any field is unassigned, or if

there's no document attached yet. Drafts can be saved without either.

Each signer with an email gets their own signing link by email. An unrecognized signer's email is automatically provisioned as a client of your firm the first time you publish a request addressed to them, so they can also sign in to the portal later.

Track progress

The requests list shows each request's status and how far along its signers are. Filter by status, search, and switch between grid and list layouts. Click a request to open its detail and the document itself.

Templates

If you send the same document repeatedly, save its configuration as a template so the field placement and signer setup come back with it the next time. Templates live in their own library, separate from the requests you've actually sent.

Rename, rescind, delete

From a request's row menu or its editor you can:

link is notified their signature is no longer needed.

The AI can do all three on request, staged for your approval.

Signer experience

A signer reaches the document one of two ways:

their own Signatures.

Either way they see the document with the fields overlaid, fill in what's assigned to them, and submit. Once every assigned field is complete, the request status flips to completed and you get a copy of the flattened, signed PDF. A signing link expires after 14 days; a re-send mints a fresh one automatically.

Completed documents

A completed request has a canonical, server-generated signed PDF: the source document with every signed value burned in. It's downloadable from the request's detail view, the signing completion screen, and the client portal.

Audit trail

Every request tracks who has viewed it, who has signed which fields and when, and the exact document version that was signed. You (and everyone you've shared the request with) are notified the moment a signer signs, so you don't have to keep checking back.

The AI panel

Signatures has an embedded assistant panel on the left, opened with the robot toggle in the header. It's aware of what you're currently looking at and can list and read your signature requests and take the rename, rescind, and delete actions for you.

Tips

Useful when you want to hand someone a link outside of email.

signed if you need to stop it.