Establishing secure connection…Loading editor…Preparing document…

Project Change in Location

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

PROJECT CHANGE IN LOCATION

Project Identification

Change Request No.:    |    Original Contract Date:    |    Effective Date of Change:

Location Change Details

New Site Coordinates (optional):    |    Site Contact Name:    |    Site Contact Phone:

Reason for Change

Scope Impact

Will the change in location alter the scope of work?   Yes   No

Deliverables and Acceptance Criteria

List deliverables affected and the acceptance criteria for each. Attach supporting documents where required.

Schedule Impact

Is the project timeline impacted?   Yes   No

Original Start Date:    Original End Date:

Proposed New Start Date:    Proposed New End Date:

Budget and Payment Impact

Cost impact due to location change:   Increase   Decrease   No Change

Permits, Access, Health & Safety

Change Approval and Process

This Project Change in Location amends the Contract only to the extent expressly set forth herein. Except as expressly modified by this document, all terms and conditions of the Contract remain in full force and effect. Execution of this change shall constitute mutual agreement that the Service Provider will perform the additional or modified obligations described above and that the Client will pay any agreed adjustments as set forth.

Representations, Warranties and Liability

Each party represents and warrants that it has full right, power and authority to enter into this Change and to perform its obligations hereunder. The Service Provider shall perform work at the new location in a workmanlike manner consistent with industry standards. Except as modified herein, the liability, indemnification and insurance provisions in the Contract continue to apply to work performed at the new location. Neither party shall be liable for consequential damages to the other except as set forth in the Contract.

Confidentiality

All information exchanged in connection with this Change that is designated confidential or that reasonably should be understood to be confidential shall be treated in accordance with the confidentiality provisions of the Contract. Neither party shall disclose confidential information to third parties except as necessary to perform obligations under this Change or as required by law.

Governing Law

This Change shall be governed by and construed in accordance with the laws of the state of , without regard to its conflicts of law principles.

Attachments and Exhibits

Acknowledgment and Acceptance

By signing below, the undersigned authorized representatives of the Client and the Service Provider acknowledge that they have read, understand and accept the changes described herein, and agree that this Change shall become effective upon execution by both parties as set forth below. This Change may be executed in counterparts, each of which shall be deemed an original.

Client:

By:

Date:

Service Provider:

By:

Date:

Enter text✕

What a Project Change in Location Is and when it applies

A Project Change in Location is a formal amendment that records an approved relocation of work, services, or deliverables from one physical site to another. It clarifies new site address, updated scope tied to the new location, revised timelines, permit and utility responsibilities, insurance coverage changes, and any cost or schedule impacts. Parties typically execute it as a contract amendment, change order, or addendum; when executed electronically it must meet ESIGN and UETA standards to be enforceable across interstate transactions (15 U.S.C. ch. 96).

Why documenting a location change matters

A clear Project Change in Location reduces disputes by documenting who approved the move, how costs and schedules change, and what new permits, inspections, or insurance updates are required. It creates a single authoritative record to route for signatures and retain under regulatory retention rules.

Why documenting a location change matters

Who typically prepares and signs this amendment

Typical organizations and roles that prepare or approve a Project Change in Location include the following.

  • Real estate developers and property managers who coordinate site transfers and ensure lease or title compliance.
  • General contractors and construction project managers responsible for permits, site safety plans, and subcontractor notifications.
  • Owners, clients, or project sponsors who must approve budget, schedule, or scope changes tied to relocation.

Each signer should have authority to change contractual obligations or receive explicit written delegation from the contracting party.

Core elements to include in a professional Project Change in Location

A complete amendment is concise, specific, and binds directly into the original contract while preserving signatures and audit history.

Change Summary

Describe what is relocated, new address, and the reason for the change in precise terms so scope comparisons remain clear and auditable.

Effective Date

State the MM/DD/YYYY effective date for the relocation and any phased move milestones tied to obligations, permits, or inspections.

Financial Impact

List any cost increases, credits, allowances, or payment schedule changes with specific dollar amounts or formulae for adjustments.

Schedule Amendments

Provide revised milestones, completion dates, and any liquidated damages or extension-of-time provisions triggered by the location change.

Permits & Approvals

Identify which party obtains updated permits, inspections, and utility transfers and the timeframe for securing them.

Insurance & Risk

Confirm that insurance coverages extend to the new site, list required endorsements, and specify which party is responsible for proof of coverage.

Step-by-step: preparing and executing the amendment

Follow this sequence to produce a complete, enforceable Project Change in Location with an auditable signature trail.

  • 01
    Draft Amendment: Prepare a concise change document referencing the original agreement and enumerating all material adjustments.
  • 02
    Review Internal Teams: Obtain approvals from legal, procurement, and risk management before sending to external parties.
  • 03
    Collect Signatures: Route for signatures in the required order and apply authentication where appropriate.
  • 04
    Distribute and Store: Share signed copies with all parties and store a locked copy in the contract repository with retention metadata.

Executing and routing the amendment online

A typical electronic workflow reduces turnaround time while preserving legal evidence of consent and execution.

  • Upload Document: Upload the amendment PDF or DOCX to the signing platform and tag required fields.
  • Assign Signers: Add signer emails and set the signing order or parallel signing as contractually required.
  • Apply Authentication: Choose authentication: email link, SMS code, or higher-assurance methods for sensitive projects.
  • Capture Audit Trail: Ensure the platform records timestamps, IP addresses, and field-by-field completion data for the execution record.

Recommended digital workflow settings

Configure these settings to align platform behavior with contract requirements and evidence standards.

Field Configuration
eSignature Provider Use an ESIGN-compliant vendor that supports audit trails and exportable PDF/A signed records.
Authentication Select email + SMS OTP for moderate risk; use KBA or enterprise SSO for high-value projects.
Routing Order Set sequential routing when approvals must follow a strict signatory hierarchy.
Storage Location Save final PDFs to the enterprise contract repository with retention tags and access controls.

Platform features to verify before eSigning

Confirm the signing platform meets legal and technical requirements for your project and jurisdiction.

  • File Formats Supported: PDF, DOCX, and fillable forms for consistent exports and archival.
  • Authentication Methods: Email, SMS OTP, SSO, and optional KBA or certified signer ID checks.
  • Integration Options: Connectors for cloud storage, ERP/CRM, and contract repositories reduce manual handling.

Match platform capabilities to your evidence requirements (audit trail, encryption, export) and to any industry-specific compliance needs.

Common timing considerations and deadlines

Track these timing items to avoid regulatory, permit, or insurance exposures when relocating a project.

Pre-move Notice:

Provide notice to affected parties and tenants at least 30 days before relocation when possible.

Permit Updates:

Apply for or transfer permits as required by local authority before work begins at the new site.

Insurance Certificate:

Deliver updated insurance endorsements to stakeholders immediately upon effective date.

Contract Effective Date:

Record the MM/DD/YYYY date when obligations for the new location begin and payment triggers bind.

Tax / Payroll Address:

Update payroll or tax-withholding addresses promptly to avoid reporting mismatches and backup withholding triggers.

Common preparation mistakes to avoid

  • Missing or vague site descriptions that leave room for disagreement about the new location and deliverable boundaries.
  • Failing to update insurance endorsements or to confirm coverage applies at the new address before work begins.
  • Not securing or transferring necessary permits, causing inspection failures or stop-work orders by local authorities.
  • Relying on handwritten amendments without a preserved audit trail when electronic execution was intended and practical.

Risks and potential penalties of an incorrect or incomplete amendment

Permit Violation: Civil fines or stop-work orders
Contract Breach: Claims for damages or delay costs
Insurance Gap: Denied coverage for incidents at the new site
Tax Reporting: Backup withholding or reporting mismatches
Lien Exposure: Subcontractor liens due to unpaid relocation costs
Signature Challenge: Disputed consent if execution lacks adequate authentication

Typical eSignature plan and feature comparison

Compare baseline pricing and common capabilities across vendors commonly considered for contract amendments; signNow is listed first per table convention.

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

Security and compliance considerations

Encryption: TLS 1.2/1.3 in transit, AES-256 at rest
Audit Trail: Field-level timestamps and signer IPs
BAA Availability: HIPAA covered with BAA
Authentication: Email, SMS, SSO, KBA options
Certifications: SOC 2 Type II, ISO 27001
Retention Controls: Exportable, tamper-evident signed PDFs

Answers to common questions about Project Change in Location

Below are practical answers to frequent legal, technical, and process questions when preparing and executing a Project Change in Location.


Need help? Contact support

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