Guide

The DCMA 14-point assessment, in plain words.

Task owners use these 14 checks to judge whether a schedule is built well enough to manage a project. Here is what each one measures, the usual threshold, and how PlanGent meets it.

  1. 01

    Logic

    Activities without a predecessor or successor (open ends).

    Threshold5 % or less

    How PlanGent meets itEvery activity is tied into the network; only the project start and finish milestones are open.

  2. 02

    Leads

    Relationships with a negative lag.

    Threshold0

    How PlanGent meets itNo negative lags are used.

  3. 03

    Lags

    Relationships with a positive lag.

    Threshold5 % or less

    How PlanGent meets itWaiting time is modelled as activities or calendars, not lags.

  4. 04

    Relationship types

    Share of finish-to-start links.

    Threshold90 % or more

    How PlanGent meets itThe network is finish-to-start.

  5. 05

    Hard constraints

    Constraints that stop the schedule moving with logic (must start / finish on).

    Threshold5 % or less

    How PlanGent meets itOnly soft “start no earlier than” dates where the contract or a work front needs them.

  6. 06

    High float

    Activities with total float above 44 working days.

    Threshold5 % or less

    How PlanGent meets itBlock alignment, just-in-time document triggers and work-front release keep float in range without moving the finish. The float limit you accept can be set per project.

  7. 07

    Negative float

    Activities with total float below zero.

    Threshold0

    How PlanGent meets itThe program meets its dates; if the contract dates cannot be met, PlanGent tells you instead of hiding it.

  8. 08

    High duration

    Activities longer than 44 working days.

    Threshold5 % or less

    How PlanGent meets itLong works are split by area, floor or zone.

  9. 09

    Invalid dates

    Forecasts in the past or actuals in the future against the data date.

    Threshold0

    How PlanGent meets itA new baseline has no actuals and no dates before the data date.

  10. 10

    Resources

    Activities with duration but no resources or cost.

    ThresholdAll loaded

    How PlanGent meets itEvery task carries the BOQ value mapped to it.

  11. 11

    Missed tasks

    Activities that finished later than baselined.

    Threshold5 % or less

    How PlanGent meets itApplies to updates; a new baseline starts at zero.

  12. 12

    Critical path test

    A delay on the critical path delays the finish by the same amount.

    ThresholdPass

    How PlanGent meets itThe critical path runs continuously from start to finish.

  13. 13

    Critical path length index (CPLI)

    How realistic the remaining critical path is against the float to the finish.

    Threshold0.95 or more

    How PlanGent meets it1.00 on a new baseline that meets its finish date.

  14. 14

    Baseline execution index (BEI)

    Tasks finished against tasks planned to finish.

    Threshold0.95 or more

    How PlanGent meets itApplies to updates; measured once progress starts.

Thresholds are the commonly used values; your contract or task owner may set different ones, and PlanGent asks for them. A passing result shows the schedule is well built. It does not prove that durations and logic suit your site, so a planner still reviews it. Back to the help center