Establishing secure connection…Loading editor…Preparing document…

Legal RSA Document

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

RESTRICTED STOCK AWARD AGREEMENT (RSA)

This Restricted Stock Award Agreement (the "Agreement") is made as of the date: / / by and between Company Name: (the "Company"), and Participant Name: (the "Participant").

Recitals

WHEREAS, the Company maintains an equity incentive plan pursuant to which the Company is authorized to grant awards of its capital stock; and

WHEREAS, the Company desires to grant to Participant, and Participant desires to accept, an award of Restricted Shares subject to the terms and conditions set forth in this Agreement and the applicable plan.

WHEREAS, the parties intend for the award to be subject to restrictions, repurchase rights and other terms necessary to protect the Company’s and its stockholders’ interests.

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, the parties agree as follows:

1. Grant of Restricted Shares

1.1 Grant. Subject to the terms of this Agreement, the Company hereby grants to Participant shares of the Company's common stock (the "Restricted Shares"). The grant date of the Restricted Shares is the date set forth above.

2. Purchase Price

2.1 Consideration. The aggregate purchase price for the Restricted Shares shall be per share, for an aggregate purchase price of . Payment shall be made in cash or such other lawful consideration as the Board determines.

3. Vesting

3.1 Vesting Schedule. The Restricted Shares shall vest in accordance with the vesting schedule set forth below, subject to Participant's continued service through each applicable vesting date. Vesting is subject to acceleration only as expressly provided in this Agreement.

4. Restrictions; Legends

4.1 Restriction. The Restricted Shares shall be subject to transfer restrictions until vested. Participant shall not sell, pledge, assign, transfer or encumber any unvested Restricted Shares except to the extent permitted by the Plan and this Agreement.

4.2 Legends. Certificates (or book-entry entries) representing Restricted Shares shall bear such legends as the Company deems necessary to reflect restrictions on transfer and compliance with applicable securities laws.

5. Repurchase Right

5.1 Right to Repurchase. If Participant's service with the Company terminates for any reason prior to the vesting of all or a portion of the Restricted Shares, the Company shall have the option to repurchase the unvested Restricted Shares at the Repurchase Price set forth below.

6. Rights as a Stockholder

6.1 Until vested, Participant shall have the right to receive dividends or other distributions, but any dividends paid with respect to unvested Restricted Shares may be subject to the same restrictions and forfeiture provisions as the underlying Restricted Shares unless otherwise determined by the Board.

7. Tax Withholding

7.1 Participant agrees that the Company may satisfy any federal, state or local tax withholding obligations arising in connection with the vesting or settlement of the Restricted Shares by any lawful means, including withholding of cash, withholding of shares otherwise deliverable under this Agreement, or by requiring Participant to remit cash prior to the vesting or issuance of shares.

Cash withholding    Company withholding shares    Sell-to-cover arrangement

8. Representations and Warranties

8.1 Participant represents and warrants to the Company that: (a) Participant is acquiring the Restricted Shares for investment and not with a view to distribution; (b) Participant has received all information reasonably necessary to evaluate the investment; and (c) to Participant's knowledge, the acceptance of this Award does not violate any agreement to which Participant is a party.

9. Transfer; Assignment

9.1 This Agreement is binding upon and inures to the benefit of the parties and their respective successors and permitted assigns. Except as otherwise provided herein, Participant may not assign or transfer any rights under this Agreement or the Restricted Shares, except by will or by the laws of descent and distribution.

10. Notices

10.1 Any notice required or permitted under this Agreement shall be in writing and delivered to the addresses set forth below or to such other address as either party may designate by notice to the other.

11. Amendments; Waiver

11.1 No amendment, modification or waiver of any provision of this Agreement shall be effective unless in writing and signed by the party against whom enforcement is sought. No waiver by either party of any breach shall be deemed a waiver of any other or subsequent breach.

12. Governing Law

12.1 This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction in which the Company is organized without regard to that jurisdiction's choice-of-law principles.

13. Entire Agreement

13.1 This Agreement, together with the Plan and any award notice or schedules attached hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreements and understandings relating thereto.

14. Severability

14.1 If any provision of this Agreement is held to be invalid, illegal or unenforceable in any respect, the validity, legality and enforceability of the remaining provisions shall not in any way be affected or impaired thereby.

15. Counterparts

15.1 This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Signatures delivered by electronic means shall be binding as originals.

16. Miscellaneous

16.1 No Employment or Service Guarantee. Nothing in this Agreement shall confer upon Participant any right to continue in the employ or service of the Company or interfere with or limit in any way the rights of the Company to terminate Participant's service at any time.

Company Printed Name:

By:

Participant Printed Name:

By:

Company Date:

Participant Date:

Enter text✕

What the Legal RSA Document Is and when it’s used

The Legal RSA Document is a formal written agreement template used to define rights, obligations, and deliverables between parties in commercial or corporate contexts. Depending on usage, RSA can refer to a revenue sharing agreement, restricted stock award, or another role-specific agreement; the template organizes recitals, operative clauses, signature blocks, and exhibits so obligations are clear. When executed properly the document creates enforceable contractual obligations governed by the chosen governing law and can be completed electronically under U.S. e-signature statutes when the required intent, consent, attribution, and retention conditions are met.

Why a clear Legal RSA Document matters

A precise RSA reduces ambiguity about payments, deliverables, and termination mechanics and limits downstream disputes. Proper formatting and required signatures improve enforceability under federal and state e-signature law, including ESIGN and UETA, and document retention practices support regulatory compliance.

Why a clear Legal RSA Document matters

Who typically prepares or signs an RSA

Multiple roles may draft, approve, or sign an RSA depending on organizational structure and transaction complexity.

  • Company legal or contracts team reviews legal clauses and ensures consistency with corporate policy.
  • Finance or accounting personnel confirm payment, reporting, and withholding provisions are correct.
  • Authorized executives or designated agents sign on behalf of the legal entity.

In larger transactions external counsel, compliance officers, and notaries may also be involved to satisfy regulatory or evidentiary needs.

Representative signers and their roles

Corporate Signatory

Vice presidents, general counsel, or other officers with delegated authority execute RSAs on behalf of the company; they confirm corporate approvals and ensure signature authority is documented in board resolutions or delegation records.

Individual Counterparty

An individual founder or contractor signs personally and accepts personal obligations; if signing for an entity they must identify their title and authority to bind the organization to the agreement.

Essential security and compliance checkpoints

Encryption: TLS 1.2/1.3; AES-256
Audit Trail: Detailed timestamp and IP logging
Access Controls: Role-based permissions required
HIPAA BAA: BAA required for PHI
Authentication: Email, SMS, or advanced options
Retention: Tamper-evident storage needed

Primary risks and legal consequences to avoid

Invalid Signature: Signature disputed; unenforceable
Missing Witness: State-specific witness defects
Late Filing: Statutory deadline exposure
Incorrect Party: Wrong entity obligated
Data Breach: Regulatory fines and liability
Ambiguous Terms: Litigation and remedial costs

Common preparation mistakes to watch for

  • Using inconsistent party names or abbreviations that don’t match formation documents leads to enforceability questions and delays in bank or registry acceptance.
  • Leaving monetary or schedule fields vague (for example, 'reasonable efforts') often causes disputes and can void payment obligations without remedial language.
  • Skipping clear signature authority evidence (board resolution or POA) increases risk that a counterparty will later challenge the agreement’s validity.
  • Failing to include governing law and venue produces uncertainty about dispute resolution and may complicate service of process and enforcement.

Step-by-step: completing the Legal RSA Document

Follow these steps in order to complete and execute an RSA accurately and consistently across parties.

  • 01
    Prepare: Assemble parties, exhibits, and definition list
  • 02
    Fill core fields: Enter names, dates, amounts, and scope
  • 03
    Review: Legal and finance verify key provisions
  • 04
    Execute: Obtain signatures and preserve audit trail

Configuring an online signing workflow

Set up signer order, authentication, and fields before sending to avoid rework and maintain a clear audit trail.

Field Configuration
Signer Order Sequential or parallel routing
Authentication Level Email link, SMS code, or KBA
Required Fields Signature, printed name, date
Attachments Permit supporting exhibits upload

Typical digital execution flow

A standard e-signature flow follows a consistent sequence from upload to archive to preserve intent and attribution.

  • Upload Document: Sender uploads final draft to platform
  • Place Fields: Insert signature, initials, and date fields
  • Invite Signers: Add signer emails or generate links
  • Complete Signing: Signers authenticate, sign, and receive copy

Technical considerations for e-submission

Confirm supported file formats, integrations, and authentication options when selecting an e-signature workflow.

  • File Formats: PDF, DOCX, or HTML supported
  • Integrations: Salesforce, NetSuite, Google Workspace
  • Browser Support: Modern Chrome, Edge, Safari required

Verify audit trail, encryption, and BAA availability for healthcare or regulated transactions before transmitting sensitive documents.

Core sections to include in a professional RSA

A complete RSA groups related provisions so obligations and remedies are clear; include essential legal, financial, and administrative sections.

Recitals

Contextual background facts and business purpose; use concise recitals to explain the transaction without creating additional obligations.

Payment Terms

Detailed schedule for payments, revenue share calculations, invoicing cadence, and any withholding or tax responsibilities.

Scope & Deliverables

Clear, measurable description of services or goods, acceptance criteria, and milestones to avoid performance disputes.

Representations

Statements of authority, capacity, and compliance; limit representations to material facts the parties can verify.

Confidentiality

Define protected information, exceptions, duration, and permitted disclosures; align with any separate NDA when necessary.

Termination

Events triggering termination, cure periods, post-termination obligations, and any wind-down or transition duties.

Supporting document elements to attach

Attach exhibits and schedules to keep the core agreement readable while preserving detailed technical or financial materials.

Exhibit A

Detailed fee schedule or revenue share calculation methodology; refer directly to exhibit when calculating amounts.

Exhibit B

Deliverable specifications, service level metrics, and acceptance tests tied to milestone payments.

Board Resolution

Evidence of corporate authorization where an entity signs; include as an exhibit to document signature authority.

Data Map

If data transfers occur, include a map showing data categories, purpose, and any applicable data protection measures.

Key dates and notice periods to track

Document dates determine performance windows, notice periods, and limitations; capture each critical deadline explicitly.

Effective Date:

When obligations commence; use MM/DD/YYYY format

Signature Date:

Date each party signs; differs from effective date if so specified

Payment Due:

Net terms or milestone dates for remittance

Notice Period:

Days required for breach cure or termination

Dispute Window:

Time to raise claims or seek arbitration

Typical milestones from draft to archive

Use a milestone view to coordinate drafting, approvals, execution, and recordkeeping tasks across teams.

01

Drafting

Prepare initial draft and exhibits, assign owner and version control

02

Internal Review

Legal and finance review and markups completed

03

Execution

Signatures collected and audit trail captured

04

Archive

Store executed copy with exhibits and retention metadata

How a Legal RSA Document compares to a standard NDA

Quick comparison highlights purpose and typical clauses so users can choose the right document type for their needs.

Criteria Legal RSA Document NDA
Purpose allocate rights and payments protect confidential information
Typical Signers commercial counterparties parties exchanging confidential data
Confidentiality often included as clause primary subject of agreement
Enforceable Remedies indemnities and payment remedies injunctive relief and damages

eSignature vendor comparison for executing the Legal RSA Document

Comparison of typical entry-level pricing and core capabilities. signNow is listed first per platform comparison standards.

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 (Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA available) Yes Yes No No

Practical examples of electronic RSA execution

Real-world examples show common outcomes when organizations move RSAs to a digital signing workflow.

Optica Ventures

The company moved routine contract signing online to reduce turnaround.

  • Resulted in fewer paper errors and faster receipt.
  • "The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers."

Martin Properties

A small broker used digital execution for revenue-sharing arrangements to close deals remotely.

  • Reduced physical meetings and courier time.
  • "I can process and execute all of these documents online with 100% compliance and built-in security."

Frequently asked questions about the Legal RSA Document

Answers to common legal and technical questions encountered when preparing, signing, and storing an RSA.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users