Can as-built plans be signed electronically?

Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are met.

When is a notary required for as-built documents?

Notarization depends on the document and jurisdiction; certain instruments (deeds, affidavits) typically need acknowledgment. Check state notary rules and the contract to confirm.

How should I store final as-built plans?

Store certified PDFs and native files in encrypted storage with version control; retain per applicable retention rules such as IRS and HIPAA where relevant.

What if the owner requests changes after signoff?

Document change requests via official change order and produce an amended as-built set signed by responsible parties to preserve contractual clarity.

Are witness signatures required?

Witness requirements vary by state and document type; some states require witnesses for deeds or powers of attorney, but most as-built packages do not require witnesses.

How do I prove who signed an electronic as-built file?

Use platforms that capture an audit trail with timestamp, IP, signer email, and authentication method. Those elements support attribution and admissibility under ESIGN and UETA.

Electronic Signature
Templates
Project Management
Project Management As-Built Plans

Project Management As-Built Plans

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 PLANS

Project Identification

Project Name Project ID / Contract No.

Client Name: Service Provider:

Project Manager (Service Provider) Site Address / Building / Area

Revision Log

Revision 1 — Date: Description:

Revision 2 — Date: Description:

Revision 3 — Date: Description:

Scope of Work (As-Built)

The Service Provider shall prepare and deliver as-built plans that accurately document the final constructed condition, including all changes made during construction, field-installed components, concealed conditions discovered during construction, and final elevations, locations and dimensions of installed systems. The as-built plans shall reflect corrections, change orders, substitutions, and deviations from contract documents.

Detailed Scope of As-Built Plans Out-of-Scope Items

Deliverables and Acceptance Criteria

The following items constitute the minimum deliverables for As-Built Plans. Each deliverable must meet the acceptance criteria specified. Electronic deliverables shall be labeled with the project ID and revision number.

Record drawings (PDF) — Accepted when drawings reflect field-verified dimensions, keyed revisions, and are sealed where required.

Acceptance criteria for record drawings

CAD/GIS files (native files and exported PDFs) — Accepted when layer structure, coordinate system and file naming meet contract requirements.

Acceptance criteria for CAD/GIS files

Marked-up construction drawings and shop drawings — Accepted when all redline revisions are legible and cross-referenced to change orders.

Acceptance criteria for marked-up drawings

Operation & Maintenance manuals, warranties, manufacturer data — Accepted when complete, indexed, and contained in both electronic and one printed copy (if required).

Deviations, Change Orders and Supporting Documentation

List all deviations from contract documents reflected in the as-built plans, together with the authorizing change order number(s). Attach supporting test reports, inspection certificates, and approvals.

Referenced change order numbers Total change order cost associated with as-built items

Timeline and Milestones

Project Start Date: Substantial Completion: Final Completion:

Milestones (description and date)

Milestone 1: Date:

Milestone 2: Date:

Milestone 3: Date:

Budget, Fees and Payment Schedule

Total Contract Amount As-Built Deliverable Fee (if separate) Payment Schedule

Payment 1 (Description): Amount/Percent:

Payment 2 (Description): Amount/Percent:

Delivery Format and Media

Delivery media required:

PDFs (named with project ID and revision)

Native CAD/GIS files (include coordinate system and layer legend)

Hardcopy sets (number of sets) — Quantity:

Electronic transfer / file naming conventions

Confidentiality

All as-built materials, data and related documentation produced under this agreement are confidential project information. The Service Provider shall not disclose such information to third parties except as required for performance, without prior written consent of the Client. Confidential materials shall be protected with appropriate administrative, physical, and technical safeguards.

Client and Service Provider acknowledge and agree to the confidentiality terms set forth above.

Governing Law

This As-Built Plans deliverable and any disputes arising under or in connection with it shall be governed by and construed in accordance with the laws of:

Certifications

Service Provider Certification: The undersigned certifies that the as-built plans submitted under this document are, to the best of the undersigned's knowledge and belief, an accurate representation of the constructed work, including all known deviations from contract documents and authorized change orders. The Service Provider agrees to correct any material inaccuracies discovered within 60 days of written notice at no additional cost unless such inaccuracies are the result of changes after final acceptance.

Service Provider Representative (name and title)

Client Acceptance: The undersigned Client representative certifies that the as-built plans delivered meet the acceptance criteria set forth in this document, except for any punch list items noted in the attached acceptance record. Client acceptance does not release the Service Provider from warranty, correction or indemnity obligations under the underlying contract.

Client Representative (name and title)

Client Name:

By:

Date:

Service Provider Name:

By:

Date:

What Project Management As-Built Plans Document

Project Management As-Built Plans are the final, authoritative record drawings and supporting documents that reflect the physical conditions of a construction project as actually built. They capture revisions, field measurements, change orders, and material substitutions that occurred during construction and replace preliminary design drawings for operations, maintenance, permitting, and warranty purposes. These documents often include annotated floor plans, elevations, MEP layouts, equipment lists, and a revision log; they serve owners, facility managers, architects, and contractors as the definitive reference after project closeout.

Why accurate as-built plans matter for project closeout

Accurate Project Management As-Built Plans reduce disputes, accelerate final payments, enable reliable facility maintenance, and support regulatory compliance. They preserve institutional knowledge, inform future renovations, and serve as evidence in warranty or liability claims. Well-prepared plans limit rework and HSE risks by providing precise, auditable documentation of what was installed.

Who commonly prepares and relies on as-built plans

Typical stewards and recipients of as-built plans include project teams, design professionals, and asset owners responsible for long‑term operations.

General contractor — assembles field measurements, change orders, and final markups for owner acceptance and final payment processing.
Architect or engineer — reviews deviations from design, certifies compliance, and issues record drawings to accompany permits and warranties.
Owner / facility manager — uses plans for O&M, preventive maintenance scheduling, and future design decisions.

Responsibility often shifts at turnover: contractors deliver, designers certify, and owners retain for lifecycle use and legal records.

Essential components included in professional as-built plans

A complete Project Management As-Built Plans package includes graphical drawings, revision history, technical lists, field verification notes, BIM updates where available, and signed closeout certifications.

Final Drawings

Scaled plans and elevations updated to reflect installed conditions, with clear revision clouds and version identifiers for easy reference.

Revision Log

Chronological record of design changes, RFI resolutions, and change orders showing who approved each update and the effective date.

Field Notes

Photographs, measurement logs, and inspector remarks documenting site conditions and any deviations from original designs.

Material & Equipment Lists

Detailed inventories with model numbers, serial numbers, manufacturer data, and installation locations for O&M and warranty claims.

BIM / 3D Models

Updated building information models or point‑cloud captures that reflect as‑installed geometry and services for facilities management systems.

Closeout Certificates

Signed statements from responsible parties confirming completion, including commissioning reports, test results, and warranty information.

Step-by-step completion checklist for as-built plans

Follow a structured closeout workflow to ensure completeness and traceability before final delivery.

01

Collect Field Data: Capture measurements, photos, and change order details on site.
02

Update Drawings: Incorporate changes into CAD/BIM files and mark revision clouds.
03

Review & Certify: Design team reviews updates and certifies accuracy.
04

Deliver & Archive: Provide signed records to owner and store secure archival copies.

Typical routing and submission flow for finalized packages

A clear routing path reduces approval time and ensures each stakeholder receives the correct version and supporting files.

Prepare Package: Combine drawings, logs, and tests into a unified deliverable set.
Route for Review: Send package to architect, engineer, and owner for sequential review.
Obtain Signatures: Collect signatures from responsible parties, in-person or electronically.
Issue Final Copies: Distribute certified PDFs and native files to stakeholders and archives.

Digital workflows and platform integrations to support as-built delivery

Use a platform that supports standard file formats, secure signatures, and integration with project systems.

File Formats: PDF, DWG/DXF, DOCX, XLSX supported
Integrations: Salesforce, NetSuite, Procore, Box, Google Workspace
Security: AES-256 at rest; TLS 1.2/1.3 in transit

Choose a solution that preserves audit trails, enables role-based routing, and supports export to archival formats for record retention.

Typical timing and deadlines during project closeout

Closeout milestones have standard timing expectations; document delivery deadlines should be tracked against contract terms.

Final Inspection Submission:

Submit as-builts during final inspections per contract schedule.

Owner Acceptance Window:

Owner typically has a defined review period (e.g., 15–30 days).

Warranty Start Date:

Effective date often tied to owner acceptance or substantial completion.

Permit Closeout:

Local authority may require record drawings for permit finalization.

Archival Transfer:

Deliver electronic archives to owner immediately upon closeout.

Common preparation mistakes to avoid

Omitting change order references makes it difficult to reconcile deviations and creates payment disputes during closeout.
Using inconsistent project names or file naming conventions leads to misplaced records and delays in archival retrieval.
Failing to capture or date field verifications weakens the evidentiary value of as-built drawings in warranty or liability claims.
Delivering unsigned or partially signed packages commonly results in rejected submissions and repeated administrative cycles.

Consequences of incomplete or inaccurate as-built plans

Payment Delays: Final payment withheld

Contract Disputes: Claims and arbitration risk

Regulatory Noncompliance: Permit denial or fines

Warranty Issues: Void or delayed warranty claims

Safety Risks: Incorrect systems data increases hazards

Record Loss: Operational inefficiencies later

Practical examples of as-built workflows in the field

Real-world users describe streamlined record capture and faster turnarounds when as-built plans are completed and managed consistently.

Martin Properties

A local property manager implemented structured as-built submission during closeout to reduce rework.

The team standardized revision logs across projects.
"I can process and execute all of these documents online with 100% compliance and built-in security," said Tim Martin, Founder, Martin Properties, describing improved efficiency.

Optica Ventures

An investment firm required unified as-built packages for portfolio assets.

They enforced naming conventions and signature workflows.
Brian Fitzgibbons, COO at Optica Ventures LLC, noted that the interface is simple and easy to use for both teams and customers, improving record consistency.

Export formats and supporting files to include with final submission

Provide signed as-built plans in formats suitable for archives, operations, and permitting; include supporting documents as searchable attachments.

Download Formats

Deliver certified PDF/A for archival, native CAD/DWG for design reuse, and exportable XLSX for equipment inventories.

Supporting Documents

Attach commissioning reports, test certificates, product manuals, and signed change orders for a complete closeout package.

Annotations

Embed revision clouds, sticky notes, and photo callouts so reviewers can correlate field evidence with plan items.

Versioning

Maintain a visible version history with timestamps and approver names to preserve auditability.

Common eSignature vendor comparison for managing as-built approvals

Basic price and capability comparisons can guide platform selection; entries indicate typical starting points and common features across vendors.

	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 by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes	Yes	Yes	Yes	Varies
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 env/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently asked questions about preparing and delivering as-built plans

Answers below cover common signing, retention, notarization, and revision questions encountered at project closeout.

Need help? Contact support

Can as-built plans be signed electronically?
Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are met.
When is a notary required for as-built documents?
Notarization depends on the document and jurisdiction; certain instruments (deeds, affidavits) typically need acknowledgment. Check state notary rules and the contract to confirm.
How should I store final as-built plans?
Store certified PDFs and native files in encrypted storage with version control; retain per applicable retention rules such as IRS and HIPAA where relevant.
What if the owner requests changes after signoff?
Document change requests via official change order and produce an amended as-built set signed by responsible parties to preserve contractual clarity.
Are witness signatures required?
Witness requirements vary by state and document type; some states require witnesses for deeds or powers of attorney, but most as-built packages do not require witnesses.
How do I prove who signed an electronic as-built file?
Use platforms that capture an audit trail with timestamp, IP, signer email, and authentication method. Those elements support attribution and admissibility under ESIGN and UETA.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now