PandaDoc Bulk Send: The Complete Setup Guide

PandaDoc bulk send takes one template and a CSV of recipient data and generates a separate, personalised document for every row, up to 1,000 recipients per batch, each sent for signature automatically. It is available on Business and Enterprise plans with a volume package add-on, and every document generated in a bulk send consumes one usage credit.

That is the two-sentence answer. The longer answer is that bulk send is the most misunderstood of PandaDoc’s three delivery mechanisms, because teams reach for it either too early, when a negotiated proposal still needs a rep, or too late, after someone has spent a week sending 400 renewal agreements one at a time. This guide covers the mechanics as they stand in late 2026, verified against PandaDoc’s current documentation: what bulk send actually does, how to prepare the template and the CSV so the batch does not bounce back with errors, the limits that bite in practice, and the decision rule for when bulk send beats both a form and a rep-sent document.

The context for that decision is the same one behind every delivery question: manual document creation was the top pain in 82 of the 129 sales calls we analysed, and the teams feeling it worst are the ones producing the same document over and over with only the names changed. That is precisely the shape of work bulk send removes.

Key takeaways

• Bulk send generates one unique document per CSV row from a single template, personalises it through variables, and sends each copy for signature. A batch is capped at 1,000 recipients, and PandaDoc enforces a limit of 1,000 documents per hour.
• It is gated to Business and Enterprise plans and requires a volume package add-on; it is not available during a trial. Each document sent in bulk consumes one usage credit, the same meter that forms and the API draw on.
• The template must have at least one role, and every field in it must be assigned to a role. The CSV’s header row lists variable names without square brackets, the email column is mandatory for every row, and the same email address cannot appear twice in one batch.
• Variables personalise the document body, and the CSV can set a per-recipient document title and email message. Variables inside the template title itself do not fill in bulk send, so use the CSV’s title column instead.
• Bulk send is the right mechanism when you already know the recipients and the document is standardized: renewals, policy updates, annual agreements. When the recipient comes to you, use a form instead, and when the deal is negotiated and priced individually, keep a rep in the loop.

What bulk send does, and what it is not

PandaDoc gives you three ways to get a document in front of someone. A rep-sent document is created from a template for one named deal, checked, and sent. A form inverts the direction: you publish a link, and recipients you have never met fill in their own details to generate the document. Bulk send sits between them: you already hold the recipient list and the data, and PandaDoc does the generating and sending in one pass.

Mechanically, a bulk send is a mail merge with signatures. PandaDoc reads your CSV, creates one document per row from the chosen template, fills each document’s variables from that row’s columns, assigns the signature and input fields to the recipient through the template’s roles, and emails every document for signing. Each recipient sees only their own copy, with their own name, their own terms, and their own signing session. Nothing about the batch is visible to them.

What bulk send is not: a campaign tool or a substitute for judgement on live deals. Every document it produces is a real, legally signable document, which is why the preparation rules below matter more than they would for an email blast. A typo in a mail merge is embarrassing; a wrong figure in 600 signed agreements is a contractual problem. The off-brand, error-prone manual alternative is the thing teams are trying to escape, and 44 of those 129 calls specifically flagged inconsistent, off-brand documents as a pain, so the template feeding a bulk send has to be watertight before the batch runs.

Plan gating and what a batch costs

Bulk send is available on Business and Enterprise plans with a volume package add-on, and the account owner has to switch the feature on first: it lives in the Extensions store under the Productivity category, and until it is enabled the option does not appear in the send menu. It is not available during a free trial.

The cost model is the usage credit meter: each document sent in bulk consumes one usage credit. That is the same meter PandaDoc applies to documents generated by forms and by the API, so a team running forms, bulk sends, and API generation is drawing down one shared allowance. Before scheduling a large batch, check the credit balance against the batch size: a 1,000-row CSV is 1,000 credits, and overages are billed once the included allowance runs out. Unlike per-send pricing on tools like Proposify or Better Proposals, ordinary rep-sent PandaDoc documents remain unlimited; the meter only applies to automated generation.

If you are weighing plans, the practical read is simple: bulk send is not a reason to buy PandaDoc on its own, but if you are already on Business for the template, content library, and integration features that justify the tier, the add-on turns recurring batch paperwork from a week of admin into an upload.

Prepare the template first

A bulk send is only as good as the template behind it, and PandaDoc enforces two hard rules before a template can be used in one.

The template needs at least one role. Roles are the placeholder recipients that fields and variables attach to. In a bulk send, each CSV row’s recipient data flows in through a role, so a template built for one-off manual sending with directly assigned recipients will not work until its recipients are converted to roles.

Every field must be assigned to a role. Signature fields, date fields, text inputs: all of them. An unassigned field has no recipient to collect it from, and PandaDoc blocks the template from bulk sending until the assignment is complete. This is worth a deliberate pass before the first batch, because templates that have been edited by several people over months often carry one or two orphaned fields nobody notices in manual sending.

Beyond the hard rules, apply the same discipline you would to any production PandaDoc template: personalisation through variables rather than hand-edits, brand elements locked, and the content current. Two variable behaviours are specific to bulk send. First, variables in the document body fill from the CSV exactly as they fill from a CRM in normal sending, and both default role variables and custom variables are supported, each listed in its own dropdown during setup. Second, variables placed in the template’s title do not fill in a bulk send: the batch would go out with literal bracketed text in every document name. Use the CSV’s document title column instead, which sets each document’s title per row. The full naming and exact-match rules are in our PandaDoc variables guide.

CSV rules that decide whether the batch runs

PandaDoc generates a blank CSV for the template during setup, with the header row already populated, and filling that file in is far safer than building one by hand. The rules it has to meet:

• Comma-separated values only. Build it in Google Sheets or Excel and export; PandaDoc’s own recommendation is Google Sheets.
• The header row lists variable names without square brackets. A template variable written as [Client.Company] appears in the CSV simply as its name. The download handles this for you; hand-built files get it wrong constantly.
• The email column is mandatory for every row. It is how PandaDoc knows where each document goes. Every other column is optional: a row with gaps still generates a document, just with those variables blank.
• One row per recipient, 1,000 rows maximum, and the same email address cannot be used for more than one recipient in a batch.
• Optional per-row columns include the document title and a personalised email message, so each recipient can get an individually named document with an individually worded covering email from one batch.

On upload, PandaDoc validates the file and reports two classes of problem. Errors, flagged red, are missing or invalid email addresses, and the batch will not proceed until they are fixed and the file re-uploaded. Warnings, flagged yellow, are unfilled variables: you can click through and send anyway, and those fields render blank. Treat warnings as seriously as errors. A blank where a payment term or renewal date should be is exactly the silent failure that turns up signed, and the fear of a document going out with wrong numbers came up in 28 of the 129 calls we analysed. The fix belongs upstream, in the sheet, not in 40 generated documents.

The send sequence, step by step

With the template and CSV ready, the run itself is short:

1. From the Home page or the Documents app, click the arrow beside +Document and choose Bulk send.
2. Select the template.
3. Review the variable mapping. Default role variables sit in each role’s dropdown; custom variables have their own dropdown. Confirm every variable you expect to fill is matched to a CSV column.
4. Download the blank CSV if you have not already, fill it, and upload it: drag and drop, from your device, or straight from Google Drive, Dropbox, Box, or OneDrive.
5. Work through the errors and warnings PandaDoc reports.
6. Continue to the final step, confirm the document count, and add a batch-level email message if your CSV does not carry one per row.
7. Send.

PandaDoc then generates and dispatches the documents, respecting the 1,000-per-hour ceiling, and emails you a confirmation when the whole batch has gone out.

Limits and restrictions worth knowing before you commit

The published numbers: 1,000 recipients per CSV, 1,000 documents per hour, unique email addresses within a batch, and PandaDoc reserves the right to suspend the feature temporarily if it detects unreasonable usage. A 3,000-document job, roughly what one client of ours produces in a year, is three batches on separate uploads, not one.

Two restrictions are easy to miss. Recipient verification, including passcode verification, is not available on bulk-sent documents: if your agreements require identity checks before signing, bulk send is not the route. And if the workspace has an approval workflow, bulk send generates the documents automatically but does not send them: each document waits for manual approval, and an approver or the document owner sends it by hand. For a 500-row batch, that means 500 individual approvals, so either scope the template’s terms so the batch qualifies for an approval exemption, or accept that the approval stage is where the time goes. How to design those exemption rules is covered in our approval workflows setup guide.

Tracking the batch after it goes out

Every bulk send creates a dedicated folder, named with the template name and the send date, holding every document in the batch. From there, each document behaves like any other PandaDoc document: it carries its own sent, viewed, and completed status, its own audit trail, and its own reminder settings, so chasing stragglers works the same way it does for rep-sent documents, just at list scale. The batch folder is the practical unit of follow-up: open it a week after sending, sort by status, and you have the outstanding list.

What bulk send does not give you is campaign analytics in the marketing sense: no aggregate open-rate dashboard across the batch. For most legal and renewal use cases that is fine, because the question is “who has not signed”, and the folder answers it.

When bulk send is the right mechanism

The decision between the three delivery mechanisms comes down to two questions: do you already know the recipients, and is the document standardized?

Bulk send wins when you know the recipients and the document is standardized. Annual contract renewals across a client base, updated terms of service that every customer must re-sign, policy acknowledgements for staff, rate-change letters, season agreements for members. You hold the list, the data is in a sheet, and no deal-by-deal judgement is needed.

A form wins when the recipients come to you. Inbound sign-ups, intake agreements, bookings: you cannot build a CSV of people you have not met. The trade-offs between the two are covered in the forms guide.

Neither wins when the deal is negotiated. A priced-per-deal proposal with scoped line items needs a rep and usually a pricing table fed from a catalog, not a mail merge. Teams that try to bulk send proposals end up hand-editing the generated documents one by one, which is the 45-to-50-minutes-per-proposal problem wearing a new hat.

If the batches are becoming a recurring part of how your documents operate, it is worth getting the foundation right once: roles, variables, catalog, and the templates the batches run on. That is the work of a proper PandaDoc implementation, and it is what makes the difference between bulk send as a reliable quarterly routine and bulk send as an annual fire drill.

Frequently asked questions

What plan do I need for PandaDoc bulk send?

Business or Enterprise, plus a volume package add-on, and the account owner must enable Bulk Send in the Extensions store under Productivity. It is not available on Starter plans or during a free trial. Each document sent in bulk consumes one usage credit from the same allowance that forms and API-generated documents use.

How many documents can I send in one batch?

Up to 1,000 recipients per CSV, with a processing ceiling of 1,000 documents per hour, and every email address in the batch must be unique. Larger jobs run as multiple batches. PandaDoc can temporarily suspend the feature if it detects unreasonable usage, so keep big jobs to genuine signing workloads.

Do variables work in a bulk send?

Yes, in the document body: both default role variables and custom variables fill from the CSV columns, mapped during setup. Variables in the template’s title do not fill in bulk send; set each document’s name with the CSV’s document title column instead. Unfilled variables trigger a warning at upload and render blank if you send anyway.

Can bulk-sent documents go through an approval workflow?

Partially. If approvals are configured, the batch generates automatically, but every document then waits for manual approval before it can be sent, one by one. For large recurring batches, design your approval rules so standard-terms documents are exempt and only exceptions queue for sign-off.

When should I use a form instead of bulk send?

Use a form when recipients come to you and fill in their own details: inbound sign-ups, intake paperwork, standardized service agreements published as a link. Use bulk send when you already hold the recipient list and the data. Both are gated to Business and Enterprise plans and both draw on usage credits per generated document.