Send BOR letters, consent forms, and policy change authorizations for signature directly from the client record. Signers draw or type their signature, and the completed PDF lands back in the documents tab automatically.
Pending
12
-3
Completed Today
8
+5
Avg. Turnaround
2.4 hrs
Completion Rate
94%
+2%
What it is
A native e-signature workflow built into the AMS — no third-party account required. Build a library of PDF templates (BOR letters, consent-to-rate forms, policy change authorizations) and send any of them for signature in a 3-step wizard. Signers draw or type their signature with three font styles. Every signing event is logged with IP address and timestamp automatically.
Creating a signature request takes three steps. Step 1: choose documents from your saved template library or upload a one-time PDF, add recipients as Signers, Approvers, or CC recipients, and choose sequential or parallel signing order. Step 2: a PDF viewer lets you drag and drop 13 field types — Signature, Initials, Date, Name, Text, Checkbox, and more — directly onto the document pages, assigned to specific signers by color. Step 3: review the configuration and send. Each signer receives a secure link that expires on your configured schedule.
Every signed document is hashed with SHA-256 at completion, with each signer's IP address and UTC timestamp recorded in the Audit Trail tab. The audit log captures every lifecycle event — sent, viewed, signed — per signer. When all parties have signed, every agency user receives an in-app notification and all signers receive a completion email with a copy of the signed PDF.
Core capabilities
Save reusable PDF templates — BOR letters, consent forms, policy change authorizations — and reuse them across any number of requests.
The Templates tab stores your agency's library of signing documents. Each template holds the uploaded PDF with pre-configured field placements and document type. When creating a request, pick from your saved templates or upload a one-time PDF instead. The 3-step wizard auto-fills the request name from the template name so repeat sends take seconds.
Place Signature, Initials, Date, Date Signed, Name, Title, Company, Email, Phone, Address, Text, Checkbox, and Dropdown fields directly on the PDF.
Step 2 of the creation wizard renders the PDF in a viewer. A sidebar lists all 13 field types organized by group — signature fields, date fields, signer info fields, text, and selection controls. Drag any field type onto any page position; fields render as color-coded placeholders sized to match real form fields. Each field is assigned to a specific signer by order number. Required, read-only, default value, placeholder, and validation settings are configurable per field.
Signers choose to draw on a touch canvas or type with three curated fonts: Script, Formal, or Casual.
The signing interface shows two modes: Draw (touch-optimized canvas with mouse or stylus) and Type (typed name rendered in one of three curated fonts — Script, Formal, or Casual). Both modes produce the same result and capture the same audit data.
Sequential signing holds each signer until the previous one completes. Parallel sends all signers simultaneously. Three recipient roles: Signer, Approver, and CC.
Recipients are added as one of three roles: Signer (must sign), Approver (reviews before the request is sent), or CC (receives a copy only). In sequential order, each signer receives their email only after the previous signer completes — the signing page shows a 'Waiting for previous signer' message if accessed early. In parallel order, all signers receive their links at the same time. Reminder emails fire on your configured schedule (default: every 3 days) until the request is complete or expired.
The signed PDF is hashed with SHA-256 at completion. The hash appears in the Audit Trail and on the signed document itself.
When the final signer completes the document, a SHA-256 hash of the signed PDF is computed and recorded in the Audit Trail alongside each signer's name and IP address. The hash is also printed on a tamper-evident verification page appended to the signed PDF, so any recipient can confirm the document hasn't been altered after signing.
Signed PDFs are automatically filed to client records. All agency users get an in-app alert. All signers receive a completion email.
When all signers complete a request, three things happen automatically: (1) the signed PDF is saved to every linked client's documents tab, (2) every user in the agency receives an in-app notification listing the signers' names, and (3) every signer receives a completion email with a link to download their copy. No manual forwarding or filing required.
What they don't do
Printing a BOR letter, getting a wet signature, scanning it, and emailing it back takes days. A tokenized signing link delivers the same legal result in minutes — no paper, no scanner, no inbox hunting.
When signed documents return as email attachments, they disappear into inboxes and need manual filing. Insurstein files the completed signed PDF to the client record automatically — every agency user sees it immediately.
Tracking who has and hasn't signed — and remembering to follow up — is busywork. Configurable reminder emails fire on your schedule (default: every 3 days) until the request is complete or expired.
Standalone e-signature tools don't know your clients, policies, or document types. Insurstein's signing flow is built inside the AMS — field placement, signer assignment, and auto-filing all use the same client and policy data.
Without document hashing, there's no way to prove a PDF wasn't altered after signing. SHA-256 hashing creates a verifiable fingerprint of the signed document at the moment of completion.
DocuSign and similar tools charge per envelope or per sender. Insurstein includes e-signatures in the platform. Trial accounts get 10 free signatures to start.
What it takes off your plate
Generates a unique, expiring link per signer — no Insurstein account required to open and sign the document.
In sequential signing, each signer's link is automatically activated only after the previous signer completes. Early access shows a 'Waiting for previous signer' message.
Sends reminder emails to unsigned signers on the configured interval (default: 3 days) — no manual follow-up needed.
Computes a SHA-256 hash of the completed signed PDF and records it in the Audit Trail alongside each signer's IP address and timestamp.
Generates the completed PDF with all signature overlays rendered and saves it to every linked client's documents tab automatically.
On completion, notifies every agency user in-app and sends a completion email with a signed copy link to every signer — all without manual action.
A day in the life
9:00 AM
A producer wins a commercial account. They open New → Signature Request, pick the BOR Letter template from the library, and add the insured as Signer 1 and the agency principal as Signer 2 — sequential order so the principal countersigns after the client.
9:05 AM
Step 2 renders the BOR PDF. The producer drags a Signature field and a Date Signed field onto the client signature line and repeats it for the principal's line. Each field is color-coded to its assigned signer. Takes about 90 seconds.
9:45 AM
The insured opens the secure link on their phone, draws their signature on the touch canvas, and hits Submit. The system records the timestamp and IP address in the audit trail and activates the principal's link.
10:10 AM
The principal receives the signing email, opens the document, sees the client's completed signature rendered as a read-only overlay, types their own signature in Formal font, and submits.
10:10 AM
The completed BOR is SHA-256 hashed, the signed PDF is generated and filed to the client record, every agency user gets an in-app alert, and both signers receive a completion email — all without anyone touching a file.
Daily impact
Field Types Available
Typing Fonts
Trial Signatures
Document Hash
13 field types, 3-step wizard, SHA-256 audit trail, and auto-filing to client records — e-signatures built into the AMS, not bolted on.