Establishing secure connection…Loading editor…Preparing document…

Architectural Delivery Act Template

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

ARCHITECTURAL DELIVERY ACT TEMPLATE

This Architectural Delivery Act (the "Act") is made and entered into as of Effective Date: by and between Client Name: , with principal place of business at ("Client"), and Architect Name: , with principal place of business at ("Architect").

RECITALS

WHEREAS, Client desires to obtain certain architectural deliverables, drawings, models, specifications and related instruments of service in connection with the project described as Project Name: (the "Project");

WHEREAS, Architect is engaged in the business of providing architectural design, documentation and delivery services and represents that Architect has the experience, personnel and capability to produce and deliver the required Deliverables as defined below; and

WHEREAS, the parties wish to set forth their respective obligations, the form and timing of delivery of instruments of service, ownership and transfer of intellectual property rights upon delivery, acceptance criteria, and remedies in the event of defective or incomplete delivery.

NOW, THEREFORE, in consideration of the mutual covenants and promises set forth herein, the parties agree as follows:

1. DEFINITIONS

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

"Deliverables" means the drawings, specifications, models, digital files, shop drawings, calculations and related documents specifically described in the Schedule of Deliverables and any subsequently approved Change Order.

"Acceptance" means the written acceptance by Client in accordance with Section 4 following inspection and completion of any punch list items identified during the Inspection Period.

2. SCOPE OF DELIVERY

Architect shall deliver the Deliverables described in the Schedule of Deliverables to Client in the formats specified therein. Architect warrants that the Deliverables supplied under this Act shall conform materially to the requirements of the Schedule of Deliverables and the accepted professional standards for architectural services in the jurisdiction of the Project.

3. DELIVERY SCHEDULE; MILESTONES

Architect shall deliver the Deliverables according to the milestones set forth below. Time is of the essence with respect to delivery dates.

Due Date:

Due Date:

4. ACCEPTANCE; INSPECTION

Upon delivery of each Deliverable, Client shall have an Inspection Period of days to inspect the Deliverable and either provide written Acceptance or identify defects in writing. If Client does not provide written notice of rejection within the Inspection Period, the Deliverable shall be deemed accepted.

If the Deliverable is rejected, Architect shall, at Architect's expense, correct or replace the Deliverable within a reasonable period and resubmit for re-inspection. Client's acceptance shall not relieve Architect of liability for defects discovered after Acceptance that arise from Architect's failure to exercise reasonable professional skill and care.

5. TRANSFER OF OWNERSHIP; INTELLECTUAL PROPERTY

Subject to full payment of all amounts due under Section 6, Architect assigns to Client all right, title and interest in the Deliverables to the extent necessary for Client to use, reproduce and modify the Deliverables for the Project. Architect retains the right to use general knowledge, skills and experience embodied in the Deliverables subject to Client confidentiality obligations.

Architect warrants that it has the authority to grant the rights granted herein and that the Deliverables do not infringe third-party intellectual property rights. Architect shall, at Architect's expense, defend, indemnify and hold harmless Client from and against any claim alleging infringement of a third party's intellectual property rights arising from Architect's Deliverables.

6. FEES; PAYMENT

As consideration for the Deliverables and services rendered under this Act, Client shall pay Architect the sum set forth below and according to the payment schedule. Payment obligations are absolute and not contingent on third-party funding unless otherwise stated in writing.

7. CHANGE ORDERS

Any changes to the scope of the Deliverables or schedule shall be effected only by a written Change Order signed by both parties describing the change, any adjustment to the fee, and any adjustment to the delivery schedule. Architect shall not be required to perform work outside the scope without an executed Change Order.

8. WARRANTIES; STANDARD OF CARE

Architect warrants that the Deliverables will be prepared in a manner consistent with the level of care and skill ordinarily exercised by members of the architectural profession practicing under similar conditions at the same time and in the same locality. Architect's sole obligation for breach of this warranty shall be to correct nonconforming Deliverables at Architect's expense as provided in Section 4.

9. INDEMNIFICATION

Architect shall indemnify, defend and hold harmless Client, its officers, directors and agents from and against all claims, liabilities, losses and expenses (including reasonable attorneys' fees) arising out of Architect's negligent acts, errors or omissions in the preparation or delivery of the Deliverables, except to the extent caused by Client's negligence or willful misconduct.

10. INSURANCE

Architect shall maintain, at Architect's expense, professional liability insurance, general liability insurance and such other coverages as reasonably required by Client. Upon request, Architect shall furnish certificates evidencing such insurance coverage to Client.

11. CONFIDENTIALITY

Each party shall maintain in confidence all proprietary or confidential information disclosed by the other party in connection with this Act and shall not disclose such information except as required by law or with the prior written consent of the disclosing party. Confidential information does not include information that is or becomes generally available to the public other than by breach of this Section.

12. NOTICES

All notices required or permitted under this Act shall be in writing and delivered to the addresses below by hand, certified mail (return receipt requested) or nationally recognized courier service, and shall be effective upon receipt.

13. AMENDMENTS; WAIVER; COUNTERPARTS

This Act may be amended only by a written agreement signed by both parties. No failure or delay by either party in exercising any right shall operate as a waiver of that right. This Act 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.

14. GOVERNING LAW; ENTIRE AGREEMENT; SEVERABILITY

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

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

15. REMEDIES; LIMITATION OF LIABILITY

The parties' rights and remedies under this Act are cumulative and in addition to any other rights and remedies available at law or in equity. Except to the extent arising from Architect's gross negligence or willful misconduct, neither party shall be liable to the other for consequential, incidental, special or punitive damages.

Notwithstanding the foregoing, Architect's aggregate liability under this Act arising from or related to the Deliverables shall not exceed the total fees paid to Architect under this Act.

Client

Printed Name:

By:

Date:

Title:

Architect

Printed Name:

By:

Date:

Title:

Enter text✕

What the Architectural Delivery Act Template Is and When It Applies

The Architectural Delivery Act Template is a standardized contract used to document delivery obligations, acceptance criteria, schedules, and ownership of architectural work product for building projects. It clarifies scope, milestones, inspection and approval steps, payment triggers, and post-delivery support. The template is suitable for fee-based design engagements, consultant deliverables, and phased project handovers where written acceptance and traceable records are required. When executed electronically it must meet ESIGN (15 U.S.C. ch. 96) and applicable state UETA or ESRA rules to be enforceable across U.S. jurisdictions.

Why a Structured Delivery Agreement Matters

A clear Architectural Delivery Act Template reduces disputes by defining deliverables, timelines, and acceptance tests, and creates an auditable record of transfers. Consistent templates speed review, help allocate risk, and support regulatory filing or permitting steps when plans are submitted to authorities.

Why a Structured Delivery Agreement Matters

Who Commonly Uses This Delivery Template

Typical users include project architects, design firms, general contractors, and owners who must track design deliverables and formal acceptance.

  • Design Firms and Architects — Use the template to specify drawing sets, BIM models, and deliverable formats for handover to construction and owners.
  • General Contractors — Rely on delivery milestones and acceptance criteria to schedule procurement, installation, and inspections.
  • Owners and Developers — Require defined deliverables, intellectual property terms, and remedies for late or incomplete submissions.

The template also supports municipal or client-facing submissions where retained records and signature logs are needed for compliance.

Core Elements to Include in a Professional Template

A complete Architectural Delivery Act Template organizes commercial, technical, and administrative terms so parties have a shared expectation for each delivery and handover event.

Scope of Work

Precisely list drawings, specifications, BIM models, deliverable formats, and associated services so there is no ambiguity about what must be delivered.

Delivery Schedule

Set milestone dates, interim submissions, and conditions for delay and extensions, including notice and approval procedures for schedule changes.

Acceptance Criteria

Define review periods, punchlist procedures, criteria for formal acceptance, and steps to correct nonconforming work before final sign-off.

Fees and Payments

Tie payments to milestones or accepted deliverables, state invoicing requirements, and include remedies for late payment or disputed amounts.

Intellectual Property

Specify ownership, license scope, permitted uses of CAD/BIM files, and restrictions on third-party reuse or modification.

Liability and Warranties

Limitations of liability, warranty periods for deliverables, insurance obligations, and indemnity provisions tailored to design-related risk.

Security and Compliance Controls to Reference

Encryption: AES-256 encryption at rest
Transport Security: TLS 1.2/1.3 in transit
Audit Trail: Timestamped event history
Access Controls: Role-based permissions
Legal Compliance: ESIGN and UETA compliant
Data Residency: GDPR and CCPA controls

Step-by-Step: Completing and Executing the Template

Follow a consistent sequence to prepare, review, sign, and archive the agreement so each party has an auditable record of the delivery obligations.

  • 01
    Prepare Document: Populate all required fields and attach exhibits.
  • 02
    Internal Review: Legal and PM review acceptance and risk clauses.
  • 03
    Execute Signatures: Use compliant eSignature or wet signature per parties' preference.
  • 04
    Archive Record: Store final executed PDF with audit trail.

Configuring an Online Delivery Workflow

Configure fields and authentication when using an eSignature platform to match your acceptance and audit requirements.

Field Configuration
Signature fields Required; signer name and date enforced
Date fields Auto-fill MM/DD/YYYY when signed
Conditional sections Show based on selected deliverable options
Authentication SMS code or email link; KBA optional

Technical and Integration Considerations for eSubmission

Identify file formats, signer authentication, and integration points before distributing the template electronically.

  • File Formats: PDF, DOCX, and native CAD exports
  • Integrations: Salesforce, NetSuite, Procore, Box
  • Authentication: Email link, SMS code, or KBA

Ensure your chosen platform supports audit trails, retention export, and the integration endpoints needed for project controls and permitting workflows.

Where to Send the Executed Template

Routing depends on the purpose: client records, permitting authorities, construction teams, or long-term project archives each require different recipients and formats.

  • Client Copy: Deliver executed PDF to owner and client contacts
  • Municipal Filing: Submit required plans to building department
  • Contractor Distribution: Share accepted drawings with general contractor
  • Project Archive: Store signed file in project document management

Real-World Examples of Electronic Delivery and Acceptance

These examples illustrate typical results when firms adopt structured digital delivery and auditable signatures for design handovers.

Martin Properties — Tim Martin

As a regional property owner we moved to online execution to speed handovers and compliance checks.

  • Result: reduced turnaround and fewer missing documents.
  • Outcome: Tim Martin reports efficient processing and secure, compliant recordkeeping for portfolio projects after switching to electronic workflows.

Optica Ventures — Brian Fitzgibbons

The firm standardized delivery templates for boutique developments to reduce ambiguity in handovers.

  • Result: clearer expectations and faster approvals.
  • Outcome: Brian Fitzgibbons highlights that a simple, consistent template improved internal coordination and made client acceptance straightforward.

Consequences of Poorly Prepared Delivery Agreements

Unclear Acceptance: Dispute over completion status
Missing Signatures: Execution may be unenforceable
Inadequate IP Terms: Ownership disputes or reuse limits
Late Deliverables: Delay claims and liquidated damages
Insufficient Insurance: Increased exposure on claims
Noncompliant Records: Regulatory rejection or rework

Common Preparation Mistakes to Avoid

  • Vague deliverable descriptions that omit file types, revisions, or model versions cause acceptance disputes and rework during construction.
  • No defined review period or acceptance procedure leads to lingering punchlists and unresolved approval responsibilities between parties.
  • Using inconsistent party names or titles on different documents can block payment, delay permitting, or create enforceability problems.
  • Failing to specify authentication or signature method creates uncertainty about whether electronic execution meets ESIGN or state UETA/ESRA requirements.

Key Timing Rules and Typical Deadlines

Standard timing provisions reduce conflict; set explicit review windows, cure periods, and invoicing deadlines tied to accepted deliverables.

Submission Deadline:

Deliver initial submission by milestone date specified in schedule

Client Review Period:

Allow a stated number of days, commonly 14 calendar days

Municipal Filing:

File plans per local building department timelines

Final Acceptance:

Trigger upon signed acceptance or lapse of review window

Invoice Due Date:

Tie payment due date to accepted milestones

Vendor Pricing and Feature Comparison for eSignatures

Compare common eSignature options used to execute contracts like the Architectural Delivery Act Template; signNow appears first per vendor listing rules.

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 No No 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
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently Asked Questions and Troubleshooting

Answers address execution, enforceability, eSignature choices, and common platform questions when using the Architectural Delivery Act Template.


Need help? Contact support

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