Can a revision be signed electronically?

Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when the four-part validity test is met: intent, consent, attribution, and retention.

When is notarization required?

Notarization is required when a revision changes a deed, easement, or document that the state or county requires notarized acknowledgement; requirements vary by state and document type.

Who may sign on behalf of an organization?

An authorized signer listed in corporate resolutions or contracting authority may sign; attach delegation evidence if authority is delegated to a project manager.

Are remote notaries acceptable?

Remote online notarization (RON) is available in many states but requirements differ; confirm state notary rules and retention obligations for audio‑video recordings.

How to correct mistakes after signing?

Issue an explicit amended revision that references the original document, captures the reason for correction, and obtains fresh approvals from required parties.

Where should signed revisions be stored?

Store signed revisions in a secure project repository with version history and access controls; retain per applicable federal, state, and industry retention rules.

Electronic Signature
Templates
Project Management
Project Management Site Revision

Project Management Site Revision

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

PROJECT MANAGEMENT SITE REVISION

Project Identification

Project Title:

Project ID: Revision Request No.:

Client Service Provider

Project Manager: Contact:

Revision Requested By: Request Date:

Scope of Revision

Describe the specific site revision requested, objectives, and functional expectations. The Service Provider shall perform the following work in accordance with the specifications below.

Out of Scope (items not included in this revision)

Deliverables and Acceptance Criteria

List each deliverable associated with this revision. Acceptance of each deliverable shall be in writing as provided below.

Deliverable 1 Deliverable 2

Acceptance Procedure: Upon completion of each deliverable, the Service Provider will submit a written acceptance request. The Client shall perform acceptance testing within days. If the Client does not provide written rejection with specific defects within that period, the deliverable shall be deemed accepted.

Timeline & Milestones

Overall Start Date: Projected Completion Date:

Milestone 1

Due Date: Responsible Party:

Milestone 2

Due Date: Responsible Party:

Budget & Payment

Total Cost for Revision (USD):

Payment Schedule

Change Orders: Any change to scope, timeline, or price must be documented in a written Change Order signed by authorized representatives of both parties prior to implementation. Check to acknowledge: Acknowledged

Change Order Authorization Process

Requests for changes shall include a description of the change, impact on deliverables, revised cost, and revised schedule. The Service Provider shall not proceed with change work until a signed Change Order is executed.

Confidentiality

Each party shall keep confidential and not disclose to third parties any Confidential Information disclosed by the other party in connection with this revision, except to those employees, contractors or advisors who have a need to know and are bound by confidentiality obligations no less restrictive than those herein. Confidential Information does not include information that is or becomes publicly available without breach of this agreement, is already in the receiving party’s lawful possession, or is independently developed. Remedies for breach shall include injunctive relief and recovery of damages.

Limitation of Liability

Except for breaches of confidentiality or indemnification obligations, neither party shall be liable for indirect, special, incidental, or consequential damages. The aggregate liability of the Service Provider for claims arising from this revision shall not exceed the total fees paid for the revision described herein.

Termination

Either party may terminate this revision for material breach if the other party fails to cure such breach within 15 days after written notice. Upon termination, the Service Provider shall deliver all work in progress and shall be entitled to payment for all services performed and documented unreimbursed expenses through the date of termination, subject to any offsets for breach.

Governing Law

This Site Revision and any dispute arising under or related to it shall be governed by and construed in accordance with the laws of the state of without regard to conflict of law principles.

Representations and Warranties

Each party represents that it has the authority to enter into this revision and that the services will be performed in a professional and workmanlike manner consistent with industry standards. The Service Provider warrants that deliverables will materially conform to the agreed acceptance criteria for thirty (30) days following acceptance.

Signatures

Client

Printed Name:

By:

Date:

Service Provider

Printed Name:

By:

Date:

What a Project Management Site Revision Is

A Project Management Site Revision is a formal record that documents planned changes to a project site, scope, schedule, or delivery methods. It captures who requested the change, the rationale, the technical or regulatory impacts, and the revised timeline or budget. The document creates an auditable trail for approvals, contractor instructions, permitting updates, and stakeholder notifications. For construction and field operations it often accompanies revised drawings, safety plans, and change orders so that site teams and inspectors have a single, current reference for execution and compliance.

Why a Site Revision Matters

A clear revision document reduces ambiguity on the worksite, aligns procurement and permitting, and preserves an audit trail for claims, inspections, and regulatory reviews.

Who Typically Prepares and Reviews a Site Revision

Small project teams through enterprise construction groups use site revisions to control scope and record approvals.

Project managers and site superintendents who coordinate work sequencing and contractor assignments.
Contractors and subcontractors who need clear instructions, quantities, and schedules to adjust crews and materials.
Owners, architects, and permitting officials who need documentation for approvals and compliance.

The revision should circulate to all impacted parties and remain attached to project records for the life of the contract.

Core Elements of a Professional Revision Document

A complete revision includes concise change descriptions, impacted drawings, cost and schedule effects, approver metadata, and an audit trail.

Change Summary

One-paragraph description of what is changing, why, and the specific areas of the site or scope that are affected; reference drawing numbers.

Scope Details

Line-item list of work added, removed, or modified with quantities, specifications, and any substituted materials or methods.

Schedule Impact

Revised milestone dates, critical-path effects, and any required acceleration or phased delivery instructions tied to the change.

Cost Implications

Estimated cost delta with breakdowns for labor, materials, equipment, and allowances; note whether change is subject to change order pricing.

Approvals

Named approvers, their roles, signature blocks, and required internal or external permits; include approval deadlines for timely execution.

Attachments

Associated drawings, photos, RFI responses, inspection checklists, and any revised method statements needed to implement the revision.

Step-by-Step: Preparing a Site Revision

Follow these sequential steps to create, approve, and distribute a revision with minimal friction on site.

01

Draft the revision: Document the change, attach drawings and photos.
02

Estimate impacts: Calculate schedule and cost deltas.
03

Obtain approvals: Route to required approvers and capture signatures.
04

Distribute and archive: Send to field teams and file in project records.

Typical Routing and Execution Flow

A standard revision follows an upload, review, approval, field distribution, and archive cycle to preserve traceability.

Upload: Sender uploads revision and attachments into the project repository.
Review: Design and discipline leads check technical and code impacts.
Approve: Authorized approvers sign and date the revision record.
Implement: Field teams receive the revision and execute changes per new instructions.

Recommended Digital Workflow Settings

Configure your e-submission workflow to enforce approvals, attach supporting files, and capture an auditable completion record.

Field	Configuration
Approval Order	Sequential routing by role required
Authentication	Email + SMS code or SSO for approvers
Attachments	Require drawings, photos, and RFI responses
Retention	Auto-archive signed revision with audit trail

Technical Distribution and Integration Options

Ensure the platform supports PDF, Word, and Excel attachments, plus API access for project systems.

File formats: PDF, DOCX, XLSX supported
Integrations: Connectors for Procore, Microsoft 365
Authentication: Email, SMS, or SSO options

Reliable integrations reduce manual uploads and preserve metadata across project management, document control, and ERP systems for regulatory and audit needs.

Risks and Consequences of Incomplete or Incorrect Revisions

Contract Claims: Incomplete revisions can produce change-order disputes and delay payments.

Permit Violations: Failure to update permits may trigger stop-work orders or fines.

Safety Incidents: Ambiguous instructions increase the risk of onsite accidents and liability.

Record Integrity: Missing approvals weaken the project audit trail for litigation or insurance claims.

Tax / Financial: Incorrect cost allocations can affect tax reporting and contractor invoicing accuracy.

Regulatory Noncompliance: Healthcare or security lapses can violate HIPAA or other sector rules.

Practical Tips to Reduce Errors and Delays

Adopt consistent naming, strict version control, and a mandatory approval sequence to keep revisions actionable.

Use version numbers

Label each revision sequentially and reference the change on all updated drawings and schedules to avoid confusion.

Require role-based approvals

Enforce an ordered approval workflow so technical, safety, and commercial approvers sign before field distribution.

Attach evidence

Include photos, marked-up drawings, and RFI responses to show the reason for changes and how to implement them.

Preserve audit data

Capture signer identity, timestamps, and delivery receipts; store signed revisions in a secured project repository.

eSignature Pricing Comparison for Revision Workflows

Vendor pricing models vary by user, features, and volume; place signNow first for a direct feature-and-price comparison without date markers.

	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 trial	No	No	No	No
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

FAQs and Troubleshooting for Site Revisions

Answers to common questions about signing, notarization, and distribution when issuing a Project Management Site Revision.

Need help? Contact support

Can a revision be signed electronically?
Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when the four-part validity test is met: intent, consent, attribution, and retention.
When is notarization required?
Notarization is required when a revision changes a deed, easement, or document that the state or county requires notarized acknowledgement; requirements vary by state and document type.
Who may sign on behalf of an organization?
An authorized signer listed in corporate resolutions or contracting authority may sign; attach delegation evidence if authority is delegated to a project manager.
Are remote notaries acceptable?
Remote online notarization (RON) is available in many states but requirements differ; confirm state notary rules and retention obligations for audio‑video recordings.
How to correct mistakes after signing?
Issue an explicit amended revision that references the original document, captures the reason for correction, and obtains fresh approvals from required parties.
Where should signed revisions be stored?
Store signed revisions in a secure project repository with version history and access controls; retain per applicable federal, state, and industry retention rules.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now