Establishing secure connection…Loading editor…Preparing document…

Collateral Agreement

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

Rider or Collateral Agreement to HIPAA Privacy Compliance Agreement for Business Associates

Agreement made on the (date), between

(Name of Covered Entity), a professional corporation organized and existing under the laws of the state of (name of state), with its principal office located at , referred to herein as Covered Entity, and (Name of Business Associate), a corporation organized and existing under the laws of the state of (name of state), with its principal office located at , referred to herein as Business Associate.

Covered Entity and Business Associate shall collectively be known herein as the Parties.

Whereas, Covered Entity is a health care provider whose activities are generally described as: (describe)

Whereas, Business Associate is in the business of providing services to the health care industry and its activities are generally described as: (describe)

Whereas, Covered Entity wishes to continue an existing business relationship with Business Associate that has been memorialized in a separate services agreement which is still in effect; and

Whereas, the nature of the existing contractual relationship between Covered Entity and Business Associate may involve the exchange of Protected Health Information (PHI) as that term is defined under the Health Insurance Portability and Accountability Act of 1996 (HIPAA) as amended by Health Information Technology for Economic and Clinical Health Act of 2009 (the HITECH Act), including all pertinent regulations issued by the Department of Health and Human Services (HHS);

I. Definitions

A. Breach. Breach has the same meaning as this term has in §13400 of Health Information Technology for Economic and Clinical Health Act of 2009 (the HITECH Act).

B. Business Associate. Business Associate shall mean .

C. Covered Entity. Covered Entity shall mean .

D. Designated Record Set. Designated Record Set has the same meaning as this term has in 45 CFR §164.501.

E. Individual. Individual has the same meaning as this term has in 45 CFR §164.501.

F. Privacy Rule. Privacy Rule shall mean the Standards for Privacy of Individually Identifiable Health Information at 45 CFR Part 160 and Part 164, Subparts A and E, as amended by the HITECH Act.

G. Protected Health Information. Protected Health Information (or PHI) has the same meaning as this term has in 45 CFR §160.103 (as amended by the HITECH Act), limited to the information created or received by Business Associate from or on behalf of Covered Entity.

H. Required By Law. Required By Law has the same meaning as this term has in 45 CFR §164.501.

I. Security Standards. Security Standards means the security standards for protection of PHI promulgated by the Secretary in Title 45 C.F.R.

J. Unsecured Protected Health Information. Unsecured Protected Health Information shall mean Protected Health Information (PHI) that is not secured through the use of a technology or methodology specified by the Secretary in regulations or as otherwise defined in the §13402(h) of the HITECH Act.

K. Any prospective amendment to the laws referenced in this definitional section prospectively amend this agreement to incorporate said changes by Congressional act or by regulation of the Secretary of HHS.

II. Obligations and Activities of Business Associate.

A. Business Associate agrees to not use or disclose Protected Health Information other than as permitted or required by the Agreement or as Required By Law.

B. Business Associate agrees to employ administrative, physical, and technical safeguards meeting required Security Standards for business associates as Required By Law to prevent disclosure or use of PHI other than as allow by this Agreement.

C. Business Associate agrees to mitigate, to the extent practicable, any harmful effect that is known to Business Associate of a use or disclosure of PHI held by Business Associate in violation of the requirements of this Agreement.

D. Business Associate agrees to report to Covered Entity any use or disclosure of the Protected Health Information not provided for by this Agreement of which it becomes aware.

E. If a breach of unsecured protected health information occurs at or by Business Associate, the Business Associate must notify Covered Entity following the discovery of the breach without unreasonable delay and, in all cases, no later than 60 days from the discovery of the breach. To the extent possible, the Business Associate should provide the Covered Entity with the identification of each individual affected by the breach as well as any information required to be provided by the Covered Entity in its notification to affected individuals. Business Associates shall comply with all regulations issued by HHS and applicable state agencies regarding breach notification to Covered Entity.

F. Business Associate agrees to ensure that any agent, including a subcontractor, to whom it provides Protected Health Information received from, or created or received by Business Associate on behalf of Covered Entity agrees to the same restrictions and conditions that apply through this Agreement to Business Associate with respect to PHI.

G. Business Associate agrees, at the request of Covered Entity, to provide Covered Entity (or a designate of Covered Entity) access to Protected Health Information in a Designated Record Set in prompt commercially reasonable manner in order to meet the requirements under 45 CFR §164.524.

H. Business Associate agrees to make any amendment(s) to Protected Health Information in a Designated Record Set that the Covered Entity directs or agrees to pursuant to 45 CFR §164.526 at the request of Covered Entity or an Individual, in a prompt and commercially reasonable manner.

I. Business Associate agrees to make internal practices, books, and records, including policies and procedures and Protected Health Information, relating to the use and disclosure of Protected Health Information received from, or created or received by Business Associate on behalf of, Covered Entity available to the Covered Entity, or to the Secretary (including official representatives of the Secretary), in a prompt commercially reasonable manner for purposes of determining Covered Entity's compliance with the Privacy Rule.

J. Business Associate agrees to document such disclosures of Protected Health Information and information related to such disclosures as would be required for Covered Entity to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with 45 CFR §164.528.

K. Business Associate agrees to provide to Covered Entity or an Individual, in a prompt commercially reasonable manner, information collected in accordance with this Agreement, to permit Covered Entity to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with 45 CFR §164.528.

III. Permitted Uses and Disclosures by Business Associate.

Except as otherwise limited in this Agreement, Business Associate may use or disclose Protected Health Information, as follows:

A. On behalf of, Covered Entity, provided that such use or disclosure would not violate the Privacy Rule if done by Covered Entity.

B. Except as otherwise limited in this Agreement, Business Associate may disclose Protected Health Information for the proper management and administration of the Business Associate, provided that disclosures are required by law, or Business Associate obtains reasonable assurances from the person to whom the information is disclosed that it will remain confidential and used or further disclosed only as required by law or for the purpose for which it was disclosed to the person, and the person notifies the Business Associate of any instances of which it is aware in which the confidentiality of the information has been breached.

IV. Obligations of Covered Entity

Covered Entity shall notify Business Associate of any limitation(s) in its notice of privacy practices of Covered Entity in accordance with 45 CFR §164.520, to the extent that such limitation may affect Business Associate's use or disclosure of Protected Health Information.

A. Covered Entity shall notify Business Associate of any changes in, or revocation of, permission by Individual to use or disclose Protected Health Information, to the extent that such changes may affect Business Associate's use or disclosure of Protected Health Information.

B. Covered Entity shall notify Business Associate of any restriction to the use or disclosure of Protected Health Information that Covered Entity has agreed to in accordance with 45 CFR §164.522, to the extent that such restriction may affect Business Associate's use or disclosure of Protected Health Information.

C. Covered Entity shall not request Business Associate to use or disclose Protected Health Information in any manner that would not be permissible under the Privacy Rule if done by Covered Entity. Nothing in this paragraph shall restrict the ability of Business Associate to use or disclose PHI as set forth in Paragraph III.A herein.

V. Remedies in Event of Breach.

Business Associate hereby recognizes that irreparable harm will result to Covered Entity, and to the business of Covered Entity, in the event of breach by Business Associate of any of the covenants and assurances contained in Paragraphs II or III of this Agreement. As such, in the event of breach of any of the covenants and assurances contained in Paragraphs II or III above, Covered Entity shall be entitled to enjoin and restrain Business Associate from any continued violation of Paragraphs II or III. Furthermore, in the event of breach of Paragraphs II or III by Business Associate, Covered Entity shall be entitled to reimbursement and indemnification from Business Associate for the Covered Entity's reasonable attorney’s fees and expenses and costs that were reasonably incurred as a proximate result of the Business Associate's breach. The remedies contained in this Paragraph V shall be in addition to (and not supersede) any action for damages and/or any other remedy Covered Entity may have for breach of any part of this Agreement.

VI. Term and Termination.

A. Term of Agreement. The Term of this Agreement shall be effective as of the date given at the top of Page 1 herein, and shall terminate when all of the Protected Health Information provided by Covered Entity to Business Associate, or created or received by Business Associate on behalf of Covered Entity, is destroyed or returned to Covered Entity, or, if it is infeasible to return or destroy Protected Health Information, protections are extended to such information, in accordance with the termination provisions in this Section.

B. Termination for Cause. Upon Covered Entity's knowledge of a material breach by Business Associate, Covered Entity shall either:

1. Provide an opportunity for Business Associate to cure the breach or end the violation and terminate this Agreement if Business Associate does not cure the breach or end the violation within the time specified by Covered Entity;

2. Immediately terminate this Agreement if Business Associate has breached a material term of this Agreement and cure is not possible; or

3. If neither termination nor cure are feasible, Covered Entity shall report the violation to the Secretary.

C. Effect of Termination.

1. Except as provided in Paragraph VI.C.2 of this Section, upon termination of this Agreement, for any reason, Business Associate shall return or destroy all Protected Health Information received from Covered Entity, or created or received by Business Associate on behalf of Covered Entity. This provision shall apply to Protected Health Information that is in the possession of subcontractors or agents of Business Associate. Business Associate shall retain no copies of the Protected Health Information.

2. In the event that Business Associate determines that returning or destroying the Protected Health Information is infeasible, Business Associate shall provide to Covered Entity notification of the conditions that make return or destruction infeasible. Upon notification to Covered Entity that return or destruction of Protected Health Information is infeasible, Business Associate shall extend the protections of this Agreement to such Protected Health Information and limit further uses and disclosures of such Protected Health Information to those purposes that make the return or destruction infeasible, for so long as Business Associate maintains such Protected Health Information.

VII. Miscellaneous Terms.

A. State Law. If state law applicable to the relationship between Business Associate and Covered Entity contains additional or more stringent requirements than federal law for Business Associates regarding any aspect of PHI privacy, then Business Associate agrees to comply with the higher standard contained in applicable state law.

B. Consideration. Business Associate recognizes that the promises it has made in this Agreement shall, henceforth, be detrimentally relied upon by Covered Entity in choosing to continue or commence a business relationship with Business Associate.

C. Modification. This Agreement may only be modified through a writing signed by the Parties and, thus, no oral modification hereof shall be permitted. The Parties agree to take such action as is necessary to amend this Agreement from time to time as is necessary for Covered Entity to comply with the requirements of the Privacy Rule and the Health Insurance Portability and Accountability Act of 1996, as amended.

D. Notice to Covered Entity.

1. Any notice to Covered Entity provided for or concerning this Agreement shall be in writing and shall be deemed sufficiently given when sent by certified or registered mail if sent to the respective address of Covered Entity as set forth at the beginning of this Agreement.

2. Any notice to Business Associate provided for or concerning this Agreement shall be in writing and shall be deemed sufficiently given when sent by certified or registered mail if sent to the respective address of Business Associate as set forth at the beginning of this Agreement.

WITNESS our signatures as of the day and date first above stated.

By:

By:

Enter text✕

What a Collateral Agreement Is and When It Applies

A Collateral Agreement is a legally binding contract in which a borrower (debtor) grants a lender (secured party) an interest in specific property or assets to secure repayment of an obligation. Typical collateral includes personal property, equipment, inventory, accounts receivable, or real estate. The agreement defines the collateral, the security interest, the events of default, and remedies available to the secured party. It is commonly paired with a financing statement (UCC-1) or deed of trust to perfect the lien and establish priority against other creditors.

Why a Collateral Agreement Matters for Risk and Priority

A Collateral Agreement protects lender recovery rights and clarifies borrower obligations, reducing lender credit risk and disputes over asset ownership. It also allows secured parties to perfect and prioritize their lien under state UCC rules. Properly drafted collateral language and recording steps reduce the chance of subordinate claims and increase enforceability during default or bankruptcy.

Why a Collateral Agreement Matters for Risk and Priority

Who Typically Prepares and Signs a Collateral Agreement

Parties should confirm signatory authority, perfection steps, and recordkeeping responsibilities before execution to ensure priority and enforceability.

  • Lenders and Credit Departments: Draft and rely on precise collateral descriptions and perfection steps to reduce loss exposure.
  • Borrowers and Business Owners: Review representations, covenants, and scope of assets encumbered to avoid unintended liens on key property.
  • Outside Counsel and Title Agents: Verify recording strategy, UCC-1 sufficiency, and any state-specific notarization or witness requirements.

Essential Sections Every Professional Collateral Agreement Should Include

A clear, organized Collateral Agreement reduces ambiguity and supports lien perfection. The following components form the core of an enforceable security arrangement.

Parties

Full legal names and organizational type for debtor and secured party, including state of formation for entities and any DBAs, to avoid identity confusion at filing and enforcement stages.

Collateral

A precise description of the assets subject to the security interest—specific inventory, equipment serial numbers, or a clear catchall (after-acquired property) clause with necessary detail for perfection.

Grant Language

Unambiguous grant of a security interest in the listed collateral, describing scope, attachments, accession rules, and any excluded property to prevent disputes.

Perfection

Procedures for perfecting the security interest, typically by filing a UCC-1 financing statement, recording instruments for real property, and obtaining necessary acknowledgements or notices.

Representations

Debtor warranties about title, authority, and absence of other liens; creditor assurances on funds disbursal and lien priority procedures to allocate risk and remedies.

Remedies

Default definitions, cure periods, rights to repossess or foreclose, sale procedures, and allocation of proceeds, including commercially reasonable disposition standards.

Key Data Elements to Capture Precisely

Debtor Name: Exact legal name
Creditor Name: Full legal entity
Collateral Type: Inventory, equipment, real estate
Consideration: Loan amount or obligation
Effective Date: MM/DD/YYYY date
Perfection Method: UCC-1 or recording

How to Complete a Collateral Agreement: Step-by-Step

Follow these sequential steps to draft, execute, and perfect a Collateral Agreement while preserving priority and enforceability.

  • 01
    Draft Terms: Define parties, collateral, obligations, and events of default clearly.
  • 02
    Verify Identities: Match legal entity names to formation documents and IDs.
  • 03
    Sign and Date: Obtain authorized signatures and written dates from all parties.
  • 04
    File to Perfect: File UCC-1 or record deed/trust instrument as required.

Typical Routing and Submission Flow for Execution and Perfection

A clear routing workflow ensures timely signatures, notarization, and record filings to perfect the security interest.

  • Prepare Document: Finalize agreement and required annexes for signing.
  • Add Signers: List authorized signatories in signing order.
  • Authenticate: Apply agreed signer authentication methods.
  • File Records: Submit UCC-1 or record instruments with the county/state office.

Configuring an Online Completion Workflow

Set up your online workflow to capture signatures, required fields, and recording outputs in one pass.

Field Configuration
Signature Authentication Email, SMS code, or stronger KBA/SAML for high-value loans
Document Template Reusable template with conditional collateral sections
Conditional Fields Reveal additional clauses if specific collateral types selected
Recording Integration Export signed PDF and data to UCC-filing or county recorder

Digital Signing Considerations and Platform Integrations

Integrations for CRMs, document storage, and filing systems help automate UCC-1 creation and preserve completion evidence.

  • File Formats: PDF, DOCX, and TIFF supported
  • Common Integrations: Salesforce, NetSuite, Google Workspace
  • Security Standards: TLS 1.2/1.3 and AES-256 encryption

Key Deadlines and Timing Expectations

Timely signing and perfection are critical; missing deadlines can change lien priority or permit competing claims.

Signing Deadline:

Agree on execution date to lock obligations and collateral scope.

Recording Window:

File UCC-1 promptly after signing to establish priority against other creditors.

Perfection Period:

Perfection is effective when the financing statement is filed per state UCC rules.

Insurance Renewal:

Track insured collateral coverage and require evidence before renewal dates.

Amendment Deadlines:

Amend financing statements promptly after name or collateral changes.

Common Preparation Mistakes to Avoid

  • Using an informal or vague collateral description that leaves key assets ambiguous and weakens enforcement options in default.
  • Filing a UCC-1 with an incorrect debtor name, which can render the financing statement seriously misleading or ineffective.
  • Neglecting required notarization or witness steps for real property instruments, leading to rejected recordings or title problems.
  • Failing to coordinate post-signature filings and insurance or perfection steps, creating unintended priority exposure to other creditors.

Consequences of an Incorrect or Incomplete Collateral Agreement

Unperfected Lien: Loss of priority
Recording Delay: Lien subordinate to others
Incorrect Debtor Name: Filing rejection or ineffective search
Missing Signature: Potential unenforceability
Vague Collateral: Debate over scope at enforcement
Failure to Amend: Stale or misleading public record

eSignature Vendor Comparison for Executing Collateral Agreements

Compare common platform capabilities and starting price points for executing and storing signed Collateral Agreements; signNow is listed first per vendor ordering requirements.

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 trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Premium tier) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About Collateral Agreements

Common questions focus on enforceability, perfection, notarization, and how electronic signatures and recordings interact with state law.


Need help? Contact support

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