Built because schedule problems are predictable
Most project delays come from structural flaws that appear in the file weeks before anyone notices them on the job. GanttScore makes those flaws visible in seconds, not after the damage is done.
Why this exists
Project schedules fail in predictable ways. Missing logic ties, hard constraints that override the network, tasks with no predecessors or successors, negative float that mathematically predicts a late finish before ground is broken. These problems show up in the file. They are measurable. And they almost never get caught until it is too late to fix them without rework.
The DCMA 14-point assessment was developed to catch exactly these problems. It is the closest thing the industry has to a standard health check for schedule files. Federal agencies use it to vet contractor schedules before committing funds. Large construction and infrastructure programs run it before submitting schedules for approval.
The problem is access. Running the assessment used to mean hiring a consultant, buying scheduling software with the feature, or knowing the right person. GanttScore makes it instant and self-serve. Drop your file. Get your score. See what is wrong and why.
What we check
Our engine runs all 14 DCMA checks: logic, leads, lags, relationship types, hard constraints, high float, negative float, high duration, invalid dates, resources, missed tasks, critical path test, CPLI, and BEI. We also add three value checks of our own that catch problems the standard does not cover: logic density, merge hotspots, and insufficient detail.
Every check is derived from the engine code. No check name, weight, or threshold is hand-authored. If the engine changes, the published methodology changes with it. Read the full methodology.
Who built it
GanttScore is a product of Richey AI Labs, built by a practitioner with a background in commercial and infrastructure construction scheduling. The scheduling problems GanttScore flags are problems that appear on real jobs: large-scale construction programs with complex logic networks, hard external constraints, and schedules that need to hold up to third-party review.
The goal is straightforward: take a standard that already exists, make it free to access, and pair it with actionable output so the score leads somewhere. A health score without the fix is just a number.
What we do with your file
Your schedule file is parsed, checked, and deleted. It is not stored. It is not used for training. It is not shared. The moment the engine returns a score, the file is gone. Read the full data handling statement.