Collaborative Field Editing for eSignature
Let more than one signer fill in or correct the same contract field. No voiding, no resending.
- You choose who can edit each field
- Old and new values on record
Trusted by 50,000+ businesses worldwide
One wrong detail, one voided contract, one more resend
BoldSign’s collaborative field editing feature lets the right signer fix or fill that detail while signing.
Works in: the BoldSign web app and the BoldSign API.
A small fix means a full resend
Without shared fields, a wrong date or quantity means voiding the contract and sending it again.
With BoldSignThe signer corrects the shared field while signing. See how it works
Only the other side knows the detail
Some fields, such as a start date or a headcount, depend on what the other party confirms.
With BoldSignYou share that field so they can fill it in. See an example
No proof of who changed what
Edits agreed over email leave no clear record of the original value.
With BoldSignEvery change keeps its old and new value. See the record
How do you let more than one signer edit a contract field?
In BoldSign, you share a field with more than one signer. Each one can update it during their turn to sign.
-
Share the field and set its rules
The field’s owner is a collaborator by default. Add the other signers who may edit it, then pick its rules.
Configure fieldsEmily CarterStart dateCollaborators SettingsEmily Carter is included as a collaborator by default. You may select additional collaborators below.Search for collaboratorsMichael BrooksMichael BrooksRequire Initials For ChangesRequire Approval For ChangesRequired For CollaboratorsSample Configure fields screen: Emily Carter's Start date field is shared. A note says Emily Carter is included as a collaborator by default, Michael Brooks is ticked as an added collaborator, and initials, approval, and required value are turned on -
The first signer fills or edits it
Emily fills in the shared date like any other field. She changes it to 11/09/2026, then signs.
Required fields left 1Start signingFill ValueStart dateSignatureSign here*Sample signing page for Emily Carter: she changes the shared Start date field to 11/09/2026 before signing -
The next signer can change it again
Michael sees a note that a collaborator updated the field. His own change asks for his initials beside it.
Required fields left 2Next fieldSignedEmily CarterShared for collaboration - this field was updated by one of the collaborators.Start dateMBSignatureSign here*Sample signing page for Michael Brooks: a note says the field was updated by one of the collaborators, and Michael changes the start date to 11/16/2026 and adds his initials beside it -
Earlier signers approve the final value
With approval required, Emily gets an email to review Michael’s change and sign again.
EmailHi Emily Carter,The document “Service agreement” that you previously signed has been changed by a collaborator. Please review the changes and sign again to complete the process.Review ChangesSample BoldSign email asking Emily Carter to review a collaborator’s change to the Service agreement and sign again
How do you control the collaborative editing process?
BoldSign gives every shared field three optional rules. You turn them on in Collaborators Settings before you send.
Require Initials
Collaborators must provide their initials whenever they change the field value.
Require Approval
Any change a collaborator makes must be approved by signers who have already signed.
Required for Collaborators
Collaborators must complete the field. It cannot be left empty before signing.
How do you see who changed a shared field?
BoldSign records every change to a shared field. It keeps the old value, the new value, who changed it, and when.
-
An entry in the audit trail
The audit trail logs which field changed, who changed it, and the exact time.
-
Old and new values side by side
View changes in Document History shows each field’s previous value beside its updated value.
-
Re-sign requests on record
When a change needs approval, the history shows who was asked to re-sign and when.
-
Initials beside each edit, if you want them
You can ask each signer who edits the field to add their initials next to the new value.
-
Your signing order kept
Re-signing follows your signing order when you have set one.
Why choose BoldSign for collaborative field editing
BoldSign suits contracts where the other side must confirm a detail before everyone signs.
-
No void and resend
A signer fixes the shared field during signing, so you skip voiding and resending the contract.
-
Completed fields stay as signed
During re-signing, only shared fields can change. Every completed field stays as it was.
-
No account for collaborators
Collaborators edit and sign from their signing link, without a BoldSign account.
-
Help when you need it
Help by chat, email, or support ticket is included on every plan.
Is collaborative field editing safe?
Yes, BoldSign lets only the signers you choose change a shared field. Nothing else in the contract moves. Each edit lands in the document history, and earlier signers can be asked to approve it.
BoldSign encrypts every document twice with AES-256. Its security controls are independently audited for SOC 2 Type 2. Each standard is listed in your account’s Compliance page, shown below.
Compliance
BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.
Data Residency
Active (US - Global)Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.
HIPAA Compliance
EnabledEnable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.
PCI DSS
CompliantPayments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.
CCPA & CPRA
CompliantEnsures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.
SOC 2 Type II
CompliantBoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.
UETA & ESIGN
CompliantBoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).
eIDAS (SES)
CompliantBoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.
eIDAS (QES)
EnabledEnable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.
Limits to know before you use collaborative fields with BoldSign
BoldSign lets signers edit the fields you share. It does not let them rewrite the contract text.
- 2+recipients neededSingle-signer and self-signed documents cannot use shared fields.
- 5field typesTextbox, radio button, checkbox, editable date, and dropdown.
Before your first shared field
- In-person signers, group signers, and reviewers cannot be collaborators.
- Shared fields cannot be used with Print and Sign, data sync tags, conditional logic, or formula fields.
More guides on collaborative fields
- Guide
Collaborative fields, step by step
Setup, options, tracking, and notifications in one walkthrough.
Read the guide - Developers
Collaborative fields in the API
Set collaborators and rules when you send through the API.
Read the API guide - Help
Collaborator options explained
How initials, approval, and required fields behave.
Read the help article
Questions about editing contract fields before signing
What tools let multiple people edit a contract before signing?
BoldSign does, with its collaborative field editing feature. You choose which fields more than one signer can fill in or correct. BoldSign records each change.
Can signers edit a contract in real time?
No. Each signer edits shared fields during their own turn to sign. They never edit side by side at the same moment. The collaborative fields guide walks through the flow.
What happens if a field changes after someone has signed?
With Require Approval on, everyone who already signed is asked to review the change and sign again. Only shared fields stay editable while they re-sign.
Can developers set up shared fields through the API?
Yes. The BoldSign API sets collaborators and rules on a field when you send the document. The API guide has code samples.
Is collaborative field editing on every plan?
Yes. Collaborative field editing is included on every BoldSign paid plan, with no extra charge.
Last updated: October 17, 2026