ClaimLogic
Open App Home

Help & Documentation

Everything you need to know to get the most out of ClaimLogic

Overview

ClaimLogic is a professional delay analysis platform designed for construction professionals. It provides two powerful analysis methods:

Time Impact Analysis (TIA)

Prospective delay analysis for Extension of Time (EOT) claims. Model delay events and calculate their impact on the critical path.

Windows Analysis

Retrospective analysis comparing schedule updates over time. Track delays and attribute responsibility by party.

As-Built vs As-Planned

Compare baseline schedule against actual progress. Visual Gantt comparison and variance analysis for progress reporting.

Which method should I use?

  • Use TIA when you need to demonstrate the impact of specific delay events on the project completion date (prospective/forward-looking)
  • Use Windows Analysis when you want to analyse what actually happened by comparing multiple schedule updates (retrospective/backward-looking)
  • Use As-Built vs As-Planned when you want a snapshot comparison between baseline and current status for progress reporting

Quick Start Guide

1

Create an Account

Sign up with your email address. You'll get access to a free trial to explore all features.

2

Create a Project

Click "New Project" on your dashboard and give it a name (e.g., the project or contract name).

3

Choose Your Analysis Method

Select either Time Impact Analysis or Windows Analysis based on your needs.

4

Upload Your Schedule

Import your P6 XER file(s). ClaimLogic automatically extracts activities, dates, and relationships.

5

Run the Analysis

Configure your delay events (TIA) or review the window comparisons (Windows Analysis).

6

Export Your Report

Generate a professional PDF or Excel report ready for submission.

Creating a Project

Projects are containers for your delay analyses. Each project can contain multiple analyses using different methods.

Steps:

  1. From the Dashboard, click the + New Project button
  2. Enter a descriptive name (e.g., "Highway Expansion Phase 2" or "Contract ABC-123")
  3. The project will appear in your dashboard
  4. Click "Open" or click the project card to start an analysis

💡 Tip

Use meaningful names that include the project name, contract number, or claim reference. This makes it easier to find analyses later.

Time Impact Analysis (TIA)

Time Impact Analysis is a prospective delay analysis method used to demonstrate the impact of specific delay events on the project completion date. It's commonly used for Extension of Time (EOT) claims.

How TIA Works

  1. Upload Baseline Schedule - Import your P6 XER baseline programme
  2. Define Delay Events - Add each delay event with dates, responsible party, and affected activities
  3. Analyse Impact - ClaimLogic calculates the critical path impact of each event
  4. Review Concurrency - Concurrent delays are automatically detected and displayed
  5. Assess Entitlement - View your EOT and cost entitlement based on the analysis

Understanding the Results

Standalone Event Impact

The delay this event would cause if it were the only delay on the project.

Critical Path Impact

The actual impact after accounting for concurrency. If an event is concurrent with a longer delay, its critical path impact may be reduced or absorbed.

Without This Event

What the project end date would be if this specific event was removed (but all other events remained).

Concurrent Delays

When two or more delay events overlap in time and both affect the critical path, they are considered concurrent. ClaimLogic automatically:

  • Detects overlapping delay periods
  • Identifies which event is "dominant" (the longer delay)
  • Shows which delays are absorbed by concurrent longer delays
  • Adjusts entitlement calculations accordingly

⚠️ Important

Concurrent delay analysis can significantly affect your entitlement. Events absorbed by a concurrent owner delay may still entitle you to EOT but not prolongation costs.

Windows Analysis

Windows Analysis is a retrospective delay analysis method that compares schedule updates over time to identify when and why delays occurred.

How Windows Analysis Works

  1. Upload Multiple Schedules - Import your baseline and subsequent schedule updates in chronological order
  2. Set Data Dates - Each schedule needs a data date (often auto-detected from the XER)
  3. Configure Responsibility Mapping - Map WBS codes to responsible parties
  4. Run Analysis - ClaimLogic compares each window to identify delays
  5. Review Results - See delay attribution, S-curves, and detailed comparisons

Key Features

📊 S-Curve Analysis

Compare planned vs actual progress over time

📈 Delay Attribution

See which party is responsible for delays

🔍 Activity Tracking

Track individual activity delays across windows

📋 Window Comparison

Compare any window against baseline or previous

As-Built vs As-Planned

The As-Built vs As-Planned module compares your original baseline schedule against the current/actual progress to identify variances at both project and activity level.

How It Works

  1. Upload Baseline Schedule - Import your original approved P6 XER programme
  2. Upload As-Built Schedule - Import your current schedule with actual dates
  3. Run Comparison - ClaimLogic matches activities by ID and calculates variances
  4. Review Results - See summary statistics, Gantt comparison, and detailed variance table
  5. Export Reports - Generate PDF or Excel reports

Understanding Results

Project Variance

The difference between the baseline completion date and the current forecast completion. Positive = late, negative = early.

Activity Status

Each activity is categorised as: Early (finished 3+ days ahead), On-Time (within 3 days), Late (3+ days behind), In Progress, or Not Started.

Gantt Comparison

Visual comparison showing planned bars (light blue) and actual bars (colour-coded by status) for each activity.

Key Features

🔍 Filter & Search

Filter by status, search by activity ID/name, focus on critical path only

📊 Top Delays

Automatically identifies the 10 most delayed activities

📈 Status Distribution

Visual bar showing the proportion of activities in each status

📋 Sortable Table

Sort activities by variance, name, or planned finish date

💡 When to Use As-Built Analysis

  • • Progress reporting and schedule health checks
  • • Identifying problem areas before they become critical
  • • Supporting monthly progress claims
  • • Baseline vs current status snapshots for stakeholders

Importing XER Files

ClaimLogic supports direct import of Primavera P6 XER files. This is the recommended format as it contains the most complete schedule data.

How to Export XER from P6

  1. Open your project in Primavera P6
  2. Go to File → Export
  3. Select Primavera PM - (XER) as the format
  4. Choose your export options (include all project data)
  5. Save the file

What ClaimLogic Extracts

  • All activities with IDs, names, and descriptions
  • Baseline and current dates (start, finish)
  • Total float values
  • WBS structure
  • Activity relationships (for critical path)
  • Progress/percent complete
  • Calendars (for working day calculations)

✅ Best Practices

  • Name your files with dates (e.g., "ProjectX_Baseline_15Jan2024.xer")
  • Export with all activity data included
  • Keep baseline and update files in a consistent format

⚠️ CSV Alternative

If XER export isn't available, you can export activity data as CSV from P6's Activity view. However, this provides less data than XER (no relationships or calendars).

Exporting Reports

ClaimLogic generates professional reports ready for submission. Two formats are available:

📄 PDF Report

Professional formatted report with:

  • • Executive Summary
  • • Project Information
  • • Visual Timeline
  • • Delay Event Analysis
  • • Entitlement Summary
  • • Definitions & Glossary

📊 Excel Export

Detailed data export with:

  • • Summary sheet
  • • Delay events detail
  • • Party attribution
  • • Concurrency analysis
  • • Raw calculation data

Adding Commentary

Both TIA and Windows Analysis allow you to add executive commentary that will be included in your PDF report. Use this to:

  • Summarise your findings and conclusions
  • Provide context for the delay events
  • Reference supporting documents (RFIs, letters, etc.)
  • Make recommendations

Frequently Asked Questions

What file formats does ClaimLogic support?
ClaimLogic supports Primavera P6 XER files (recommended) and CSV exports. XER files contain the most complete data including relationships and calendars.
How is concurrent delay handled?
When two or more delays overlap in time, ClaimLogic identifies the "dominant" delay (the longest one) and shows how shorter concurrent delays are absorbed. The entitlement calculation reflects this - you may be entitled to EOT for the absorbed period but not prolongation costs.
Can I save my analysis and come back later?
Yes! Your analyses are automatically saved to the cloud. You can also manually save sessions using the Save/Load feature in the Export tab. Sessions are stored locally in your browser.
What's the difference between TIA and Windows Analysis?
TIA (Time Impact Analysis) is prospective - you define specific delay events and calculate their impact on the baseline schedule. It's used to demonstrate what delay a particular event caused.

Windows Analysis is retrospective - you upload multiple schedule updates and ClaimLogic shows how delays accumulated over time. It's used to analyse what actually happened.
How do I assign responsibility for delays?
In TIA, you assign a responsible party when defining each delay event. In Windows Analysis, you can set up responsibility mappings based on WBS codes - for example, all activities under "Design" WBS can be mapped to "Consultant".
Is my data secure?
Yes. All data is encrypted in transit (HTTPS) and at rest. Your schedule files are stored securely in the cloud and are only accessible to you. We never share your data with third parties. See our Privacy Policy for more details.

Glossary

Baseline Schedule

The original approved programme against which progress and delays are measured.

Concurrent Delay

When two or more delay events occur during overlapping time periods and both affect the critical path.

Critical Path

The longest sequence of activities that determines the minimum project duration. Delays to critical activities directly delay the project completion.

Data Date

The date up to which actual progress has been recorded in a schedule update.

EOT (Extension of Time)

Additional time granted to complete the works beyond the original contract completion date.

Excusable Delay

A delay caused by events beyond the contractor's control (e.g., adverse weather, force majeure). May entitle EOT but typically not costs.

Compensable Delay

A delay caused by the client/employer. Entitles the contractor to both EOT and prolongation costs.

Float

The amount of time an activity can be delayed without affecting the project completion date (Total Float) or successor activities (Free Float).

Prolongation Costs

Time-related costs incurred due to project delays (e.g., extended site overheads, additional supervision).

TIA (Time Impact Analysis)

A prospective delay analysis method that models the impact of specific delay events on the project schedule.

WBS (Work Breakdown Structure)

A hierarchical decomposition of the project scope into manageable components, used to organise activities.

Support & Contact

We're here to help! If you have questions, feedback, or need assistance, please don't hesitate to reach out.

📧 Email Support

For general enquiries and support:

[email protected]

🏢 Business Enquiries

For enterprise and partnership enquiries:

[email protected]

Response Times

  • Starter Plan: Response within 48 hours
  • Professional Plan: Priority support, response within 24 hours
  • Team Plan: Priority support with dedicated account manager