Establishing secure connection…Loading editor…Preparing document…

Project Condition Schedule

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

PROJECT CONDITION SCHEDULE

WHEREAS, Owner and Contractor entered into a written agreement identified as Contract Number dated , for improvements to the Project identified above; and

WHEREAS, the parties desire to document existing site and building conditions prior to commencement of Work so that pre-existing conditions are recorded and responsibility for repair or remediation is allocated as provided in the Contract Documents; and

WHEREAS, this Project Condition Schedule establishes an itemized record of existing conditions, observations, recommended corrective actions, and acknowledgements which will be incorporated by reference into the Contract as a condition-reporting exhibit.

Scope of Work

The scope of this Project Condition Schedule includes documented observations of visible and readily accessible conditions at the Project location as specified below. This Schedule is not a warranty of condition nor a comprehensive destructive investigation; it documents the conditions observed at the time of inspection.

Payment Terms

Payment for the preparation, inspection, and delivery of the Project Condition Schedule and related services shall be made in accordance with the following terms.

Term and Termination

This Project Condition Schedule is effective as of the Start Date and remains in effect until the earlier of the completion of the Work or the End Date, except as may be extended or earlier terminated in accordance with this Section.

Confidentiality

The parties acknowledge that certain information and documents provided in connection with preparation of this Schedule may be confidential. Each party shall keep confidential and shall not disclose to any third party Confidential Information except as required by law or as necessary to perform obligations under the Contract. Confidential Information excludes information that is or becomes publicly available without breach of this Schedule.

Governing Law

This Project Condition Schedule shall be governed by and construed in accordance with the laws of the jurisdiction where the Project is located, without regard to its conflicts of law rules.

Entire Agreement

This Schedule, together with the Contract Documents, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreements and understandings relating to the Project conditions documented herein.

Project Condition Items

The following entries document existing observed conditions. The inspector shall complete each item with as much detail as necessary to identify location, condition, and recommended action. Photographs and attachments referenced below shall be appended to this Schedule and identified by Item Number.

Item 1

Condition:

Item 2

Condition:

Item 3

Condition:

Item 4

Condition:

Item 5

Condition:

Item 6

Condition:

Attachments: List and identify any photographs, sketches, or test reports appended to this Schedule and indicate their corresponding Item Numbers:

Inspector Certification: By signing below, the inspector attests that the foregoing entries are true and correct to the best of the inspector's knowledge and that observations reflect conditions visible and accessible at the time of inspection.

Owner / Client:

By:

Date:

Contractor:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the Project Condition Schedule is and when it's used

A Project Condition Schedule is a written record attached to a contract that documents the physical condition of a site, asset, or work area at a defined point in time. It typically lists existing defects, finishes, equipment status, and measurable conditions so that responsibility for pre-existing items is clear before work begins. The schedule helps allocate repair or replacement obligations, supports progress assessments, and reduces post-completion disputes by establishing an objective baseline tied to the main contract and drawings.

Why including a clear Project Condition Schedule matters

A well-prepared schedule reduces ambiguity about pre-existing conditions, limits claims, and creates a defensible record for contract performance, inspections, and final acceptance.

Why including a clear Project Condition Schedule matters

Who typically prepares and relies on the Project Condition Schedule

Typical participants who prepare, review, or rely on the schedule include project managers, contractors, owners, and inspectors.

  • Owner representatives and facility managers who need a baseline for warranty and maintenance responsibilities.
  • General contractors and specialty subcontractors documenting start-of-work conditions to limit claims.
  • Inspectors and third-party surveyors providing independent verification before mobilization.

The schedule supports project governance by providing a shared factual starting point for change management and dispute resolution.

Common signer roles and responsibilities

Project Manager

The Project Manager compiles condition observations, coordinates corrective actions, and certifies that the schedule reflects site conditions at the specified inspection date. Their signature confirms the baseline accepted by the contractor and owner.

Owner Representative

The Owner Representative reviews and signs the schedule to acknowledge existing damage or deviations. Their approval fixes owner responsibility boundaries and aids final account reconciliation.

Step-by-step: preparing and issuing the Project Condition Schedule

Follow these steps in order to prepare an accurate and enforceable schedule before work starts.

  • 01
    Collect contract data: Confirm project ID and contract reference.
  • 02
    Inspect and document: Survey site, note measurements, and photograph conditions.
  • 03
    Draft schedule: Enter observations with clear references to drawings.
  • 04
    Circulate for signatures: Obtain signatures from owner, contractor, and inspector.

How the schedule flows through project teams

A typical routing sequence shows who prepares, reviews, and retains the signed schedule.

  • Preparation: Contractor or inspector compiles initial entries.
  • Review: Owner and PM review details for accuracy.
  • Sign-off: Authorized signatories endorse the final schedule.
  • Distribution: Signed copies issued to all contracting parties.

Digital workflow settings to support the schedule

Configure your e-submission workflow to capture signatures, timestamps, and evidence attachments reliably.

Field Configuration
Signature Field Require signer name, title, and date.
Attachment Field Allow multiple photo uploads, preserve timestamps.
Authentication Use email or SMS code, escalate for high-risk signers.
Audit Trail Enable IP/timestamp logging and exportable certificate.

Technical considerations for eSubmission and eSigning

Choose a platform that preserves evidence, supports attachments, and meets your compliance needs.

  • File formats: PDF and DOCX widely supported.
  • Integrations: Sync with NetSuite, Salesforce, or Procore as needed.
  • Authentication: Options: email, SMS, or advanced methods.

Ensure the chosen tool provides tamper-evident signed PDFs, a clear audit trail, and meets any industry-specific compliance such as HIPAA when applicable.

Common preparation errors to avoid

  • Leaving vague descriptions that later generate differing interpretations or scope disputes.
  • Failing to include photo or measurement references that would corroborate written observations.
  • Not obtaining signatures from all required parties before mobilization, weakening enforceability.
  • Using inconsistent project identifiers that make document retrieval and cross-reference unreliable.

Key risks if the schedule is incomplete or inaccurate

Contract claims: Increased disputes and delay claims.
Financial exposure: Unexpected repair costs allocated incorrectly.
Liability disputes: Ambiguity over pre-existing damage.
Regulatory issues: Noncompliance in regulated projects.
Insurance disputes: Coverage denials or contested claims.
Evidence weakness: Lost opportunity to rebut later claims.

Essential elements of a professionally prepared Project Condition Schedule

Include these elements so the schedule serves as a clear, objective baseline and a defensible contractual exhibit.

Project Identifier

Clear project name, contract number, and drawing references so the schedule unambiguously ties to the main contract and avoids misapplication across multiple sites or phases.

Detailed Condition Entries

Itemized descriptions that specify location, quantity, measurable dimensions, and severity so later reviewers can verify whether changes occurred post-baseline.

Photographic References

High-resolution photos with file names and timestamps that corroborate textual descriptions and provide independent visual evidence for inspections and claims.

Reference Documents

Attach or cite drawings, previous reports, and specifications to show the context for each condition and its relationship to contracted work or warranties.

Sign-off Blocks

Designated blocks for authorized signatures, printed names, titles, and dates to confirm mutual acknowledgement and acceptance of the recorded conditions.

Distribution Log

A record of who received the signed schedule and when, supporting traceability and serving as proof of notice to contracting parties.

When to prepare, issue, and retain the schedule

Timing affects enforceability and the ability to allocate responsibility—observe these common milestones.

Before mobilization:

Prepare and sign prior to work start or site handover.

At contract execution:

Attach as an exhibit when practical for immediate reference.

Interim reviews:

Update at key milestones or handovers during phased work.

Final closeout:

Reference original schedule during final acceptance inspections.

Retention:

Preserve signed copies per contractual and statutory retention rules.

Key milestones from inspection to closeout

A sequential view of the main processing stages helps coordinate stakeholders and documental handoffs.

01

Site Inspection

Survey and record observable conditions with photos and measurements.

02

Draft Schedule

Compile observations into a formatted schedule and attach evidence.

03

Stakeholder Review

Distribute draft to owner, contractor, and inspector for comment.

04

Final Sign-off

Obtain signatures, distribute copies, and store the executed record.

eSignature vendor overview for executing Project Condition Schedules

Compare basic pricing and feature availability; signNow appears first per vendor listing conventions.

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 trial Varies Varies Varies Varies
Bulk Send Yes Varies Varies Varies Varies
Audit Trail Yes Yes Yes Yes Yes
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Practical examples showing schedule use in real projects

Two concise scenarios illustrate how schedules reduce disputes and accelerate closeout.

Site Turnover Example

A tenant improvement contractor documented pre-existing wall damage with labeled photos and measurements

  • Contractor attached the schedule to the subcontract
  • The schedule prevented a $12,000 disputed repair charge and sped final payment by clarifying responsibility.

Equipment Handover Example

An owner recorded serial numbers and operational status before equipment installation

  • Inspector timestamped photos and uploaded evidence
  • At warranty claim time, the schedule established that claimed defects post-dated installation, simplifying liability resolution.

Security and compliance features to protect schedules and attachments

Transport Encryption: TLS 1.2/1.3
Data at Rest: AES-256 encryption
Audit Capability: Tamper-evident audit trail
Regulatory Standards: SOC 2 Type II
Healthcare Compliance: HIPAA (BAA required)
21 CFR Support: 21 CFR Part 11 compliance

Practical tips for accurate, defensible schedules

Adopt these practices to make the schedule a reliable contractual exhibit and reduce downstream friction.

Use numbered items
Number each condition and reference it consistently across photos and drawings to avoid cross-reference errors.
Include scale and measurements
Provide measurable dimensions rather than subjective descriptions to assist independent verification.
Timestamp photos
Preserve metadata or filename conventions that show when photos were taken and uploaded.
Keep distribution logs
Record who received the executed schedule and when to support notice and service obligations.

Frequently asked questions about Project Condition Schedules

Answers to common questions about completing, signing, and storing the schedule.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.