Header
Include exhibit title, parent agreement name, effective date, and version or revision number so reviewers can immediately place the update in context and avoid misapplication of prior exhibit versions.
A clear Exhibit Update reduces ambiguity, aligns expectations, and creates an auditable record of changes tied to the original agreement. It minimizes disputes by documenting what changed, when, and by whom, and it supports regulatory and tax compliance when exhibits affect reporting or deliverables.
Internal stakeholders commonly responsible for updates include contract managers, legal counsel, and business operations teams who must ensure accuracy and authorization before distribution.
An employee with delegated signing authority may sign if the parent agreement permits delegation. Confirm corporate resolution, procurement limits, or delegation matrices before accepting the signature as binding.
An officer or officer-equivalent (CEO, CFO, COO) typically has express authority to execute contract amendments. Where authority is unclear, obtain a confirming delegation or board minute to prevent later disputes.
Include exhibit title, parent agreement name, effective date, and version or revision number so reviewers can immediately place the update in context and avoid misapplication of prior exhibit versions.
A one- or two-sentence description that explains why the exhibit is being updated, summarizing the substantive change without repeating the full exhibit text.
Provide the amended exhibit text with tracked changes or show 'deleted' and 'added' language. When entire exhibits are replaced, include both the prior and the replacement exhibit for clarity.
Cite the governing clause in the parent agreement that authorizes amendments and any internal change control numbers used by project or contract management systems.
Provide printed name, title, company name, date, and witness or notary fields if required by the parent agreement or applicable law; identify signer authority explicitly.
List supporting documents, version-controlled exhibits, and any approvals or purchase orders that must accompany the update for downstream processing.
| Field | Configuration |
|---|---|
| Template | Create a reusable template with locked reference fields and required signature blocks. |
| Recipients | Define signer order and role-based recipients to enforce approvals. |
| Authentication | Select email link, SMS code, or stronger methods for sensitive exhibits. |
| Notifications | Enable reminders and completion notifications for auditability. |
Use an eSignature platform that supports audit trails, required authentication, and the file formats used by your organization.
Determine whether the update is retroactive or prospective and document the date clearly.
Set an internal deadline to secure all required signatures before implementation.
Account for any notice periods triggered by the change per the parent agreement.
Coordinate with finance for period-end recognition and billing cycles.
Mark records for retention after execution per corporate policy.
Draft finalized and versioned for review; includes change log and attachments.
Legal and finance approvals obtained according to signing thresholds.
All parties sign using chosen authentication and witness/notary processes.
Executed exhibit filed in the repository and relevant teams receive notice.
| Criteria | Exhibit Update | Amendment | Addendum |
|---|---|---|---|
| Primary Purpose | replace or revise exhibit text | change contract terms | add supplemental terms |
| Reference | exhibit-specific | agreement clause | agreement attachment |
| Execution | same signature block typical | often requires full signatures | typically requires signatures |
| Scope | limited to exhibit content | broad contractual scope | narrow supplemental scope |
Export a PDF/A copy with an embedded audit trail and visible signature blocks for long-term storage and distribution.
Keep an editable copy for internal records only; do not circulate as the executed version to external parties.
Download the full signed package including audit report, certificate of completion, and any attachments in one file set.
Store the executed file in the contract management system with metadata: effective date, parties, and change summary.