Establishing secure connection…Loading editor…Preparing document…

Site Revision Document

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

SITE REVISION DOCUMENT

This Site Revision Document (the "Agreement") is made effective as of between Client Name: and Service Provider Name: with respect to Site Name/Identifier: .

RECITALS

WHEREAS, Client contracted Service Provider to design, develop, maintain or host the Site pursuant to a prior agreement between the parties ("Original Agreement"); and

WHEREAS, Client requires modifications to the Site identified in this document (the "Revision"), including updates to features, content, and functional behavior as specified below; and

WHEREAS, the parties desire to set forth the scope, schedule, compensation and other terms applicable to the Revision in writing.

SCOPE OF WORK

TIMELINE AND MILESTONES

Revision Commencement Date: . Estimated Completion Date: .

PAYMENT TERMS

Total Additional Compensation (for the Revision): $ payable in accordance with the schedule below.

Late Payment Fee: If any invoiced amount is not paid within days of the invoice due date, Client will pay a late fee equal to per month on the outstanding balance, or the maximum allowed by law, whichever is less.

TERM AND TERMINATION

This Agreement shall commence on the Revision Commencement Date specified above and shall continue until the Completion Date specified above unless earlier terminated as provided herein.

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure such breach within days after written notice. Either party may terminate for convenience upon days' prior written notice; in such event Client shall pay Service Provider for all work performed through the effective date of termination and any non-cancellable obligations.

CONFIDENTIALITY

"Confidential Information" means non-public business, technical, product or financial information disclosed by either party to the other in connection with this Agreement. Each party shall protect Confidential Information of the other with the same degree of care it uses to protect its own confidential information, but in no event less than reasonable care. Confidential Information shall not include information that is or becomes publicly available through no fault of the receiving party or that is independently developed without use of the disclosing party's Confidential Information.

The receiving party will not disclose Confidential Information except to employees, contractors or advisors who have a need to know and who are bound by confidentiality obligations at least as protective as those herein. Upon termination, each party will return or destroy Confidential Information of the other as directed.

INTELLECTUAL PROPERTY AND LICENSES

Unless otherwise agreed in writing, Service Provider retains ownership of pre-existing tools, software, libraries, and templates. To the extent Service Provider creates new materials specifically for Client under this Revision and Client has paid all amounts due, Service Provider assigns to Client all right, title and interest in such deliverables excluding underlying tools and third-party components, which remain subject to their respective licenses. The parties will execute any documents reasonably required to evidence such assignment.

LIMITATION OF LIABILITY

Except for liability for gross negligence or willful misconduct, each party's aggregate liability arising out of or relating to this Agreement shall be limited to direct damages not to exceed the total amounts paid and payable by Client to Service Provider under this Agreement during the twelve (12) months prior to the event giving rise to the claim. Neither party shall be liable for consequential, special or punitive damages.

GOVERNING LAW

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

ENTIRE AGREEMENT

This Agreement, together with the Original Agreement and any written change orders executed by both parties, constitutes the entire agreement between the parties with respect to the Revision and supersedes all prior and contemporaneous understandings, agreements, negotiations and communications, whether written or oral.

MISCELLANEOUS

Any amendment or modification to this Agreement must be in writing and signed by authorized representatives of both parties. If any provision of this Agreement is found to be invalid or unenforceable, the remainder shall remain in full force and effect. The parties are independent contractors and nothing in this Agreement creates a partnership, joint venture or agency relationship.

Client Printed Name:

By:

Date:

Service Provider Printed Name:

By:

Date:

Enter text✕

What a Site Revision Document Is and When It’s Used

A Site Revision Document records proposed or approved changes to an existing site plan, scope, or specifications for a project site. It creates a dated, auditable record of who requested the change, what is being altered, attachments (revised drawings or schedules), and the approvals required for implementation. The document is used by contractors, design teams, permitting authorities, and owners to coordinate scope, cost, and timing changes and may be executed electronically or on paper depending on jurisdictional and contract requirements.

Why a Clear Site Revision Document Matters

A formal revision record reduces disputes, speeds reviews, preserves approvals, and preserves a versioned audit trail. Accurate revisions protect contract obligations, change-order accounting, and permit compliance.

Why a Clear Site Revision Document Matters

Who Typically Prepares and Signs This Document

Multiple project stakeholders prepare or approve site revisions depending on the change type and contract terms.

  • Project managers and general contractors who control scope and schedule and coordinate downstream trades.
  • Architects and engineers who issue revised drawings, specifications, and technical approvals for the change.
  • Owners, property managers, and permitting officials who approve cost, schedule, or code-related revisions.

Identifying the right preparer and signers up front prevents delays during review and permit processing.

Step-by-Step: Completing a Site Revision Document

Follow a simple sequence to produce a legally robust revision record and streamline approvals.

  • 01
    Prepare Draft: Collect drawings, specs, and cost estimates for the proposed change.
  • 02
    Attach Supporting Files: Include redlines, revised sheets, and cost breakdowns in PDF or DOCX format.
  • 03
    Route for Review: Send to required approvers in the defined order with clear due dates.
  • 04
    Record Approval: Capture signer name, title, signature, and effective date; archive the signed record.

Typical Digital Workflow for Site Revision Approvals

A repeatable online flow keeps revisions consistent: upload, field placement, authentication, signature, and archive.

  • Upload Document: Add the revision form and all supporting attachments to the platform.
  • Place Fields: Add signature, date, initials, and conditional fields for approvals or cost impacts.
  • Authenticate Signers: Choose authentication level: email link, SMS code, or stronger methods if required.
  • Sign and Archive: Capture signatures and an audit trail, then store the executed version in the project folder.

Configuring an Online Approval Workflow

Suggested settings streamline routing and maintain a reliable audit trail for each revision.

Field Configuration
Approval Order Sequential routing by role or email; escalate on delay.
Signer Authentication Email link by default; use SMS or KBA for higher assurance.
Reminder Schedule Automated reminders at 3 and 7 days after initial request.
Final Storage Save signed version to a project folder and retain audit trail.

Technical Requirements and Integrations for Digital Revisions

Choose a platform that supports your document formats, workflows, and integration needs.

  • File Formats: PDF, DOCX, and common image files supported.
  • Integrations: Salesforce, NetSuite, and Google Workspace integrations available.
  • Storage Options: Box, Egnyte, and cloud repository support.

Essential Elements of a Professional Site Revision Document

Include structured fields and controls so the revision is reviewable, enforceable, and auditable across stakeholders.

Revision Tracking

Record who made the change, the revision number, and the timestamp so project history remains clear and auditable across teams.

Version History

Maintain prior versions and redlines so reviewers can compare changes and identify scope drift or unintended edits.

Approval Routing

Define the order of approvals and required signers so changes do not proceed without necessary authorizations.

Conditional Fields

Show cost or schedule impact fields only when a change exceeds defined thresholds, reducing reviewer workload.

Audit Trail

Capture timestamps, IP or device metadata, and signer attribution to support dispute resolution and compliance needs.

Document Templates

Use templates with required fields prebuilt to ensure consistency and speed for repeat revisions.

Security and Compliance Features to Expect

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Certifications: SOC 2 Type II and ISO 27001 certified
HIPAA Support: HIPAA BAA available when required
21 CFR Part 11: Compliant options for regulated records
Access Controls: Role-based permissions and SSO
Audit Records: Immutable audit trail and activity logs

Key Risks If a Revision Document Is Incomplete or Incorrect

Contract Disputes: May lead to claims, delays, or costly litigation
Permit Rejection: Incomplete filings risk municipal denial or re-submission
Cost Overruns: Unapproved scope changes can create unbillable work
Liens and Claims: Contractor payment disputes can trigger lien filings
Regulatory Fines: Code violations from unauthorized work may incur penalties
Recordkeeping Gaps: Missing audit trails complicate insurance and warranty claims

Common Preparation Mistakes to Avoid

  • Submitting a redline without a clear description of the scope and cost impact increases review time and disagreement.
  • Using inconsistent revision numbers or file names leads to version conflicts and misapplied changes in the field.
  • Failing to route to required signers or omitting titles and authority statements causes approvals to be invalidated.
  • Attaching incorrect or low-resolution drawings creates ambiguity and may result in rework or permit delays.

Typical Timelines and Review Deadlines

Timelines vary by project size and municipal processing; the list below gives typical internal and external review expectations.

Submit for Permit Review:

Allow 5–30 business days for municipal review depending on jurisdiction and complexity.

Internal Review Period:

Plan 3–10 business days for multidisciplinary internal approvals before external submission.

Municipal Review:

Municipal response often ranges from 10–45 days; expedited reviews may cost extra.

Approval Effective Date:

The effective date is set when all required signers complete approvals and dates are captured.

Record Update:

Archive signed revision and notify stakeholders within 48 hours of approval.

Key Milestones from Request to Archive

A compressed milestone view highlights the primary steps from submission through final archival of a revision.

01

Draft and Attach

Prepare the revision form and include all supporting documents and redline drawings.

02

Internal Approval

Route to internal stakeholders for technical and budgetary sign-off.

03

External Approval

Submit to owner or permitting authority and capture external signatures.

04

Archive and Notify

Store the executed revision and notify all affected teams and contractors.

eSignature Vendor Comparison for Site Revision Workflows

Compare typical vendor pricing and core features relevant to high-volume site revision and approval workflows. No datestamps or verification dates are included in this summary.

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 credit card) Varies Varies Varies Varies
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Real-World Examples of Using Digital Signatures for Revisions

Practical examples show how digital workflows reduce turnaround and maintain compliance across project types.

Tim Martin — Martin Properties

Tim Martin found end-to-end online processing reduced turnaround for property revisions.

  • He used mobile and offline signing when needed.
  • The result was faster execution with consistent security and compliance across property transactions, avoiding in-person delays.

Dan Rotelli — BIS

BIS prioritized SOC 2 and ESIGN compliance for its document workflows.

  • The team preferred an audit trail and strong controls.
  • They achieved compliant, auditable approval records that supported internal controls and vendor accountability.

Practical Tips for Accurate and Efficient Completion

These best practices reduce rework and help ensure approvals are accepted by all stakeholders and recorders.

Confirm Signer Authority
Verify that each signer has explicit authority to approve changes; document titles and company affiliation to avoid later challenges.
Use Clear Versioning
Adopt a consistent naming and revision-number convention and include redline comparisons to highlight exactly what changed.
Attach Complete Evidence
Include cost breakdowns, revised drawings, and referenced specifications to give reviewers full context and reduce back-and-forth.
Preserve Audit Trail
Keep timestamps, signer metadata, and a stored signed PDF that includes the audit record for dispute resolution.

Frequently Asked Questions and Troubleshooting

Answers to common questions about eSigning, notarization, version control, and platform selection for Site Revision Documents.


Need help? Contact support

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