Can this form be signed electronically?

Yes. Electronic signatures that meet ESIGN (15 U.S.C. ch. 96) and state UETA requirements are legally valid for most client relative disclosures, provided intent, consent, attribution, and retention are met.

When is notarization required?

Notarization is rarely required for a basic relative disclosure, but state-specific transactions (real estate deeds, some powers of attorney) may require notarized acknowledgements.

What if a client revokes authorization?

Record the revocation in writing, date it, and update the stored form immediately; preserve the prior version with a legal hold if required for audits or disputes.

How should updates be handled?

Collect a signed amendment or a new completed form noting the effective date; maintain version history and an audit trail for each change.

Who may access these records?

Access should be limited by role-based permissions; in healthcare, follow HIPAA access rules and document disclosures per policy.

What if a name does not match ID?

Clarify discrepancies by obtaining supporting documentation and note the verification steps taken; unresolved mismatches can delay processing or trigger additional verification.

Client Relative Form

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

CLIENT RELATIVE FORM

Recitals

This Agreement is entered into by Client Name: and Service Provider Name: (collectively, the Parties) as of Effective Date: .

WHEREAS, Client requires that Service Provider collect, maintain, and, when authorized, contact designated relatives and emergency contacts for purposes of notifications, care coordination, and authorized communications; and

WHEREAS, Service Provider has agreed to provide such services under the terms set forth herein, and Client hereby provides identification and authorizations for the relatives listed on this form.

Scope of Services

Scope of Work

Client Relative Information

Enter up to four relatives or emergency contacts. Information provided will be used only as authorized by the Client and in accordance with the Confidentiality provisions below.

Relative / Contact 1

Full Legal Name Relationship to Client

Phone:

Email:

DOB:

Address Emergency contact / Authorized to be notified Authorized to receive limited client information as necessary for care coordination

Relative / Contact 2

Full Legal Name Relationship to Client

Phone:

Email:

DOB:

Address Emergency contact / Authorized to be notified Authorized to receive limited client information as necessary for care coordination

Additional Relatives (Optional)

Relative 3 - Full Legal Name Relative 3 - Relationship Relative 4 - Full Legal Name Relative 4 - Relationship

Consent, Use and Authorization

By checking the box below and signing this form, Client expressly authorizes Service Provider to contact the listed relatives and to disclose limited client information necessary for the purposes described in the Scope of Work. Such information shall be the minimum necessary to accomplish the authorized purpose.

Client authorizes contact and limited disclosure to the relatives listed herein. Client authorizes Service Provider to notify and provide emergency information to designated emergency contacts when the Client is incapacitated or in urgent situations.

Payment Terms

In consideration for services provided under this form, Client agrees to pay the Service Provider the fees set forth below.

Fee Amount Payment Schedule / Due Dates Late Fee

Term and Termination

This Agreement commences on Start Date: and shall continue until End Date: , unless earlier terminated in accordance with this section.

Either Party may terminate this Agreement for convenience upon written notice delivered no fewer than Notice Period (days): days prior to the intended termination date. Termination for cause may be immediate where a material breach is not cured within thirty (30) days following written notice of breach.

Confidentiality

Each Party shall maintain the confidentiality of personally identifiable information and health or sensitive information of the Client and relatives, disclosing such information only as expressly authorized by this form, required by law, or necessary to perform services under this Agreement. The receiving Party shall implement reasonable administrative, technical, and physical safeguards to protect such information against unauthorized use or disclosure.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of State: without regard to conflict of laws principles.

Entire Agreement

This document, together with any attachments and executed amendments, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, representations, and warranties, whether written or oral.

Representations and Certifications

The undersigned Client certifies that the information provided on this form is accurate and complete to the best of Client's knowledge, and authorizes Service Provider to rely upon the information and authorizations contained herein until such time as Client provides written notice of any change.

I certify that the information provided is true and that I have authority to authorize the disclosures indicated.

Client Name:

By:

Date:

Service Provider Name:

By:

Date:

What the Client Relative Form Is and when it’s used

The Client Relative Form is a standardized disclosure used to identify and document individuals related to a client, their relationship, and contact details for purposes such as conflict checks, eligibility reviews, emergency contacts, or family-consent tracking. Organizations commonly collect this information at intake and update it when relationships change. The form typically records full legal names, relationship type, dates of birth or age where relevant, contact phones and addresses, and any authorizations the client grants for information sharing. Accurate completion supports compliance, informed consent, and reliable case or account management.

Why completing the Client Relative Form matters

Completing the form reduces legal and operational risk by documenting relationships that affect conflicts, consent, or benefits eligibility, and it creates a verifiable record for audits and care or case decisions.

Who typically completes or uses this form

Maintain the completed form with the client file and update it whenever the client reports a change in relationship status or contact information.

Healthcare intake teams collecting next-of-kin and emergency contact details for treatment and billing.
Legal intake and conflict-check personnel documenting relationships that could create representation conflicts.
Financial services and trust officers recording beneficiaries, authorized contacts, and joint-account relationships.

Stepwise process to complete the Client Relative Form

Follow these steps to gather, verify, and record relative information consistently and in a compliance-ready format.

01

Gather details: Collect full names, relationships, and contact information directly from the client.
02

Verify identity: Check photo ID or other documents when required to confirm the relative's identity.
03

Record consent: Document any client authorization for data sharing or decision-making authority.
04

Save and review: Store with the client record and review for updates at each major interaction.

How the form flows through your organization

This sequence explains typical routing from intake to secure storage and any downstream actions that rely on the recorded relative information.

Intake: Front-line staff capture relative details during intake or account setup.
Verification: Compliance or intake teams confirm identity and consent where required.
Authorization: Authorized staff use recorded permissions for information release or emergency contact.
Archive: Signed forms are stored in the secure client file with audit metadata.

Digital workflow settings recommended for e-submission

Configure a consistent online workflow to reduce missing data and provide a verifiable signing trail.

Field	Recommended configuration
Name field	Required; autofill disabled for accuracy
Relationship field	Required; dropdown with common values
Consent checkbox	Required; capture timestamp
Signer authentication	Email + SMS code or stronger where sensitive

Technical and integration requirements for online completion

Integration with records systems reduces manual entry and preserves the audit trail required for compliance and dispute resolution.

File formats: PDF and DOCX preferred
Authentication: Email link plus optional SMS code
Integrations: CRM and cloud storage connectivity

Essential elements a professional Client Relative Form should include

A compliant form balances clear data capture with consent and auditability to meet administrative and legal needs.

Identifying data

Collect full legal name, date of birth when required, and government ID details to support later verification and reduce identity disputes.

Relationship type

Use standardized relationship descriptors (spouse, parent, agent) so conflict-check systems and decision workflows can process the information automatically.

Contact information

Record mailing address, phone, and email with preferred contact method to ensure reliable outreach for notices or emergencies.

Consent and scope

Capture written authorization specifying what information may be shared and with whom, including any time limits or revocation instructions.

Signature and date

Include signature blocks for the client and, when applicable, the relative, and record the signing method, timestamp, and IP or audit metadata.

Audit trail

Preserve a tamper-evident completion record with signer identity attributes, timestamps, and any authentication challenge results for future review.

Security and compliance checklist

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

Access controls: Role-based permissions and SSO

Audit logs: Immutable event history

HIPAA readiness: BAA available where required

Data residency: Configurable storage region

Accessibility: WCAG 2.0 Level AA compliance

Common preparation mistakes to avoid

Entering incomplete contact details which prevents notification in time-sensitive situations and complicates follow-up.
Recording informal relationship labels that do not translate into legal authority during conflicts or transfers of care.
Failing to document or date consent language, leaving ambiguity about the client’s permission to share information.
Storing signed forms without an audit trail, making it difficult to resolve disputes about attribution or timing.

Risks and potential penalties for incorrect or missing information

Privacy breach: Civil fines and corrective action

HIPAA violation: Enforcement and monetary penalties

Incorrect authority: Unauthorized disclosures or actions

Operational delay: Interrupted services or access

Regulatory audit: Document requests and sanctions

Legal challenge: Contract or estate disputes

Timelines and typical processing expectations

Use these timing benchmarks to set internal SLAs and to meet any statutory or contractual obligations tied to the form.

Provide at intake:

Collect the form when a client is onboarded or first evaluated

Update on change:

Require an updated form within 30 days of reported relationship changes

Respond to requests:

Produce requested relative data within 30 days unless law requires otherwise

Retention minimum:

Retain for at least 3 years unless a longer period applies

Legal hold:

Preserve records immediately when litigation or an audit is reasonably anticipated

Key milestones from collection to archival

Track these sequential milestones to ensure the form is complete, verified, and retained correctly.

01

Collection

Client or staff completes the form during intake or when the relationship is reported

02

Verification

Identity and consent are validated by staff, including ID checks where required

03

Acceptance

Authorized reviewer signs off that the form meets intake criteria

04

Archival

Signed form is stored in the secure client record with audit metadata

eSignature vendor comparison for completing and signing the form

This comparison highlights common capability and pricing benchmarks across vendors; signNow is listed first per platform data and plan structure.

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

Frequently asked questions about the Client Relative Form

Answers to common procedural and legal questions about signing, storing, and updating the form.

Need help? Contact support

Can this form be signed electronically?
Yes. Electronic signatures that meet ESIGN (15 U.S.C. ch. 96) and state UETA requirements are legally valid for most client relative disclosures, provided intent, consent, attribution, and retention are met.
When is notarization required?
Notarization is rarely required for a basic relative disclosure, but state-specific transactions (real estate deeds, some powers of attorney) may require notarized acknowledgements.
What if a client revokes authorization?
Record the revocation in writing, date it, and update the stored form immediately; preserve the prior version with a legal hold if required for audits or disputes.
How should updates be handled?
Collect a signed amendment or a new completed form noting the effective date; maintain version history and an audit trail for each change.
Who may access these records?
Access should be limited by role-based permissions; in healthcare, follow HIPAA access rules and document disclosures per policy.
What if a name does not match ID?
Clarify discrepancies by obtaining supporting documentation and note the verification steps taken; unresolved mismatches can delay processing or trigger additional verification.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now