Bulk send

What does Bulk send mean?

Bulk send is an e-signature feature that sends the same document to many people in one action, while giving each recipient a separate copy to sign. Sometimes called mass send or batch sending, it is designed for the moment when one agreement must reach dozens or hundreds of individuals rather than a single counterparty.

It usually starts from a template. You upload a list, often a CSV, with each recipient's name, email and any personalized values, such as a start date or unit number. The platform then creates one envelope per row, sends them all, and tracks each separately, so one person's delay never holds up the others.

An HR team rolling out an updated handbook acknowledgment to 200 employees is the textbook case. Without bulk send, someone creates 200 envelopes by hand. With it, they upload the staff list once and watch the completions arrive, chasing only the stragglers. A landlord sending rent policy notices across a building has the same need at a smaller scale.

A common confusion is between bulk send and adding many signers to one document. If fifty people sign one envelope, they all sign the same copy, and it completes only when the last person finishes. Bulk send creates fifty separate documents, each with its own audit trail and certificate. The right choice depends on whether you need one shared agreement or many individual ones.

Bulk send relies on a template for the document layout and produces one envelope per recipient. Reminders matter even more here, since chasing people manually at volume is where time disappears.

Before a bulk send, a little preparation goes a long way. Clean the recipient list first, since a typo in one email address means one person never gets their copy. Test with a small batch before sending to everyone, and double-check any personalized values merged into the document. Set reminders so the platform chases late signers automatically. Afterward, export or review the status list to see who has signed, who has declined, and who still needs a nudge.

Our take: bulk send is a must for HR and property teams, and a nice-to-have for most freelancers and small firms. If you only send to a handful of people at a time, templates plus reminders get you most of the way.

Bulk send is available in eSignSimple: pick a single-signer template, paste name and email lines or upload a two-column CSV, and send to up to 200 people at a time. Each recipient gets their own copy, and each copy has its own audit trail.

What is an example of bulk send?

A school's HR office needs 60 staff members to sign an updated safeguarding policy. The admin makes a template with one signer role, exports names and emails from the staff directory as a CSV, and runs bulk send in eSignSimple. Each person receives an individual copy, signs it, and the admin tracks who has signed on the dashboard while reminders chase the rest.

How do you prepare the recipient list for a bulk send?

In eSignSimple, bulk send starts from a template and a list with one name and email per signer role on each line (two columns for a one-signer template). You can paste lines or upload a CSV, and up to 200 recipients go out per send. Export the list from wherever the truth lives, such as your HR system or tenant database, rather than retyping it, then clean it: remove duplicates, trim spaces, fix obviously broken addresses like missing dots, and drop anyone who has left.

Save the CSV as UTF-8 so names with accents come through correctly, and look at the preview before you send. If you have more than 200 people, split the list into batches by team, building or region; it also makes follow-up easier, because you can see at a glance which group is lagging.

What happens after you press send?

Each recipient becomes their own document with its own signing link, audit trail and certificate of completion. Recipients sign independently, so one person's absence never holds up anyone else. On paid plans, reminders go out automatically every three days, up to three times, to people who have not signed yet. Recipients who decline appear as declined, and you can void individual documents if someone should no longer receive one.

Your dashboard shows the status of each copy, which is where the real work of a bulk send happens. Expect most signatures in the first two days, a second wave after the first reminder, and a small group who need a personal nudge. Plan for that last group from the start rather than assuming the reminders will catch everyone.

Common bulk send mistakes and how to avoid them

Sending the wrong version of the template is the costliest mistake, because it means voiding and re-sending to everyone. Check the template once more right before the send, and do a test batch to yourself and a colleague. Another frequent error is using a template with two signer roles; bulk send is for documents each person signs alone, so if a manager also needs to countersign every copy, send those individually or reconsider the workflow.

A quieter mistake is a vague email message. People are more likely to open a signing request if it says who it is from, what the document is, and by when it should be signed. One clear sentence, such as Please sign the updated 2026 remote work policy by Friday, beats a generic subject line. Our bulk send product page and the HR solutions page show typical uses.

Which terms are related?

• Envelope: An envelope is a container for one or more documents sent to one or more recipients for signature as a single transaction with one shared audit trail.
• Template: An e-signature template is a reusable document with preset signer roles and fields, so you can send the same agreement repeatedly without setting it up again.
• Web form (signing link): A web form in e-signing is a hosted, fill-and-sign page with a public link, letting anyone complete and sign a document without being invited first.
• E-signature API: An e-signature API lets software create, send, track and download signature requests programmatically instead of through the web app.