Grant of Rights
Specifies whether the contributor grants a license or transfers copyright, and defines the scope (e.g., worldwide, perpetual, sublicensable).
A CLA reduces legal uncertainty by documenting license scope, ensuring projects can redistribute and relicense contributed work, and protecting both contributors and maintainers from downstream IP disputes.
CLAs are used across open-source projects, corporate developer programs, and institutions that accept external contributions.
The agreement helps each party understand rights granted and the project’s permitted uses before contributions are accepted.
Specifies whether the contributor grants a license or transfers copyright, and defines the scope (e.g., worldwide, perpetual, sublicensable).
Clarifies whether the contributor retains copyright and grants a license, or assigns ownership outright, with consequences for future reuse.
Includes an express patent license or covenant not to sue for any patent claims the contributor holds that read on the contribution.
Contributor affirms originality, authority to grant rights, and that contribution does not infringe third-party rights or violate agreements.
Addresses waiver or assertion of moral rights where applicable to enable modification and redistribution without author attribution constraints.
Describes when rights lapse, remedies for breach, and dispute resolution basics such as governing law and venue.
| Field | Configuration |
|---|---|
| Authentication | Email link or SMS code for signer verification |
| Signing Order | Contributor signs first; project maintainer countersigns |
| Templates | Use a locked template to ensure consistent terms |
| Notifications | Automatic email confirmations to contributor and project |
Choose an eSignature platform that supports reliable audit trails, legal compliance, and the file formats you use for code or documents.
Ensure the chosen platform preserves a time-stamped certificate of completion and stores signed CLAs in a secure, searchable archive.
Effective when signed; include MM/DD/YYYY format
Maintainers often review CLAs within 3–14 business days
Respond to clarifying questions within 7–14 days
Project sends acceptance confirmation when linked to PR
Signed CLAs kept per governance retention policy
Project logs the signed CLA and tags the contributor record
Legal or maintainers check scope, corporate approvals, and patent language
Signed CLA is associated with the pull request or submission
Signed copy is stored and contributor receives confirmation
A volunteer submits a library used by the project
An employee contributes a plugin developed at work
Project maintainers or authorized representatives sign on behalf of the receiving organization. They should have documented authority to accept contributions and bind the project to license terms.
Individual contributors sign for personal contributions. Employees or contractors must be signed by the contributor and, when required, by an authorized officer of their employer.
| 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 vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |