Establishing secure connection…Loading editor…Preparing document…

California Civil Code Section 8132

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

CONDITIONAL WAIVER AND RELEASE
UPON PROGRESS PAYMENT

(CA Civil Code § 8132)

THIS DOCUMENT WAIVES THE CLAIMANT'S LIEN, STOP PAYMENT NOTICE, AND PAYMENT BOND RIGHTS EFFECTIVE ON RECEIPT OF PAYMENT. A PERSON SHOULD NOT RELY ON THIS DOCUMENT UNLESS SATISFIED THAT THE CLAIMANT HAS RECEIVED PAYMENT.

Identifying Information:

This document waives and releases lien, stop payment notice, and payment bond rights the claimant has for labor and service provided, and equipment and material delivered, to the customer on this job through the Through Date of this document. Rights based upon labor or service provided, or equipment or material delivered, pursuant to a written change order that has been fully executed by the parties prior to the date that this document is signed by the claimant, are waived and released by this document, unless listed as an Exception below.

This document is effective only on the claimant's receipt of payment from the financial institution on which the following check is drawn:

Exceptions:

(1) Retentions.

(2) Extras for which the claimant has not received payment.

(3) The following progress payments for which the claimant has previously given a conditional waiver and release but has not received payment:

(4) Contract rights, including (A) a right based on rescission, abandonment, or breach of contract, and (B) the right to recover compensation for work not compensated by the payment.

Signature:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What California Civil Code Section 8132 Covers and why it matters

California Civil Code Section 8132 is a numbered provision within the California Civil Code. This page summarizes practical implications for parties who reference the statute in contracts or filings, explains how to complete related forms, and highlights electronic signing, notarization, and retention considerations under federal and state e-signature law.

Why understanding Section 8132 is useful for document accuracy

Knowing how Section 8132 applies helps avoid procedural errors when preparing agreements or statutory notices that rely on California law. Clear compliance reduces the risk of rejection, procedural delay, or later challenge in court; it also informs whether electronic execution and remote notarization are permissible.

Why understanding Section 8132 is useful for document accuracy

Who typically references California Civil Code Section 8132

Parties that commonly reference Section 8132 include attorneys, title and escrow professionals, compliance officers, and contract administrators who work with California-governed agreements or notices.

  • Attorneys and paralegals ensuring statutory language is properly included and executed
  • Real estate and title professionals preparing deeds, acknowledgements, or disclosure-related filings
  • Corporate legal and compliance teams that need to confirm method of execution and record retention

Core elements to check when your document cites Section 8132

A professional document referencing California Civil Code Section 8132 should explicitly note the statute, the parties, effective date, execution blocks, notarization needs (if any), and retention instructions so downstream users can validate compliance and preserve chain-of-custody.

Statute citation

Include the exact citation 'California Civil Code Section 8132' and any subsection identifiers to avoid ambiguity.

Parties

List full legal names and entity types (LLC, corporation, individual) as they appear on government records.

Effective date

State the MM/DD/YYYY effective date and whether performance or notice triggers begin on execution.

Execution block

Provide distinct signature lines, printed names, titles, and signature dates for each signing party.

Notary elements

Where notarization is required, include acknowledgement or jurat text consistent with California practice.

Retention note

Add a short directive on how long parties must retain the signed record and where it will be stored.

Security and legal controls to protect Section 8132 documents

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit trail: Timestamped signer actions and IP address
Authentication: Email, SMS code, or advanced signer verification
Certifications: SOC 2 Type II; ISO 27001
Compliance: ESIGN, UETA, HIPAA (BAA required)
Tamper evidence: Document integrity checks and version history

Quick steps to prepare and finalize a Section 8132 document

Follow these sequential steps to prepare, sign, and preserve a document that relies on California Civil Code Section 8132.

  • 01
    Prepare: Draft text, include the statute citation and parties' details.
  • 02
    Review: Confirm effective date, execution blocks, and any notary requirements.
  • 03
    Sign: Execute by hand or e-sign using a method that meets ESIGN/UETA tests.
  • 04
    Retain: Store the signed copy and audit trail in a secure repository.

Recommended digital workflow settings for documents citing Section 8132

Configure your e-signing workflow to collect the right evidence of execution and to route documents for review and storage.

Field Recommended Setting
Signature type Audit-tracked electronic signature with timestamp
Authentication Email + SMS code for signer verification
Notary option Support for in-person or RON where permitted
Storage Encrypted cloud storage with versioning enabled

How electronic execution typically flows for statute-linked documents

A simple, auditable electronic signing flow reduces friction and preserves the evidence required to show valid execution under ESIGN and UETA.

  • Upload: Sender uploads the completed document to the signing platform.
  • Place fields: Designate signature, date, and notary fields before sending.
  • Authenticate: Signer verifies identity via email, SMS, or KBA.
  • Complete: Signed PDF and audit trail are generated and stored.

Platform features to look for when eSigning documents referencing Section 8132

Choose a platform that provides secure storage, comprehensive audit trails, and appropriate authentication and notarization support.

  • Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
  • Document formats: PDF, DOCX, HTML, Excel supported
  • Notarization support: In-person and remote-notary workflows

Verify the platform supports the legal and technical evidence you need (audit trail, tamper protection, and secure long-term storage).

Consequences and statutory penalties for incorrect filings or missing disclosures

Invalid execution: Execution defects can render a document unenforceable
Tax penalties: 1099 failures: $60–$330 per form (IRC §6721)
I-9 penalties: I-9 paperwork fines $281–$2,789 per violation (8 CFR §274a.2)
Intentional disregard: $660+ per form with no maximum (IRC §6721)
Notary errors: Improper notarization can trigger rejection or re-execution
Data breach: HIPAA or state privacy violations risk fines and corrective action

Common pitfalls when preparing a Section 8132 document

  • Using inconsistent party names between sections and signature blocks, which complicates enforcement and tax reporting.
  • Failing to record signer's consent to electronic records where ESIGN consumer disclosures are required.
  • Placing notarization language incorrectly or signing before the notary completes the acknowledgement.
  • Not preserving the audit trail or original signed PDF, undermining chain-of-custody evidence.

Real-world examples of using eSignatures alongside statutory language

Two representative examples show how digital signing and secure workflows support statutory compliance and document lifecycle management.

Martin Properties

Local broker digitized signature collection to execute a statutory disclosure quickly

  • Used mobile e-signing for remote clients
  • The process reduced turnaround, preserved audit trails, and avoided re-execution due to missing signatures.

BIS (Business Services)

Corporate legal team standardized a statute-referenced acknowledgement form for vendor onboarding

  • Deployed template and automated routing
  • That standardization improved completeness and produced a consistent retention path across the organization.

Practical tips to reduce risk when relying on Section 8132

Adopt these practices to ensure enforceability and maintain clear records when executing documents that reference the statute.

Use exact citations
Cite 'California Civil Code Section 8132' precisely and avoid shorthand to prevent ambiguity in interpretation.
Confirm execution method
Determine whether electronic signatures, in-person signatures, or notarization are required before sending for signature.
Preserve proof
Retain the signed document plus a complete audit trail showing identity verification, timestamps, and IP addresses.
Consult counsel
When uncertain about procedural or jurisdictional effects, seek legal advice to prevent downstream disputes.

Typical timing considerations and response windows

Timing affects enforceability and procedural obligations. Below are standard timing considerations to track when preparing, serving, or filing documents.

Provide on request:

Certain records must be produced 'on request' to counterparties or regulators without delay

Execution date:

Document should be dated upon final signature to fix effective obligations

Notary timing:

Do not sign the notary block before the notary completes the acknowledgement

Retention start:

Retention typically begins on execution or the effective date, depending on the record type

Consult deadlines:

When filing with public offices, verify local cutoff and recording schedules

Comparison: signNow and commonly used eSignature providers

Below is a feature and price snapshot to help select an eSignature provider for executing and storing statute-linked documents. Pricing reflects typical per-user plans; verify vendor sites for plan details.

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 execution, e-signing, and Section 8132

Answers to common questions cover enforceability, electronic signatures, notarization, and record retention when a document cites California Civil Code Section 8132.


Need help? Contact support

Explore Templates

Agreement to Partition Community Property Non-Exclusive Easement Affidavit of Marital Status Consulting Agreement With Former Employee Company Name Change Affidavit Medical Directive
be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.