Reference Clause
Identify the parent agreement by title, date, and parties so the add-on clearly amends that specific contract and avoids ambiguity about which agreement is modified.
A concise add-on reduces ambiguity, documents negotiated exceptions, and aligns operational obligations with the parent agreement. Electronically executed add-ons are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, but some categories remain excluded or require additional steps.
The following roles commonly prepare, approve, or sign contract add-ons depending on organizational structure and transaction complexity.
Ensure each role understands approval authority and retention responsibilities to prevent execution or enforcement problems later.
General counsel or senior attorney who prepares or approves add-on language and confirms that the modification aligns with corporate policy and legal risk tolerance. They often document delegated signing authority and review governing-law clauses to ensure enforceability.
A department head or project manager authorized to accept commercial or operational changes within preapproved thresholds. This person verifies scope, schedule, and budgets before routing the add-on for signature or escalation to legal.
Identify the parent agreement by title, date, and parties so the add-on clearly amends that specific contract and avoids ambiguity about which agreement is modified.
Describe exactly what is added, removed, or modified, using numbered subparts or exhibits when necessary to reduce interpretive disputes.
State when the add-on takes effect, and whether it applies retroactively, prospectively, or conditionally upon further events.
Provide printed names, titles, signature lines, and dates for each authorized signatory; include corporate acknowledgment for entities if required.
Confirm that the parties have authority to execute the add-on and that execution does not violate other obligations or require third-party consent.
List any exhibits, schedules, or DPA addenda attached to the add-on so all referenced material is included and preserved.
| Field | Configuration |
|---|---|
| Template Name | Standardize file name and versioning for reusability |
| Conditional Fields | Show fields only when specific answers apply |
| Signer Order | Set sequential or parallel signing as required |
| Authentication | Select email, SMS code, or stronger methods |
Choose platforms that accept standard formats and preserve audit information when sharing or storing executed add-ons.
Maintain an immutable audit trail and export signed PDFs in ISO-compatible formats; retain signature metadata for compliance and dispute resolution.
10 business days to propose changes
5 business days for legal review
Sign within 15 calendar days unless extended
30 days after effective date typical
Begin retention from effective date
Initiation of add-on drafting and allocation of responsible parties
Legal and business review conclude and prepare for approval
All authorized signers complete signatures and any notarization
Store final signed add-on with parent contract and update records
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no card | Varies | Varies | Limited trial | Limited trial |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 env/user/year | Varies by plan | Varies by plan | Varies by plan |