Fix a Dropbox Sign request after sending it

If you find a wrong date, sentence, or field in a pending Dropbox Sign request, you can edit and resend the request without canceling the original. A request can still be pending after one person has signed it.

Check every date before editing

In this fictional example, a sender has sent an October design project agreement to illustrator Alex and client Morgan. Alex has signed; Morgan has not. Paragraph 4 says the service delivery date is October 18, 2026, but the intended date is October 20. The DeliveryDate field also says 10/18/2026. The $1,200 fee is correct.

Before opening the editor, compare the agreement text, any attached schedule, the signature-page fields, and the email you plan to send with the corrected request.

Location	Sent value	Corrected value
Paragraph 4, service delivery	October 18, 2026	October 20, 2026
Attached schedule, if it repeats the date	October 18, 2026	October 20, 2026
DeliveryDate field	10/18/2026	10/20/2026
Resend email draft	Check its wording	October 20, 2026

DeliveryDate describes the project deadline in this example. The fictional agreement uses SignatureDate for the date a person signs. That field should not be forced to October 20 to make the project dates match.

A small before-and-after excerpt makes the text change easy to review. This is illustrative project wording, not a contract template:

Before: “The designer will provide one logo concept by October 18, 2026. The project fee is $1,200.”

After: “The designer will provide one logo concept by October 20, 2026. The project fee is $1,200.”

If the sender cannot confirm which delivery date was intended, the next step is a factual question before changing the request: “Can you confirm whether the service delivery date should be October 18 or October 20, 2026? Paragraph 4 and the DeliveryDate field currently say October 18.”

Edit and resend the request

Open Documents, select the pending request’s more options menu, then Edit and resend. You can change recipients, fields, the email, and document parts. Select Save after correcting them. The editor initially shows existing entries, but Dropbox instructs senders to reenter signers, documents, and CC recipients. Access codes need reentry too.

Previously signed recipients get an email and must sign again; they should review prefilled unchanged responses. Removed signers are notified, and edits enter the audit trail. Dropbox’s editing instructions describe this behavior.

For the October example, first correct paragraph 4, then read the attached schedule. If the schedule already says October 20, leave that value alone. Next find the DeliveryDate entry assigned to the project date. Compare its value with the paragraph, including the year. Finally read the email message that will accompany the request. An old October 18 deadline left in that email would make the recipient wonder which date to follow.

Keep a short correction note alongside your project records. This is an optional authored example, not a Dropbox Sign field or an export from the service:

Request: October design project agreement
Correction: Service delivery changes from October 18 to October 20, 2026.
Places to inspect: Paragraph 4, attached schedule, DeliveryDate, resend message.
People: Alex (already signed) and Morgan (awaiting signature).
Unchanged: One logo concept; $1,200 project fee.
Access code used: Confirm before saving; keep the actual code outside this note.

A useful note identifies the affected text and the parts you intend to preserve. “Fixed agreement” would give another project worker no way to distinguish the date correction from a fee or scope change. If your review finds a second error, add its old and new values before revising the message. Do not describe the fee as unchanged if you also corrected it.

Tell recipients what changed

Use a specific correction message so Morgan can compare the new request with what was sent earlier:

Subject: Corrected October design project agreement

Paragraph 4 and the DeliveryDate field now show the service delivery date as October 20, 2026 (10/20/2026), replacing October 18, 2026 (10/18/2026). The $1,200 project fee is unchanged. Please review the service date in paragraph 4 and the DeliveryDate field before signing.

Send Alex a separate note that acknowledges the extra step:

Subject: Please sign the corrected October design project agreement

I’m sorry to ask you to review and sign again. You had already signed when I corrected the service delivery date in paragraph 4 and the DeliveryDate field from October 18, 2026 (10/18/2026) to October 20, 2026 (10/20/2026). The $1,200 fee is unchanged. Please check both the paragraph and the field before signing again.

If the request also needs a deadline

On a paid plan, the sender can open the request’s more options menu under Documents, choose Add expiration date, select Expiration date, set a date and time, and select Save. The deadline must be more than 24 hours away and within 90 days. The sender specifies a timezone, and signers see a localized expiration banner.

For example, if you set the deadline on October 7 at 10 a.m. New York time, choosing October 9 at 5 p.m. New York time leaves 55 hours. October 7 at 5 p.m. would be only seven hours away and would not meet the more-than-24-hour rule.

Source note: Product steps come from Dropbox’s pending-request editing instructions, updated August 12, 2026, and expiration instructions; the example and messages are illustrative, with no account test recorded.