Establishing secure connection…Loading editor…Preparing document…

Legal BCC Rider Agreement

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

LEGAL BCC RIDER AGREEMENT

This Legal BCC Rider Agreement ("Rider") is made effective as of by and between Client Name: , with principal place of business at and Service Provider Name: , with principal place of business at .

RECITALS

WHEREAS, the parties entered into a principal agreement identified as the Principal Agreement effective on (the "Principal Agreement"); and

WHEREAS, the parties desire to amend and supplement the Principal Agreement by adding certain requirements, procedures and obligations relating to the BCC subject described below; and

WHEREAS, the parties intend that this Rider be read together with and form a part of the Principal Agreement, and that the terms of this Rider shall govern to the extent of any inconsistency.

NOW, THEREFORE

In consideration of the mutual covenants contained herein and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. DEFINITIONS

1.1 "BCC Subject" means the matter set forth by the parties in the field below describing the specific scope of this Rider. Parties shall specify the subject matter, which will govern interpretation and obligations under this Rider.

1.2 "Rider" means this Legal BCC Rider Agreement, including all attachments and schedules specifically incorporated by reference herein.

2. INCORPORATION; PRIORITY

2.1 This Rider is incorporated into and made part of the Principal Agreement. Except to the extent expressly modified by this Rider, all terms, conditions and provisions of the Principal Agreement remain in full force and effect.

2.2 In the event of a conflict between the terms of this Rider and the Principal Agreement, the terms of this Rider shall control with respect to the BCC Subject.

3. SCOPE AND OPERATION

3.1 The parties agree that the obligations described in this Rider apply to all activities, communications and deliverables that relate to the BCC Subject. The party with primary operational responsibility shall be identified here:

3.2 Operational Procedures. The responsible party shall implement reasonable procedures, controls and documentation necessary to effectuate the BCC Subject, including but not limited to creation and maintenance of policies, logging of relevant activities, training of personnel and retention of records in accordance with Section 6 (Records and Audit).

4. DUTIES, REPRESENTATIONS AND WARRANTIES

4.1 Each party represents and warrants that it has the full right, power and authority to enter into this Rider and to perform its obligations hereunder.

4.2 Compliance. Each party shall comply with all applicable laws, regulations and industry standards applicable to its performance under this Rider and shall not knowingly take any action that would cause the other party to be in breach of applicable law.

5. CONFIDENTIALITY AND DATA PROTECTION

5.1 Confidential Information. For the purposes of this Rider, Confidential Information includes any non-public information exchanged in connection with the BCC Subject. Each party agrees to protect Confidential Information using at least the same degree of care it uses to protect its own confidential information, but in no event less than reasonable care.

5.2 Permitted Disclosures. Confidential Information may be disclosed to a party's employees, agents or contractors who have a legitimate need to know for performance under this Rider, provided that such recipients are bound by confidentiality obligations no less protective than those in this Rider.

6. RECORDS, AUDIT AND REPORTING

6.1 Records. Each party shall maintain complete and accurate records relating to performance under this Rider for a period of from the date of creation.

6.2 Audit Rights. Upon reasonable prior written notice, a party may, not more than once annually, audit the other party's records and procedures insofar as they pertain to the BCC Subject. Audits shall be conducted during normal business hours and in a manner designed to minimize disruption.

7. INDEMNIFICATION; LIMITATION OF LIABILITY

7.1 Indemnification. Each party (the "Indemnifying Party") shall indemnify, defend and hold harmless the other party (the "Indemnified Party") from and against all third-party claims, liabilities, losses, damages and expenses arising out of or resulting from the Indemnifying Party's breach of this Rider, negligence or willful misconduct.

7.2 Limitation of Liability. Except for liability arising from a party's willful misconduct or gross negligence, each party's aggregate liability for claims arising under this Rider shall be limited to direct damages not to exceed or the amount paid under the Principal Agreement in the 12 months preceding the event, whichever is greater. Neither party shall be liable for incidental, consequential or punitive damages.

8. TERM AND TERMINATION

8.1 Term. This Rider shall commence on the Effective Date and shall continue in effect for the duration of the Principal Agreement unless earlier terminated in accordance with this Rider.

8.2 Termination for Cause. Either party may terminate this Rider 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.

9. NOTICES

All notices required or permitted under this Rider 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.

10. AMENDMENTS; WAIVER; COUNTERPARTS

10.1 Amendments. No amendment to this Rider shall be effective unless in writing and signed by authorized representatives of both parties.

10.2 Waiver. No waiver by either party of any breach of this Rider shall constitute a waiver of any other breach or of the same breach at a different time.

10.3 Counterparts. This Rider 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.

11. GOVERNING LAW; ENTIRE AGREEMENT; SEVERABILITY

11.1 Governing Law. This Rider shall be governed by and construed in accordance with the laws of the state or jurisdiction selected by the parties: , without regard to its choice of law principles.

11.2 Entire Agreement. This Rider, together with the Principal Agreement and any attachments expressly incorporated herein, constitutes the entire agreement of the parties with respect to the BCC Subject and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral, relating to such subject.

11.3 Severability. If any provision of this Rider is held to be invalid or unenforceable, the remainder of this Rider shall remain in full force and effect and the invalid or unenforceable provision shall be replaced by a valid and enforceable provision that most closely reflects the parties' original intent.

12. MISCELLANEOUS PROVISIONS

12.1 Survival. The provisions of this Rider that by their nature survive termination or expiration of the Principal Agreement shall so survive, including but not limited to confidentiality, indemnification and limitation of liability provisions.

12.2 Assignment. Neither party may assign its rights or delegate its obligations under this Rider without the prior written consent of the other party, except to a successor in interest by merger or sale of substantially all assets.

Party A (Client):

By:

Date:

Party B (Service Provider):

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What a Legal BCC Rider Agreement Is and when it’s used

A Legal BCC Rider Agreement is a contract rider appended to a primary agreement that adds, modifies, or clarifies specific terms related to billing, compliance, counterpart communication, or business continuity clauses. It is not a standalone contract but becomes enforceable when incorporated by reference into the underlying agreement. In the United States, electronic execution of riders is generally valid under the ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes when parties demonstrate intent, consent, attribution, and the ability to retain the record.

Why parties include a BCC rider in contracts

A BCC rider narrows or extends obligations without redrafting the entire agreement. It clarifies responsibilities, assigns risk, and records negotiated exceptions in one place to reduce disputes and administrative friction.

Why parties include a BCC rider in contracts

Who typically prepares and signs a BCC rider

The rider is most often drafted or approved by legal or contract teams and signed by authorized representatives of each party.

  • Corporate counsel and contract managers who need precise amendment language and internal sign-off.
  • Procurement or vendor managers negotiating billing and continuity terms for vendor agreements.
  • Real estate managers or lessors who need specific conditional clauses integrated with master lease documents.

Smaller businesses may use standardized rider templates and e-signature workflows to streamline execution, while regulated industries should review compliance or privacy addenda before signing.

Essential sections to include in a professional BCC rider

A clear structure makes the rider enforceable and easy to reference. Include headings and short clauses so the rider can be attached and incorporated by reference into the master agreement.

Parties & Recital

Identify each contracting party exactly as named in the main agreement and state the rider’s purpose and relationship to the primary contract.

Scope

Specify which provisions of the main agreement are changed, added, or excluded and attach any referenced exhibits or schedules.

BCC Clause

State the precise billing, communication, or business continuity change including triggers, thresholds, and responsibilities.

Effective Date & Term

Provide the effective date and whether the rider survives termination or automatically expires with the master agreement.

Signatures & Authority

Include signature blocks with printed names, titles, and a statement confirming signatories have authority to bind their organizations.

Integration & Governing Law

Confirm the rider is part of the contract and identify the governing law and dispute resolution procedure.

Key required data elements at a glance

Party Names: Exact legal names
Reference: Master agreement title
Effective Date: MM/DD/YYYY
Rider Terms: Summary line
Signatory Info: Printed name and title
Notary Block: If required

Simple step-by-step: complete and attach the rider

Follow these sequential steps to prepare, approve, execute, and distribute the rider with minimal risk.

  • 01
    Draft: Prepare the rider using exact references to the master agreement.
  • 02
    Internal Approval: Obtain legal and business sign-offs before sending to the counterparty.
  • 03
    Execute: Collect signatures and notarization if required.
  • 04
    Distribute: Attach rider to master file and provide copies to all parties.

How the rider integrates into the contract lifecycle

The rider moves through the same lifecycle as the main contract but must be explicitly referenced to ensure enforceability.

  • Attach: Physically or electronically attach the rider to the master agreement file.
  • Authorize: Confirm the signatory has authority per corporate resolution or delegation.
  • Execute: Sign in the prescribed order and notarize if needed.
  • Record: Store with the contract management system and update version control.

Platform and format requirements for digital completion

Choose a platform that preserves an auditable trail, supports required file types, and meets authentication needs.

  • File Types: PDF or DOCX preferred
  • Authentication: Email link, SMS code, or stronger
  • Audit Trail: Timestamps and IP capture

Confirm the chosen solution integrates with your document repository and supports retention and export formats required by auditors. Common integrations include Salesforce, Microsoft 365, NetSuite, Google Workspace, and cloud storage providers.

Typical digital workflow settings for a BCC rider

These common configuration choices reduce signer confusion and create a consistent audit trail for rider execution.

Field Configuration
Signature Field Required; visible
Date Field Auto-fill MM/DD/YYYY
Attachments Allow supporting exhibits
Authentication Email + optional SMS code

Key risks and potential consequences of an incorrect rider

Invalid Amendment: Rider may be unenforceable
Signature Defect: Execution challenge or delay
Misidentified Parties: Creates ambiguity in obligations
Missing Notarization: May void state-required acknowledgements
Tax Impact: Incorrect billing terms can trigger tax reporting issues
Operational Delay: Business continuity gaps or disputes

Common drafting and execution mistakes to avoid

  • Failing to reference the master agreement by title and date, which can create uncertainty about which contract the rider modifies.
  • Using vague or ambiguous language for key terms such as 'reasonable' or 'industry standard' without measurable benchmarks.
  • Allowing unauthorized signatories to execute the rider without confirming delegated authority or corporate resolutions.
  • Not preserving a single executed copy attached to the contract management system, leading to inconsistent follow-up and enforcement.

Practical tips for accurate, efficient completion and review

Adopt standardized templates, clear internal approval processes, and a consistent e-sign and filing workflow to lower risk and speed execution.

Use unambiguous references
Cite the master agreement by full title, effective date, and contract ID where available. This ensures the rider is attached to the correct primary document and prevents later disputes about applicability.
Confirm signer authority
Require confirmation that each signer has authority to bind their organization — a brief corporate resolution or authority line in the signature block reduces later challenges.
Preserve an audit trail
Capture timestamps, IP addresses, and method of authentication for every signatory. An auditable record supports enforceability under ESIGN (15 U.S.C. ch. 96) and UETA.
Version control and attachment
Store the executed rider with the master contract and update version metadata. Keep exhibits referenced by the rider as attachments to maintain contractual context.

Representative use cases for a Legal BCC Rider Agreement

Two concise examples show common situations where a BCC rider is useful and how it resolves specific gaps in the master agreement.

Case Study 1

A landlord adds a billing and continuity rider to a commercial lease to specify tenant responsibility for backup utilities

  • Rider defines billing thresholds and interruption notice procedures
  • The rider avoids re-opening the full lease while clarifying billing triggers and cure periods for both parties, reducing operational disputes.

Case Study 2

A healthcare vendor appends a BCC rider to address billing changes and data access during system migration

  • Rider adds a HIPAA-compliant data-handling clause and interim invoicing rules
  • The rider provides temporary billing procedures and a privacy addendum, ensuring continuity while preserving overall contract terms.

Who has authority to sign a BCC rider

General Counsel

Typically reviews and approves contractual language and may sign where the company delegates authority to legal officers; signatory authority should be confirmed in corporate documents.

Authorized Officer

C-suite executives or specifically delegated officers (e.g., VP of Contracts) may execute riders once internal approvals and any required corporate resolutions are in place.

eSignature vendor comparison for executing a BCC rider

This compact comparison highlights starting price and common capabilities across vendors; signNow appears first per page conventions.

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 Yes, 7-day free trial Varies Varies Varies Varies
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently asked questions about executing and enforcing a BCC rider

Answers to common execution, enforceability, and compliance questions for U.S. contracts and electronic workflows.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.