One document, a whole list of people.
When the same document has to reach dozens or hundreds of people, and each of them signs on their own account, bulk send turns your list into individual envelopes in one go. Each person gets their own copy, with their own details filled in, and you watch the returns come in from one place.
Is this a bulk send at all?
The first decision is the one people most often get wrong. Ask whether the people on your list are signing one agreement together or the same agreement separately.
- Together: a partnership deed of variation signed by all five partners, or a shareholders' agreement signed by every shareholder. That is one envelope with several signers, and it completes when the last person signs.
- Separately: sixty drivers each confirming the updated vehicle policy, or every tenant in a block agreeing new parking rules. That is a bulk send, and one slow person does not hold anyone else up.
Getting ready
- Make a template from your document. Place the fields for one signer role. That role is filled by each person on your list in turn.
- Prepare the list. A spreadsheet with a row per person and at least a name and email address.
- Add columns for anything personal. A depot, a start date or a staff number can fill matching fields on each person's copy.
- Decide on reminders and an expiry date before sending, not halfway through.
SignAndGo checks the file before anything is sent and flags rows with a missing name, an invalid email address or a repeated address, quoting the row number so you can fix the source.
Running a bulk send well
Tidy the data at the source
If the list comes from payroll or a customer database, correct mistakes there as well as in the spreadsheet, or the same bad address will turn up in the next send.
Try a small batch first
Send to yourself and two colleagues before the full list. Check that the personalised fields land in the right places and that the message reads well on a phone.
Think about the calendar
Avoid sending on the afternoon before a bank holiday weekend, and remember that people on shifts may not read work email until their next shift starts. Give a deadline that allows for that.
A worked example: a courier firm's annual policy refresh
Consider a regional courier company with depots in Derby, Stoke and Wolverhampton. The company is invented for illustration. Each spring every driver confirms the updated vehicle use and safety policy. The operations manager saves the policy as a template with fields for name, depot, date and signature. She exports the driver list from the company's HR system with three columns: name, email and depot. After a test send to herself and the Derby depot manager, she uploads the full list. Each driver gets their own copy with their depot already filled in. The dashboard shows returns building over the next two weeks. Automatic reminders bring most of the rest in, and the depot managers have a word with the handful who have not opened theirs.
If drivers only need to confirm they have received and read the policy, rather than agree to it, an acknowledgement-only envelope may describe the act more accurately than a signature.
Following up
- Filter to the people still outstanding and remind them, not the whole list.
- Treat bounced emails as a data fix in your source system.
- Download completed copies as they arrive, or collect them all at the deadline.
- Keep a short note of what to change next time, such as a clearer subject line or an earlier start.
Privacy between recipients
Every row becomes its own envelope. Nobody on the list sees anyone else's name, address or copy, which matters when you are sending to staff or customers who do not know each other.
Pacing a long list
One bulk send can hold up to 500 rows, so split a longer list into two sends. You can send everything at once or spread it out: choose how many go each day, whether to send on weekdays only, and a start date. Pacing helps when replies land in one shared inbox, or when your team would rather answer questions as they arrive than face them all on a Monday morning.
Reminders can go to anyone who has not signed, every two days, every three days or once a week. You can also name one person, such as an office manager, to receive each signed copy as it comes back. That person is not asked to sign anything.
Common mistakes
- Merging the wrong column into the greeting, so people are addressed by surname or by their company's name.
- Putting a date in the document that will have passed by the time the slower half of the list gets round to it.
- Using one bulk send where each person's terms are different. If the substance changes from row to row, send separate envelopes.
- Forgetting leavers. Check the list against your current staff or customer records on the day you send.
For the click-by-click steps see send one document to lots of people, and for the longer background read the bulk sending guide.
Frequently asked questions
- Can recipients see who else was sent the document?
- No. Each row becomes a separate envelope, so each person sees only their own copy.
- What if my spreadsheet has errors?
- SignAndGo flags rows with a missing name, an invalid email address or a repeated address, with the row number, before anything is sent.
- Can each copy carry personal details?
- Yes. Extra columns in your list fill matching fields on each person's copy, such as a depot or a start date.
- Is there a limit on how many people one bulk send can reach?
- Up to 500 rows in a single send. Split a longer list into two sends.
See SignAndGo for your team
Send your first envelope in a few minutes, and keep every signed copy with its audit trail.
See how it works