How to Send a Document to a Large Recipient List

Policy updates for 400 employees. NDAs for every event attendee. Consent forms for a whole customer list. Bulk Send (Business plan) sends one document to up to 1,000 recipients in a single batch, and each recipient gets their own copy and signing link.

Running a Bulk Send

Click the arrow next to Create Request and choose Bulk send. The wizard has five steps:

1. Upload Document. Click Choose Template to start from a saved template, or drop in a file (PDF, Word, Excel, text or image, up to 10 MB). An uploaded file is turned into a template for this send. It does not appear in your template list or count toward your plan's template limit. Starting from a template uses a copy, so the original template never changes.
2. Sign Request Editor. Place at least one field, usually a signature. For every value that changes per recipient, such as a start date or region, add a text field and give it a clear label: the label becomes a column in your recipient list. See how to personalize documents within a bulk send.
3. Signers. Set exactly one role to Varies per recipient: that is the person on each row of your list. Set any other role to Same for all, for example a manager who countersigns every copy. For each role, choose how they verify (No security, Email OTP, SMS OTP or Access Code; see choosing signer security) and how the request is delivered (Email or Text).
4. Recipients. Add the people who sign: Upload a file (a CSV built from Download CSV template), Type rows, or From a saved list. Inkfree checks every row and flags any that need attention before anything is sent. See how to prepare a recipient list.
5. Review & Send. Check the summary, set the Email subject and Email message, turn on Automatic reminders, choose when Requests expire, set signer permissions and name the batch (only you see the name). Then click Send.

Inkfree confirms "Queued N requests. They'll go out over the next few minutes." and opens the batch, where you can track every recipient. Nothing is sent before you click Send.

How It Differs from a Regular Request

• Each recipient signs independently: there is no shared signing order between rows, so nobody waits on anyone else.
• You get one completed document per recipient, each with its own audit trail and Certificate of Completion.
• A Same for all signer, such as a countersigning manager, receives one request per recipient. They can work through them from Your signing queue on the batch page.
• Each copy counts as one document toward your plan's usage. See Bulk Send limits and best practices.

Tip: Test with a two-row list (you and a colleague) before the real send. Five minutes of testing beats correcting a mistake that has reached 400 people.