RSQI: How to Tell If Your Schedule Is Suitable for Forensic Analysis

Introduction

RSQI, short for Retrospective Schedule Quality Index, is an indicator developed in xerPlanner to measure schedule quality from one specific perspective: its usefulness for reconstructing the project execution history and analyzing responsibility for delays.

The purpose of RSQI is not to assess the entire general quality of the schedule. Its focus is more precise: to determine whether the critical path is reliable, traceable, and defensible enough to be used in a retrospective analysis.

What RSQI measures

RSQI measures what proportion of the schedule’s critical activities is free from certain findings that may compromise forensic analysis.

This distinction matters because not all schedule issues carry the same weight in a contractual dispute. A duplicated activity name, an incomplete resource assignment, or a weak Activity ID structure may affect overall schedule quality, but they usually do not invalidate a delay analysis by themselves.

By contrast, a logic issue affecting a critical activity can directly compromise the causal reconstruction of the project. If the critical path contains open-ended activities, hard constraints, unjustified lags, leads, negative float, or inconsistent actual dates, then conclusions about delay may become technically questionable.

For this reason, RSQI does not try to measure everything. It measures what matters most when the schedule is used to explain what happened, when it happened, and which party had control over the events that affected time.

Why it focuses on the critical path

In forensic schedule analysis, the critical path plays a central role. It is the sequence of activities that determines the project finish date and, therefore, the axis around which many discussions about time extensions, responsibility, impact, and mitigation are built.

A schedule may contain issues in non-critical activities and still retain some usefulness for delay analysis. But if the same issues appear on the critical path, the technical risk is much higher.

For example, a non-critical activity with a questionable lag may be a poor practice, but it may not affect the main conclusion about the project finish date. By contrast, an unjustified lag on the critical path may alter the sequence used to explain the delay. In that case, the issue is no longer just a quality observation; it becomes a potential weakness in the evidence.

RSQI focuses on that sensitive area of the schedule.

How RSQI is calculated

RSQI identifies how many critical activities have at least one finding considered relevant for forensic analysis. It then expresses that result as a proportion of the total number of critical activities.

The formula is:

RSQI = (1 − critical activities with findings / total critical activities) × 100

The result is expressed as a percentage between 0% and 100%.

An important point is that each critical activity is counted only once, even if it has more than one finding. The purpose of the indicator is not to count the total number of issues, but to measure how many critical activities have compromised forensic reliability.

This avoids distortions. A critical activity with five different findings is not counted five times. For RSQI purposes, it represents one critical activity that must be reviewed before the schedule is used as a forensic basis.

If the schedule has no identified critical activities, the indicator is reported as N/A, because there is no valid basis for calculating the index.

How to interpret the result

An RSQI of 100% indicates that no critical activity presents the findings considered relevant for forensic analysis. This does not mean that the schedule is perfect, but it does indicate that its critical path does not show, according to the evaluated criteria, obvious signals that compromise its retrospective use.

A low RSQI indicates that a significant portion of the critical activities contains findings that may affect the causal traceability of the schedule. The lower the result, the greater the risk that the schedule will require corrections, explanations, or special considerations before being used in forensic analysis.

An RSQI of 0% means that all critical activities have at least one relevant finding. In that scenario, the schedule would hardly be usable as a reliable technical basis without a prior detailed review.

The value of RSQI is not to replace the professional judgment of the analyst. Its value is to provide a quick, objective, and easy-to-interpret signal about the forensic reliability of the critical path.

Findings considered in RSQI

RSQI considers only findings that may directly affect the logical integrity of the network, the reliability of the critical path calculation, or the causal traceability of project events.

It does not include every possible schedule finding. Conditions that may be important for general quality, but do not directly compromise the forensic validity of the critical path, are deliberately excluded.

The main findings considered are the following.

Activities with no predecessors or no successors

A critical activity with no logical connection at one of its ends is not fully controlled by the network. It may float within the schedule or depend on implicit dates that do not properly explain the causal sequence.

In forensic analysis, this weakens the ability to demonstrate how an activity was affected by earlier events or how it affected later activities.

Activities with open start or open finish

An open start or open finish indicates that the activity is not sufficiently anchored in the logic network through appropriate relationships. Even if it has some relationship, that relationship does not properly control the start or finish side of the activity.

In a critical activity, this may make its position in the network arbitrary and affect the reconstruction of the path that led to the delay.

Activities with hard constraints

Hard constraints impose fixed dates and may override or distort the natural effect of schedule logic. On the critical path, this type of constraint may artificially alter float, calculated dates, and causal sequences.

For forensic analysis, this is especially sensitive because the logic should demonstrate how the project moved, instead of being dominated by imposed dates without clear justification.

Activities with actual dates equal to or later than the Data Date

An actual date equal to or later than the Data Date represents a data integrity issue. If the Data Date marks the point up to which actual progress is known, there should be no actual events recorded from that date onward.

In a forensic context, this type of inconsistency may weaken the reliability of an entire update, because it calls into question the quality of the historical record used to reconstruct the facts.

Activities with negative float

Negative float indicates that the schedule does not have enough margin to meet a target date under its current conditions. On the critical path, this condition may call the validity of the calculation into question and complicate the interpretation of the real magnitude of the delay.

If the cause of the negative float is not understood, any conclusion about criticality, responsibility, or schedule recovery may be technically weak.

Finish to Start relationships with positive lags

A positive lag in a Finish to Start relationship introduces a waiting period between two activities. If that waiting period is not documented or does not represent a real technical condition, it may be hiding work that should have been modeled as an activity.

On a critical path, an unjustified lag may artificially shift or extend the sequence used to explain the delay.

Relationships with excessive positive lags

A lag may be reasonable if it represents a short and justified technical waiting period. But when its duration is excessive compared with the predecessor activity, it may indicate that the schedule is hiding activities, approvals, waiting periods, or conditions that should be explicitly represented.

In xerPlanner, a lag is considered excessive when it exceeds 10% of the predecessor activity duration. For milestones, since they have no duration of their own, 10% of the total project duration in calendar days is used as the reference.

Relationships with leads or negative lags

A lead allows a successor activity to anticipate the logical condition defined by its predecessor. This introduces an artificial overlap that should usually be modeled more clearly through another relationship type, an activity breakdown, or a more explicit sequence.

In forensic analysis, leads are especially problematic because they make the real work sequence harder to explain and may weaken any argument based on the critical path.

Start to Finish relationships

Start to Finish relationships are uncommon and difficult to justify in most engineering and construction schedules. Their presence on the critical path may indicate unclear logic or a modeling approach that requires review.

Although Primavera P6 allows this relationship type, it may be difficult to defend in forensic analysis if there is no explicit technical justification.

Why RSQI matters

In forensic analysis, the critical path is not a minor technical detail. It is the basis on which delay arguments are built or challenged.

If the critical path is compromised by logic issues, hard constraints, inconsistent actual dates, or relationships that are difficult to defend, the schedule loses strength as evidence. It may become difficult to demonstrate when the delay started, which activity caused it, which party controlled the event, and how much real impact it produced.

RSQI helps summarize that risk into a simple indicator. It does not replace detailed analysis, but it helps quickly answer an essential question:

Does this schedule have a critical path reliable enough to be used in forensic analysis?

If the result is high, the schedule provides a stronger basis. If the result is low, the analyst should review the critical path carefully before using it to support a technical or contractual conclusion.

Conclusion

RSQI is an indicator designed to evaluate the forensic reliability of a schedule from the perspective of its critical path. It does not measure the entire quality of the file, nor does it replace the professional judgment of the analyst, but it provides a clear signal about the strength of the logic foundation supporting a retrospective analysis.

A schedule may be useful for day-to-day management and still be weak for defending a claim. RSQI helps identify that risk before the schedule is used as evidence, as support for a claim, or as the basis for expert analysis.

In projects where time has contractual, financial, or reputational impact, having an updated schedule is not enough. The schedule must also be defensible. RSQI helps determine how close or far the schedule is from meeting that condition.