Reference
Cite the original contract by title and date, identify affected sections or paragraph numbers, and state the addendum’s effective date so the amendment integrates cleanly with existing provisions.
Use a Construction Project Contract Addendum to document agreed changes, allocate risk, and preserve contract continuity. A clear addendum helps avoid scope creep, provides a record for payment adjustments and claims, and supports enforceability under ESIGN and UETA when executed electronically.
General contractors, subcontractors, owners, architects, and engineers commonly prepare or approve project contract addenda when scope, budget, or schedule change.
Ensure the signatory has authority and document routing reflects corporate approval processes to maintain enforceability.
Cite the original contract by title and date, identify affected sections or paragraph numbers, and state the addendum’s effective date so the amendment integrates cleanly with existing provisions.
Describe additions or deletions to work with precise specifications, deliverables, measurable outcomes, and exact boundaries to avoid ambiguity and downstream disputes during construction and contract administration.
Specify any change in contract sum, unit rates, allowances, retainage effects, and how additional costs will be invoiced and paid, including timing and conditions for payment.
State adjustments to the completion date, milestones, or liquidated damages, including any extension for weather, delays, or owner-directed changes and the method for computing new deadlines.
Identify required approvals, signatures, authorized representatives, and any third-party consents, and record the sequence of approvals necessary before work or payment changes take effect contractually.
Attach revised drawings, specifications, price breakdowns, revised schedules, insurance certificates, or revised permits with version dates to provide a complete record supporting the amendment documentation.
| Field Name and Configuration Settings | Configuration instructions and expected input format |
|---|---|
| Signature field placement and role | Assign signer role and set required flag |
| Conditional field logic and triggers | Show cost fields only if change exceeds threshold |
| Date and project milestone fields | Use MM/DD/YYYY format; link to schedule for updates |
| Signer authentication settings and strength | Choose email, SMS code, or identity verification according to risk |
Digital submission requires a platform that supports secure e-signature, audit trails, and conditional fields.
Issue within the period defined by the contract or within 7–14 days of change discovery.
Typical review 3–10 business days depending on complexity.
Owner should respond within contractual notice period or risk deemed approval.
Allow one payroll or invoice cycle plus verification.
Preserve rights by providing written notice within contract-specified timeframes.
| 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 free trial | Varies | Varies | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Optica Ventures used an addendum to formalize a midproject scope increase, ensuring pricing and schedule were agreed in writing before work proceeded.
A regional property manager added a schedule extension via addendum after unexpected site conditions delayed mobilization and required revised contractor responsibilities.