The DCMA negative float check identifies incomplete schedule activities with total float below zero. The Defense Contract Management Agency (DCMA) 14-point assessment uses a goal of zero negative-float activities. Therefore, even one flagged activity requires analysis.
Negative float indicates that the current schedule cannot satisfy a required or constrained date without recovering time. However, the check is a diagnostic metric, not an instruction to manipulate the schedule until every value displays zero. A credible Integrated Master Schedule (IMS) should show the actual forecast, explain the date conflict and support a realistic recovery decision.
What the DCMA negative float check measures
The check evaluates total float on incomplete activities. A commonly used calculation is:
Negative float percentage = incomplete activities with total float below zero ÷ total incomplete activities × 100
NASA schedule-assessment training material describes this formula and states that flagged tasks should have an explanation and corrective action plan. Meanwhile, the Department of Defense Risk, Issue, and Opportunity Management Guide lists zero negative-float tasks as the goal for the metric.
Assessment populations can vary by customer procedure and software configuration. For example, an implementation may exclude completed work, summary rows, level-of-effort activities, planning packages or unbaselined tasks. Some implementations also exclude zero-duration milestones from the percentage denominator. Consequently, verify the governing schedule-assessment procedure before comparing results from different tools.
What a negative value means
Total float measures the time an activity can move before it affects the date that controls its late dates. When total float becomes negative, the schedule needs to recover that amount of working time to satisfy the controlling date.
For example, an activity with negative 12 days of total float does not have 12 days available. Instead, its driving path needs approximately 12 working days of recovery under the schedule’s current logic, durations and calendars. For a broader explanation, see what negative float is and what causes it.
Do not confuse total float with free float. Free float addresses the effect on an immediate successor, while total float reflects the effect on the applicable completion or constrained date. The distinction is explained in free float versus total float.
Why the DCMA goal is zero
The DCMA check treats negative float as an exception because it signals a conflict between the calculated forecast and a required date. That conflict may affect a contractual delivery, technical event, customer review, test window or another key milestone.
Negative float also weakens schedule predictiveness when the team cannot explain its source. Program managers may see a required milestone on one date while the network logic forecasts a later result. Control Account Managers (CAMs) may then plan work against dates that the schedule cannot support.
However, a zero-result metric does not prove that the schedule is healthy. A scheduler can remove negative float by deleting a valid required date, changing logic without technical justification or imposing unrealistic durations. Those actions improve the metric while making the schedule less credible.
The correct objective is to understand and resolve the underlying conflict. If the required date remains valid and recovery is not yet achievable, the schedule should continue to show the negative float.
What causes negative float?
Negative float usually appears when a backward-pass date occurs earlier than the network’s calculated early dates. Common causes include:
- A late forecast against a required milestone. Progress, remaining duration or downstream logic now places completion after the required date.
- Finish No Later Than or similar late constraints. The constraint establishes a date the logic-driven forecast cannot meet.
- A missed deadline in Microsoft Project. Microsoft Project recalculates total slack when a task’s forecast extends beyond its Deadline field.
- External dependencies. Government-furnished equipment, test facilities, subcontractor deliveries or customer approvals may arrive too late to support a required event.
- Out-of-sequence progress. Actual work performed outside the planned sequence can produce confusing path and float results, depending on the scheduling method.
- Incorrect logic or calendars. Missing relationships, inappropriate relationship types, calendar mismatches or obsolete links can exaggerate the shortfall.
- Unrealistic remaining durations. A duration that no longer reflects the execution plan can push the forecast beyond the required date.
Hard constraints deserve particular attention because they can override or distort logic-driven behavior. Review the related DCMA hard constraints check before removing or replacing a constraint.
How to perform the negative float check
1. Confirm the assessment population
First, identify which activities belong in the test. At a minimum, remove completed activities and non-schedule records that your approved process excludes. Also confirm whether the assessment counts milestones, planning packages and level-of-effort work.
Use the same filters each reporting period. Otherwise, changes in the percentage may reflect a changed denominator rather than an actual improvement or decline.
2. Filter for total float below zero
Filter incomplete activities where total float is less than zero. Then count the results and calculate the percentage against the defined population.
Do not stop with the percentage. Also record the most negative value, the affected milestones and the number of distinct driving paths. The basic metric does not distinguish between one activity at negative one day and a major delivery path that needs several months of recovery.
3. Group activities by controlling milestone
Many flagged activities will belong to the same path. Therefore, hundreds of negative-float records may trace to one missed milestone rather than hundreds of separate problems.
Group the results by delivery, contract event, test milestone or other controlling date. This step converts a task-level exception list into management information.
4. Trace the driving path
Start with the most negative milestone or activity and trace backward through its driving predecessors. Continue until you reach completed work, the status date, an external dependency or the activity where the delay originated.
Check relationship types, lags, constraints, calendars, remaining durations and actual status as you trace. If you use Microsoft Project, the techniques in how to trace a critical path in Microsoft Project can help isolate the controlling chain.
5. Identify the date imposing the negative float
Determine which date drives the late calculation. It may be a contractual delivery date, an internal target, a deadline field, an intermediate milestone constraint or an external interface date.
Then verify the date’s authority. A contractual requirement should remain visible unless the parties formally change it. By contrast, an obsolete internal target may need correction through normal schedule-change control.
6. Develop a credible disposition
Each significant negative-float path should have a documented disposition. Typical responses include:
- Correct invalid status, logic, calendar or duration data.
- Implement a resource-supported recovery plan.
- Resequence work where the technical plan allows it.
- Split activities to model approved parallel work more accurately.
- Resolve an external dependency with the responsible organization.
- Escalate an unrecoverable milestone forecast to program leadership.
- Process an authorized schedule or contractual change when appropriate.
A recovery plan should identify specific actions, owners and expected time savings. A management instruction to “work faster” does not constitute a schedule recovery plan.
Example: tracing a negative-float delivery path
Consider a fictional avionics upgrade program with a qualification-complete milestone required on September 30. After the August status update, the IMS forecasts completion on October 14. Under the program calendar, the difference equals 10 working days.
The milestone and its driving predecessor chain now show approximately negative 10 days of total float. The scheduler traces the path and finds three contributing conditions:
- An environmental test started four working days late.
- The remaining test duration increased by three days after a failed procedure.
- A seven-day customer review lag remained in the schedule even though the approved review plan now calls for five days.
Correcting the obsolete lag removes two days of unsupported delay. However, the schedule still needs eight days of recovery. The program team evaluates parallel report preparation, additional test shifts and earlier customer review of completed sections.
The revised, resource-supported plan recovers five days. The schedule still shows negative three days because the team has not identified a credible way to recover the full shortfall. That result is more useful than forcing the metric to zero. It gives management an honest forecast and a defined residual risk.
Checking negative slack in Microsoft Project
Microsoft Project uses the term total slack rather than total float. Microsoft’s Total Slack field guidance states that a negative value represents the time that must be saved to prevent delay. Microsoft also notes that constraint dates commonly cause negative slack.
Use this practical review sequence:
- Add the Total Slack, Deadline, Constraint Type, Constraint Date, Predecessors and Successors fields.
- Filter for incomplete tasks with Total Slack less than zero.
- Sort from the most negative value toward zero.
- Inspect deadlines and late constraints on the flagged task and its successors.
- Trace the driving path to the relevant milestone.
- Review task calendars, relationship types and remaining durations.
- Recalculate the schedule after correcting confirmed data errors.
Microsoft’s guidance on displaying slack in Project also explains how deadlines and inflexible constraints affect total slack. Remember that a deadline usually provides a warning date without directly fixing the task’s scheduled date. Nevertheless, it can drive total slack negative when the forecast passes the deadline.
Common ways teams hide rather than solve the problem
- Deleting the required date. This may remove negative float while concealing a missed commitment.
- Changing a hard constraint without checking its basis. Some constraints represent real contractual or interface requirements.
- Shortening durations without execution support. Duration compression must reflect resources, productivity or an approved technical approach.
- Breaking logic to improve float. Missing successors can create artificial positive float and disconnect the delivery path.
- Treating every flagged activity as a separate root cause. One late milestone can propagate the same negative float through an entire chain.
- Reporting only the percentage. Management also needs the controlling milestone, magnitude, cause, trend and recovery status.
- Rebaselining solely to eliminate negative float. Rebaselining does not recover schedule performance and requires the applicable authorization and change-control process.
Is the DCMA negative float threshold contractual?
The 14-point negative float goal is a schedule-analysis criterion. It is not, by itself, a universal Federal Acquisition Regulation (FAR) prohibition against submitting a schedule with negative float.
For contracts containing FAR 52.234-4, Earned Value Management System, the contractor must use a compliant Earned Value Management System (EVMS) and submit reports according to the contract. DoD contracts may instead use applicable Defense Federal Acquisition Regulation Supplement provisions and clauses. However, the exact IMS content, assessment thresholds, reporting format and corrective-action obligations depend on the solicitation, contract, data item descriptions, incorporated guidance and approved contractor processes.
Therefore, do not describe the zero-negative-float goal as a universal contractual mandate. A customer may make specific schedule-quality criteria enforceable through contract language or an incorporated requirement. Always review the actual contract before assigning compliance significance to the metric.
How program controls should report negative float
A useful schedule-health report should include more than a red or green indicator. For each material negative-float condition, report:
- The affected contractual or program milestone.
- The current forecast and required date.
- The amount of negative float in working days.
- The principal driving path.
- The root cause and responsible organization.
- Approved recovery actions and quantified time savings.
- The remaining shortfall after recovery.
- The trend since the previous status period.
- Any related cost, technical or resource risk.
This approach connects the metric to execution. It also supports CAM discussions, schedule risk analysis, Estimate at Completion reviews and customer reporting.
Finally, use the negative float check with the other schedule-quality tests. Missing logic, hard constraints, leads, lags and high float can all affect the result. The complete DCMA 14-point schedule assessment guide explains how these checks work together.
Frequently asked questions
Does one negative-float activity fail the check?
Yes. The stated DCMA goal is zero negative-float activities. Still, the professional response is to investigate and explain the condition rather than alter valid schedule data merely to pass.
Is negative float always a schedule-quality defect?
No. Negative float may accurately disclose that the forecast misses a valid required date. The unexplained conflict is the concern. The schedule should continue to show the shortfall until the team implements recovery or formally changes the date.
Can a completed activity have negative float?
Software may display float values on completed records, but the standard check focuses on incomplete activities. Completed work cannot recover future time, although its actual performance may explain the current delay.
Should the scheduler remove a constraint to clear negative float?
Only if the constraint is invalid, obsolete or incorrectly applied and the authorized schedule owner approves the correction. Never remove a valid contractual or interface date solely to improve the metric.