Can the Note be signed electronically?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the signing process demonstrates intent, consent, attribution, and record retention capability.

Is notarization always required?

Not always. Notarization is commonly required when recording the Note with a county recorder; local recorder rules determine whether a notary or witnesses are necessary for recordation.

What if a party changes ownership?

Record transfers and assign responsibilities via an amendment or assignment document. Recording an assignment gives notice to future purchasers and maintains enforceability in most jurisdictions.

How should inspection records be stored?

Store signed Notes and inspection reports in a secure, auditable format (PDF with audit trail). Maintain records per federal and state retention rules and for the life of the obligation plus recommended retention.

Can the Note be amended later?

Yes. Amendments should be executed by all parties, dated, and notarized or witnessed if required. Record the amendment where the original Note was recorded to preserve public notice.

Who enforces the maintenance obligations?

Enforcement may be performed by the designated responsible party, a homeowners association, or by municipal authorities under the permitting ordinance; the Note should identify enforcement mechanisms clearly.

Electronic Signature
Templates
Miscellaneous
Rainwater Management Note

Rainwater Management Note

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

RAINWATER MANAGEMENT NOTE

This Rainwater Management Note (the "Note") is made and entered into effective as of by and between:

Obligor (Property Owner): Payee (Management Entity): Property Address (subject to this Note):

WHEREAS

WHEREAS, Obligor is the owner of the property identified above and is required to design, install, operate and maintain certain rainwater and stormwater management facilities (the "System") in accordance with applicable permits, plans, and specifications; and

WHEREAS, Payee has agreed to administer, inspect, and manage the System on an ongoing basis and Obligor acknowledges a monetary obligation to Payee for management services, monitoring, maintenance, and compliance activities associated with the System; and

WHEREAS, Obligor desires to evidence the obligation to pay management fees and to record the responsibilities for long-term rainwater management by executing this Note.

1. PRINCIPAL AMOUNT

Obligor promises to pay Payee the sum of (the "Principal Amount"), plus any applicable fees, interest and costs as set forth in this Note.

2. SCOPE OF WORK

Detailed Scope of Rainwater Management Services:

3. PAYMENT TERMS

Payments shall be made in accordance with the following schedule and terms:

Payment Amount (per schedule): Payment Schedule: Late Fee:

All sums unpaid when due shall bear interest at the rate set forth above and Obligor shall also be liable for Payee's costs of collection, including reasonable attorneys' fees and administrative costs incurred to enforce this Note.

4. TERM AND TERMINATION

This Note commences on and shall continue in full force until unless earlier terminated in accordance with this Section.

Notice Period for Termination by Either Party:

Either party may terminate this Note for material breach by the other party if the breaching party fails to cure such breach within the notice period specified above. Termination shall not relieve Obligor of obligations accrued prior to termination, including payment obligations and corrective actions required for compliance with permits.

5. CONFIDENTIALITY

Each party shall maintain in confidence all non-public technical, financial, and proprietary information disclosed by the other party in connection with the System and the services hereunder ("Confidential Information"). Confidential Information shall not include information that is (a) publicly known through no fault of the receiving party; (b) independently developed by the receiving party without use of or reference to the disclosing party's Confidential Information; or (c) required to be disclosed by law, court order, or governmental authority, in which event the receiving party shall provide prompt written notice to the disclosing party to allow for protective measures.

Confidentiality obligations shall survive termination or expiration of this Note for a period of three (3) years.

6. DEFAULT AND REMEDIES

An Event of Default occurs if Obligor fails to pay any sum when due, fails to perform any material obligation respecting the System, or otherwise breaches any material term of this Note and such failure is not cured within the applicable cure period. Upon Event of Default, Payee may pursue all remedies available at law or equity, including acceleration of amounts due, recording notices or liens, seeking injunctive relief to compel corrective action, and recovering costs of enforcement.

7. NOTICES

Notices under this Note shall be sent to the addresses set forth below or to such other address as either party designates by written notice.

Obligor Contact Name: Obligor Notice Address: Payee Contact Name: Payee Notice Address:

8. GOVERNING LAW

This Note shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles.

9. ENTIRE AGREEMENT

This Note, together with any exhibits, schedules, and attachments expressly incorporated by reference, 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.

10. MISCELLANEOUS

Headings in this Note are for convenience of reference only and shall not affect its interpretation. If any provision of this Note is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. No amendment or modification of this Note shall be effective unless in writing and signed by both parties.

Obligor Printed Name:

By:

Date:

Payee Printed Name:

By:

Date:

What the Rainwater Management Note Is and When It Applies

The Rainwater Management Note is a written record that documents site-specific stormwater controls, maintenance obligations, inspection schedules, and responsible parties for a property or project. It is typically attached to permit files, construction closeout documentation, or property records to create a durable, auditable statement of ongoing duties. The Note clarifies technical features (e.g., retention basins, swales, permeable pavement), service intervals, and contact information so owners, contractors, and municipal authorities can monitor compliance and performance over time.

Why a Formal Note Matters for Compliance and Clarity

Because the Rainwater Management Note records ongoing obligations and inspection schedules, it reduces operational ambiguity and supports regulatory compliance. Electronic execution is accepted under federal ESIGN (15 U.S.C. ch. 96) and UETA (1999) in applicable jurisdictions, enabling lawful e-signatures.

Primary users and stakeholders

Typical users include property owners, civil engineers, municipal stormwater managers, contractors, and environmental consultants involved in site drainage and compliance.

Property owners responsible for ongoing maintenance and record-keeping of stormwater controls.
Municipal stormwater or public works departments tracking permits, inspections, and enforcement actions.
Design and construction firms documenting BMP specifications, handover obligations, and inspection plans.

The Note aligns operational duties across stakeholders and creates a durable record useful for enforcement, transfers, and permit renewals.

Stepwise process to complete and finalize the Note

Follow these steps to populate, verify, and finalize the Rainwater Management Note for recordation or project files.

01

Gather Details: Collect BMP descriptions, installation dates, and maintenance schedules.
02

Assign Responsible Party: Name the entity and primary contact for long-term maintenance.
03

Set Inspection Plan: Specify frequency, reporting format, and responsible inspector.
04

Record Execution: Sign, date, and notarize if jurisdiction or recording requires it.

Configuring an online signing and record workflow

Configure an online workflow to collect signatures, route approvals, and attach inspection records to the Rainwater Management Note.

Field	Configuration
Signer Authentication	Email link with optional SMS code
Document Fields	Signature, date, inspector initials, maintenance checkbox
Routing	Sequential or parallel signer order configurable
Storage	Save signed PDF with audit trail to cloud

How digital submission and signing typically flow

This sequence shows how a Rainwater Management Note moves from draft to an executed, auditable record in project files.

Upload Document: Add the Note draft or template to the platform.
Place Fields: Insert signature, date, and maintenance fields.
Invite Signers: Send secure links or email invites to signers.
Complete Audit: System captures timestamps, IPs, and action logs.

Platform and integration considerations

Choose platforms and integrations that support secure e-signing, storage, and regulatory compliance.

Supported Formats: PDF, DOCX, and PDF/A
Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
Authentication: Email, SMS, and SSO options

Representative e-sign pricing and capability snapshot

Compare foundational pricing and feature indicators for common e-sign providers; signNow is listed first in the vendor column ordering.

	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

Security and compliance controls for recorded Notes

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

Access Controls: Role-based permissions and SSO support

Audit Trail: Detailed timestamps, IP addresses, and action logs

Certifications: SOC 2 Type II; ISO 27001; PCI DSS

HIPAA: BAA available when handling protected health information

Retention: Secure archival with exportable audit reports

Consequences and risks from an incorrect or incomplete Note

Incomplete Note: May impede enforcement; regulatory notice risk

Missing Signatures: Contract unenforceable against non-signing parties

Incorrect Dates: Affects inspection schedules and statute calculations

Unrecorded Instrument: Limits notice to future purchasers

False Statements: Civil penalties or permit revocation possible

Data Breach: Privacy fines if protected information is exposed

Common preparation problems to avoid

Using vague maintenance language that fails to define measurable standards and intervals creates disputes and enforcement gaps during inspections and transfers.
Failing to list a specific responsible party and contact information leaves municipalities or new owners unable to obtain timely repairs or reports.
Not recording the Note when required by local rule can leave subsequent buyers unaware of obligations and complicate compliance enforcement.
Relying on inconsistent file formats or unsigned scanned templates increases the chance of missing signatures and makes audit trails incomplete.

Typical timing and processing expectations

Typical timelines for completing and recording a Rainwater Management Note vary by permit and jurisdiction; the following are common scheduling expectations.

Permit Submission:

Submit the Note with stormwater permit or before final site approval

Initial Inspection:

Complete initial BMP inspection within 30 days of installation

Annual Inspection:

Schedule yearly inspections and record findings

Post-Storm Repair:

Repair or remediate within 7–30 days depending on severity

Record Retention:

Maintain records for minimum three years, longer if required

Key milestones from draft to ongoing compliance

Key milestones take a project from initial design through recorded maintenance obligations and ongoing inspections.

01

Design Approval

Accept BMP designs and document maintenance responsibilities.

02

Installation Completion

Verify installation and record installation date and inspector.

03

Execution and Notarization

Signers execute the Note; notarize or witness as jurisdiction requires.

04

Recording and Monitoring

Record with county if applicable; begin scheduled inspections.

Practical examples of how Notes are used on projects

Selected, hypothetical scenarios show typical use and outcomes for Rainwater Management Notes in project workflows.

Municipal Permit Condition

A city required a recorded Note attached to stormwater permit

The Note specified quarterly inspection and maintenance
After enforcement language and a clear repair timeline were recorded, the city had documented authority to require corrections and a consistent inspection record for permit renewals.

Residential Development

A developer included a Note in subdivision recordation

The Note assigned homeowner association maintenance duties
With defined standards and a recorded maintenance schedule, future owners received clear obligations and the association could budget inspections and repairs.

Core elements every professional Rainwater Management Note should include

A complete Note combines technical detail, duties, timing, enforcement, and recording instructions to make obligations clear and actionable.

Parties

Identify all responsible parties: owner, operator, and any third-party maintenance providers with full legal names and contact information.

Control Description

Describe each BMP in detail, including location, design standards, dimensions, materials, and reference to engineered drawings or exhibits.

Maintenance Requirements

State specific tasks, frequency, acceptable performance standards, and who bears costs to avoid ambiguity during inspections.

Inspection Schedule

Specify inspection frequency, required reports, acceptable formats, and retention period for inspection records and photographs.

Enforcement Remedies

Include remedies for default, notice procedures, and rights of municipal authorities to perform work and assess costs if needed.

Recording Instructions

State whether the Note will be recorded with the county recorder and include any attachments required for recording or title notice.

Practical tips to reduce errors and speed approval

Follow these practices to make the Note clear, enforceable, and easy to manage for all participants.

Use precise, measurable language

Avoid vague terms like reasonable maintenance. Specify tasks, frequencies, inspection deliverables, and acceptable thresholds so inspectors and courts can apply objective criteria.

Attach supporting technical exhibits

Include as-built drawings, manufacturer specs, and a site map. Clear exhibits reduce interpretation disputes and help future maintenance crews locate controls quickly.

Coordinate recording early

Confirm county recording requirements and notary or witness needs before execution to prevent rework and ensure the Note provides public notice when required.

Standardize templates

Use a vetted template for consistency across projects. Standardization reduces drafting errors, accelerates review, and simplifies transition to digital workflows.

Example signatories and their roles

City Stormwater Manager

Typically reviews and approves inspection schedules, enforces maintenance obligations, and receives inspection reports. The manager ensures the Note aligns with permit terms and municipal ordinances and can initiate enforcement where necessary.

Site Contractor

Often certifies installation and transfers maintenance duties at project closeout. The contractor provides as-built information and initial inspection documentation to support the Note and future compliance activities.

Frequently asked questions about the Rainwater Management Note

Answers to common execution, recording, and compliance questions to address routine obstacles encountered during preparation and signing.

Need help? Contact support

Can the Note be signed electronically?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the signing process demonstrates intent, consent, attribution, and record retention capability.
Is notarization always required?
Not always. Notarization is commonly required when recording the Note with a county recorder; local recorder rules determine whether a notary or witnesses are necessary for recordation.
What if a party changes ownership?
Record transfers and assign responsibilities via an amendment or assignment document. Recording an assignment gives notice to future purchasers and maintains enforceability in most jurisdictions.
How should inspection records be stored?
Store signed Notes and inspection reports in a secure, auditable format (PDF with audit trail). Maintain records per federal and state retention rules and for the life of the obligation plus recommended retention.
Can the Note be amended later?
Yes. Amendments should be executed by all parties, dated, and notarized or witnessed if required. Record the amendment where the original Note was recorded to preserve public notice.
Who enforces the maintenance obligations?
Enforcement may be performed by the designated responsible party, a homeowners association, or by municipal authorities under the permitting ordinance; the Note should identify enforcement mechanisms clearly.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now