Send Separate Signature Requests with a CSV

Use a batch when each person needs an individual request

Bulk Send is useful when you need separate signature requests based on the same prepared document. Start with the right template, download its CSV and fill in the intended recipients. The CSV prepares a batch of requests; it does not make one person sign many documents automatically.

If the parties all need to execute one shared agreement, use a request with multiple signers and the appropriate order instead. A company-wide policy acknowledgment and a lease signed by several parties have different routing needs.

Check the template before opening the spreadsheet

Review the version, clauses, fields and recipient roles in the template. Make sure the document is suitable for every person in this batch. When details vary, decide which can be supplied through supported dynamic fields and which require a different document.

An Ohio HR team is collecting an acknowledgment of a new expense policy from 60 employees. Each employee needs their own request and completed record. The HR team checks the policy version once, then checks each employee's recipient details before preparing the batch.

A template is reusable preparation, not a reason to skip review. An old policy date or a field assigned to the wrong role can be repeated across all requests.

Prepare the CSV from Sign.Plus

Bulk Send is documented for Business and Enterprise plans, using the web app. In Templates, open the chosen template's menu and select Bulk Send. Follow the documented CSV preparation flow and use the file it provides.

1. Keep the downloaded headers. Do not replace them with your own contact-list column names.
2. Enter only the intended recipients. Check names against email addresses and remove accidental duplicates.
3. Respect the batch limit. The documented maximum is 100 rows. Split a larger list into clearly named batches.
4. Preserve CSV formatting. Save as CSV, then reopen the file to check that names, addresses and columns remain in the right places.
5. Review template-specific values. If the template uses variables, use the corresponding generated structure and verify each value against the correct recipient.

Do not invent column names or copy a CSV from an unrelated template. Treat the downloaded file as the format for this batch. A spreadsheet that looks tidy can still contain a shifted column, an extra row or an address copied from the wrong employee.

Review three things before sending

When a workflow is new, first validate the template and recipient mapping with controlled, authorized test recipients before using the operational list. Only send the production batch when someone responsible has checked both the document and the list.

Track completion at the individual-request level

After sending, check outstanding requests under Pending and finished requests under Completed. A batch can contain both at the same time. One person's completion does not complete everyone else's request.

Use a simple internal control list to reconcile the intended recipients with completed records. If someone did not receive the invitation or their request stopped, investigate that request's status before repeating the whole batch.

If the template itself was wrong, identify the affected requests and follow a versioned correction process. Avoid a second live batch that leaves recipients uncertain which document to use.

As each request completes, retain the signed file and its evidence with the right employee or transaction reference. Keep the source list in an appropriately restricted location; it contains recipient information and is not a public reporting file.