Can I e-sign a site plan modification?

Yes. Electronic signatures are generally valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Confirm agency acceptance for specific filing types and any required signer authentication.

When is notarization required?

Notarization is required when a jurisdiction or specific record (easement, deed, or certain affidavits) demands an acknowledgement. Check the permitting office rules and state notary requirements before submitting.

What level of signer authentication is appropriate?

Use an authentication level that matches risk: email-only for low-risk approvals, SMS or MFA for higher-sensitivity approvals, and notarization or RON where legally required by the agency.

How do I handle version control?

Include version identifiers, dates, and a change log on each revision. Archive superseded versions with clear labels to preserve auditability and to support dispute resolution.

Who should sign if the owner is an entity?

An authorized officer, manager, or agent with documented authority should sign. Attach a corporate resolution or signed power of attorney if signature authority is not obvious.

What if the agency requests more information after submission?

Respond promptly with revised exhibits and a cover letter identifying changes. Track communications and retain the reviewer request and your response as part of the record.

Electronic Signature
Templates
Project Management
Project Management Site Plan Modifications

Project Management Site Plan Modifications

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

PROJECT MANAGEMENT SITE PLAN MODIFICATIONS

Project Identification

Project Title:

Project ID: Original Site Plan Date: Modification Request Date:

Client Name Client Address

Service Provider Name Service Provider Contact

Project Manager

Recitals

This Site Plan Modifications document (the "Modification") amends the original site plan and associated project documents identified above. The parties intend this Modification to define the scope, schedule, cost impact, deliverables, acceptance criteria, and authorization required to implement the changes described herein.

Scope of Modifications

Detailed Description of Modifications Items Specifically Out of Scope

Affected Documents and Drawings

The following documents, drawings, and specifications are amended by this Modification. Mark all that apply and provide identifying numbers or titles.

Drawings
Specifications
Engineering Reports
Other

Identify Affected Documents, Drawing Numbers, Revision Dates

Deliverables and Acceptance

Specify deliverables produced as part of this Modification and the acceptance criteria for each.

Deliverable 1 — Description Deliverable 2 — Description Deliverable 3 — Description Overall Acceptance Criteria

Timeline and Milestones

Proposed Start Date: Proposed Completion Date:

Milestone 1 Milestone 2 Milestone 3

Budget and Payment

Estimated Additional Cost: $

Cost Breakdown and Assumptions Payment Schedule (milestone-based or lump sum) Change Order Fee or Rate (if applicable)

Change Order Authorization Process

All modifications described herein require written authorization as specified below prior to implementation. Emergency work necessary to address imminent safety or regulatory threats shall be documented and authorized retroactively in accordance with this process.

Requires written change order authorization prior to work
Allows emergency work with retroactive authorization

Authorized Approver for Change Orders

Permitting, Regulatory and Approvals Impact

Identify Permit or Approval Changes Required

Risk, Safety and Site Conditions

Risk or Safety Considerations

Confidentiality

Both parties acknowledge that information exchanged under this Modification may include confidential and proprietary information. Each party agrees to maintain such information in confidence and to use it only for the purposes of performing obligations under this Modification, except as required by law. Confidential materials shall be returned or destroyed on request upon conclusion or termination of the modification work.

Governing Law and Dispute Resolution

This Modification shall be governed by the laws of the state indicated below without regard to conflict of laws principles. The parties shall first attempt to resolve disputes in good faith through their designated project representatives. If unresolved, disputes shall be resolved through binding arbitration or as otherwise agreed in the underlying contract.

Miscellaneous Provisions

All other terms of the underlying contract remain in full force and effect except as expressly modified by this document. Any conflict between this Modification and prior documents shall be resolved in favor of this Modification with respect to the subject matter herein.

Acknowledgement

By signing below, the parties certify that they are authorized representatives with authority to bind their respective organizations and that the scope, schedule, cost and authorization requirements set forth above have been reviewed and accepted.

Client — Printed Name:

Service Provider — Printed Name:

Client — By:

Service Provider — By:

Client — Date:

Service Provider — Date:

What Project Management Site Plan Modifications Are

A Project Management Site Plan Modifications document records formal changes to an approved site plan for a construction or development project. It describes scope adjustments, revised layouts, phasing updates, and related schedule or drainage changes; it typically attaches redlined drawings, rationale for each revision, and references to the original permit and approval conditions so reviewers can assess impacts quickly and consistently.

Why a Clear Modification Record Matters

A well-prepared site plan modification reduces confusion, speeds permit review, and protects project stakeholders by documenting approvals, scope limits, and any revised obligations tied to the development permit or contract terms.

Who Typically Prepares or Reviews These Modifications

Project managers, design professionals, permitting coordinators and contractors commonly prepare or submit site plan modification documents.

Municipal planning staff who review compliance and zoning impacts during permit amendment reviews.
Project managers who need to formalize scope, schedule, or layout changes to avoid disputes.
Contractors and subcontractors who require approved revisions before mobilizing or changing field work.

Each party uses the document differently — preparing it to show compliance, reviewing it for permitability, or relying on it to trigger change orders and payment adjustments.

Representative Roles and Responsibilities

Project Manager

Coordinates the modification request, compiles revised drawings and justifications, circulates the document to stakeholders, and tracks approvals to update schedule and budget controls.

Municipal Reviewer

Assesses zoning, stormwater, and code impacts; issues conditional approvals or requests for additional information and records decisions on permit files for enforcement and future inspections.

Key Security and Compliance Considerations

Encryption: TLS 1.2/1.3 in transit

Data at Rest: AES-256 encryption

Audit Trails: Timestamped action logs

HIPAA BAA: Available when required

ESIGN / UETA: Legal e-signature compliance

Certifications: SOC 2 Type II, ISO 27001

Common Legal and Operational Risks

Permit Delays: Resubmission extends review time

Stop-Work Orders: Noncompliance risks enforcement

Contract Disputes: Unapproved changes cause claims

Financial Penalties: Fines or remediation costs

Data Loss: Missing revision history risks disputes

Invalid Signatures: Noncompliant e-signatures risk rejection

Frequent Preparation Mistakes to Avoid

Submitting redlines without a clear change log, forcing reviewers to compare versions manually and increasing rejection risk.
Failing to update related documents such as drainage reports, phasing schedules, or landscaping plans that the modification affects.
Using inconsistent version identifiers or filenames, which causes contractors and inspectors to reference obsolete drawings.
Omitting signatory authority or corporate resolution for entity-level approvals, which can invalidate the modification.

Step-by-Step: Preparing a Site Plan Modification

Follow these sequential steps to assemble, authorize, and submit a consistent modification packet that ties directly to the original permit record.

01

Gather Documents: Collect original plan, permit, and all affected exhibits.
02

Draft Changes: Produce redlined plans and a concise change log.
03

Obtain Approvals: Secure internal and contractual sign-offs before submission.
04

Submit Packet: Send to the permitting authority using their required channel.

How Submission, Review, and Approval Typically Flow

A predictable routing sequence reduces processing time and clarifies reviewer responsibilities during the amendment review.

Upload Packet: Sender uploads files to agency portal or email per instructions.
Intake Check: Clerk confirms completeness and assigns a tracking number.
Technical Review: Department reviewers evaluate zoning, engineering, and code impacts.
Decision Issued: Approval, conditional approval, or request for additional information.

What a Professional Site Plan Modification Contains

Include these sections consistently so reviewers can find relevant information quickly and make a determination without repeated requests.

Cover Letter

A short summary stating the applicant, permit number, scope of changes, and a brief rationale for the modifications with contact details for follow-up.

Change Log

A table listing each revision, affected sheet numbers, summary of change, and reference to the original plan elements for easy cross-checking by reviewers.

Redlined Drawings

Clear, labeled plans showing additions, deletions, and dimension changes; include scale, north arrow, and revision clouding consistent with the original submission.

Technical Exhibits

Updated engineering calculations, drainage reports, soil reports, and any revised landscape or erosion control plans necessary to support the changes.

Approvals and Signatures

Authorized signatory block(s) for the owner, design professional, and contractor with dates and role identification for legal clarity.

Submission Checklist

A checklist mapping required forms, fees, and supporting documents to the items included in the packet to simplify intake review.

Configuring an Online Workflow for Submissions

Set up the digital routing to mirror permit office expectations and reduce intake rejections.

Field	Configuration
Submission Portal	Use agency portal or email per local rules
Notifications	Auto-notify reviewers and applicant on status changes
Authentication	Use email + optional MFA for signer verification
Document Naming	Include permit number and version in filenames

Technical Requirements for Digital Submission and Signing

Confirm supported file types, signer authentication options, and integrations before uploading to avoid rejection.

Integrations: Salesforce, NetSuite, Procore available
File Formats: PDF, DOCX, DWG exports supported
Authentication: Email, SMS code, or KBA options

Ensuring the platform meets agency file, security, and signer authentication expectations shortens review cycles and preserves audit records.

Typical Timelines and Processing Expectations

While timelines differ by jurisdiction, these are common timeframes to plan for when submitting a modification request.

Intake Confirmation:

1–5 business days after submission for completeness check

Technical Review:

10–30 business days depending on complexity and agency workload

Public Notice Period:

7–21 days when statutory notice or neighbor notification is required

Response Time:

Applicant typically has 10–30 days to provide additional information

Final Decision:

30–90 days total for many municipal processes

Key Milestones in the Modification Lifecycle

Track these sequential stages from initial request through final approval to keep stakeholders aligned and to schedule inspections.

01

Prepare Request

Assemble redlines, change log, exhibits, and sign-offs before submission.

02

Submit Packet

Upload or deliver to the permitting authority and obtain a tracking number.

03

Respond to Comments

Address technical reviewer comments promptly with revised documents.

04

Receive Approval

Document becomes part of the permit record; update field teams and contractors.

Real-World Examples of Digital Modification Workflows

These condensed case notes illustrate how organizations used digital workflows to manage site plan changes.

Martin Properties — Tim Martin, Founder

Martin Properties moved all modification workflows online to reduce field delays and centralize approvals.

Quick site approval enabled same-week mobilization.
The firm reported being able to process and execute modifications online while preserving compliance and security, which minimized costly site standby time and improved coordination among contractors and inspectors.

Xerox — Kodi-Marie Evans, Director

Xerox integrated modification approvals into ERP workflows to align procurement and change orders.

Integration reduced manual handoffs between teams.
This centralized approach ensured the right signatures were obtained in the correct sequence and supported auditability for internal controls and vendor payments.

Practical Tips for Accurate and Efficient Completion

Adopt these practices to reduce rework, simplify reviews, and maintain a defensible record of approvals.

Use a Clear Change Log

Provide a table listing each revision, reason, affected sheet numbers, and date. A concise change log speeds reviewer understanding and prevents misinterpretation during inspections or enforcement.

Standardize File Naming

Include permit number, revision number, and date in filenames. Consistent names prevent version confusion and make it easier for agencies and contractors to reference the correct document.

Attach Supporting Calculations

Include updated engineering calculations, drainage exhibits, and stamped professional seals when changes affect technical systems. Omitted exhibits are a common cause of review delays.

Confirm Signatory Authority

Ensure signers have authority (owner, officer, or agent) and provide corporate resolutions or signed authorization when required; unauthorized signatures may be rejected.

How Site Plan Modifications Differ from Other Project Documents

Compare modification records with related document types to choose the correct form and process for your change.

Document Type	Purpose	Typical Timing
Site Plan Modification	revise approved plans	during project lifecycle
Change Order	adjust contract scope or cost	when contract terms change
Addendum	supplement to contract or bid	pre-contract or during bidding
As-Built Plan	record actual constructed conditions	at project completion

eSignature Pricing Comparison for Modification Workflows

Selected vendor pricing and feature availability to evaluate e-signature options for submitting and authorizing site plan modifications.

	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

Common Questions and Practical Answers

Answers to routine questions about preparing, signing, and submitting site plan modifications.

Need help? Contact support

Can I e-sign a site plan modification?
Yes. Electronic signatures are generally valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Confirm agency acceptance for specific filing types and any required signer authentication.
When is notarization required?
Notarization is required when a jurisdiction or specific record (easement, deed, or certain affidavits) demands an acknowledgement. Check the permitting office rules and state notary requirements before submitting.
What level of signer authentication is appropriate?
Use an authentication level that matches risk: email-only for low-risk approvals, SMS or MFA for higher-sensitivity approvals, and notarization or RON where legally required by the agency.
How do I handle version control?
Include version identifiers, dates, and a change log on each revision. Archive superseded versions with clear labels to preserve auditability and to support dispute resolution.
Who should sign if the owner is an entity?
An authorized officer, manager, or agent with documented authority should sign. Attach a corporate resolution or signed power of attorney if signature authority is not obvious.
What if the agency requests more information after submission?
Respond promptly with revised exhibits and a cover letter identifying changes. Track communications and retain the reviewer request and your response as part of the record.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now