Can an Institutional Support Agreement be e-signed?

Yes: electronic signatures generally bind parties under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Confirm the agreement does not fall into statutory exceptions and ensure required consumer disclosures when applicable.

When is notarization required?

Notarization depends on state law and the document's purpose. Many Institutional Support Agreements do not require a notary, but certain state-specific clauses or attachments may trigger a notarization requirement or recommend RON.

What authentication level is recommended?

Use email plus SMS or knowledge-based authentication for higher-risk transactions; require multi-factor authentication for agreements involving PHI, payments, or high-value commitments to strengthen enforceability and audit records.

How do I confirm signer authority?

Verify authority with corporate resolutions, delegations, or officer certifications. Require printed name and title in the signature block and consider a certificate of authority to reduce later challenges.

How can the agreement be amended or revoked?

Follow the contract's amendment clause: obtain written, signed consent from all parties for changes. For revocation, comply with termination provisions and preserve signed releases and supporting records for audit purposes.

How long must executed agreements be retained?

Retain executed agreements per retention schedules: at least three years for financial records (IRC §6501(a)), six years for HIPAA-related records (45 CFR §164.530(j)), and longer if state law or contract requires it.

Electronic Signature
Templates
Miscellaneous
Institutional Support Agreement

Institutional Support Agreement

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

INSTITUTIONAL SUPPORT AGREEMENT

This Institutional Support Agreement ("Agreement") is entered into as of Effective Date: by and between Institution Name: and Recipient Name: .

RECITALS

WHEREAS, Institution Name: seeks to provide institutional support to advance certain programs and initiatives consistent with its mission; and

WHEREAS, Recipient Name: operates programs for which the Institution intends to provide financial and/or in-kind support under the terms set forth herein; and

WHEREAS, the parties desire to set forth the scope, payment terms, reporting obligations, and the respective rights and responsibilities of each party with respect to such institutional support.

PARTIES AND CONTACT INFORMATION

Institution Address Institution Primary Contact (Name, Title) Recipient Address Recipient Primary Contact (Name, Title)

SCOPE OF SUPPORT

The Institution agrees to provide support to Recipient as described below. The support shall be used only for the purposes set forth in this Agreement and in accordance with the Recipient's approved budget and accepted practices.

Detailed Scope of Work

PAYMENT TERMS

Institution shall pay Recipient the Support Amount in accordance with the schedule below. Payments are contingent upon receipt of required deliverables and reports as set forth in this Agreement.

Support Amount (USD) Payment Schedule (installments, dates, milestones) Payment Method Late Payment Fee / Interest

If any payment due hereunder is not paid within thirty (30) days of the due date, Institution may impose the Late Payment Fee specified above in addition to any other remedies available under this Agreement or at law.

TERM AND TERMINATION

This Agreement shall commence on Start Date: and shall terminate on End Date: , unless earlier terminated as provided below.

Notice Period for Termination (days)

Either party may terminate this Agreement for material breach by the other party if such breach remains uncured thirty (30) days after written notice specifying the breach. Institution may terminate for convenience upon the notice period specified above by providing written notice to Recipient; in such event Institution will pay Recipient for allowable costs and eligible work performed to the date of termination in accordance with this Agreement.

REPORTING AND RECORDS

Recipient shall maintain accurate records of expenditures, receipts, and programmatic activity related to the use of support provided under this Agreement. Such records shall be retained for at least three (3) years following final payment and shall be made available to Institution upon reasonable request for inspection and audit.

Reporting Frequency

CONFIDENTIALITY

Each party may disclose Confidential Information to the other party in connection with the performance of this Agreement. "Confidential Information" means non-public information that is designated as confidential or that reasonably should be understood to be confidential. The receiving party shall (i) use Confidential Information only for the purposes of performing its obligations under this Agreement, (ii) protect Confidential Information with at least the same degree of care it uses to protect its own confidential information, and (iii) not disclose Confidential Information to any third party except as permitted herein.

Confidentiality Term (years)

The obligations in this section shall survive termination or expiration of this Agreement for the period specified above.

USE OF NAME AND PUBLICITY

Neither party shall use the other party's name, logo, or trademarks for promotional or publicity purposes without the prior written consent of the other party. Permission for press releases, public announcements, or logo usage must be requested in writing and, if granted, will be subject to the other party's standard branding and approval procedures.

Consent to Use Name/Logo for Institutional Acknowledgment

Institution grants Recipient permission to acknowledge support in materials in accordance with prior written guidance.

INDEMNIFICATION; LIMITATION OF LIABILITY

Each party (the "Indemnifying Party") shall indemnify, defend and hold harmless the other party from and against any third-party claims, liabilities, losses, damages, costs and expenses (including reasonable attorneys' fees) arising out of the Indemnifying Party's negligent or willful acts or omissions in connection with performance under this Agreement. EXCEPT FOR LIABILITY FOR A PARTY'S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT, NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES.

COMPLIANCE WITH LAWS

Each party shall perform its obligations under this Agreement in compliance with all applicable laws, regulations, and policies, including those governing procurement, export controls, data protection, and financial reporting.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction specified below, without regard to conflict of laws principles.

Governing Law (State or Jurisdiction)

ENTIRE AGREEMENT; AMENDMENT

This Agreement, together with any attachments, exhibits, or schedules expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior negotiations, understandings, and agreements. No amendment to this Agreement shall be effective unless in writing and signed by authorized representatives of both parties.

NOTICES

Notices under this Agreement shall be in writing and delivered to the primary contacts listed above, or to such other address as either party may specify in writing. Notices shall be deemed given when received.

Notice to Institution (address or email) Notice to Recipient (address or email)

MISCELLANEOUS

If any provision of this Agreement is determined to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. The failure of either party to enforce any provision of this Agreement shall not constitute a waiver of that or any other provision.

Institution Representative:

By:

Date:

Title:

Recipient Representative:

By:

Date:

Title:

What an Institutional Support Agreement Is

An Institutional Support Agreement is a legally binding contract that documents the terms under which one organization provides administrative, financial, or operational support to another institution. It typically defines the scope of services, payment or resource commitments, reporting obligations, compliance responsibilities, and duration. The agreement clarifies roles, allocates risk, and sets dispute-resolution and termination procedures. Organizations use this document for sponsored research, shared services, grant administration, and partnership arrangements where institutional authorization and oversight are required. It supports audit readiness and documents delegated authorities between parties.

Why a Clear Agreement Matters

Use an Institutional Support Agreement to reduce ambiguity around responsibilities, ensure compliance with funding or regulatory requirements, and document financial commitments. It provides clear expectations for reporting, indemnities, and oversight while establishing remedies and termination mechanics to protect institutional interests.

Who Typically Prepares and Signs This Agreement

Common users and signers include funders, institutional administrators, legal counsel, and department managers who approve or manage support commitments.

Research administration teams that manage sponsored projects, compliance reporting, and grant-related institutional commitments.
Chief financial officers overseeing budget allocations, cost-sharing, and fund transfer approvals.
Legal and contracts offices responsible for risk, indemnity, and governance review.

Institutions, external funders, and collaborating partners rely on this agreement to document obligations and provide an auditable record of institutional commitments.

Essential Sections to Include

Core sections define services, financial terms, compliance obligations, reporting, liability allocation, and termination to create a complete Institutional Support Agreement for institutional use.

Scope of Support

Describe the specific services, resources, or administrative functions provided by the supporting institution, including deliverables, performance standards, limitations, and any time or resource caps to avoid scope creep and disputes.

Financial Terms

Specify payment amounts, invoicing schedule, allowable costs, indirect cost treatment, reimbursement procedures, and conditions for withholding or audit adjustments, plus reference to accounting standards that govern fund use.

Compliance & Reporting

List required reports, frequency, responsible parties, data custodianship, recordkeeping obligations, and applicable regulatory frameworks such as HIPAA or FERPA when protected information is involved for compliance.

Liability & Indemnity

Define each party’s indemnification obligations, liability caps, insurance requirements, and responsibilities for third-party claims, including notice, defense, and settlement procedures to manage institutional risk appropriately.

Term & Termination

State the effective date, initial term, renewal conditions, termination for convenience or cause, notice periods, and post-termination obligations such as final reporting and disposition of funds or records.

Governing Law

Identify the governing state law, venue for disputes, and applicable choice-of-law clauses; note that ESIGN and UETA generally validate electronic signatures across jurisdictions, subject to statutory exceptions.

Step-by-Step: Completing and Executing the Agreement

Follow these steps to complete and execute an Institutional Support Agreement accurately, securely, and in compliance with applicable rules.

01

Prepare: Gather parties, funding details, and supporting documents.
02

Draft: Populate scope, financials, and compliance clauses.
03

Review: Have legal and finance review terms and risks.
04

Sign: Obtain valid signatures, dates, and witness or notary as required.

Configuring an Online Workflow

Set up routing, authentication, and retention so the Institutional Support Agreement executes with an auditable trail and integrates with institutional systems.

Field	Configuration
Signer Sequence	Sequential routing with signer order enforced.
Authentication Level	Email + SMS code; KBA optional for added assurance.
Conditional Fields	Reveal budget or compliance fields based on selections.
Retention Settings	Auto-archive signed PDF, export XML metadata.

Typical Routing Process

Typical routing for Institutional Support Agreements moves from preparer to reviewers to approvers and then to final signatories with tracking at each step.

Upload: Upload final draft PDF or DOCX to the platform.
Place Fields: Insert signature, date, and initial fields.
Invite Signers: Send secure email or link with authentication.
Complete: Capture signatures and generate completion certificate.

Platform Capabilities to Verify

For digital execution, verify the platform supports secure authentication, detailed audit trails, and integration with institutional systems like ERPs or CRMs.

Authentication: Email, SMS, or KBA options.
Audit Trail: Timestamped logs and IP addresses.
Integrations: Connects with NetSuite, Salesforce, and Box.

Key Dates and Timing to Track

Key timing considerations include effective dates, invoice schedules, reporting deadlines, signatory response times, and retention start dates under regulatory rules.

Effective Date Entry:

Determine and record the MM/DD/YYYY effective date.

Invoice Schedule:

Match invoicing to contract milestones and funder terms.

Reporting Deadlines:

Align report due dates with funder timelines to avoid penalties.

Signature Turnaround:

Allow reasonable time for institutional routing and approvals.

Retention Start Date:

Retention often begins on execution or final accounting date.

Consequences of Errors or Noncompliance

Breach Exposure: Contract damages and reputational harm.

Funding Withhold: Suspension or recoupment of funds.

Regulatory Fines: HIPAA or grant compliance penalties.

Audit Findings: Required repayments and remediation.

Invalid Signatures: Enforceability risk

Data Breach Risk: Exposure of protected information.

Common Pitfalls to Avoid

Vague scope descriptions that omit deliverables or timelines lead to disputes and unbillable work, increasing administrative burden and potential compliance violations.
Failing to list funding sources, fiscal codes, or cost-sharing splits causes invoicing errors and may trigger funder audits or disallowed cost findings.
Signing by unauthorized personnel or using initials instead of full signatures can render the agreement unenforceable or delay acceptance.
Not addressing data handling or PHI leads to HIPAA noncompliance; omit specific retention and access controls and you create legal risk.

Comparing eSignature Providers for This Agreement

Basic pricing and feature comparisons for common eSignature solutions; signNow appears first per table rules to aid platform selection context.

	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	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

Answers to common questions about executing and managing Institutional Support Agreements, including electronic signing and compliance considerations.

Need help? Contact support

Can an Institutional Support Agreement be e-signed?
Yes: electronic signatures generally bind parties under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Confirm the agreement does not fall into statutory exceptions and ensure required consumer disclosures when applicable.
When is notarization required?
Notarization depends on state law and the document's purpose. Many Institutional Support Agreements do not require a notary, but certain state-specific clauses or attachments may trigger a notarization requirement or recommend RON.
What authentication level is recommended?
Use email plus SMS or knowledge-based authentication for higher-risk transactions; require multi-factor authentication for agreements involving PHI, payments, or high-value commitments to strengthen enforceability and audit records.
How do I confirm signer authority?
Verify authority with corporate resolutions, delegations, or officer certifications. Require printed name and title in the signature block and consider a certificate of authority to reduce later challenges.
How can the agreement be amended or revoked?
Follow the contract's amendment clause: obtain written, signed consent from all parties for changes. For revocation, comply with termination provisions and preserve signed releases and supporting records for audit purposes.
How long must executed agreements be retained?
Retain executed agreements per retention schedules: at least three years for financial records (IRC §6501(a)), six years for HIPAA-related records (45 CFR §164.530(j)), and longer if state law or contract requires it.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now