Are electronic signatures legally valid?

Yes. Electronic signatures that meet ESIGN’s four-part test (intent, consent, attribution, and reliable record retention) are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes in most jurisdictions.

When is notarization required?

Notarization is required when the contract, property recording, or specific state law demands it. Requirements vary by state and by document type; for deeds or certain official filings, a notary or remote online notarization (where permitted) is often mandatory.

How do I correct an error after signing?

Best practice is to create a revision or amendment signed by the same authorized parties documenting the correction. Never alter a signed original without a signed amendment that records the change and links to the original version.

Who should sign the as-built document?

Signers typically include the contractor’s authorized representative, the project engineer or designer where applicable, and the owner or owner’s representative. Role-based sign-offs preserve responsibility and contractual acceptance.

Can as-builts contain protected health information (PHI)?

Yes, if they include PHI or system details affecting patient data. In such cases, handle distribution under HIPAA rules, execute a BAA with the e-sign provider, and limit access per privacy policies.

What archival formats and retention should I use?

Store a signed PDF/A copy with an immutable audit trail and retain it per applicable regulators: IRS three-year baseline (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and any longer state or contract-specific period.

Electronic Signature
Templates
Project Management
Project Management As-Built Document

Project Management As-Built Document

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

Project Management As-Built Document

Project Identification

Project Title: Project ID:

Client Name Project Manager Service Provider / Contractor Site Address

Contract Number: Original Contract Date:

Scope of Work (As-Built)

Final Scope as Constructed Items Specifically Excluded from As-Built Scope

Deliverables and Acceptance

Deliverable 1: Delivered Date:

Acceptance Criteria (Deliverable 1)

Deliverable 2: Delivered Date:

Acceptance Criteria (Deliverable 2)

Timeline and Milestones

Construction Start Date: Substantial Completion Date: Final Completion Date:

Key Milestones

Budget, Payments, and Change Orders

Original Contract Value: $ Total Approved Change Orders: $

Final Contract Value (incl. COs): $ Retention Held: $

Payment Schedule / Final Payment Conditions Change Order Summary (list references and brief description)

As-Built Technical Details

As-Built Drawing Revisions Deviations from Design / Field Changes Final Quantities and Test Results

Commissioning Complete: Commissioning Report Reference:

Warranties, Defects Liability, and Remedies

Warranty Period (months):

The Service Provider certifies that, to the best of its knowledge, the as-built documents, records, and drawings attached to this document accurately reflect the condition of the work as constructed, except for items expressly noted in Deviation attachments. The Service Provider shall, at its sole cost, correct any defects identified within the defects liability period arising from non-conformance with contract requirements.

Confidentiality and Records

All technical documents, drawings and reports submitted as part of these as-built records are confidential between the parties and shall not be disclosed except as required by law or as necessary for operations and maintenance. Each party shall retain a complete copy of all as-built records for a minimum of years following Final Completion.

Governing Law

This As-Built Document shall be governed by and construed in accordance with the laws of the State of without regard to conflict of laws principles.

Attachments and Supporting Documentation

List of Attachments (drawings, reports, test certificates, photos) Outstanding Items / Punchlist (if any)

Certifications

The undersigned representative of the Service Provider certifies that the work reflected in these as-built documents has been completed in accordance with the contract documents and that all required tests and inspections have been performed and documented, except as noted herein. The undersigned further certifies that all permits, inspections and approvals required for the work have been obtained where applicable.

Certifying Officer (Service Provider) Title

Client

Client Name:

By:

Date:

Service Provider

Service Provider Name:

By:

Date:

What the Project Management As-Built Document Is and when it matters

A Project Management As-Built Document records the final, built condition of a project after construction or implementation, showing deviations from design documents, field-measured dimensions, materials used, and final system configurations. It consolidates redline drawings, revision logs, approvals, test results, and equipment lists so owners, contractors, and regulators have a single authoritative record of what was actually delivered. As-builts support warranty claims, maintenance planning, regulatory compliance, and future renovations; they are typically prepared at closeout and signed by responsible parties to confirm accuracy and completeness.

Why an accurate As-Built Document is essential

An accurate Project Management As-Built Document reduces disputes, speeds maintenance, and establishes contractual and regulatory proof of completion. Properly executed as-builts support warranty enforcement, change-order reconciliation, and regulatory inspection. Electronic execution meets U.S. legal standards under the ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes when intent, consent, attribution, and retention are satisfied.

Typical teams that prepare and rely on as-built records

Use role-based sign-offs to ensure each party accepts their section of the record before finalization.

Project managers and PMO teams overseeing closeout, quality assurance, and acceptance procedures.
Contractors and subcontractors providing field measurements, change logs, and installation notes for warranty and invoicing.
Facility owners, maintenance teams, and asset managers who use as-builts for operations and future renovations.

Core components to include in a professional As-Built Document

As-built quality depends on comprehensive content, clear references, and traceable approvals. Include all items below for a complete closeout deliverable.

Redline Drawings

Final drawings showing field-measured deviations from design, layered by discipline and dated to reflect the final coordinate/measurement changes for construction verification and future work.

Revision Log

A dated record of all change orders and revisions with author, reason, and approval reference to track why and when each deviation occurred during construction.

Materials & Equipment

Complete listing of installed materials, model numbers, serial numbers, and vendor data to support warranties, spare part procurement, and lifecycle planning.

Test & Commissioning Reports

Results of system tests, commissioning checklists, and acceptance criteria demonstrating that installed systems meet performance requirements at handover.

Deviation Justifications

Narrative explanations for design changes or field decisions tied to approvals and supporting documentation to reduce later claims or ambiguity.

Signatures & Approvals

Role-based sign-off blocks for contractor, engineer, and owner with dates and method of execution recorded for legal and contractual traceability.

Step-by-step: preparing and finalizing an As-Built Document

Follow these sequential steps to assemble, verify, and execute the final as-built package for project closeout.

01

Collect Field Data: Gather measured drawings, photos, and vendor documentation from site teams.
02

Update Drawings: Apply redlines to CAD/PDF master files and reconcile version history.
03

Assemble Closeout Pack: Combine drawings, logs, test reports, and deviation narratives into one package.
04

Execute Signatures: Obtain role-based approvals and timestamped signatures before archiving.

How to configure a digital workflow for as-built review and sign-off

Set minimal friction authentication, clear signer order, and document retention options to match contract and compliance needs.

Field	Configuration
Signer Order	Sequential or parallel routing
Authentication	Email + optional SMS code or KBA
Versioning	Automatic version control enabled
Audit Trail	Capture IP, timestamps, and action log

Where to send the completed As-Built Document

Determine destination recipients and archival locations before final signing to ensure contract obligations and regulatory filings are met.

Owner / Client: Primary recipient for acceptance, operations, and warranty start.
Contractor Archive: Contractor retains a signed copy for warranties and claim defense.
Regulatory Agencies: Submit required deliverables to permitting authority where statute or permit requires filing.
Facilities Team: Operations and maintenance receive equipment lists and O&M manuals for lifecycle support.

Delivery and technical requirements for e-submissions

Ensure archival storage is searchable and includes an immutable audit trail for future reference and dispute resolution.

File Formats: PDF, DOCX, CAD exports
Integrations: Salesforce | NetSuite | Procore
Authentication: Email, SMS, or SSO

Typical timing expectations and contractual deadlines

Contract language sets exact deadlines; these are typical timing expectations during project closeout.

Substantial Completion:

Issue preliminary as-builts at substantial completion for owner review.

Final Submission:

Deliver final signed as-builts as required by contract, often before final payment or retainage release.

Warranty Start:

Effective date on as-builts often triggers warranty commencement and service obligations.

Regulatory Filing:

Submit any required permit closeout documents within the timeframe specified by the issuing agency.

Record Archival:

Archive signed package immediately after acceptance to preserve version integrity.

Common mistakes to avoid when preparing as-built records

Inconsistent naming or numbering between drawings and submittals, which breaks traceability and causes rework.
Failing to capture and attach approval references for deviations, leaving change justifications undocumented.
Using ambiguous language in deviation descriptions rather than precise measurements and location references.
Not preserving an immutable audit trail of signer identity and timestamps before final archival.

Risks and contractual consequences of incomplete or incorrect as-builts

Payment Delay: Final payment or retainage may be withheld.

Warranty Disputes: Unclear records can void warranty claims.

Regulatory Fines: Failure to file required closeout documents can incur agency penalties.

Change Order Claims: Missing evidence undermines contractor entitlement to extras.

Liability Exposure: Inaccurate as-builts increase risk in future design or remediation work.

Record Rejection: Owner or regulator may reject incomplete packages.

Comparison of common eSignature vendors and considerations for as-built workflows

Platform selection affects cost, bulk send capability, HIPAA support, and envelope limits. signNow appears first for clarity and comparison.

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

Frequently asked questions about completing and e-signing as-built documents

Answers address legal validity, notarization, revisions, secure delivery, PHI handling, and storage to reduce common friction during closeout.

Need help? Contact support

Are electronic signatures legally valid?
Yes. Electronic signatures that meet ESIGN’s four-part test (intent, consent, attribution, and reliable record retention) are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes in most jurisdictions.
When is notarization required?
Notarization is required when the contract, property recording, or specific state law demands it. Requirements vary by state and by document type; for deeds or certain official filings, a notary or remote online notarization (where permitted) is often mandatory.
How do I correct an error after signing?
Best practice is to create a revision or amendment signed by the same authorized parties documenting the correction. Never alter a signed original without a signed amendment that records the change and links to the original version.
Who should sign the as-built document?
Signers typically include the contractor’s authorized representative, the project engineer or designer where applicable, and the owner or owner’s representative. Role-based sign-offs preserve responsibility and contractual acceptance.
Can as-builts contain protected health information (PHI)?
Yes, if they include PHI or system details affecting patient data. In such cases, handle distribution under HIPAA rules, execute a BAA with the e-sign provider, and limit access per privacy policies.
What archival formats and retention should I use?
Store a signed PDF/A copy with an immutable audit trail and retain it per applicable regulators: IRS three-year baseline (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and any longer state or contract-specific period.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now