Box enables you to define up to 35 recipients in each signature request, according to Box.
Set signing order and expiration dates in e-signature tools
Business owners often face uncontrolled signing sequences where documents remain open indefinitely or signers act out of order. You need specific numeric limits and toggle settings to manage who signs, when they sign, and when the request closes. These controls prevent administrative clutter and ensure your contracts follow the exact workflow you designed.
The first setting to verify is the maximum capacity for recipients. This limit determines how many parties can participate in a single workflow within that specific tool. If your contract involves multiple stakeholders, such as legal teams, finance departments, and external partners, you must confirm this number covers your needs.
Another platform offers a different constraint for the same function. In the Manage signers dialog, you can add up to 10 signers and assign labels for each signer to identify the signers in the document, as reported by Google. If you have more than ten parties, split documents or choose a tool with sufficient signer capacity. The ability to assign labels helps you track which specific role each signer fulfills within the document.
These two examples show that signer capacity varies significantly between tools. You cannot assume that a limit in one application applies to another. Check your current tool’s settings panel to see the specific maximum number of signers it allows. This number is a hard limit that you must plan around when drafting complex agreements.
Check your current e-signature tool's settings panel to verify the maximum signer count and enable the expiration date option.
Key takeaways for how to set signing order and expiration dates in e-signature tools
- Box advises setting a file version limit of 10 or more to avoid constraints, or keeping versioning unlimited, as noted in the Box Sign FAQ.
- Dropbox Sign allows you to add up to 20 signers to each signature request, according to Dropbox Help.
- Dropbox requires that a selected expiration date be more than 24 hours from the current date and time, and within 90 days.
- PandaDoc’s sequential logic means recipient 2 does not receive the document or a notification until recipient 1 completes required fields and clicks Finish.
- Verify that the "Set signing order" toggle is on in the Recipients panel for each new document.
Platform specific signer limits and version controls
Box Sign allows you to define up to 35 recipients in each signature request, according to Box. This capacity applies to each individual request you initiate within the platform. If your contracts require more parties, you must split the request or use a different tool. Each signature request has a maximum of 35 recipients.
File versioning controls in Box Sign require attention to prevent access errors. To avoid constraints, set a file version limit of 10 or more, or keep versioning unlimited, as recommended by Box. If a file version is deleted before the signature request is complete, Box Sign loses a reference point, and signers could no longer access the document, according to Box. This risk applies specifically to versions deleted while the request is active. Deleting a version does not recover the document for signers if the reference point is lost.
Dropbox Sign has different signer capacities depending on your plan. You can add up to 20 signers to each signature request on paid plans, according to Dropbox. If you're on a Dropbox Sign free plan, you can have up to 3 signers on each document, as stated by Dropbox. The free plan limit is significantly lower than the paid tier. Verify your current plan before sending a request to ensure the signer count fits within the allowed limit.
The difference in signer caps between Box and Dropbox means you must check your specific tool’s settings. Box supports 35 recipients, while Dropbox supports 20 on paid plans and 3 on free plans. These numbers are distinct and not interchangeable. If you move a workflow from one platform to another, adjust the recipient list accordingly. Do not assume that a signer count valid in one tool is valid in the other.
Configuring expiration dates and time zones
To control when a signature request expires and signing access ends, configure the request's expiration date in your tool. The settings available depend heavily on your subscription plan and the exact interface provided by the platform. For Dropbox Sign, the ability to set an expiration date is tied directly to your account tier. According to Dropbox, customers on paid plans can include an expiration date in their request. When that date passes, the signer will no longer be able to open or sign the document. This feature is not available to all users; it is restricted to those with paid subscriptions.
If you are on a paid plan, the process for adding this date is straightforward. As reported by Dropbox, you check the box beside "Set expiration date and time." Then, you click the calendar icon and use the date picker to select a specific date for the request to expire. This action locks the document into a time-bound state, preventing indefinite access.
However, you cannot pick any arbitrary date. The system enforces specific boundaries on your selection. According to Dropbox, your selected date must be more than 24 hours from the current date and time. Additionally, it must fall within 90 days. This means you cannot set an expiration for tomorrow if it is less than 24 hours away, nor can you set it for next year. The window is strictly bounded by these two constraints.
Time zone behavior is another critical factor when setting these dates. This time-zone rule applies to Dropbox shared links; Dropbox Sign request expiration is a separate setting. According to Dropbox, the shared link expires at 11:59 pm on the day you choose, based on your time zone. The shared link expires at 11:59 pm on the chosen day in your time zone. If you are working with international clients, this local time zone application is the rule that applies to the link's validity period.
Managing sequential signing and reminders
Control the sequence of signatures to prevent out-of-order approvals. PandaDoc enforces this through a specific toggle setting. According to PandaDoc, when the sequence logic is on, recipient 2 does not receive the document or even a notification until recipient 1 has completed their required fields and clicked Finish. This strict dependency ensures that later signers only see the document after prior steps are fully completed.
Before sending a document, verify the configuration in the Recipients panel. PandaDoc advises checking that the "Set signing order" toggle is on when creating the document. This toggle can be off on an individual document, so check it before sending. This check prevents accidental parallel signing where multiple recipients receive the document simultaneously. If the toggle is off, the sequential logic does not apply, and recipients may sign in any order.
Google Docs eSignature uses automated reminders to keep documents moving. When enabled, signers who haven't completed the request receive a reminder email 3 days (72 hours) after the initial request is sent, according to Google. This initial reminder helps prompt action without immediate manual follow-up.
Additional reminders follow a set cycle. Google sends these every 3 days after the first reminder, for up to 9 days, or until the document is signed, as reported by Google. These automatic reminders stop when the 9-day limit is reached or the document is signed, whichever occurs first. The 9-day limit applies to the reminder sequence, not necessarily the document's validity period.
To manage these settings effectively: * Enable the signing order toggle in PandaDoc's Recipients panel for every new document. * Verify the toggle status on individual documents, not just examples. * Enable the reminder option in Google Docs eSignature to automate follow-ups. * Note that Google reminders stop after 9 days or upon signing.
A filled reference table of signing constraints
The table below lists the nine specific settings and limits for document security and timing. Each row names the publisher and cites the exact value or behavior from their support documentation. Use this list to verify your current tool settings against the documented constraints.
| Publisher | Setting or Limit | Specific Value or Behavior |
|---|---|---|
| Box | Version limit | To avoid constraints, set a file version limit of 10 or more, for example, or keep versioning unlimited, according to Box. |
| Box | Version risk | If a file version is deleted before the signature request is complete, Box Sign loses a reference point, and signers could no longer access the document, reported by Box. |
| Dropbox | Signer cap | You can add up to 20 signers to each signature request, according to Dropbox. |
| Dropbox | Date window | Your selected date must be more than 24 hours from the current date and time, and within 90 days, according to Dropbox. |
| Dropbox | Paid expiry | For customers on paid plans, your request can include an expiration date, so when the expiration date expires, the signer will no longer be able to open or sign your document, reported by Dropbox. |
| PandaDoc | Sequence logic | When it's on, recipient 2 does not receive the document — or even a notification — until recipient 1 has completed their required fields and clicked Finish, published by PandaDoc. |
| PandaDoc | Toggle check | Check that Set signing order is on in the Recipients panel when creating each document, because it can be off on an individual document, according to PandaDoc. |
| Signer limit | In the Manage signers dialog, you can add up to 10 signers and assign labels for each signer to identify the signers in the document, reported by Google. | |
| Reminder cycle | Additional reminders are sent every 3 days after that, for up to 9 days, or until the document is signed, published by Google. |
Common errors when editing sent documents
Editing recipients on a sent PandaDoc document may clear signature and initials fields and require re-signing after you resend. You must understand how each platform handles these specific changes before you modify a live document.
Data loss in PandaDoc If you change the recipient list on a document that has already been sent, you risk wiping out completed work. According to PandaDoc, editing recipients on a sent document may clear signature and initials fields. This means that if a signer has already completed their part, those fields can be emptied. After you resend the document, the signers may be required to re-sign. To avoid this, do not edit the recipient list on an active document. If you need to change who signs, start a new version.
Verification status in Box Sign When you use Box Sign, the method of signing affects the final verification label. According to Box, any in-person signatures indicate “not verified by Box Sign.” This status appears on the document record. If you rely on the platform’s verification for your records, in-person signatures will not carry the standard verified label. Check your compliance requirements to see if this status is acceptable for your business. If you need a fully verified record, avoid using the in-person signing option.
Related guides
FAQ: How to set signing order and expiration dates in e-signature tools
What is the maximum number of signers in Box Sign?
Box enables you to define up to 35 recipients in each signature request. This limit applies specifically to the Box Sign platform as described in their support documentation. You should verify this count against your current tool settings to ensure compliance.
How long can a Dropbox signature request remain active?
Your selected date must be more than 24 hours from the current date and time, and within 90 days. These limits constrain the expiration date you select for a Dropbox Sign request. Ensure your expiration date falls within this specific timeframe.
Does PandaDoc notify the next signer immediately?
When the sequential setting is on, recipient 2 does not receive the document or even a notification until recipient 1 has completed their required fields and clicked Finish. This logic prevents premature access to the document. Check your PandaDoc settings to confirm this sequence is enabled.
How often does Google send reminder emails?
When this feature is enabled, signers who haven't completed the request will receive a reminder email 3 days (72 hours) after the initial request is sent. This initial reminder is part of Google's automated follow-up process. Verify that this reminder option is active in your Google Docs settings.
What happens if a file version is deleted in Box?
If a file version is deleted before the signature request is complete, Box Sign loses a reference point, and signers could no longer access the document. This action can disrupt the signing process entirely. Avoid deleting file versions while a request is pending.