The one-to-many problem

Most signing is one document to a handful of people. But a whole class of agreements is the opposite: one document that the same way to a long list of people. A policy acknowledgment to every employee. A new rate card to every reseller. A waiver to 300 event attendees. A 1099 contractor agreement to a seasonal hiring wave.

Sending those one envelope at a time is mind-numbing: upload, place fields, type a name and email, send, repeat — for the 200th time. Bulk send collapses that into a single action: you bring a template and a list, and the platform mints one personalized envelope per row.

How bulk send works

The flow has three inputs and one button:

  1. A template. The document and its field layout and routing are saved once. Every envelope in the batch is generated from it, so field placement and required acknowledgments are identical across all of them.
  2. A recipient list. A CSV where each row is one signer — at minimum a name and an email, plus any per-recipient values you want merged in (employee ID, region, contract amount).
  3. Send. Hosting Sign reads the CSV and creates a separate envelope per row — up to 500 recipients in one batch. Each signer gets their own unique link, their own copy, and their own audit trail. Nobody can see anyone else's document.

The critical point: bulk send is not one shared document that everyone signs. It's N independent envelopes created in one motion. Each one is as private and as defensible as if you'd sent it by hand.

Map your columns, don't hand-type

The CSV is where bulk send earns its keep. Beyond name and email, map columns to the template's fields:

  • A text field for "Department" populated from a column.
  • A number field for a per-recipient amount, so each contractor sees their own rate.
  • An auto-fill name/email field so the signer never re-types what you already know.

Build the template's fields to match your spreadsheet's headers and the merge is mechanical. The signer opens a document that already has their details in the right places and only needs to apply a signature.

Credits are consumed on send — plan the batch

One thing to get right before you click send: credits are decremented when an envelope is sent, not when it's completed. A 500-row bulk send consumes 500 credits up front, whether or not every recipient signs. That's not a gotcha — it's how the billing works across the product — but it means a sloppy CSV is expensive. Two habits prevent waste:

  • Validate the list first. Dedupe email addresses, strip test rows, and confirm there are no blank or malformed emails before sending. A typo'd address is a wasted credit and a signer who never gets the document.
  • Send a single test envelope from the template to yourself before the batch. Confirm the fields land correctly and the merged values look right. Fix the template once, then run the 500.

Tracking 500 envelopes without losing your mind

A batch is only useful if you can see its status. After a bulk send you don't want 500 line items you have to eyeball — you want to know who hasn't signed yet. Per-recipient delivery and signing status tells you exactly that: who received the email, who opened it, who signed, and who needs a nudge. From there:

  • Let automatic reminders chase the stragglers on a cadence instead of doing it by hand.
  • Set a hard expiration so a compliance acknowledgment can't be signed three months late and quietly counted as on-time.
  • For anything that needs to trigger downstream work on completion, wire an envelope.completed webhook so each finished signature files itself and updates your system of record automatically.

When not to bulk send

Bulk send is for documents where the terms are identical and only the recipient changes. It is the wrong tool when:

  • Each agreement is genuinely negotiated (use a normal envelope per deal).
  • Signers need to sign the same shared document in sequence (that's multi-recipient routing, not bulk send).
  • The document varies materially per recipient beyond a few merge fields — at that point you want separate templates, not one stretched too thin.

The takeaway

Bulk send turns "the same form, 500 times" from a day of clerical work into a CSV and a click. Build the template once, validate the list, send a test, then run the batch — and let reminders, expirations, and webhooks handle everything after. The signatures come back personalized, private, and each backed by its own court-ready audit trail.