The DCMA high float check identifies incomplete schedule activities with more than 44 working days of total float. Under the commonly used Defense Contract Management Agency (DCMA) 14-point schedule assessment, the goal is to keep these activities below 5 percent of the applicable incomplete-task population.
A high-float result does not automatically prove that an activity or schedule is defective. However, excessive total float often points to missing logic, incorrect sequencing, absent scope, or a weak connection to an intermediate milestone. The scheduler should investigate the network rather than simply force the metric below its threshold.
What the DCMA high float check measures
Total float is the amount of time an activity can slip before it delays the completion date that controls its late dates. Depending on the network, that date may be the project finish, a contractual delivery, or another constrained milestone.
The public DoD Risk, Issue, and Opportunity Management Guide describes high float as incomplete tasks with total float greater than 44 working days. It gives the metric a goal of less than 5 percent.
The common calculation is:
High Float Percentage = High-Float Incomplete Activities ÷ Applicable Incomplete Activities × 100
For example, assume an Integrated Master Schedule (IMS) contains 400 applicable incomplete activities. If 28 have more than 44 working days of total float, the result is 7 percent. The schedule exceeds the commonly used 5 percent threshold and requires further analysis.
The test uses greater than 44 working days. Therefore, an activity with exactly 44 working days does not meet the standard high-float condition.
Confirm the assessment population before comparing results
The calculation can vary because organizations and analysis tools do not always use identical filters. Some procedures evaluate all incomplete tasks. Others limit the population to incomplete discrete activities and exclude level of effort (LOE), milestones, planning packages, or other non-discrete records.
For example, the Department of Energy’s schedule health metrics training excludes completed tasks, LOE tasks, and milestones from its high-float calculation. Other agency testing protocols use different percentages or separate baseline and forecast thresholds.
Consequently, two tools can report different results for the same schedule file. Before reconciling the numbers, compare:
- The numerator and denominator definitions
- Milestone, LOE, and summary-task exclusions
- The treatment of planning packages and external activities
- The schedule status date used for the test
- Calendar and duration-unit conversions
- Whether the test uses current or baseline total float
Use the metric definition required by the contract, customer procedure, surveillance plan, or approved schedule management plan. If none applies, document the rules used for the internal assessment.
Why more than 44 working days of float raises concern
High float suggests that an activity can move by roughly two working months without affecting its controlling completion date. That flexibility may be valid. However, it may also show that the network does not represent the actual technical workflow.
The GAO Schedule Assessment Guide explains that unreasonable total float commonly results from missing or incomplete logic. Because total float depends on early dates, late dates, and network relationships, unreliable logic also produces unreliable float.
Several conditions commonly create high float:
- Missing successors: The activity does not connect to the next technical event, integration step, or delivery.
- Overly distant successors: The activity connects directly to program completion instead of the next meaningful milestone.
- Missing scope: Necessary review, fabrication, test, approval, or integration activities do not appear in the IMS.
- Incorrect sequencing: Relationships do not represent how the work will actually proceed.
- Weak interface logic: Supplier, government, subcontractor, or cross-control-account dependencies remain undocumented or disconnected.
- Date controls: Constraints, deadlines, or calendar settings alter the late-date calculation.
- Independent networks: A workstream finishes early but has no valid connection to the program’s downstream objectives.
High float can therefore indicate a broader missing predecessor or successor problem. It can also reveal an incorrect path endpoint even when every activity technically has at least one predecessor and successor.
High float is a diagnostic flag, not an automatic failure
The 44-day threshold is a schedule health screening criterion. It is not proof that every flagged activity is planned incorrectly. Some work can legitimately finish well before it becomes necessary.
Valid examples may include:
- Early procurement of long-lead material that will be stored before installation
- Software components completed before a planned integration window
- Facilities work separated from equipment installation by an approved operational restriction
- Government-furnished equipment available well before its required need date
- A deliverable prepared early to reduce later execution risk
However, the program should be able to explain why the activity can slip by the calculated amount. A useful review question is: Can this activity truly move by its reported total float without affecting another technical event, resource commitment, interface, or delivery?
If the answer is no, the logic probably needs correction. If the answer is yes, retain the legitimate float and document the rationale. Do not damage a credible schedule merely to produce a favorable score.
How to investigate high-float activities
Start with the activities that have the largest total float. A few extreme values often reveal a repeated structural issue that affects an entire branch of the network.
1. Identify the controlling endpoint
Determine which completion milestone, constraint, or deadline controls the activity’s late dates. If the path runs directly to program completion, ask whether it should first connect to an intermediate delivery, integration event, or decision point.
2. Trace the successor chain
Follow the activity’s successors through the network. Look for missing handoffs, inappropriate relationship types, large lags, and paths that bypass required work.
Also review whether the next activity has the correct driving predecessor. An activity can have several relationships yet remain weakly connected to the work it actually supports.
3. Review related schedule health checks
High float rarely exists in isolation. Compare the flagged records with the results for missing logic, constraints, lags, and relationship types. In particular, review the DCMA hard constraints check and the relationship types and finish-to-start logic check.
A constraint may change the late-date calculation. Meanwhile, an incorrect start-to-start or finish-to-finish relationship can leave part of the technical workflow without an effective finish-side connection.
4. Confirm that all necessary scope exists
Ask the Control Account Manager (CAM) what occurs after the activity finishes. If the answer describes work that does not appear in the IMS, the problem may involve missing scope rather than one missing relationship.
5. Validate calendars and software settings
Make sure the assessment treats 44 days as working days under the agreed calendar and duration settings. Multiple task calendars can produce values that appear inconsistent when a reporting tool converts stored hours or minutes into days.
6. Correct the model and recalculate
Add or revise logic only when the change reflects the execution plan. Then recalculate the schedule and rerun the metric. Check the critical and near-critical paths because corrected logic can move float to another branch.
Running the check in Microsoft Project
Microsoft Project uses the term Total Slack for total float. According to Microsoft’s Total Slack field documentation, Project calculates the field from early and late start and finish dates while accounting for successor tasks.
A practical review process is:
- Update the schedule through the approved status date and recalculate it.
- Insert the Total Slack, Percent Complete, Summary, Milestone, Predecessors, Successors, Constraint Type, Constraint Date, and Deadline fields.
- Filter for incomplete tasks with Total Slack greater than 44 working days.
- Apply the required exclusions for summary tasks, milestones, LOE, or other records.
- Sort the remaining activities from highest to lowest Total Slack.
- Group the results by Work Breakdown Structure, control account, Integrated Product Team, or responsible organization.
- Trace the successor path for each major cluster of exceptions.
Deadlines need special attention in Microsoft Project. A deadline does not schedule a task in the same way as an inflexible constraint, but it can affect the Total Slack calculation. Therefore, understand the software’s date behavior before interpreting a large or unexpectedly small value.
For a broader explanation of float terminology, see what total float means in project scheduling and the distinction between free float and total float.
Fictional program example
Consider the fictional Falcon Ridge avionics upgrade program. Its IMS contains 180 applicable incomplete discrete activities. Thirteen activities have more than 44 working days of total float, producing a high-float result of 7.2 percent.
Eight exceptions belong to the environmental qualification workstream. The successor analysis shows that completed test procedures connect directly to the final system acceptance milestone 11 months later. The schedule omits the intervening laboratory readiness review, test article delivery, test execution, discrepancy resolution, and qualification report approval.
The scheduler works with the engineering CAM to add the missing scope and valid finish-to-start relationships. After recalculation, those eight activities have between 18 and 31 working days of total float. Five legitimate high-float activities remain because the team intentionally completes reusable support equipment before the flight-test need date.
The revised result is 2.8 percent. More importantly, the schedule now shows a credible qualification path and meaningful dates for laboratory support, engineering reviews, and resource planning.
Common ways teams misuse the metric
- Adding constraints to suppress float: This changes the score without improving the technical network. It may also weaken critical path analysis.
- Linking every exception to project completion: A relationship to a distant finish milestone can satisfy a missing-logic test while preserving excessive float.
- Deleting legitimate float: Float is a calculated output and a management resource. Not all positive float is waste or schedule margin.
- Reviewing only the percentage: A schedule may pass overall while one control account contains a serious open-ended network.
- Ignoring repeated values: A large group of activities with identical float often shares the same downstream logic or controlling milestone.
- Using calendar days: The standard screening threshold refers to working days, not 44 calendar days.
- Changing logic without CAM input: The scheduler owns network quality, but the CAM and technical team must validate the execution sequence.
Contractual requirement or recommended practice?
The DCMA high float threshold is widely used as a schedule health metric. However, it is not, by itself, a universal requirement imposed on every federal contract.
DFARS 252.234-7002, when included in a contract, requires an acceptable Earned Value Management System (EVMS) and procedures that generate timely, reliable, and verifiable IMS information required by the applicable data items. The clause does not state that every schedule must independently satisfy the 5 percent high-float threshold.
A contract, Contract Data Requirements List, data item description, statement of work, surveillance plan, or agency procedure may impose more specific schedule criteria. Thresholds and exclusions can also vary by agency or program. Therefore, review the governing contract documents before treating the standard DCMA metric as an acceptance requirement.
What management should expect from the review
A useful high-float review produces more than a score. It identifies weak logic, missing interfaces, incomplete scope, and workstreams whose dates do not respond credibly to change.
Program managers should expect the scheduler and CAMs to explain the largest exceptions, correct invalid network conditions, and document valid high-float cases. They should also monitor changes in float over time. Because total float is shared along a path, its consumption can provide early warning before a path becomes critical.
Use the high-float check with the other measures in the DCMA 14-point schedule assessment. No single metric establishes schedule credibility. Together, the checks help determine whether the IMS can support execution decisions, customer reporting, forecast analysis, and schedule risk assessment.
Frequently asked questions
What is considered high float under the DCMA check?
An incomplete activity generally meets the condition when its total float exceeds 44 working days. Exactly 44 working days is not greater than the threshold.
Does one high-float activity fail the schedule?
No. The common metric compares the number of high-float activities with the applicable incomplete-task population and seeks a result below 5 percent. Even so, a single extreme exception may still reveal an important network problem.
Should schedulers eliminate all float above 44 days?
No. Correct invalid logic, but retain float that accurately reflects the execution plan. Document why the work can slip without affecting downstream objectives.
How often should the check be run?
Run it during schedule development, before baseline reviews or customer delivery, and after each status cycle. Also rerun it after major logic changes because total float can shift throughout the network.