- Data fields need to be populated by someone other than the signer
- An internal team member must add details that will be visible to other recipients
- Contract terms or values need to be entered by a specific party
- Administrative information must be collected separately from signatures
Preparers are functionally equivalent to approvers. The only differences are in the UI wording and confirmation messages shown to the recipient during the ceremony.
Preparer’s Ceremony
The preparer interacts with the envelope and its documents through the Preparer’s Ceremony. During the ceremony, the preparer reviews the documents and fills out input places assigned to them. These places may include:- Text input fields for names, dates, or other information
- Checkboxes for selecting options
- Other data entry fields as defined in the document


Preparers do not create a record on the Audit Log. Only signers have their actions recorded in the audit log that is included in the deliverable.
Workflow Example
A typical workflow involving a preparer:Preparer completes their ceremony
The preparer enters required information (e.g., pricing, dates, terms).
Subsequent recipients see the data
Recipients after the preparer see the document with the preparer’s fields filled in.
Creating an Envelope with a Preparer
When creating an envelope, specifytype: "preparer" for recipients who should fill in information without signing.
Assigning Places to a Preparer
Preparers can fill in input places such as text inputs, checkboxes, and dropdowns. Places are assigned to an preparers using therecipient_key property. Signature and initials places cannot be assigned to preparers.
Next Steps
- Recipient object - Learn about recipient properties
- Recipient lifecycle - Understand recipient status transitions
- Envelope routing - Configure the order recipients interact with documents