Preamble
Reference the original Managed Network Agreement by title and execution date, identify the parties, and label the document clearly as 'Amendment One' to avoid confusion with other modifications.
Use this amendment to document agreed changes cleanly and avoid conflicts between prior contract language and new expectations; it preserves the original agreement while updating targeted terms. Electronic signatures executed under the ESIGN Act and state UETA/ESRA frameworks are generally recognized as legally binding for contract amendments.
Final signatures should come from individuals with express authority per corporate bylaws or delegation of signing authority.
Reference the original Managed Network Agreement by title and execution date, identify the parties, and label the document clearly as 'Amendment One' to avoid confusion with other modifications.
State brief background statements that explain why the parties are amending the agreement, such as new services, pricing changes, or regulatory requirements necessitating the update.
Provide precise strike-and-replace language or numbered clause additions. Use exact clause citations and insert full replacement text where appropriate to prevent divergent interpretations.
Declare the amendment's effective date using MM/DD/YYYY format and note whether changes apply prospectively, retroactively, or for future invoices and performance.
Document any new fees, credits, payment schedule changes, or service credits tied to the amendment and specify invoicing and payment timing.
Include signature lines, printed names, titles, dates, and any required witness or notarial blocks; indicate if electronic signatures are acceptable and under what authentication method.
| Field | Configuration |
|---|---|
| Authentication method | Email link with optional SMS code or KBA depending on risk and party agreement |
| Signature field types | Use signature, printed name, and date fields; add initial fields for multi-page acknowledgment |
| Conditional fields | Show rate or term fields only if a pricing change is selected to reduce signer confusion |
| Notifications and reminders | Enable automatic reminders and final signed-copy distribution to all parties |
Maintain copies in both the contract management system and a secure backup location; ensure platform logs and certificates are retained for the full retention period.
Specify MM/DD/YYYY and whether the change is retroactive or prospective.
Align pricing changes with the next invoice period to avoid proration disputes.
Set an internal deadline for legal and finance approvals before execution.
Schedule technical changes during maintenance windows when possible.
Start retention from the amendment effective date for compliance timelines.
Complete the amended clause language and internal redline review.
Obtain counsel approval for liability and governing-law implications.
Collect signatures from authorized signatories and record timestamps.
Distribute to finance, operations, and archive the final document.
| 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 | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies | Varies | Varies |
Typically a vice president, director, or other officer with delegated signing authority signs on behalf of the company. Confirm authority via corporate resolution, delegation of authority, or Board minutes to avoid later challenges.
A contracts manager or corporate counsel may sign under delegated authority for routine amendments. Maintain a record of delegation and any limits on monetary or term changes.