When Bulk-Send Signature Requests Make Sense
Most trades you close one at a time: one buyer, one item, one signature. But some documents go out to twenty people at once, and sending them individually wastes the afternoon. Bulk-send exists for that case. Knowing which case you are in is the whole decision.
When bulk-send beats sending one request at a time
Bulk-send is for one situation: the document is finished, the terms do not change, and you need the same thing signed by a list of people. Think a consignment agreement going to thirty consignors on identical terms, an NDA sent to every dealer walking into a private showing, or a revised hold policy that your regulars all need to acknowledge. The text is fixed. The only variable is who signs.
That is the opposite of a negotiated deal. When you are trading a single watch and the price, the NAD fee, and the shipping terms are still moving, you are not bulk-sending anything. You are drafting one contract for one counterparty. Bulk-send does not fit, and forcing it there creates more cleanup than it saves.
The volume threshold is lower than most dealers assume. You do not need hundreds of recipients to justify a batch. If the same document is going to more than a handful of people and you would otherwise copy, paste, and re-send it by hand each time, the batch already pays for itself in the time you do not spend re-keying recipient details. The saving is not only speed; it is consistency, because every copy comes off the same master instead of from whatever you typed that particular afternoon.
There is a common point of confusion worth clearing up. Bulk-send does not mean one document that collects many signatures on the same page. It means many copies of the same document, each routed to one signer, each signed and returned on its own. A question that surfaces repeatedly in signature-tool forums is from people trying to put seventy-five signature blocks on a single PDF through a bulk feature; that is a different job, and bulk-send is the wrong tool for it. If you need every name on one sheet, you want a single routed document, not a fan-out.
So the test is simple. Ask whether each recipient gets their own signed copy with their own name on it. If yes, and the body text is identical across all of them, bulk-send is the efficient path. If the document body differs per recipient, or everyone signs one shared sheet, it is not.
One more fit test: the optional clauses need to be identical too. On lockd the optional pieces that matter to the trade are things like NAD terms, shipping, jurisdiction, and hold expiry. If those are the same for everyone on the list, bulk-send is clean. If one consignor needs a different jurisdiction clause, pull them out of the batch and send theirs on its own rather than editing the master mid-run.
What breaks at scale, and how to keep tracking clean
The failure mode of bulk-send is not the sending. It is the tracking afterward. One request is trivial to follow. Forty requests from one template, sent in a batch, turn into forty open threads, and the mess shows up a week later when signer fourteen replies with a question and you cannot tie their message to a record.
Three things keep a fan-out clean. First, every copy needs its own reference number, not a shared one, so a returned document maps to exactly one signer. Second, every copy needs its own audit trail: who opened it, when, from what address, and when they signed. A batch that shares one log is not auditable per signer, which defeats the point. Third, you need a status view that lets you filter the batch, see who has signed and who is still outstanding, and export the lot for your records.
This is where template discipline matters more than at single-deal scale. The template is the one thing every copy inherits, so an error in it multiplies by your recipient count. Proofread the clauses once, carefully, before the batch goes out. Lock the fields that should not change. Leave only the recipient details to vary.
Delivery channel matters at scale too. A one-off request you can hand-send however the counterparty prefers. A batch should go out through a channel you can track in one place, so a bounced email or an unopened link shows up in the same view as everything else. lockd states that a signing link can go by WhatsApp, SMS, email, or copied link, and that the signer opens it on their phone with no account, app, or signup. For a fan-out, pick the channel your recipients actually read, and keep the batch pointed at one dashboard rather than scattered across inboxes.
Plan for the partial batch before you send it, because you will rarely get a clean return on the first pass. Decide up front how long you will wait, what your reminder cadence is, and what the fallback is for the names that never sign. With a per-copy reference number and a status filter, chasing the outstanding few is a two-minute task; without them, you are guessing at who is missing from a list of forty.
lockd states that every action on a deal, from drafted to sent to signed to finalized, is timestamped with IP, and that each document carries a reference number and a signed copy in both dashboards. The optional Document Management add-on tracks a document through stages, with filter, search, and export; the listed default stages run Sent, Signed, Shipped, Received, Inspected, Paid, Closed. Those are the pieces that keep a high-volume batch legible after the fact. Whether a given plan fits the volume you are planning to send, and how batching is handled on your account, is worth confirming with the team before you rely on it.
The short version: reach for bulk-send only when the document is done and the signer list is the only variable. Keep one reference number and one audit trail per copy, get the template right before you fan it out, and make sure you can filter and export the batch when it comes back. Do that and sending forty is as controlled as sending one.