Are electronically signed RCDs legally binding?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted; ensure intent, consent, attribution, and record retention are documented to meet the four‑prong legal test.

When is notarization required?

Notarization depends on the action and state. For example, certain deed or notarized affidavits require notarization; check state rules before assuming an RCD requires notarization for disposal authorizations.

How long must I retain signed RCDs?

Retention depends on record type and regulator: IRS generally three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and industry rules may extend these periods; document the legal basis on the RCD.

Can I accept click-to-sign for approvals?

Yes if the signing method captures intent, attribution, and an audit trail. For consumer-facing financial or healthcare records include required ESIGN consumer disclosures before obtaining consent to electronic records.

What if a record is under legal hold?

Immediately suspend scheduled disposal when a legal hold is issued; record the hold on the RCD and preserve associated audit logs to avoid spoliation claims.

How do I revoke or amend an RCD after signing?

Amendments should be handled through a signed addendum or replacement RCD with clear effective dates; retain both versions and their signatures to preserve historical custody and change rationale.

Business RCD Document

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

BUSINESS RCD DOCUMENT

This Business RCD Document ("Agreement") is entered into on Effective Date: by and between:

Party A Name: Party A Address: Party B Name: Party B Address:

WHEREAS

WHEREAS, Party A is engaged in the business identified by the parties and possesses certain rights, records, compliance protocols and deliverables described in this Agreement; and

WHEREAS, Party B desires to retain Party A to provide the services and deliver the records, compliance, and disclosure deliverables described herein (collectively, "RCD Services"), and Party A agrees to perform such services subject to the terms and conditions of this Agreement.

WHEREAS, the parties intend by this Agreement to allocate responsibilities, payment obligations, confidentiality obligations, and risk with respect to the RCD Services.

Scope of Work

Party A will perform and deliver RCD Services as described below. Specific tasks, milestones, and deliverables will be governed by the description entered in the field below and any appendices incorporated by reference.

Payment Terms

As consideration for the RCD Services, Party B shall pay Party A the Total Contract Amount specified below in accordance with the schedule and conditions set forth in this Section.

Total Contract Amount (USD): Payment Schedule:

Invoices shall be due and payable within days of invoice date. Late payments shall bear interest at the rate specified below.

Late Fee / Interest: Payment Method and Instructions:

Term and Termination

This Agreement shall commence on the Start Date and continue until the End Date, unless earlier terminated in accordance with this Section.

Start Date: End Date:

Either party may terminate this Agreement for convenience upon written notice delivered to the other party not less than days prior to the intended termination date. Either party may terminate immediately upon material breach by the other party if such breach remains uncured for a period of 10 days following written notice.

Early Termination Fee (if any):

Confidentiality

"Confidential Information" means all non-public information disclosed by one party to the other in any form related to the RCD Services, including but not limited to business processes, records, compliance documents, trade secrets, technical data, financial information, and client lists. Confidential Information does not include information that: (a) is or becomes publicly available through no fault of the receiving party; (b) is already lawfully known to the receiving party prior to disclosure; or (c) is rightfully obtained from a third party without restriction.

The receiving party shall: (i) maintain Confidential Information in strict confidence; (ii) use Confidential Information solely for the purposes of performing obligations under this Agreement; and (iii) restrict disclosure to employees, agents or subcontractors with a need to know and bound by confidentiality obligations at least as protective as those set forth herein. The receiving party shall be responsible for breaches by its representatives.

The obligations set forth in this Section shall continue for a period of years following termination or expiration of this Agreement, except with respect to trade secrets, for which duration shall be as permitted by applicable law.

The parties acknowledge that a breach of this Section may cause irreparable harm for which monetary damages are inadequate and agree that injunctive relief shall be an available remedy in addition to any other remedies at law or in equity.

Acknowledgement of Confidentiality: By checking, the signing party acknowledges and accepts the confidentiality obligations above.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of laws principles. Venue for any dispute arising out of or in connection with this Agreement shall lie in the state or federal courts located within said state.

Entire Agreement

This Agreement, together with any appendices or exhibits expressly incorporated herein in writing, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, negotiations, and communications, whether oral or written. Any amendment or modification must be in writing and signed by authorized representatives of both parties.

If any provision of this Agreement is held to be invalid or unenforceable, the remaining provisions will remain in full force and effect and the parties will negotiate in good faith a substitute valid and enforceable provision that most nearly effects the original intent.

Party A Name:

By:

Date:

Party B Name:

By:

Date:

What the Business RCD Document Is and When It Applies

A Business RCD Document (Records Custody and Disposal) is a company-level form that records who controls, stores, and disposes of specified business records. It lists record categories, custodians, retention schedules, access controls, and authorized disposal methods so organizations can meet legal, tax, and regulatory retention obligations while documenting chain-of-custody for audits and internal governance.

Why maintaining a clear RCD matters for your business

A formal RCD reduces legal and regulatory exposure by assigning custody, standardizing retention, and documenting disposal actions. It supports audits, tax examinations, and privacy compliance while creating a repeatable process for records lifecycle decisions.

Which teams typically complete a Business RCD Document

Start the RCD with the department responsible for records management and legal oversight; this ensures correct retention and approvals.

Legal and Compliance teams: establish retention rules and legal holds for regulated records.
Finance and Accounting: maintain financial and tax records custody details for audits.
IT and Records Management: specify storage locations and access controls for electronic records.

After completion, circulate the RCD to custodians and executive sponsors for acknowledgement and to ensure operational alignment.

Core sections to include in a professional RCD

A complete RCD groups information so reviewers can quickly confirm custody, retention period, and disposition authority.

Record Type

Clear category name for the records (e.g., payroll, contracts, patient records) to align retention with legal obligations and searchability.

Custodian

Name and role of the person or team responsible for storage, access, and disposition decisions to establish accountability during audits.

Retention Period

Specific retention timeframe (MM/DD/YYYY or years) and the legal or policy basis for the duration to avoid inadvertent premature disposal.

Storage Location

Physical address or digital repository path with access rules so authorized personnel can retrieve records when required.

Disposition Method

Approved disposal procedure (secure shredding, digital erasure, RON-enabled notarized destruction) ensuring chain-of-custody is preserved.

Approval Signatures

Signature blocks for custodian, legal, and an executive approver documenting consent and providing a clear audit trail for retention actions.

Step-by-step: completing and approving an RCD

Follow these sequential steps to populate, review, and finalize a Business RCD Document so it is audit-ready.

01

Prepare draft: Identify records and fill core fields.
02

Legal review: Confirm retention basis and legal holds.
03

Custodian acknowledgement: Custodian reviews storage and access details.
04

Final approval: Executive signs and files final RCD.

Configuring an online RCD workflow

Map each form field to a workflow action, signer, or approval step to automate routing and retention enforcement.

Field	Configuration
Custodian Field	Auto-assign to HR group; trigger email
Retention Field	Trigger retention timer; calendar entry
Legal Approval	Sequential approval required from counsel
Disposition Action	Send disposal request to custodian

Digital routing overview for e‑submission and approvals

A typical digital RCD flow reduces manual handoffs by combining fields, automated routing, and audit logging.

Upload Document: Sender uploads RCD and attachments.
Place Fields: Add custodian, retention, and signature fields.
Route for Approval: Sequential approvals are enforced automatically.
Store & Log: Signed RCD and audit trail are archived.

Technical considerations for eCompletion and storage

Verify that your chosen platform supports secure eSigning, role-based access, and auditable retention exports before deploying the RCD.

File formats: PDF, DOCX, or archived XML
Authentication: Email, SMS code, or stronger
Integrations: Connectors to cloud storage

Ensure the platform retains an immutable audit trail and supports export for legal review; confirm BAA or other contractual protections if protected health information is involved.

Key dates to include and monitor for each RCD

Document these dates so retention and disposition actions occur reliably and in compliance with legal holds.

Creation Date:

Date record was created or received.

Retention Start:

Trigger event that begins retention clock.

Review Date:

Periodic review schedule (e.g., annually).

Disposition Window:

Authorized date range for disposal.

Legal Hold Start:

Date legal hold suspends disposal actions.

Common mistakes to avoid when preparing an RCD

Using inconsistent record categories that create duplicate retention rules and retrieval delays during audits.
Failing to identify the correct retention trigger, causing premature disposal or unnecessarily long retention.
Omitting custodian contact information which results in delayed disposition approvals and unclear accountability.
Relying on non‑auditable disposal methods without documented proof of secure destruction, weakening defensibility.

Risks and consequences of incorrect RCD entries

Regulatory Fines: Civil penalties possible

Tax Exposure: Record gaps trigger IRS inquiries

Litigation Risk: Spoliation claims may follow

HIPAA Violations: Privacy breaches increase fines

Operational Disruption: Loss of business continuity

Reputational Harm: Public trust erosion

Real-world examples of RCD practices in action

Two organizations describe how formal custody and disposal records supported compliance and faster processing.

Martin Properties

Martin Properties uses an online RCD to process closing documents consistently.

The system enforces retention and disposal dates for each file.
As a result the firm reports reliable compliance at closings and fewer manual retrievals for audits, improving operational consistency and evidence for any post-closing inquiries.

BIS

BIS adopted a centralized RCD for contracts and invoices.

Custodians receive automated review tasks.
This reduced missing records during financial review cycles and provided clear audit logs used to resolve vendor disputes and support internal controls documentation.

Comparing eSignature options for executing and storing RCDs

Platform features and costs vary; the following comparison highlights starting price, trial availability, bulk send, audit trail presence, HIPAA compliance, and envelope caps.

	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	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Security and compliance highlights relevant to RCD handling

Encryption Transit: TLS 1.2/1.3

Encryption Rest: AES-256

HIPAA: BAA required for PHI workflows

Audit Trails: Detailed signer and event logs

21 CFR Part 11: Supported for FDA-regulated records

SOC 2: SOC 2 Type II available

Practical tips for accurate and efficient RCD completion

Use standardized fields, clear triggers, and automation to reduce errors and speed approvals.

Use consistent taxonomy

Adopt a company-wide list of record categories and retention templates. Consistency reduces misclassification during discovery, supports bulk processing, and simplifies staff training.

Document legal basis

Record the statute or internal policy supporting each retention period. This makes reviews faster and provides defensible reasoning during audits or litigation.

Automate review tasks

Set automated reminders and retention timers tied to the RCD fields so custodians receive timely disposition requests and compliance teams can monitor overdue reviews.

Keep an immutable audit trail

Retain signed copies and event logs for the full retention period to demonstrate custody, approvals, and disposal actions to regulators or auditors.

Frequently asked questions about using and enforcing an RCD

Answers below address common legal, technical, and operational questions when creating, signing, and storing Business RCD Documents.

Need help? Contact support

Are electronically signed RCDs legally binding?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted; ensure intent, consent, attribution, and record retention are documented to meet the four‑prong legal test.
When is notarization required?
Notarization depends on the action and state. For example, certain deed or notarized affidavits require notarization; check state rules before assuming an RCD requires notarization for disposal authorizations.
How long must I retain signed RCDs?
Retention depends on record type and regulator: IRS generally three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and industry rules may extend these periods; document the legal basis on the RCD.
Can I accept click-to-sign for approvals?
Yes if the signing method captures intent, attribution, and an audit trail. For consumer-facing financial or healthcare records include required ESIGN consumer disclosures before obtaining consent to electronic records.
What if a record is under legal hold?
Immediately suspend scheduled disposal when a legal hold is issued; record the hold on the RCD and preserve associated audit logs to avoid spoliation claims.
How do I revoke or amend an RCD after signing?
Amendments should be handled through a signed addendum or replacement RCD with clear effective dates; retain both versions and their signatures to preserve historical custody and change rationale.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now