Can this notice be signed electronically?

Yes. Electronic signatures are generally valid under the ESIGN Act and UETA when intent, consent, attribution, and retention are present; use stronger authentication for higher-risk certificates.

What if the issuer misses the deadline?

Document the missed deadline, escalate per contract terms, and assess remedies. Preserve all communications to support any future breach or cure analysis.

Is notarization required for validity?

Notarization depends on the certificate type and state law; where required use in-person or RON procedures that meet state notary rules and preserve the notary record.

How to prove the certificate was requested?

Include dated copies of the submission, confirmation receipts, and signed delivery evidence; preserve the sender and recipient audit trail for later reliance.

How long should records be kept?

Follow the longest applicable retention rule: IRS 3 years (IRC §6501(a)), HIPAA 6 years (45 CFR §164.530(j)), and longer where industry or state law mandates it.

What authentication strength is recommended?

Match authentication to risk: basic email for low risk, SMS or KBA for moderate risk, and multi-factor or identity-proofing for high-risk regulatory or court-bound certificates.

Electronic Signature
Templates
Legal
Legal Certificate Pending

Legal Certificate Pending

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

LEGAL CERTIFICATE PENDING

This Legal Certificate Pending Agreement (the Agreement) is entered into as of by and between Issuer: (entity type: Corporation LLC Other ), having a principal address at ; and Holder: (entity type: Individual Corporation LLC ), having a principal address at .

RECITALS

WHEREAS, Issuer is authorized to issue the following certificate: a evidencing (the Certificate); and

WHEREAS, the parties acknowledge that issuance and delivery of the Certificate is subject to the satisfaction of certain conditions and approvals set forth below, and the parties desire to record their agreement as to the pending issuance, rights, obligations and remedies in the interim.

WHEREAS, Holder will be entitled to receive the Certificate upon satisfaction of the Conditions to Issuance described in this Agreement.

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. DEFINITIONS

For purposes of this Agreement, the following terms shall have the meanings set forth below:

(a) "Certificate" means the instrument described above to be issued by Issuer to Holder evidencing ownership of the units specified in this Agreement.

(b) "Conditions to Issuance" means the conditions, approvals, and deliverables set forth in Section 3 and in the Conditions Description field below.

2. PENDING CERTIFICATE

Issuer hereby acknowledges that it has agreed to issue the Certificate to Holder, subject to the Conditions to Issuance. Until the Certificate is delivered to Holder and, if applicable, recorded on Issuer's register, Holder shall hold only the rights expressly set forth in this Agreement. Issuer shall not issue, register, or deliver any certificate with respect to the units described in the Certificate to any person other than Holder except as permitted by this Agreement.

3. CONDITIONS TO ISSUANCE

The Certificate shall be issued by Issuer to Holder upon satisfaction of the following conditions, each of which is a material obligation under this Agreement:

Expected date for issuance if Conditions are satisfied:

4. REPRESENTATIONS AND WARRANTIES

4.1 Issuer represents and warrants that: (a) it is duly organized and validly existing under applicable law and has full corporate or organizational power to enter into this Agreement; (b) the execution, delivery and performance of this Agreement by Issuer have been duly authorized by all necessary corporate or organizational action; and (c) issuance of the Certificate upon satisfaction of the Conditions will not violate any agreement, judgment or law applicable to Issuer.

4.2 Holder represents and warrants that: (a) it has full power and authority to enter into this Agreement; (b) the execution, delivery and performance of this Agreement by Holder have been duly authorized; and (c) Holder will comply with any transfer restrictions and other requirements set forth in this Agreement.

5. TRANSFER RESTRICTIONS; RECORDS

Until the Certificate is duly issued and delivered and, where applicable, registered on Issuer's books, Holder acknowledges that transfer, assignment, or encumbrance of the rights identified herein is prohibited except with the prior written consent of Issuer. Issuer shall, upon issuance, record the Certificate on its register and provide Holder with evidence of such registration.

6. REMEDIES

In the event Issuer fails to issue the Certificate after Holder has satisfied the Conditions to Issuance within a commercially reasonable time, Holder shall be entitled to seek specific performance and injunctive relief to compel issuance, in addition to any other remedies at law or in equity. The parties agree that monetary damages may be an inadequate remedy for breach of this Agreement and that equitable relief is appropriate.

7. NOTICES

Any notice required or permitted under this Agreement shall be in writing and delivered to the address set forth below or to such other address as a party may designate by notice delivered in accordance with this Section. Notices shall be deemed given when delivered personally, sent by nationally recognized overnight courier, or three (3) business days after deposit in the United States mail, postage prepaid, certified or registered.

Issuer Notice Address Holder Notice Address

8. AMENDMENT; WAIVER

No amendment, modification or waiver of any provision of this Agreement shall be effective unless in writing and signed by both parties. No failure or delay by any party in exercising any right or remedy under this Agreement shall operate as a waiver thereof.

9. COUNTERPARTS

This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Signatures delivered by electronic facsimile or other electronic means shall be binding for all purposes.

10. GOVERNING LAW; ENTIRE AGREEMENT; SEVERABILITY

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction chosen by the parties below without regard to conflict of laws principles. The parties select:

This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings, whether written or oral. If any provision of this Agreement is held to be invalid or unenforceable, the remaining provisions shall continue in full force and effect.

11. MISCELLANEOUS PROVISIONS

11.1 Assignment. Neither party may assign its rights or obligations under this Agreement without the prior written consent of the other party, except that Issuer may assign this Agreement to an affiliate or in connection with a merger, acquisition or sale of all or substantially all of its assets.

11.2 Further Assurances. At the request of either party, the other party shall execute and deliver such further documents and take such further actions as may be reasonably necessary to effectuate the purposes of this Agreement.

CERTIFICATION OF PENDING STATUS

Issuer certifies that the Certificate described herein is due to be issued to Holder upon satisfaction of the Conditions to Issuance and that Issuer will, within a commercially reasonable time after such satisfaction, deliver and, if required, register the Certificate. Issuer further certifies that no other certificate representing the same units will be issued or delivered to any third party in violation of the transfer restrictions set forth herein.

Additional Instructions or Notes

Issuer:

By:

Date:

Holder:

By:

Date:

What the Legal Certificate Pending means

A Legal Certificate Pending is a written notice or form indicating that a required legal certificate, clearance, or approval has not yet been issued but is expected. It documents the outstanding item, identifies the responsible issuer, and records any interim conditions or limitations that apply while the certificate is outstanding. Common uses include real estate closings, corporate filings, regulatory compliance holds, and contract performance conditions. The record helps parties track status, preserve timelines, and create an auditable trail for later reliance once the certificate is issued.

Why recording a Legal Certificate Pending matters

Documenting a pending certificate preserves each party’s expectations, creates an auditable status record, and reduces disputes about timing or responsibility. It clarifies interim rights, conditions precedent, and next steps while a formal certificate is being obtained.

Who commonly prepares or relies on this notice

Each party uses the document to assign responsibility, set deadlines, and support later verification when the certificate is delivered.

Corporate counsel and compliance officers responsible for filings and regulatory clearances.
Title companies and real estate closing agents using it to note outstanding title or survey certificates.
Contract administrators and project managers tracking conditional approvals or permits.

Filling out a Legal Certificate Pending: step-by-step

Complete the form in sequence to ensure clarity, assign responsibility, and set measurable deadlines.

01

Identify the item: Name the specific certificate or approval required.
02

Assign issuer: List the authority or third party responsible for issuing it.
03

Set deadline: Provide a concrete date or timeframe for expected issuance.
04

Record conditions: Note interim limitations, contingencies, and follow-up steps.

Typical routing and lifecycle of the notice

A standard flow moves the notice from drafter to issuer, back to requester, and into the permanent record.

Draft and attach: Prepare notice and attach supporting documents.
Send to issuer: Deliver to the named authority for action or comment.
Receive response: Issuer provides certificate or status update.
File final record: Place completed certificate or final disposition in the project file.

Digital workflow settings to use for this notice

Configure workflow fields and authentication to match legal sensitivity and required auditability.

Field	Configuration
Authentication level	Email link \| SMS code \| KBA as needed
Document format	PDF/A preferred for long-term retention
Routing order	Sequential signing with conditional steps
Retention setting	Retain audit trail and final PDF export

Technical and integration considerations

Choose settings that balance signer friction with evidentiary strength and store audit data alongside the final document.

Authentication: Email, SMS, or KBA
Integrations: Salesforce, NetSuite, Google Workspace
File types: PDF, DOCX, HTML

Practical tips to keep the notice useful and enforceable

Adopt consistent templates, require essential fields, and match digital controls to the document’s legal sensitivity.

Use a standard template

Standardized language reduces interpretation disputes and ensures every notice captures issuer, deadline, and conditions.

Set measurable deadlines

Specify exact dates rather than vague timeframes to create clear performance expectations and compute remedies precisely.

Attach supporting evidence

Include copies of applications, receipts, or emails showing submission to the issuing authority for later proof.

Preserve the audit trail

Keep signed PDFs, metadata, and access logs to support reliance and to meet ESIGN/UETA retention expectations.

Common preparation mistakes to avoid

Omitting the issuer’s full legal name, causing confusion when multiple agencies have similar titles and delaying verification.
Failing to set a concrete deadline, which prevents measuring breach or delay and complicates remedies.
Leaving supporting documents out of the record, weakening proof that the request for a certificate was timely submitted.
Relying on a handwritten status note without an audit trail, making attribution and timestamping difficult under ESIGN tests.

Potential consequences of errors or omissions

Invalid reliance: Delayed or missing certificate

Contract remedies: Breach claims or delayed performance

Regulatory fines: Agency penalties possible

Tax exposure: Backup withholding risk

Litigation costs: Increased counsel fees

Operational delay: Project hold or termination

Security and compliance features to require

Transport encryption: TLS 1.2/1.3

At-rest encryption: AES-256

Certifications: SOC 2 Type II, ISO 27001

Regulatory support: HIPAA BAA available

Audit trail: Timestamps, IP, action log

Access controls: SSO, role-based permissions

Time expectations and operational deadlines

Estimate internal and external timelines so parties can manage dependencies and avoid penalties.

Request response time:

Ask issuing authority for status within 7–14 days of request

Internal follow-up:

Set an internal reminder 7 days before the expected issue date

Escalation window:

Escalate to counsel or supervisor if not resolved within 30 days

Final filing:

File issued certificate in permanent record within 5 business days

Record update:

Update contract or project trackers upon receipt

Key milestones from notice to closure

Track these sequential stages to ensure timely resolution and archival of the final certificate.

01

Draft Notice

Prepare and attach supporting materials, identify issuer and deadline.

02

Submit Request

Send to issuing authority and capture proof of delivery.

03

Receive Certificate

Obtain formal certificate, note any limiting language or conditions.

04

Close Record

Attach final certificate, update trackers, and archive audit trail.

Typical eSignature plan comparison for issuing and tracking notices

Essential vendor criteria for managing Legal Certificate Pending workflows; signNow appears first for parity with other major providers.

	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	Free trial available	Free trial available	Free trial available	Free trial available
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions and practical solutions

Answers to common issues that arise when preparing, signing, or relying on a Legal Certificate Pending.

Need help? Contact support

Can this notice be signed electronically?
Yes. Electronic signatures are generally valid under the ESIGN Act and UETA when intent, consent, attribution, and retention are present; use stronger authentication for higher-risk certificates.
What if the issuer misses the deadline?
Document the missed deadline, escalate per contract terms, and assess remedies. Preserve all communications to support any future breach or cure analysis.
Is notarization required for validity?
Notarization depends on the certificate type and state law; where required use in-person or RON procedures that meet state notary rules and preserve the notary record.
How to prove the certificate was requested?
Include dated copies of the submission, confirmation receipts, and signed delivery evidence; preserve the sender and recipient audit trail for later reliance.
How long should records be kept?
Follow the longest applicable retention rule: IRS 3 years (IRC §6501(a)), HIPAA 6 years (45 CFR §164.530(j)), and longer where industry or state law mandates it.
What authentication strength is recommended?
Match authentication to risk: basic email for low risk, SMS or KBA for moderate risk, and multi-factor or identity-proofing for high-risk regulatory or court-bound certificates.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now