The DCMA missing logic check identifies incomplete schedule activities that lack a predecessor, a successor or both. The standard metric counts each affected activity once, divides that count by the incomplete activity population and compares the result with the commonly used threshold of less than 5 percent.
A passing percentage does not prove that the logic is correct. It only shows that most activities have links. Therefore, schedulers must also confirm that each relationship represents the real sequence of work and carries schedule movement through the network.
The check belongs to the broader DCMA 14-point schedule assessment. Use it as a diagnostic tool, not as a substitute for detailed logic review or critical path analysis.
What the DCMA Missing Logic Check Measures
Schedule logic defines how activities depend on one another. A predecessor controls or influences a later activity, while a successor follows the activity being reviewed.
The Defense Contract Management Agency methodology focuses on incomplete activities with missing predecessor or successor links. The DoD Risk, Issue, and Opportunity Management Guide summarizes the logic metric as incomplete tasks with missing predecessor or successor links and shows a goal of less than 5 percent.
The metric normally addresses three conditions:
- Missing predecessor: An incomplete activity has no incoming relationship.
- Missing successor: An incomplete activity has no outgoing relationship.
- Missing both: An incomplete activity is isolated from the surrounding network.
Missing both does not create two defective activities. It creates one activity with two missing sides. As a result, the calculation must remove the duplicate count.
Missing logic formula
The commonly used calculation is:
Activities missing logic = activities missing predecessors + activities missing successors − activities missing both
Then calculate the percentage:
Missing logic percentage = activities missing logic ÷ incomplete activity count × 100
The Department of Energy’s Earned Value Management System and Project Analysis procedure documents this formula and explains that a result above 5 percent should trigger further investigation. It also emphasizes that a triggered metric indicates a need for analysis rather than automatic proof of system failure.
Calculation example
Assume a program schedule contains 240 incomplete discrete activities. The review finds eight activities without predecessors, six without successors and three missing both.
- Unique activities missing logic: 8 + 6 − 3 = 11
- Missing logic percentage: 11 ÷ 240 × 100 = 4.58 percent
The schedule falls below the 5 percent screening threshold. However, the scheduler still needs to investigate all 11 activities. One unconnected activity near a contractual delivery can cause more damage than dozens of defects in low-risk work.
Why Missing Predecessors and Successors Matter
A critical path method schedule works because logic transmits change. When an upstream activity moves, its downstream network should respond according to the defined relationships, calendars, durations and constraints.
An activity without a predecessor may start according to a typed date, constraint, project start date or software default rather than an executable condition. Meanwhile, an activity without a successor can slip without affecting later work. An isolated activity does neither.
These defects can produce several management problems:
- Critical and near-critical paths may be incomplete.
- Total float may not represent the available scheduling flexibility.
- Forecast delivery dates may fail to respond to current performance.
- Schedule risk analysis may omit real paths to key milestones.
- Control account managers may receive misleading completion forecasts.
- Proposal evaluators or customers may question schedule credibility.
The GAO Schedule Assessment Guide states that, except for appropriate start and finish points, schedule activities should have predecessors and successors. GAO also explains that missing logic reduces the credibility of calculated dates.
Missing logic can also weaken an Earned Value Management System because schedule status, forecast dates and the Performance Measurement Baseline must operate as an integrated management model. However, the DCMA percentage itself is not a universal contractual acceptance requirement.
The 5 Percent Threshold Is a Diagnostic, Not a Universal Regulation
The less-than-5-percent value comes from schedule assessment methodology. It does not independently create a Federal Acquisition Regulation or Defense Federal Acquisition Regulation Supplement requirement for every contract.
For example, DFARS 252.234-7002, when included in a contract, addresses EVMS compliance and reliable Integrated Master Schedule information. It also calls for logical scheduling during the Integrated Baseline Review. However, the clause does not state that every contractor must satisfy each DCMA 14-point threshold as a standalone contractual requirement.
Actual obligations depend on the contract, applicable clauses, Contract Data Requirements List, data item description, statement of work and approved contractor processes. Some solicitations or agency clauses may impose more specific schedule-network requirements. Therefore, always compare the assessment result with the governing contract before labeling a threshold miss as contractual noncompliance.
How to Find Missing Logic in Microsoft Project
Microsoft Project provides Predecessors and Successors fields that display the task IDs, relationship types and lag values associated with each activity. Microsoft’s explanation of the Predecessors task field confirms that the field can be used to display and update task dependencies.
1. Preserve the submitted schedule
First, save an untouched copy of the schedule. Record the status date, file version and calculation settings. This step preserves the audit trail and lets you compare the repaired network with the submitted model.
2. Build a logic-review table
Add fields that help explain each result rather than showing blank links alone. A practical table may include:
- ID and Unique ID
- Task Name and Work Breakdown Structure
- Summary and Milestone indicators
- Percent Complete
- Predecessors and Successors
- Start and Finish
- Constraint Type and Constraint Date
- Total Slack
- Notes or a disposition field
Unique IDs are useful because ordinary task IDs can change when users insert, delete or move rows.
3. Limit the metric to the defined population
Filter for incomplete activities, then remove categories excluded by the documented assessment method. At minimum, distinguish detail activities from summary rows. Also identify level-of-effort activities, external tasks, completed work and legitimate network boundary milestones.
Do not change the denominator simply to improve the result. Instead, document the population and every exclusion. Different tools may treat milestones, level-of-effort work and external activities differently, so a repeatable business rule matters.
4. Separate the three missing-logic conditions
Review incomplete detail activities using three groups:
- Blank Predecessors field with at least one successor
- Blank Successors field with at least one predecessor
- Both fields blank
This separation supports the formula and helps assign corrective action. For example, a missing predecessor often requires the scheduler to identify the condition that releases the work. A missing successor requires a discussion about what consumes the activity’s output.
5. Investigate before adding a link
Ask the responsible control account manager or technical lead:
- What must occur before this activity can start or finish?
- What work, review or delivery depends on its completion?
- Does an external organization provide an input?
- Is a constraint masking the absent dependency?
- Was a relationship deleted during status or replanning?
- Should this activity exist as a discrete task?
Add the relationship that reflects the technical sequence. Do not link activities merely because they appear next to each other in the task list.
6. Recalculate and inspect the result
After correcting logic, recalculate the schedule and review the changed dates, float values and critical paths. Microsoft’s description of how Project schedules tasks explains how dependencies, constraints and calendars influence automatically scheduled activities.
Pay special attention to manually scheduled tasks. Their dates may not respond to logic changes in the same way as automatically scheduled tasks. Therefore, a visible link does not always prove that the schedule will calculate as expected.
Finally, trace the paths to important deliveries. The Microsoft Project critical path tracing process can help confirm that the repaired logic reaches the intended completion milestone.
Realistic Example: A Missing Interface Milestone
Consider a fictional avionics development program. The activity Begin Environmental Qualification Test has no predecessor, although the task starts on September 14 because a Start No Earlier Than constraint holds it there.
The team explains that testing depends on three conditions:
- Qualification unit assembly complete
- Test procedure approved
- Government test facility available
The constraint hides the missing entry logic. If assembly or procedure approval slips beyond September 14, the test activity will not move correctly unless the schedule settings force the constraint conflict to appear.
The scheduler removes the unsupported date constraint and adds valid relationships from assembly and procedure approval. The team also creates an external interface milestone for facility availability, supported by the current need date and interface owner.
Next, the scheduler links qualification test completion to the test report and design verification milestone. That second step matters because an activity can have sound incoming logic while still lacking a successor that transmits its finish.
The repaired path now carries delays from component assembly through qualification and into design verification. It also gives management a more credible forecast than the original fixed date. For more on constraints that can conceal network defects, see hard constraints versus soft constraints.
Missing Logic Is Not the Same as Dangling Logic
An activity can pass the basic missing-logic check and still have an incomplete path. This condition often appears as dangling logic.
For example, a task may have only a Finish-to-Finish predecessor. That relationship can control its finish, but it may not establish what drives the task’s start. Likewise, a task with only a Start-to-Start successor may affect another activity’s start without carrying the first task’s finish into the downstream network.
GAO distinguishes basic missing links from dangling logic. Its guidance expects logic to drive activity starts and carry activity finishes forward, subject to legitimate exceptions. Therefore, review both the existence and placement of each relationship.
Also determine which predecessor actually controls the activity. A task may have several predecessors, yet only one is currently driving its calculated date. The article What Is a Driving Predecessor? explains that distinction in more detail.
Common Ways Teams Create False Logic Quality
Linking tasks in row order
Schedulers sometimes connect consecutive rows with Finish-to-Start links to eliminate blanks. This produces a low missing-logic percentage but creates a false execution sequence. Logic should follow the work, not the outline display.
Using summary-task relationships
Links on summary rows can obscure the detailed network and create unexpected calculations. Build logic between the lowest practical activities, then let summary dates roll up from the detail.
Replacing external dependencies with fixed dates
A constrained date does not describe the external event or show ownership. Instead, model a clearly named interface milestone when practical. Document the source, responsible organization and expected date.
Ignoring completed activities
The metric focuses on incomplete work, but completed logic still affects historical traceability and out-of-sequence conditions. Do not delete valid historical relationships only because the activities no longer appear in the numerator. Review the implications through the out-of-sequence progress process.
Stopping after the percentage passes
A schedule with 1 percent missing logic can still have a broken contractual delivery path. Rank defects by potential effect on key milestones, not only by quantity.
A Practical Disposition for Every Flagged Activity
Each missing-logic record should end with a clear disposition:
- Corrected: The team added valid predecessor or successor logic.
- Valid boundary: The activity is an approved project start, project finish or other documented network boundary.
- External interface: The dependency sits outside the file and has a documented treatment or interface milestone.
- Excluded by method: The activity belongs to a category excluded by the documented metric basis.
- Pending action: The responsible owner and due date are recorded.
This approach turns the metric into a controlled schedule-quality process. It also gives reviewers evidence that the team investigated the causes instead of forcing a green dashboard.
Final Scheduler Check
Run the DCMA missing logic calculation consistently, but do not manage to the percentage alone. Confirm that incomplete discrete work has valid incoming and outgoing logic, with documented exceptions at legitimate network boundaries.
Then test whether the relationships drive starts, carry finishes and produce credible paths to program milestones. A healthy schedule is not simply well connected. It is connected in a way that accurately models how the program intends to execute.