One document going to a whole list of people.

A policy update for every employee, renewed terms for every client, a waiver for every participant. These are the same document, signed separately by each person. Bulk send creates an individual envelope for every row of your list, so each person signs their own copy and you track them all from one dashboard.

Bulk send versus one envelope with many signers

These two look similar and behave very differently, and choosing the wrong one is the most common mistake.

  • One envelope, several signers is for a single agreement that several parties sign together, such as a partnership agreement signed by all four partners. Everyone signs the same copy, and it is not complete until the last person signs.
  • Bulk send is for the same document going to many people who each sign independently. Forty staff acknowledging a new code of conduct do not need to see each other's names, and one slow person should not hold up the other thirty-nine.

A useful test: if you would print one copy and pass it around, use one envelope. If you would print forty copies and hand one to each person, use bulk send.

What you need before you start

  • A template made from your document, with fields placed for a single signer role. Every row of your list becomes that signer.
  • A spreadsheet with one row per person, holding at least a name and an email address.
  • Optional extra columns for anything that differs per person, such as a start date or a branch name, matched to fields on the template.
  • A decision on reminders and an expiry date, made before you press send rather than after.

Planning a large send

The send itself takes moments. The planning is where a bulk send succeeds or causes a week of tidy-up.

Clean the list first

SignAndGo checks your file before anything goes out and flags rows with a missing name, an invalid email address or a repeated address, quoting the row number. It is still worth sorting the file by email and scanning for obvious problems, such as a personal address where you expected a work one.

Pilot with a handful

Send to three or four people first, including yourself and one colleague. Open each copy and confirm the personalised fields read correctly. A start date in the wrong column is easy to fix before the full send and painful after.

Time it sensibly

A send that lands at eight in the morning on a weekday is read sooner than one that arrives at six on a Friday evening. Avoid the day before a statutory holiday, and remember that a national list spans several time zones, from Newfoundland to British Columbia.

A worked example: annual policy acknowledgements

Picture a home care agency in Halifax with staff spread across several towns. The agency is invented for illustration. Each year every worker must acknowledge the updated client privacy and safety policy. The HR coordinator turns the policy into a template with a name field, a region field, a date field and a signature. She exports the staff list from the agency's HR system with three columns: name, email and region. After a pilot to herself and a team lead, she uploads the full list. Each worker receives their own copy, with their region already filled in. Over the next fortnight the dashboard shows who has signed. Automatic reminders handle most of the stragglers, and the coordinator phones the few who have not opened the email at all, starting with anyone whose address might be out of date.

After the send

  • Use the dashboard to see what is still waiting, and remind those people rather than the whole list.
  • Treat a bounced address as a data problem in your source system, and fix it there as well as resending.
  • Download completed copies as they come in, or wait and file them together at the end.
  • Note what went wrong this time so next year's send is smoother.

One more check pays off on large lists: look at who owns the source data. If your staff list comes from payroll and your client list from your accounting system, the people who keep those systems tidy are the ones who can stop the same bad address appearing next year.

For the exact steps and spreadsheet tips, see sending one document to lots of people and the longer bulk sending guide.

Frequently asked questions

Does each person see the others on the list?
No. Every row becomes its own envelope, so each person sees only their own copy.
What happens to rows with mistakes?
Rows with a missing name, an invalid address or a repeated address are flagged with their row number before anything is sent, so you can correct the file.
Can each copy include personal details?
Yes. Extra columns in your list can fill matching fields on each person's copy, such as a start date or location.

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