Skip to content
Kairos OneBook a demo
Menu
Intermediate · 2 min read

Schedule quality thresholds and exception management

Set project-specific screening thresholds, investigate exceptions, and trend the quality of the native schedule without gaming the score.

Working definition

Quality thresholds turn broad principles into repeatable screening rules for open ends, dangling logic, lags, relationship types, constraints, durations, float, invalid progress, baseline fields, and out-of-sequence work. They are useful only when the values, calendars, exclusions, and disposition process are controlled.

Key takeaways

  • Define thresholds from project context and document the calendar basis.
  • Require a disposition for every exception.
  • Trend identical-rule results and underlying causes across periods.
01

Thresholds are not universal truths

A long activity on a daily construction schedule may be appropriate on a high-level program schedule; a 40-hour lag means different elapsed time on different calendars. Define thresholds from contract requirements, schedule level, reporting cycle, work type, and organizational policy.

02

Trend causes, not only counts

Counts can fall because defects were fixed, activities were deleted, thresholds changed, or filters hid work. Preserve the rule set and analyze repeat causes by WBS, contractor, planner, and period.

Establish a defensible quality protocol

Use metrics to focus professional review rather than replace it.

Before you start

    1. Define the schedule population

      State schedule level, activity types, project boundaries, exclusions, and data date.

      Verify: The denominator and included records are reproducible.

    2. Set rules and thresholds

      Define tests for logic, lags, constraints, durations, float, progress, baselines, relationships, codes, and required fields.

      Verify: Each threshold has a source, rationale, and calendar or unit basis.

    3. Run against the native file

      Calculate the schedule under controlled options and run the approved checks.

      Verify: The result identifies individual activities and relationships, not only percentages.

    4. Investigate and disposition

      Trace each exception and classify corrected, accepted with reason, not applicable, or pending.

      Verify: Material exceptions have owners and due dates.

    5. Trend consistently

      Compare results using the same rule version and explain changes in population or thresholds.

      Verify: Management can distinguish real improvement from changed measurement.

      Field-ready control

      Quality protocol check

      • Population defined
      • Rule version recorded
      • Threshold rationale documented
      • Calendar and unit basis stated
      • Individual exceptions available
      • Dispositions complete
      • Rerun after corrections
      • Period trend uses comparable rules

      Common questions

      Should DCMA-style thresholds be used on every construction project?

      They can be useful screening references, but the contract, schedule level, work type, calendars, and organizational protocol should determine the actual checks and thresholds.

      Sources and scope

      Follow the reference trail.

      This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

      Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01Checking schedulesOracle · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01DoD Earned Value Management System Interpretation GuideU.S. Department of Defense · checked 2026-08-01