Who can request changes?

Any authorized party or their designated representative may submit a Relationship Change Request Form, provided they show required proof of authority. Organizations should verify the signer against account records and request power of attorney or notarized authorization when authority is unclear.

What ID is acceptable?

Acceptable identification typically includes a current government-issued photo ID, such as a state driver's license or passport. For entity changes, include formation documents or a board resolution. Organizations may require notarization or remote online notarization depending on internal policy and state rules.

Can this be e-signed?

Yes—electronic execution is generally valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the signer consents, intent is clear, and records are retained. Some exceptions (wills, certain court orders) may still require ink signatures.

When is notarization needed?

Notarization is required when the recipient's policy or state law calls for an acknowledgment, witness, or notarized statement—common for durable powers, property transfers, or when statutory authority is at issue. Remote online notarization may be accepted where state law permits.

Processing times vary by organization; simple contact or authorization updates often complete within 3–10 business days, while changes requiring review, notarization, or third-party verification can take several weeks. Ask the recipient for their standard SLA for accurate expectations.

What happens if information is wrong?

Incorrect or incomplete submissions can delay processing, trigger denials, or create liability for unauthorized changes. Organizations may require resubmission with corrected documents, additional verification, or legal review; repeated errors can lead to temporary account restrictions until matters are resolved.

Electronic Signature
Templates
Miscellaneous
Relationship Change Request Form

Relationship Change Request Form

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

Relationship Change Request Form

Parties

Client Name: Account/ID:

Other Party Name: Relationship Contact:

WHEREAS

1. WHEREAS, Client and Other Party are currently bound by an existing commercial relationship pursuant to agreements, contracts, or account terms between the parties (collectively, the Existing Relationship); and

2. WHEREAS, Client has requested a change in the nature of the Existing Relationship to the relationship described in this Relationship Change Request Form, and Other Party is willing to consider or accept such change subject to the terms and conditions set forth herein; and

3. WHEREAS, the parties intend for this Request, once accepted and executed by authorized representatives of both parties, to document the agreed modification to the Existing Relationship and to bind the parties with respect to the matters set forth below.

Requested Change Details

Current Relationship Type Requested Relationship Type Requested Effective Date Reason for Change Anticipated Impact on Services or Obligations

Scope of Work

The parties agree to the following revised scope of work, duties, or deliverables as a result of the relationship change. The Scope below supersedes any conflicting scope in prior arrangements to the extent expressly modified herein.

Revised Scope of Work

Payment Terms

Unless otherwise agreed in writing, any change to the relationship that affects compensation, invoicing, or payment obligations will be governed by the terms below.

Agreed Amount / Fee Payment Schedule Late Payment Fee or Interest

Term and Termination

The relationship change shall commence and terminate as set forth below unless earlier terminated in accordance with the terms of this form or applicable agreements.

Start Date: End Date:

Notice Period for Termination

Either party may terminate this relationship change upon written notice if the other party materially breaches any material obligation and fails to cure such breach within the notice period specified above, or immediately for cause where permitted by applicable law or existing agreements.

Confidentiality

All non-public information disclosed in connection with the requested relationship change shall be treated as Confidential Information. Each party shall protect Confidential Information of the other party with at least the same degree of care it uses to protect its own confidential information, but in no event less than a reasonable standard of care.

The obligations in this clause do not apply to information that: (a) is or becomes generally available to the public other than through a breach of this obligation; (b) was known to the receiving party prior to disclosure; (c) is rightfully received from a third party without restriction; or (d) is independently developed by the receiving party.

I acknowledge and agree to the confidentiality obligations set forth above.

Representations and Warranties

Each party represents and warrants that it has the full power and authority to enter into this Relationship Change Request Form, that execution and delivery of this Request and performance of the obligations hereunder have been duly authorized, and that the person signing on behalf of each party is duly authorized to bind that party.

Governing Law

This Relationship Change Request Form and any dispute arising out of or related to it shall be governed by and construed in accordance with the laws of the state of , without regard to conflict of law principles.

Entire Agreement

This Relationship Change Request Form, together with any incorporated attachments or amendments executed by the 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 oral or written, relating to such subject matter.

Authorization

By submitting this Relationship Change Request Form and providing the signature below, the undersigned represent and warrant that they are duly authorized to request or approve the change on behalf of the party indicated and that all information provided herein is true, complete, and accurate to the best of their knowledge.

Primary Contact for Implementation

Certification: I certify that I am authorized to request or approve this change and that this request will be binding upon execution by authorized representatives of both parties.

Client - Printed Name:

By:

Date:

Other Party - Printed Name:

By:

Date:

What the Relationship Change Request Form Is

The Relationship Change Request Form is a standardized document used to record and authorize changes to an existing relationship between two parties, such as account ownership, authorized representatives, billing contacts, or account access privileges. It captures current details, specifies requested changes, and documents approval by authorized signers. Organizations use it to maintain auditable records, ensure internal controls, and reduce disputes arising from unauthorized modifications. The form can be executed on paper or electronically; when completed digitally it must meet ESIGN and applicable state rules to be legally enforceable. Use clear, complete information to avoid processing delays.

Why the Form Matters for Compliance and Accuracy

The Relationship Change Request Form streamlines approvals, creates a documented audit trail, and reduces operational risk by ensuring only authorized parties make changes. It supports compliance with ESIGN and UETA standards when executed electronically and clarifies responsibilities for internal and external recordkeeping.

Who Typically Prepares or Signs This Form

Typical users range from account administrators to compliance officers and authorized representatives submitting or approving relationship changes.

Account Administrator — updates account contact details, access levels, and authorized signer lists.
Compliance Officer — verifies identity, approves changes, and maintains audit records for regulatory reviews.
Authorized Representative — requests changes on behalf of a party and provides required identification and documentation.

Determine role-based signing authority before submission to speed approval and avoid rejections due to insufficient authorization.

Step-by-Step: Complete and Submit the Form

Follow these steps to complete and submit a Relationship Change Request Form accurately and ensure timely processing by the receiving organization.

01

Prepare Details: Confirm current account data and specify precise changes requested.
02

Attach ID: Include government ID or authorization letters as required.
03

Sign & Date: Authorized signers sign, date, and provide printed names.
04

Submit & Track: Send to the designated department and save confirmation.

Frequently Asked Questions and Troubleshooting

Answers to common questions about completing, submitting, and validating a Relationship Change Request Form, including identity requirements, acceptable supporting documents, and electronic signing considerations.

Need help? Contact support

Who can request changes?
Any authorized party or their designated representative may submit a Relationship Change Request Form, provided they show required proof of authority. Organizations should verify the signer against account records and request power of attorney or notarized authorization when authority is unclear.
What ID is acceptable?
Acceptable identification typically includes a current government-issued photo ID, such as a state driver's license or passport. For entity changes, include formation documents or a board resolution. Organizations may require notarization or remote online notarization depending on internal policy and state rules.
Can this be e-signed?
Yes—electronic execution is generally valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the signer consents, intent is clear, and records are retained. Some exceptions (wills, certain court orders) may still require ink signatures.
When is notarization needed?
Notarization is required when the recipient's policy or state law calls for an acknowledgment, witness, or notarized statement—common for durable powers, property transfers, or when statutory authority is at issue. Remote online notarization may be accepted where state law permits.
How long to process?
Processing times vary by organization; simple contact or authorization updates often complete within 3–10 business days, while changes requiring review, notarization, or third-party verification can take several weeks. Ask the recipient for their standard SLA for accurate expectations.
What happens if information is wrong?
Incorrect or incomplete submissions can delay processing, trigger denials, or create liability for unauthorized changes. Organizations may require resubmission with corrected documents, additional verification, or legal review; repeated errors can lead to temporary account restrictions until matters are resolved.

Security and Compliance Considerations

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

HIPAA: Compliant — BAA required

ESIGN / UETA: Compliant with ESIGN and UETA

SOC 2: SOC 2 Type II available

21 CFR: Supports 21 CFR Part 11 workflows

Access Controls: Two-factor and role-based authentication

Consequences of Incorrect or Unauthorized Changes

Processing Delays: Incomplete data causes rejection

Unauthorized Changes: Potential financial or legal exposure

Tax Penalties: Backup withholding or IRS fines

Regulatory Fines: HIPAA or state penalties possible

Notary Failure: Document may be invalid

Reputational Risk: Loss of trust with clients

Common Mistakes to Avoid

Incomplete identification or mismatched names are leading causes of rejections; always verify government IDs and exact legal names before submitting to avoid delays.
Failing to specify effective dates or leaving the change ambiguous forces manual follow-up and may result in the original status remaining in force.
Providing unsigned or undated forms, or using initials instead of required signatures, commonly invalidates the request and necessitates resubmission.
Submitting conflicting supporting documents, such as differing authority letters, leads to extended verification and may require notarization or legal review.

How the Submission Workflow Typically Operates

Typical routing for a Relationship Change Request Form follows a defined workflow to collect approvals, verify identity, and update account records with an auditable history.

Upload Document: Sender uploads the completed form to the system.
Assign Reviewers: Route to verifier for identity and authority checks.
Approve Changes: Authorized approver signs and timestamps.
Apply Update: Record updated and audit trail stored.

Digital Workflow Settings to Configure

Common configuration settings when digitizing a Relationship Change Request Form include authentication, conditional fields, and notifications to downstream systems.

Field	Configuration
Authentication	Email link, SMS code, or KBA
Conditional Fields	Show fields based on role or selection
Notifications	Email confirmations and admin alerts
Integrations	Push updates to CRM or ERP systems

Platform Requirements for eSubmission

Ensure the eSignature platform supports identity verification, conditional fields, and audit logging before enabling electronic submissions.

File Formats: PDF and Word (DOCX) supported
Integrations: CRM, ERP, cloud storage
Authentication: Email, SMS, or advanced methods

Vendor Pricing and Feature Comparison for eSignature

Compare common eSignature plan features and pricing considerations for completing Relationship Change Request Forms across popular vendors.

	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	Yes, varies	Yes, varies	Yes, varies	Yes, varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now