A four-step send
Details, signers, fields, review. Name the signing package, add the PDFs, then send. Save a draft when you are not ready.
Signatures
Get it signed.
Upload the PDF, pick who signs, place the fields, and send a secure link. Signers, reviewers, and CC'd go in order. You get the executed document and a Certificate of Completion.
The whole signing package
Build it, send it, watch it, and keep the proof.
Templates with role slots
Save the signing package once. Signer 1, Client, Reviewer. Next time you assign people to the slots and skip placing fields again.
Signer, reviewer, or CC'd
Signers adopt a signature and finish the fields. Reviewers approve. CC'd people see the document and get the completed copy.
They sign in order
Set the routing order. Later recipients wait until the people ahead of them finish. The link says when it is their turn.
Fields on the page
Place signature, initials, text, date, checkbox, and dropdown on the PDF. Prefill what you already know before you send.
A secure link to sign
Recipients open an email link. They agree to electronic records, type or draw a signature, click the boxes, and finish. No Base Assist account required.
The proof stays with it
Audit trail with who opened, consented, signed, declined, or voided it. SHA-256 hashes on the original and the final. Download the executed PDFs and a Certificate of Completion.
How it works
Build the signing package. Send the link. Close it with a certificate.
Build
Start blank or from a template.
Name the signing package. Drop in the PDFs, or pick a template that already has role slots and fields.
- 01Name the signing package.
- 02Upload the PDFs, or start from a template.
- 03Keep a draft if you need more time.
People
Pick who signs, reviews, or is copied.
Search people in the office, client contacts, or a group. Or type an email. Set the role and the order.
- 01Search users, contacts, or groups.
- 02Set Signer, Reviewer, or CC'd.
- 03Put them in signing order.
Fields
Put the boxes on the page.
Place signature, initials, text, date, checkbox, and dropdown on each PDF. Prefill what the sender already knows.
- 01Open the field palette.
- 02Drop fields onto the PDF pages.
- 03Prefill sender values before you send.
Close
Send the link. Keep the proof.
Recipients get a secure email. They consent, sign, and finish in order. You download the executed files and the certificate.
- 01Send for signature.
- 02Watch status and the audit trail.
- 03Download the executed PDFs and the certificate.
Recipients you already know
The Signatures app looks up people from the office and from the CRM app. Clients do not need a seat to sign.
Pricing
You pay per person who sends signing packages.
Team
1-9 users
$10/ user / month
The full Signatures app. Signing packages, templates, field placement, signing order, consent, audit trail, executed PDFs, and certificates.
Studio
10-24 users
$8/ user / month
The full Signatures app. Every seat at this rate once you are in the band.
Firm
25-49 users
$6/ user / month
The full Signatures app. Same features, lower seat price as the firm grows.
Organization
50+ users
$5/ user / month
The full Signatures app. Volume rate.
A seat is anyone licensed for the Signatures app. People who build signing packages, place fields, and send for signature. Recipients who only sign, review, or get copied do not need a seat. All seats are billed monthly at the rate for your current size. The CRM app is licensed separately.
Need more than one app? Estimate a monthly total.
Questions
How the Signatures app is set up in Base Assist.
Anyone licensed for the Signatures app. People who build signing packages, place fields, and send for signature. Recipients who only sign, review, or get copied do not need a seat.
No. They open a secure email link, agree to electronic records, adopt a signature, and finish the fields. People in your office can be picked from the directory. Client contacts come from the CRM app.
A signing package is the PDFs, the recipients, the fields, and the status. Draft, sent, in progress, completed, declined, voided, or expired. Completed signing packages can sit on legal hold.
Yes. Save a template with role slots and fields already placed. Next signing package, assign people to the slots and send.
The executed PDFs with signatures burned in, SHA-256 hashes on the original and the final, a Certificate of Completion, and the audit trail. You can void a signing package with a reason, or put a completed one on legal hold. Retention defaults to seven years and you set that in Admin.
Help with the Signatures app
Signing packages, templates, field placement, consent, and certificates.