Run Your First Quality Check
Available in: All plans
Last updated: 26-Feb-2026
Overview
Kazinex includes 30+ automated quality checks based on industry standards including the DCMA 14-Point Assessment, GAO Schedule Assessment Guide, and PMO best practices. This tutorial shows you how to run your first quality analysis and interpret the results.
Prerequisites
- At least one project imported into Kazinex (see Upload Your First Schedule)
- The project should be open in the schedule management tool
Step-by-Step Guide
Step 1 — Navigate to the Quality Tab
With your project open, click the Quality tab in the main tab navigation. The quality analysis runs automatically when you open the tab for the first time.
Step 2 — Read the Overall Score
At the top of the Quality tab you will see the Quality Hero section displaying:
- Overall score (0–100) — A weighted aggregate of all check results
- Grade — Excellent (≥90), Good (≥70), Fair (≥50), Poor (≥30), or Critical (<30)
- Score cards for each check category showing pass/fail/warning counts
Step 3 — Explore Category Panels
Below the hero section, checks are organized into expandable category panels:
| Category | What It Checks | # Checks |
|---|---|---|
| Logic & Relationships | Missing logic, high float, constraints, lags, leads, FS ratio | 8 |
| Durations | High/zero duration, milestones, invalid dates, LOE, approval | 6 |
| Critical Path | CP length ratio (CPLI), CP logic test (BEI) | 2 |
| Constraints | Constraint percentage, dangling activities, open-ended, SF relationships | 4 |
| Resources | Missing resources, resource loading coverage | 2 |
| Progress | Invalid progress, out-of-sequence progress | 2 |
| Best Practices | Logic density, baseline integrity, milestone spacing | 3 |
| Regional | Ramadan calendar alignment, authority approval | 2 |
| Configuration | Activity type, % complete type, duration type, constraint type validation | 5 |
Click a category panel to expand it and see individual check results.
Step 4 — Drill Into a Finding
Each check row shows:
- Check name and description
- Severity — Critical, Major, Minor, or Info
- Result — Pass ✅, Warning ⚠️, or Fail ❌
- Count of affected activities
Click a check row to open the Check Detail Drawer. This shows:
- A table of all affected activities with their IDs, names, and the specific values that triggered the finding
- Sorting and filtering within the drawer
- Links to navigate back to the Activities tab
Step 5 — Understand Key Checks
Here are the most important checks to review first:
Missing Logic (DCMA #1)
Activities that have no predecessor, no successor, or both. A healthy schedule has logic on 95%+ of activities.
High Float (DCMA #3)
Activities with total float exceeding 44 working days. High float suggests the activity is disconnected from the critical path.
Negative Float (DCMA #6)
Activities with negative float indicate the schedule is behind — the project cannot finish on time without corrective action.
Critical Path Length (DCMA #12)
The Critical Path Length Index (CPLI) compares the critical path length to the total project duration. A ratio below 0.95 suggests risk.
What to Do Next
- Address critical findings first — Focus on checks with "Critical" severity and "Fail" results
- Fix your schedule in P6 or MS Project, re-export, and re-upload to see improvements
- Customize thresholds — Open Quality Settings to adjust thresholds for your organization
- Compare before and after — Upload the fixed version and use the Comparison tab to verify improvements
Tips & Best Practices
- Run quality checks after every schedule update to track improvement trends
- Use the weightage configuration to emphasize categories that matter most to your project
- Share the quality score with stakeholders as a schedule health KPI
- The DCMA 14-Point Assessment is the industry standard — start with the default thresholds and adjust only if you have a documented reason
Troubleshooting
| Problem | Solution |
|---|---|
| Quality tab shows no results | Ensure you have a project open. The tab only analyzes the currently active project. |
| Score seems too low | Review which checks are failing. Often, missing logic and missing resources drive the score down significantly. |
| Check counts don't match expectations | Some checks exclude certain activity types (e.g., LOE activities, milestones). Review the check descriptions for inclusion/exclusion rules. |