Can this extension be signed electronically?

Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are generally enforceable if the parties show intent, consent, attribution, and the record can be retained and reproduced.

When is notarization required?

Notarization depends on the document’s subject matter and state law; if the extension alters a deed or instrument requiring acknowledgement, a notary may be necessary. Check the relevant state statute or filing office rules.

What if a signer lacks authority?

If a signatory lacks actual or apparent authority, the extension may be voidable; document delegation of authority or obtain ratification from an authorized officer to cure defects.

Are witness signatures ever needed?

Witness requirements depend on state law and document type; certain acknowledgements (e.g., some property instruments) may require one or two witnesses per state rules, so confirm local requirements.

How do I revoke an executed extension?

Revocation typically requires a signed amendment or mutual rescission. If unilateral withdrawal is needed, consult legal counsel about contractual remedies and notice requirements to avoid repudiation claims.

How should I store executed copies?

Retain the signed extension with the original contract in your contract repository; ensure long-term access and integrity with secure storage, index metadata, and retention consistent with IRS, HIPAA, or other applicable rules.

Electronic Signature
Templates
Miscellaneous
Miscellaneous RCCP Extension

Miscellaneous RCCP Extension

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

MISCELLANEOUS RCCP EXTENSION

This Miscellaneous RCCP Extension Agreement ("Extension") is entered into by and between Requesting Party: and Approving Party: .

WHEREAS

WHEREAS, the Requesting Party and Approving Party previously entered into a Remedial Corrective Compliance Plan identified by RCCP Reference Number (the "RCCP");

WHEREAS, the RCCP established an original completion date of for corrective actions; and

WHEREAS, the Requesting Party has submitted a written request for an extension and the Approving Party is willing to grant a limited extension on the terms set forth in this Extension.

EXTENSION GRANT

Subject to the terms and conditions of this Extension, the Approving Party hereby extends the completion date of the RCCP to . The extension shall be effective as of the Execution Date below.

SCOPE OF WORK

Describe scope of work to be completed under the extended schedule

PAYMENT TERMS

Consideration for grant of this Extension shall be as follows. Amount payable: $ .

Payment schedule and milestones

Late payment shall accrue interest at the rate of on overdue amounts until paid in full. The Requesting Party shall also be responsible for any collection costs and reasonable attorneys' fees incurred by the Approving Party.

TERM AND TERMINATION

This Extension shall commence on and shall terminate on , unless earlier terminated in accordance with this Section.

Either Party may terminate this Extension for material breach by the other Party if the non-breaching Party provides written notice and the breaching Party fails to cure the breach within days of receipt of such notice.

CONFIDENTIALITY

Each Party shall maintain in strict confidence all non-public information disclosed by the other Party in connection with this Extension ("Confidential Information"), and shall not disclose such Confidential Information to any third party except as required by law or with the disclosing Party's prior written consent. Confidential Information does not include information that is or becomes generally available to the public other than as a result of a breach of this Section.

Upon termination or expiration of this Extension, each Party shall return or destroy Confidential Information of the other Party, and certify such return or destruction in writing upon request.

REPRESENTATIONS AND WARRANTIES

Each Party represents and warrants that it has full power and authority to enter into this Extension and that the person executing this Extension on its behalf is duly authorized to do so.

APPROVAL AND CONDITIONS

Primary reason for extension (select all that apply)

Supply chain disruption Weather or force majeure Additional scope of work required

Describe justification for extension and any conditions imposed by Approving Party

GOVERNING LAW

This Extension 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 Extension, together with the RCCP and any documents expressly incorporated herein, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written. No amendment or modification of this Extension shall be effective unless in writing and signed by both Parties.

NOTICES

Notice address for Requesting Party Notice address for Approving Party

MISCELLANEOUS PROVISIONS

If any provision of this Extension is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. No waiver of any breach shall be deemed a waiver of any subsequent breach.

Requesting Party:

By:

Date:

Approving Party:

By:

Date:

What the Miscellaneous RCCP Extension Is and when it applies

The Miscellaneous RCCP Extension is a short-form amendment used to extend deadlines, performance periods, or administrative timelines tied to an existing RCCP-related agreement. It records the parties, the original agreement reference, the new extended term, and any altered obligations. Use it when parties agree to postpone a contractual deadline without drafting a full replacement agreement; the extension should reference the original document by date and section to preserve continuity.

Why using a clear RCCP extension matters

A properly completed Miscellaneous RCCP Extension creates an auditable, written record of agreed-upon changes that reduces later disputes and preserves contractual intent. When executed electronically under ESIGN (15 U.S.C. ch. 96) or UETA, it can be legally enforceable provided intent, consent, attribution, and retention requirements are met.

Who typically completes a Miscellaneous RCCP Extension

Common users include contract administrators, project managers, legal teams, and counterparties who need to formalize a deadline or term change without redrafting the full agreement.

Contract managers and procurement teams managing project timelines and milestone adjustments for existing contracts.
Legal and compliance staff who must document agreed amendments and maintain an audit trail for regulatory or audit purposes.
External counterparties and vendors that require a brief, binding amendment for schedule shifts or administrative changes.

Core elements to include in a professional Miscellaneous RCCP Extension

A concise extension should be clear about what changes, who agrees, and when the change takes effect. It should be traceable to the original agreement and include signature blocks, dates, and any conditional language needed to avoid ambiguity.

Reference the original

Cite the original agreement title, execution date, and specific section(s) being modified so the extension can be read together with the base contract and enforcement context is preserved.

Describe the change

State exactly what is extended (deadline, obligation, notice period), the new date or term, and whether related obligations or deliverables are affected by the extension.

Effective date

Specify the date the extension takes effect and whether it is retroactive, prospective, or conditioned on an event, to avoid disagreements about applicability.

Consideration

If required, recite any consideration or mutual concessions supporting the extension; clear language reduces the risk of future defenses based on lack of consideration.

Signatures and authority

Identify each party, the signatory’s name and title, and include signature blocks with dates to show authorized execution of the extension.

Integration clause

Include a brief clause confirming the extension is an amendment to and read with the original agreement, and that unchanged terms remain in full force.

Step-by-step: complete and execute the extension

Follow these sequential steps to prepare, approve, and store the Miscellaneous RCCP Extension with minimal friction.

01

Prepare draft: Populate reference, parties, reason, and proposed new date; keep language concise and precise.
02

Internal review: Have legal or contract admin verify authority, consideration, and impact on related obligations.
03

Execute signatures: Obtain signatures from authorized signatories; notarize if a state or transaction requires it.
04

Store and notify: Attach executed extension to the original contract record and notify stakeholders and systems of the updated timeline.

Configure an online workflow for the Miscellaneous RCCP Extension

Set up a simple, auditable signing workflow that assigns reviewers, signers, and final storage locations to avoid manual handoffs.

Field	Configuration
Upload document	PDF or DOCX preferred; attach original agreement reference.
Signers	Add signers in role order (approver, counterparty, finalizer).
Authentication	Choose email link, SMS code, or multi-factor as needed.
Storage	Save signed copy to contract repository and archival folder.

Typical electronic execution flow

Most online signing follows a short sequence from document preparation to a completed audit trail; align each step with your compliance needs.

Upload: Upload the extension and attach the original agreement reference.
Place fields: Insert signature, date, and any conditional fields for optional approvals.
Invite signer: Send secure signing link or email invite with authentication method.
Complete: Signer signs, system records timestamp, IP, and audit details.

Technical considerations for eSigning and eSubmission

Confirm your signing platform supports required authentication, audit trails, and file formats before e-execution.

Document formats: PDF, DOCX, and HTML supported
Integrations: Salesforce, NetSuite, Google Workspace, Microsoft 365
Security: Audit trail, AES-256 storage

Choose providers that meet your compliance requirements (HIPAA BAA, 21 CFR Part 11) and integrate with contract repositories to automate retention.

Key timing and processing expectations

Timelines vary by organization and whether additional approvals or notarization are required; account for internal review and external processing.

Submission timing:

Submit extension before the original deadline to avoid potential breach

Internal review:

Allow 3–5 business days for legal and finance approvals

Processing time:

Expect 5–14 business days if external agency review is required

Acknowledgment:

Receive confirmation or countersigned copy within 1–5 business days

Notarization window:

If notarized, schedule signings consistent with state notary availability

Milestones from draft to recorded extension

Track these stages as numbered milestones to visualize the extension lifecycle and handoffs between teams.

01

Draft prepared

Create amendment referencing the original contract and proposed new date.

02

Internal approvals

Legal and finance confirm authority and consider impacts.

03

Execution

Parties sign; notarize if required by law or contract.

04

Record and notify

Attach to contract file and notify stakeholders and systems.

Common mistakes to avoid when preparing an RCCP extension

Failing to cite the original agreement precisely leads to confusion about which provisions remain effective and can invalidate the amendment.
Using ambiguous date language (e.g., "within a reasonable time") instead of a fixed MM/DD/YYYY can cause enforcement disputes and timeline disputes.
Permitting an unauthorized signer or failing to document delegation of authority risks claims that the extension is ineffective or voidable.
Neglecting to update downstream systems and stakeholders means operational teams may act on outdated deadlines, causing compliance or delivery failures.

Penalties and legal risks from an incorrect or missing extension

Contract breach: Damages or acceleration of obligations

Regulatory fines: Industry-specific penalties possible

Tax consequences: Reporting errors may trigger IRC penalties

I-9 violations: Paperwork fines under 8 CFR §274a.2

Notarization defects: Invalid acknowledgements can impair enforceability

Disputed authority: Unauthorized signatures risk rescission

Security and compliance items to verify before e-executing

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

Certifications: SOC 2 Type II; ISO 27001 available

HIPAA: BAA required for protected health information

Audit trail: Timestamps, IP, and action history retained

Access controls: Role-based permissions and SSO/SAML support

File formats: PDF/A-compatible signed documents recommended

Comparison: eSignature vendor pricing and key capabilities

This vendor comparison highlights basic pricing and features relevant to executing the Miscellaneous RCCP Extension. signNow is listed first in accordance with platform guidance.

	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, no card	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Practical tips for accurate, efficient completion

Adopt these habits to reduce rework and strengthen enforceability when using a Miscellaneous RCCP Extension.

Use precise references

Always reference the original agreement by exact title and date, and identify the specific section(s) being amended to prevent uncertainty during enforcement or audit.

Standardize templates

Maintain a vetted template with required clauses and signature blocks so every extension is consistent and legal review focuses only on exceptions.

Validate signer authority

Confirm signatory titles and delegation in writing; retain corporate resolutions or power-of-attorney documents when signers are not officers.

Integrate records

Store executed extensions with the original contract in a centralized repository and update contract management fields so operational systems reflect the new dates.

Frequently asked questions about the Miscellaneous RCCP Extension

Answers to common legal and practical questions when preparing, signing, and storing a Miscellaneous RCCP Extension.

Need help? Contact support

Can this extension be signed electronically?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are generally enforceable if the parties show intent, consent, attribution, and the record can be retained and reproduced.
When is notarization required?
Notarization depends on the document’s subject matter and state law; if the extension alters a deed or instrument requiring acknowledgement, a notary may be necessary. Check the relevant state statute or filing office rules.
What if a signer lacks authority?
If a signatory lacks actual or apparent authority, the extension may be voidable; document delegation of authority or obtain ratification from an authorized officer to cure defects.
Are witness signatures ever needed?
Witness requirements depend on state law and document type; certain acknowledgements (e.g., some property instruments) may require one or two witnesses per state rules, so confirm local requirements.
How do I revoke an executed extension?
Revocation typically requires a signed amendment or mutual rescission. If unilateral withdrawal is needed, consult legal counsel about contractual remedies and notice requirements to avoid repudiation claims.
How should I store executed copies?
Retain the signed extension with the original contract in your contract repository; ensure long-term access and integrity with secure storage, index metadata, and retention consistent with IRS, HIPAA, or other applicable rules.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now