Establishing secure connection…Loading editor…Preparing document…

Notice of Default

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

What a Notice of Default Is and when it’s used

A Notice of Default is a formal written notice that a borrower or obligor has failed to meet payment or performance obligations under a secured agreement, most commonly a mortgage. It identifies the breached provision, the amount in arrears or performance required, and the deadline to cure. Notices of Default often trigger statutory cure periods and can be recorded in county land records for real property. The document serves both as procedural prerequisite in many foreclosure processes and as clear written evidence of default for dispute resolution or loan workout discussions.

Why a clear Notice of Default matters

A properly prepared Notice of Default preserves legal rights, starts required cure periods, and creates an administrative record. Clear language reduces disputes, supports later enforcement steps, and documents attempts to notify the obligor.

Why a clear Notice of Default matters

Who typically prepares and receives a Notice of Default

The document is used across finance and property workflows; accuracy and proper service are essential to avoid procedural challenges.

  • Mortgage servicers and banks who manage loan portfolios and initiate default processes.
  • Commercial landlords and property managers when tenants breach lease payment obligations.
  • Loan investors and trustees who require recorded notice to preserve enforcement rights.

Core elements every professional Notice of Default should include

A complete Notice of Default combines factual detail, contractual references, and a clear cure instruction so recipients and recorders can understand the default and next steps without ambiguity.

Identifying parties

Clearly name the creditor/holder and the borrower or obligor, including entity type and contact details, so the party receiving the notice can be unambiguously identified in later proceedings.

Property description

Provide the legal description or full street address and parcel number for real property; inaccuracies here can invalidate recording or create disputes over which asset is affected.

Default details

State the breached covenant, the date of default, and a concise explanation of how the contractual obligation was not met to enable the recipient to verify and respond.

Cure amount and actions

Itemize amounts due (principal, interest, fees) or specific acts required to cure the default and explain calculation dates and any applicable per-diem accruals.

Cure deadline

Specify the deadline to cure in MM/DD/YYYY format and reference any contractual cure period or statute governing the time allowed to remedy the default.

Execution and service

Include the date and signature block for the sender, notarization if required, and a statement of how and when the notice was served to satisfy procedural rules.

How to complete and issue a Notice of Default

Follow these sequential steps to prepare, serve, and record a Notice of Default while preserving legal rights and minimizing procedural risk.

  • 01
    1. Verify authority: Confirm the sender is authorized to issue notice
  • 02
    2. Populate form: Complete all required fields with contract-accurate data
  • 03
    3. Choose service method: Select certified mail, personal delivery, or statutory method
  • 04
    4. Record if required: File with county recorder and retain proof of recording

Configuring an online Notice of Default workflow

When using an eSignature platform, set up fields, authentication, and routing to match legal and internal process requirements.

Field Configuration
Required fields Property, borrower, amount, cure date — make mandatory
Signature type Enable electronic signature with audit trail
Authentication Email plus SMS code or stronger KBA for identity
Routing Sign order, send to trustee or recorder, archive automatically

Where to send and file a Notice of Default

A Notice of Default must be served to the obligor and, where required, recorded with appropriate public offices; follow contractual and state procedures.

  • Serve borrower: Certified mail or statutory method
  • Record notice: County recorder or land records office
  • Notify trustee: Send copy to trustee handling security interest
  • Archive: Retain proof of service and recording

Technical considerations for eSigning and eFiling

Use platforms that produce tamper-evident signed PDFs and exportable audit logs to meet recording and compliance needs.

  • Formats: PDF and DOCX supported
  • Integrations: Connects to Salesforce, NetSuite, MS 365
  • Authentication: Email, SMS, or advanced methods

Typical timing and deadlines to watch for

Timing varies by contract and state law; use the dates in the loan documents and applicable statutes to calculate cure and enforcement deadlines accurately.

Initial cure period:

Often 30–90 days per contract

Notice issuance:

Issue promptly after determining default

Service proof:

Keep proof of mailing or delivery date

Recording timeline:

Record immediately if required by jurisdiction

Foreclosure window:

Varies widely; consult state statute or counsel

Key milestones from default to resolution

A Notice of Default starts a sequence of events; track each milestone to preserve rights and comply with statutory windows.

01

Default Occurs

Borrower misses payment or breaches covenant; lender documents the event

02

Notice Issued

Formal Notice of Default drafted and signed by authorized party

03

Service & Record

Notice is served to obligor and recorded if jurisdiction requires

04

Enforcement Action

If uncured, lender may commence foreclosure or other remedies

Common preparation and service mistakes to avoid

  • Using an incomplete or inaccurate legal description that leads to rejection at the recorder's office and potential title disputes.
  • Failing to confirm the sender’s authority or loan assignment, which opponents use to challenge standing in enforcement proceedings.
  • Incorrect service method or failure to retain proof of service that defeats procedural prerequisites for foreclosure.
  • Listing an improper cure deadline or calculation that allows the obligor to claim procedural unfairness or invalid notice.

Consequences of an incorrect or improperly served Notice of Default

Loss of standing: May forfeit right to enforce
Recording rejection: Recorder may refuse invalid filings
Procedural delays: Remediation can delay enforcement
Litigation exposure: Increases risk of challenge
Costs: Added legal and administrative expense
Reputational risk: Adverse impacts with stakeholders

Real-world examples of Notices of Default in use

These examples illustrate how organizations use structured notices to preserve rights and streamline downstream processes.

Tim Martin — Martin Properties

Martin Properties issued a Notice of Default after documenting missed rent payments and late fees.

  • The standardized form listed amounts and cure date clearly.
  • The clear record sped resolution discussions and supported an expedited eviction where cure did not occur.

Dan Rotelli — BIS

BIS used templated Notices of Default integrated with their loan servicing system to ensure consistent language.

  • Integration produced audit trails for each notice.
  • That consistency reduced disputes about service dates and improved internal compliance reporting.

eSignature vendor comparison for preparing and signing Notices of Default

Basic pricing and capability criteria for common eSignature providers. Choose a vendor that meets security, HIPAA, and recording format needs.

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 Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Security and compliance features to look for

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
ESIGN / UETA: Platform compliance with 15 U.S.C. §7001 and UETA where applicable
HIPAA: Supports HIPAA compliance with a signed BAA
21 CFR Part 11: Capabilities consistent with FDA 21 CFR Part 11 controls
SOC 2 / ISO: SOC 2 Type II and ISO 27001 certifications available
Audit Trail: Tamper-evident logs with timestamps and signer metadata

Frequently asked questions about Notices of Default

Answers to common procedural and technical questions about preparing, serving, and signing Notices of Default.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users