Can an RSA be e-signed?

Yes. Electronic signatures meet ESIGN (15 U.S.C. ch. 96) and UETA requirements in most U.S. jurisdictions when intent and consent are present and records are retained.

Is notarization required?

Not usually for RSAs. Notarization is sometimes used to verify identity or for state-specific formalities; treat notarization as optional unless state law or company policy says otherwise.

What about 83(b) elections?

An RSA should note 83(b) election rights and filing deadlines; recipients must file Form 83(b) with the IRS within 30 days of grant to preserve election benefits.

Who can sign for the company?

Typically an authorized officer identified in corporate minutes or a designee with written delegation. Confirm authorization before accepting the signature.

How to correct errors after signing?

Execute an amendment or corrective addendum signed by all original parties. Keep copies of both documents and the reason for the change.

How long to keep executed RSAs?

Retain executed RSAs for the longer of the agreement term plus three years or applicable federal/state retention periods; follow IRS and industry rules.

Business RSA Document

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

BUSINESS RSA DOCUMENT

This Business RSA Document (the "Agreement") is entered into as of by and between the parties set forth below.

Party A: Legal Entity Name Party A: Principal Address Party A: Primary Contact Party B: Legal Entity Name Party B: Principal Address Party B: Primary Contact

RECITALS

WHEREAS, Party A is engaged in the development, marketing and commercialization of certain products and services and wishes to obtain the services and revenues described in this Agreement; and

WHEREAS, Party B has the capability to perform the services and to share in revenues in accordance with the terms set forth herein; and

WHEREAS, the parties desire to set forth the terms governing their revenue sharing arrangement and related obligations.

SCOPE OF WORK

Party B shall perform the services and deliverables described below in accordance with the schedules and performance standards specified. All services must conform to applicable professional standards and any specifications agreed in writing.

Detailed Scope of Work

PAYMENT TERMS

In consideration of the services and rights granted herein, Party A shall pay Party B as follows:

Revenue Share Percentage (if applicable) Guaranteed Minimum Payment (if applicable) Payment Schedule and Calculation Method

Payments due to Party B shall be remitted within days of invoice or calculation, together with an itemized statement showing gross revenues, deductions and computation of the share due to Party B.

Late Payment Fee

TERM AND TERMINATION

The initial term of this Agreement shall commence on and shall continue until unless earlier terminated in accordance with this Section.

Either party may terminate this Agreement for material breach by the other party if such breach remains uncured for a period of days after receipt of written notice specifying the breach.

Termination Notice Period

Upon termination for any reason, all payments then due shall become immediately payable and each party shall return or destroy Confidential Information as provided below.

CONFIDENTIALITY

"Confidential Information" means non-public information disclosed by one party to the other in any form that is designated as confidential or that reasonably should be understood to be confidential. Each party shall: (a) use Confidential Information solely for the purposes of performing under this Agreement; (b) restrict disclosure to employees, contractors or advisors who have a need to know and who are bound by confidentiality obligations at least as protective as those herein; and (c) take reasonable measures to protect such Confidential Information from unauthorized use or disclosure.

The obligations set forth in this Section shall survive termination of this Agreement for a period of years, except that trade secrets shall be protected for so long as they meet the legal definition of a trade secret.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of laws principles. The parties consent to jurisdiction and venue in the courts located within that State for any action arising out of this Agreement.

ENTIRE AGREEMENT

This Agreement, including all exhibits and schedules hereto and any written amendments signed by both parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations and understandings, whether written or oral. No modification of this Agreement shall be effective unless in a written instrument signed by duly authorized representatives of both parties.

MISCELLANEOUS

Assignment: Neither party may assign or delegate its rights or obligations under this Agreement without the prior written consent of the other party, except to an affiliate or in connection with a merger or sale of substantially all assets, provided that the assignee agrees in writing to be bound by the terms of this Agreement.

Remedies: The rights and remedies provided in this Agreement are cumulative and in addition to any other rights or remedies available at law or in equity. Irreparable harm: Each party acknowledges that a breach of the confidentiality obligations may cause irreparable harm for which monetary damages are inadequate, entitling the non-breaching party to injunctive relief.

Party A:

By:

Date:

Party B:

By:

Date:

What the Business RSA Document Is and when it applies

The Business RSA Document (Restricted Stock Agreement or RSA) is a written contract that governs the conditional grant, vesting, transfer restrictions, and tax treatment of company stock issued to founders, employees, or contractors. It records the number of shares, vesting schedule, repurchase or forfeiture rights, and any restrictions on transfer or sale. An RSA typically includes representations, confidentiality provisions, and termination effects, and it works alongside equity award plans and board resolutions to create a legally enforceable equity interest in the issuing corporation.

Why a clear Business RSA Document matters

A precise RSA defines ownership expectations, reduces disputes over vesting and transfer, and clarifies tax obligations for issuer and recipient. Properly executed RSAs support downstream securities compliance and make it easier to manage equity onboarding and exit events under ESIGN (15 U.S.C. ch. 96) and state electronic transactions laws (UETA).

Who prepares and signs a Business RSA

Common participants span company and recipient roles and internal reviewers before signature.

Company legal or HR teams managing equity grants, ensuring plan compliance and corporate approvals.
Recipients (employees, founders, contractors) who review vesting, tax election, and transfer restrictions.
Outside counsel or finance teams for tax advice, 83(b) election coordination, and securities compliance.

In practice, RSAs are routed to corporate signatories, the recipient, and retained in personnel and equity ledgers after execution.

Step-by-step: completing a Business RSA

Follow a consistent sequence to reduce errors: prepare, verify corporate approvals, fill fields, obtain signatures, and file copies with HR and finance.

01

Prepare: Confirm plan authority and board resolution before populating the RSA.
02

Populate: Enter grant specifics, vesting, and repurchase rights accurately.
03

Review: Have legal and finance confirm tax treatment and securities compliance.
04

Execute: Collect signatures, record the grant, and store executed copies.

How to set up an electronic RSA workflow

Configure signing order, authentication level, and recipient notifications before sending the RSA for signature.

Field	Configuration
Signing Order	Company signatory → Recipient → Witness (if required)
Authentication	Email link or SMS code; use stronger methods for key executives
Notifications	Enable reminders and completion notices for all parties
Audit Trail	Capture IP, timestamps, and action history

Technical considerations for eSigning and eSubmission

Choose a platform that supports required authentication, audit trails, and storage formats for corporate records.

File formats: PDF, DOCX supported for signed, auditable output
Integrations: Connectors for HR and document storage (e.g., NetSuite, Google Workspace)
Compliance: BAA, SOC 2, and ESIGN/UETA support where required

Ensure the platform preserves a complete audit trail, stores signed PDFs securely, and meets any industry-specific compliance obligations.

Where signed RSAs are filed and who receives copies

Routing after signature should be predictable: record keeping, payroll, and corporate secretary functions need copies.

Company Records: Stock ledger entry and corporate minute book updates.
HR/Payroll: Copies for compensation and tax withholding.
Recipient: Signed PDF delivered to the recipient for personal records.
Legal Counsel: Retain for securities and tax compliance review.

Essential data fields to include on every Business RSA

Grant Date: MM/DD/YYYY

Share Count: Number of shares

Vesting Terms: Cliff and schedule

Repurchase Terms: Trigger events

Tax Notice: 83(b) election status

Governing Law: State name

Common preparation mistakes to avoid

Using ambiguous vesting language that omits cliff periods or triggers, which creates interpretation disputes and enforcement delays.
Failing to verify corporate authority or board approval prior to grant, risking invalidation or later corrective filings.
Mixing share classes or failing to reference the applicable equity plan, leading to ledger inconsistencies and administrative errors.
Neglecting to document whether an 83(b) election was filed and the date, complicating tax reporting for recipient and issuer.

Potential legal and tax consequences of errors

Tax Misclassification: IRS penalties possible

Securities Violations: State or federal fines

Forfeiture Disputes: Litigation risk

Recordkeeping Failures: Audit exposure

Missing 83(b): Unfavorable tax timing

Invalid Execution: Contract unenforceable

Real-world examples of RSAs in use

These examples show how companies used RSAs to document equity grants, streamline signing, and preserve compliance.

Optica Ventures (COO)

Optica granted early founder equity with clear vesting and repurchase terms to prevent future disputes.

The company used concise vesting milestones tied to performance goals.
The executed RSAs simplified cap table management and made subsequent funding rounds cleaner by preventing ambiguity about outstanding vested and unvested shares.

Martin Properties (Founder)

Real-estate founder issued RSAs to key hires with time-based vesting and change-of-control clauses.

Signatures were collected electronically to speed onboarding.
Having executed RSAs integrated with payroll reduced onboarding friction, clarified ownership percentages for investors, and preserved enforceability across jurisdictions.

eSignature vendor comparison for Business RSA document workflows

Comparison of baseline pricing and common capabilities. Prices reflect published per-user annual billing tiers and standard feature availability.

	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 credit card required	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes (Business Premium)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA available)	Yes (BAA available)	Yes (BAA available)	No	No

Practical tips for accurate and efficient RSA completion

Apply consistent templates, centralize recordkeeping, and standardize signatory authority to minimize rework and compliance risk.

Use a single template

Standardized language reduces negotiation time and avoids missing clauses across grants.

Document approvals

Capture board or committee resolutions in the file before signature to prove authority.

Track 83(b)

Record whether recipients filed 83(b) elections and keep a copy for payroll and tax records.

Store securely

Maintain signed copies in a tamper-evident archive with access controls.

Frequently asked questions about Business RSA Documents

Answers to common questions about execution, tax consequences, and electronic signatures for RSAs.

Need help? Contact support

Can an RSA be e-signed?
Yes. Electronic signatures meet ESIGN (15 U.S.C. ch. 96) and UETA requirements in most U.S. jurisdictions when intent and consent are present and records are retained.
Is notarization required?
Not usually for RSAs. Notarization is sometimes used to verify identity or for state-specific formalities; treat notarization as optional unless state law or company policy says otherwise.
What about 83(b) elections?
An RSA should note 83(b) election rights and filing deadlines; recipients must file Form 83(b) with the IRS within 30 days of grant to preserve election benefits.
Who can sign for the company?
Typically an authorized officer identified in corporate minutes or a designee with written delegation. Confirm authorization before accepting the signature.
How to correct errors after signing?
Execute an amendment or corrective addendum signed by all original parties. Keep copies of both documents and the reason for the change.
How long to keep executed RSAs?
Retain executed RSAs for the longer of the agreement term plus three years or applicable federal/state retention periods; follow IRS and industry rules.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now