
Sending a reusable document to many recipients as independent requests, rather than one jointly signed agreement.
Bulk send distributes a prepared document to many recipients as separate signing requests. Each recipient completes their own copy; the group is not collectively signing one agreement.
Bulk signing can describe applying signatures to many documents. Bulk send instead describes distribution. Several people signing the same contract belongs to multi-recipient signing order, not this separate-copy model.
In Sign.Plus, Bulk Send uses a template and recipient CSV. Where configured, variable values personalize individual copies. Review names, addresses and variable mappings before dispatch; a batch does not remove the need for correct recipient data.
A reusable e-signature template suits repeated agreements or acknowledgments. Public signing forms offer a different entry point: people start from a shared link rather than a sender-provided recipient list. Track each resulting request separately.
A Common Case: Distributing contractor agreements
Consider a Texas real-estate company engaging several maintenance contractors. Bulk send could distribute a prepared agreement as separate requests, with each contractor’s details checked beforehand. The team would track each completed agreement independently, rather than combine everyone into one contract.
No. It creates separate requests or copies; a shared multi-party agreement uses a different recipient workflow.
No. Bulk send describes distribution, while bulk signing can describe applying signatures to multiple documents.