SOURCE-CHECKED · BUSINESS DOCUMENTS
Send a Dropbox Sign request: a complete two-signer example
Place every signer field correctly in Dropbox Sign with a two-page practice PDF, seven-field map, invitation text, and examples of mistakes to fix.
To send a document through Dropbox Sign, upload it in the web app, add the signers, place fields and assign each field to its owner, then add the invitation and send. With two signers, the easy mistake is giving both signatures to the same person. The example below includes a complete document and field map so you can see the difference before creating your request.
Download the two-page practice PDF, field map CSV, request brief, and invitation text. These original materials can be copied and adapted. The PDF contains blank placement spaces; you add the actual signing fields in Dropbox Sign.
Start with the document, then the recipients
The practice packet is an acknowledgement of details for a fictional River Studio online workshop: 22 October 2026, 2:00-3:30 PM New York time, registration WS-104. It does not record actual attendance or supply contract terms.
Taylor Morgan is the participant and Alex Chen is the organizer. Both need to sign. A records inbox needs a copy, so it belongs in CC. The names, organization, event and example.org addresses are fictional. Replace them before a real send.
Put facts you already know into the document itself. The organizer knows the event date and time; asking a participant to type them again creates an unnecessary chance of a different answer. Recipient fields belong where the recipient supplies information or signs: a name, an optional booking reference, and the acknowledgement on page 2.
That division also makes corrections simpler. If the workshop time changes, change the source document. If the participant’s name is misspelled in your records, let the participant enter their own full name in the textbox. Do not ask a signature field to carry information that belongs in a separate text field.
Map all seven fields
Dropbox Sign’s standard fields include Textbox, Signature and Sign date. This example uses those three types. It does not need advanced conditional fields. Dropbox’s field reference
| Page | Printed space | Field type | Owner | Required |
|---|---|---|---|---|
| 1 | Participant full name | Textbox | Taylor | Yes |
| 1 | Booking reference | Textbox | Taylor | No |
| 2 | Participant signature | Signature | Taylor | Yes |
| 2 | Participant sign date | Sign date | Taylor | Yes |
| 2 | Organizer printed name | Textbox | Alex | Yes |
| 2 | Organizer signature | Signature | Alex | Yes |
| 2 | Organizer sign date | Sign date | Alex | Yes |
Taylor owns four fields; Alex owns three. There are six required fields and one optional field. Taylor’s name on page 1 and signature on page 2 have different jobs, so both remain in the map.
Open the CSV in a spreadsheet if you are planning a longer document. Filtering its owner column gives you the places one person must complete. A blank owner exposes an unfinished assignment. The coordinate columns describe the blank spaces in this PDF using points from its lower-left corner; they are not Dropbox Sign API coordinates or an automatic import. Place the fields manually in the editor.
For your own document, add a row when a person must complete another field, including repeated signatures on later pages. Delete unused rows. Keeping a row for a nonexistent field makes the map misleading even if the rest is correct.
Build the request in the web app
At app.sign.dropbox.com, choose Sign documents, upload the file, and continue with Next. Add each signer’s name and email, then open the editor. Drag fields onto the corresponding spaces. Click a field and use Assigned to for its owner. Fields are required by default; switch Required off for the optional booking reference. After placing fields, continue to the invitation screen, add any CC recipient, and choose Send for signature when the request is ready. Dropbox’s sending instructions
For the practice layout, work through Taylor’s two textboxes on page 1 first. On page 2, Taylor’s signature and date occupy the upper section. The lower section has Alex’s printed name, signature and date. Match each overlay to the printed label without covering the acknowledgement sentence above it.
The editor lets you move, resize or delete fields. Use Preview to inspect the signer view. If a field covers a label, move or shrink it; shrinking the surrounding document text would make the document harder to read. Dropbox’s editor instructions
Two mistakes in this sample have specific fixes. Assigning all five fields on page 2 to Taylor would give Taylor the organizer’s section: change the three organizer fields to Alex. Making the booking reference required would contradict its printed optional label: turn that field’s Required setting off. Correcting the invitation wording alone would leave either mistake in the form.
The acknowledgements in this example are independent, so leave signing order off. Use an ordered workflow when one person’s action depends on an earlier signature; adding an order to every request can make otherwise independent work wait.
Give the recipient enough context to respond
A useful invitation names the document and explains any part a signer could misunderstand. Copy the editable text and change its details:
Subject: Please acknowledge your River Studio workshop details
Hi Taylor and Alex,
Please review the two-page workshop acknowledgement for 22 October, 2:00-3:30 PM New York time.
Taylor: enter your full name on page 1; the booking reference is optional. Sign and date the participant section on page 2.
Alex: complete the organizer name, signature and date on page 2.
If the event details or your role are wrong, reply before signing so the document can be corrected.
Thank you, Workshop coordination
Keep a copy recipient out of the signer list when they only need the document. In this example, the records inbox has no action to take. Someone who must provide an acknowledgement needs their own signer role and assigned field.
A request deadline in a message and a technical expiration serve different purposes. This example has no expiration. On eligible paid English-language requests, Dropbox’s sending guide permits expiration; the selected time must be more than 24 hours away and within 90 days. Expiration stops the recipient opening or signing the request. For cross-time-zone recipients, use an explicit time zone instead of an ambiguous “Friday at five.” Dropbox’s expiration instructions
Fix the file before sending, or edit the pending request
If a page has the wrong date, correct the source and replace the whole file. Dropbox Sign’s editor replaces document files, not individual pages. Inspect the overlay positions against the replacement: a paragraph that became longer might have pushed a signature space down the page. Dropbox’s editor instructions
For a request already pending, open it under Documents and choose Edit and resend from its menu. Update the recipients, fields, message or document and save. Previous signers receive a notice and must sign again; unchanged fields can be prepopulated. Inspect retained answers, especially beside corrected text. Signer access codes do not automatically repopulate. Dropbox’s pending-request instructions
Explain what changed in the message: “The workshop time on page 1 was corrected. Please review the new time and sign the acknowledgement again.” This tells an earlier signer why another request needs attention without implying their first signature is enough.
Use the web app for this two-person, optional-field example. The Dropbox mobile flow permits only one signer and makes added fields required, so it cannot reproduce this map. Dropbox’s sending instructions
The practice packet is an original static sample, with no electronic signatures applied. Product instructions follow Dropbox’s linked documentation; no live signature request was sent.