Desktop P6 Professional workflow. Menu labels are aligned with Oracle’s current Version 26 help; older 24.x deployments may show minor wording or privilege differences.
Key takeaways
- Set and record project-appropriate thresholds before running the report.
- Investigate findings in context; metrics are screening evidence, not automatic verdicts.
- Retain the report, disposition register, corrected file, and rerun.
Configure thresholds before interpreting results
Long duration, long lag, and large float require project-specific thresholds and calendar awareness. Record the values used so counts can be reproduced from one update to the next.
Every exception needs a disposition
Classify each finding as corrected, accepted with reason, not applicable, or pending evidence. Preserve the before and after report. A lower issue count without a disposition can indicate deletion or relaxed thresholds rather than improvement.
Run a reproducible P6 quality screen
Use a controlled copy when the reviewer should not alter the submitted schedule.
Menu path: Tools > Check Schedule Report
Before you start
- Native submitted file
- Correct data date and schedule calculation
- Approved thresholds
- Disposition register
Open only the intended project set
Confirm open projects, external links, and the calculation used for review.
Verify: Project IDs, data dates, and activity counts match the submission record.
Select checks
Choose logic, lags, relationship types, constraints, float, durations, progress, resources/cost, late work, baseline, links, OOS, and dangling checks as applicable.
Verify: The selected scope matches the review protocol.
Set thresholds
Enter approved long-lag, large-float, and large-duration values using the schedule’s calendar convention.
Verify: Thresholds are recorded with the report.
Generate the report
Choose a controlled filename and run Check Schedule.
Verify: The report identifies project, data date, counts, and individual exceptions.
Inspect failures
Use View > Check Schedule filters or controlled exception layouts to trace each material item.
Verify: Every exception has a cause, effect, owner, and proposed disposition.
Correct and rerun
Apply authorized corrections in a working copy and rerun with identical thresholds.
Verify: The before/after change is explained and no new defect was introduced.
Field-ready control
Check Schedule evidence package
- Submitted native file preserved
- Correct project and data date
- Checks and thresholds recorded
- Report retained
- Exceptions traced to activities
- Disposition recorded
- Authorized corrections only
- Identical-threshold rerun retained
Common questions
Does a schedule pass if it is under every threshold?
No. The report does not validate scope completeness, means and methods, duration basis, field status, contract alignment, or whether the relationships describe a buildable plan.
Sources and scope
Follow the reference trail.
This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.
Checking schedulesOracle · checked 2026-08-01Check a scheduleOracle · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01