Of all the ways a project schedule can be manipulated, float falsification is the most technically sophisticated and the most difficult to detect using conventional compliance tools. It does not leave obvious marks. It passes DCMA 14-Point checks. It satisfies EVMS reporting requirements. And it can hide months of true schedule deterioration behind a clean-looking network.
What Float Is
Total float is the amount of time an activity can be delayed without delaying the project's contractual end date. An activity with 20 days of float can slip by 20 days before it affects the critical path. An activity with zero float is on the critical path — any delay to it is a delay to the program.
Float is not just a scheduling artifact. On federal programs, float can have contractual implications. Owner-owned float versus contractor-owned float is often a contested concept in construction claims. A contractor who has allowed float to erode below contractual thresholds may be required to submit a recovery schedule. A program showing widespread negative float may face corrective action requirements from DCMA or the contracting agency.
This creates a direct financial incentive to manage float values in ways that serve the contractor's reporting interests rather than the project's true status.
How Float Gets Falsified
Float falsification is not typically a single act. It is a pattern of accumulated adjustments, each individually defensible, that collectively produce a schedule which appears healthy while concealing real problems.
Disconnected network segments. Adding activities with no predecessor or successor removes them from the critical path calculation entirely. These activities carry artificially high float because they are not connected to the network. The DCMA 14-Point check for missing logic has a 5% tolerance — a schedule with 4.9% disconnected activities passes the check while carrying a significant volume of artificially inflated float.
Lag insertion. Positive lag values on predecessor-successor relationships introduce artificial buffers into the network. A finish-to-start relationship with a 30-day lag gives the successor activity 30 additional days before it is constrained by its predecessor. Individually, a 30-day lag is often justifiable — procurement lead times, cure periods, regulatory review windows. Systematically, lag insertion is one of the primary mechanisms for building hidden float reserves into a schedule.
Constraint manipulation. Imposed date constraints can override network-driven dates. A "start no earlier than" constraint on a downstream milestone can hold the critical path away from activities that would otherwise appear on it, artificially extending the float of those activities. When the constraint is later removed or adjusted, float collapses — often dramatically.
Baseline modification. When float erodes through genuine schedule slippage, a contractor may request a baseline revision. An approved baseline change that resets the performance measurement baseline to the current forecast hides the accumulated variance. The schedule looks current and healthy because the benchmark has moved, not because performance has improved.
Why DCMA Checks Miss It
The DCMA 14-Point Assessment evaluates schedule structure at a point in time. It checks whether float values are within acceptable ranges — but it does not verify whether those float values are real. A schedule with 3% of activities showing high float passes the check. The assessment does not compare today's float distribution against last month's, does not flag activities whose float has increased without a corresponding scope change, and does not identify lag patterns that cluster suspiciously around DCMA thresholds.
The threshold for high float activities is greater than 44 days — a number widely known within the contractor community. Float values engineered to sit at 43 days pass the check without review.
What Detection Actually Requires
Detecting float falsification requires looking at the schedule as a network over time, not as a snapshot. The questions that reveal manipulation are trajectory questions: Which activities gained float in the last reporting period without a documented scope change? Which predecessor relationships acquired new lag values between baseline and current? Which activities were added to or removed from the critical path without a formal replan event?
Statistical distribution analysis is also meaningful. Real project schedules have characteristic float distributions that reflect genuine network complexity. A schedule whose float values cluster suspiciously near threshold boundaries, or whose critical path contains an unusually small proportion of the total activity count, exhibits a pattern inconsistent with organically built schedules.
These are the questions that require reading the schedule as a graph with history — not as a spreadsheet with today's values.
The Stakes
On a $500 million capital program, the difference between 20 days of true float and 20 days of falsified float can represent tens of millions of dollars in contingency decisions, recovery schedule obligations, and claims exposure. A program office that trusts the float values in a manipulated schedule is making resource allocation and risk decisions based on false information.
The manipulation is sophisticated enough that it is not always intentional. Sometimes float inflation is the result of poor scheduling practice — optimistic logic, disconnected networks, excessive lag — rather than deliberate misrepresentation. The outcome is the same. The schedule cannot be trusted.
The Forensic Intelligence Engine detects float manipulation by analyzing schedule graph topology and trajectory — not just today's values. Every finding is traceable to the specific task or relationship that triggered it.