Can I sign the ROC form electronically?

Yes—electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the transaction meets intent, consent, attribution, and retention requirements.

What if I filed the wrong information?

Correct promptly: prepare an amended ROC Notification Form, attach a cover explaining the error, obtain required approvals, and refile with the original recipient and any affected counterparties.

Who is authorized to sign the form?

An authorized officer or an agent with a valid power of attorney must sign. Verify authority via corporate resolutions or POAs to prevent rejections or disputes.

Is notarization always required?

Not necessarily; notarization and witness requirements depend on jurisdiction and document type. Confirm local rules—some states or document categories require notarization or witnesses.

What supporting documents should be attached?

Common attachments include board resolutions, government ID, amended certificates, and powers of attorney. Missing attachments are a frequent cause of processing delays.

How long must I retain the filed ROC record?

Retain records per the applicable retention timeline: IRS minimums, HIPAA six-year rule for PHI (45 CFR §164.530(j)), and any longer state or industry-specific requirements.

ROC Notification Form

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

ROC Notification Form

Notification Reference No.: Date of Notification:

Parties

Notifier (Party A) - Name Notifier (Party A) - Registered Address Notifier Contact Person Recipient (Party B) - Name Recipient (Party B) - Address

WHEREAS

WHEREAS, Notifier (Party A) is obligated under applicable corporate registration rules to provide timely written notification of certain corporate changes affecting its registration and records; and

WHEREAS, Recipient (Party B) administers or processes such notifications and provides administrative support, filings, and related services pursuant to the terms agreed between the parties; and

WHEREAS, the parties enter this ROC Notification Form to document the specific notification being made, the scope of services, payment terms, and the responsibilities and certifications of the parties.

Scope of Notification and Services

Specify the change(s) for which notification is being made and the services to be provided by Recipient. Describe any documents to be prepared, filings to be made, or enquiries to be conducted.

Scope of Work

Details of Change

Change Type: Registered Office Address Director/Officer Change Share Structure Other

If Other, specify Effective Date of Change Supporting Documents Provided

Payment Terms

Fees payable in consideration of the services described in this form shall be as follows.

Total Fee Payment Schedule Late Payment

All payments are due in cleared funds on the dates specified. In the event of late payment, Recipient reserves the right to suspend services until outstanding amounts are paid and to recover reasonable costs of collection.

Term and Termination

This Notification Form is effective as of the Effective Date set forth below and shall continue until the completion of the services described in the Scope of Work or until terminated in accordance with this section.

Start Date End Date (if applicable) Notice Period for Termination

Either party may terminate this Notification Form for material breach by the other party if the breach is not cured within the notice period set forth above. Termination shall not relieve a party of liability for obligations accrued prior to termination.

Confidentiality

Each party shall maintain in confidence all non-public information disclosed by the other party in connection with this Notification Form and shall not use such information except to perform its obligations hereunder. The obligations in this clause survive termination or expiration of this Notification Form for a period of three (3) years.

Confidentiality Acknowledgement I acknowledge and agree to the confidentiality obligations set out above.

Governing Law

This Notification Form shall be governed by and construed in accordance with the laws of the following jurisdiction. The parties submit to the exclusive jurisdiction of the courts of that jurisdiction for disputes arising under this Notification Form.

Governing Jurisdiction

Entire Agreement

This Notification Form, including any attachments or schedules expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, negotiations and understandings, whether written or oral.

Certifications and Authorizations

The undersigned certifies that they are authorized to submit this notification on behalf of the notifying party, and that the information provided in this form and the attached documents is true, complete and correct to the best of their knowledge. The undersigned agrees to indemnify and hold harmless Recipient for reliance on the information supplied unless Recipient acted negligently or in bad faith.

Certification Acknowledgement I certify that I am authorized to make this notification and that the information provided is accurate.

Notifier (Party A) - Print Name:

By:

Date:

Recipient (Party B) - Print Name:

By:

Date:

What the ROC Notification Form Is and When It's Used

The ROC Notification Form is a standardized notice used to record and communicate a material change to an official record or registration—for example a change of authorized representative, business address, ownership, or other key corporate or regulatory details. Organizations use it to update registries, contract counterparties, licensing authorities, or internal compliance files. The form documents who is changing what, when the change takes effect, and what supporting evidence is attached; it is typically incorporated into compliance, HR, real estate, financial, and government workflows and often accompanies identity or corporate documentation.

Why a Clear ROC Notification Form Matters

A properly completed ROC Notification Form reduces operational risk by creating a clear, auditable record of changes, ensuring regulatory compliance and minimizing disputes about authority or timing.

Typical users and recipients of ROC Notification Forms

ROC Notification Forms are completed by compliance teams, legal departments, HR or authorized officers and sent to registries, counterparty legal teams, or internal records managers.

Compliance officers or corporate secretaries — prepared for state filing offices, licensing authorities, or internal records management.
HR administrators — notify payroll, benefits, and personnel records teams when authorized representative or address changes occur.
Contract managers or legal counsel — provide updated signatory or contact information to counterparties and contract repositories.

Use lists below to match likely preparers with common recipients to streamline routing and approvals.

Step-by-step: completing a ROC Notification Form

Follow these sequential steps to prepare, validate, and submit the form with supporting documents and required approvals.

01

Gather records: Collect board resolutions, ID, registration documents.
02

Complete fields: Enter party names, effective date, and change details.
03

Attach proof: Scan or upload supporting documents in PDF format.
04

Authorize and submit: Obtain authorized signature, then file or send per recipient instructions.

Configuring an online workflow for ROC submissions

Set up a repeatable digital workflow so ROC notifications follow the same validation, approval, and retention steps every time.

Field	Configuration
Document upload	Require PDF attachments and name convention checks
Signer roles	Assign roles: preparer, approver, authorized signatory
Authentication	Enable email link, SMS code, or advanced signer auth
Notifications	Auto-email recipients and store signed PDF

Where to file or send the completed ROC Notification

Choose the correct destination to ensure legal effect and timely processing: regulator portal, counterparty, or internal records repository.

Regulatory portal: File with the state or federal registry per agency instructions
Counterparty delivery: Email legal contact and attach signed document and evidence
Internal records: Save certified copy in corporate recordkeeping system
Certified mail: Use for proof of receipt when required by statute or contract

Digital signing and sharing: platform and format requirements

Use platforms that support secure PDFs, an audit trail, and required authentication methods for legal validity.

File formats: PDF, DOCX accepted; final signed copy must be PDF
Authentication: Email link, SMS code, or advanced signer authentication
Integrations: Salesforce, NetSuite, Google Workspace supported

Essential sections to include on a professional ROC Notification Form

A well-structured ROC Notification Form groups key information into clear sections to speed review and reduce follow-up requests.

Header

Form title, reporting party, file/reference number, and filing agency identification.

Effective date

Explicit MM/DD/YYYY effective date and any backdating limitations stated.

Party details

Full legal names, addresses, EIN/TIN or other identifiers for involved parties.

Change description

Concise description of prior value and new value, with relevant dates and scope.

Attachments

List of supporting documents and their file names; include board resolutions or identity documents as required.

Certification

Statement by signatory attesting to accuracy, plus printed name, title, and contact information.

Security and compliance items to include with digital ROC filings

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

Audit trail: Detailed time, IP, and action logs

HIPAA: BAA required for PHI-containing filings

21 CFR Part 11: Compliant workflows for FDA-regulated records

SOC 2: SOC 2 Type II available on request

Access control: Role-based permissions and SSO

Common mistakes that delay or invalidate ROC notifications

Submitting incomplete supporting documentation, which causes agencies or counterparties to request clarifications and extend processing time.
Using an incorrect or abbreviated entity name that does not match the registration record, triggering rejections or manual reconciliation.
Failing to obtain an authorized signature or using someone without authority to sign, resulting in invalid or contested filings.
Not confirming whether the recipient requires notarization, witness signatures, or specific delivery methods, leading to non-acceptance.

Potential penalties and risks from incorrect or late ROC submissions

Late filing fines: Monetary penalties, fines, or administrative fees

Invalid filing: Submission rejected, no legal effect

Contract breach: Counterparty claims or damages

Tax exposure: Backup withholding or reporting errors

Regulatory action: Licensing suspension or compliance orders

Operational delay: Loss of authority to transact

Typical timing expectations and deadlines for ROC notifications

Timing requirements vary by recipient; where statutory deadlines exist, submit promptly and document delivery for proof of compliance.

Immediate notification:

Submit as soon as the change is effective when contracts require prompt notice

Agency window:

Many agencies require filing within 30 days of the change

Contractual notice:

Follow contract-specified notice periods; these may be shorter than regulatory windows

Tax reporting alignment:

Ensure changes affecting tax forms align with payer reporting deadlines

Retention start:

Date retention clocks from the effective or filing date as required

eSignature vendor comparison for executing ROC Notification Forms

Compare basic plan pricing and key features for common e-signature platforms used to execute ROC forms; signNow is listed first for reference.

	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
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions about ROC Notification Forms

Answers to common questions on electronic signing, errors, who must sign, notarization, and retention for ROC Notification Forms.

Need help? Contact support

Can I sign the ROC form electronically?
Yes—electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the transaction meets intent, consent, attribution, and retention requirements.
What if I filed the wrong information?
Correct promptly: prepare an amended ROC Notification Form, attach a cover explaining the error, obtain required approvals, and refile with the original recipient and any affected counterparties.
Who is authorized to sign the form?
An authorized officer or an agent with a valid power of attorney must sign. Verify authority via corporate resolutions or POAs to prevent rejections or disputes.
Is notarization always required?
Not necessarily; notarization and witness requirements depend on jurisdiction and document type. Confirm local rules—some states or document categories require notarization or witnesses.
What supporting documents should be attached?
Common attachments include board resolutions, government ID, amended certificates, and powers of attorney. Missing attachments are a frequent cause of processing delays.
How long must I retain the filed ROC record?
Retain records per the applicable retention timeline: IRS minimums, HIPAA six-year rule for PHI (45 CFR §164.530(j)), and any longer state or industry-specific requirements.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now