Grant of Rights
Specifies whether upgrades are included, limited to versions, or available for separate purchase; clarifies license scope and transfer restrictions.
A written Software Upgrade License reduces disputes by defining what constitutes an upgrade, when updates are delivered, who pays, and how compatibility and support are handled. Clear terms help manage risk, allocate support costs, and provide evidence of agreed rights across vendor and customer systems.
This document is used by licensing teams, procurement, and technical stakeholders to align commercial and technical upgrade expectations.
Each stakeholder group contributes different inputs — legal provides clauses, finance approves fees, and technical teams confirm compatibility and acceptance criteria.
Specifies whether upgrades are included, limited to versions, or available for separate purchase; clarifies license scope and transfer restrictions.
Defines what counts as an upgrade versus a patch, whether major releases are included, and whether feature additions fall under the license.
Sets response times, severity levels, update cadence, and whether remote or on-site support is included or billable.
Describes pricing model for upgrades, invoicing schedule, refunds for failed upgrades, and any recurring maintenance charges.
Allocates responsibility for testing upgrades, defining acceptance criteria and rollback procedures in case of incompatibility.
Protects vendor intellectual property, limits reverse engineering, and requires handling of confidential upgrade code and release notes.
| Field | Configuration |
|---|---|
| Access controls | Set role-based signer order and permissions |
| Conditional fields | Show upgrade options only if paid box selected |
| Signature authentication | Choose email, SMS code, or KBA as needed |
| Retention settings | Enable export to PDF/A and archive copies |
Decide how the agreement will be sent, signed, and stored based on your security, integration, and format needs.
Use eSignature platforms that capture an audit trail, timestamp, and signer attribution; verify export formats and integration points before large-scale rollout.
Date when upgrade obligations begin
Vendor must deliver upgrades within agreed days
Time for licensee to test and provide notice
Invoice frequency and payment due date
Advance notice required to end renewal
A technical integration team required version-specific upgrade paths
A compliance-led firm required strict audit trails for every release
An officer or director with delegated contract authority should sign for commercial license obligations; ensure corporate records authorize the signer and verify title and signature authority.
An IT leader or authorized technical manager signs acceptance of upgrade testing and compatibility criteria where specific technical consent is required.
| 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 |