Schedule integrity assessment
How to Perform a Schedule Health Check
Inspect the schedule’s structure, logic, durations, constraints, calendars, float, status, milestones, critical paths, resources, and baseline integrity—then convert technical findings into controlled, prioritized corrections.
Purpose and boundaries
A schedule health check tests whether the model can be trusted
A Schedule Health Check is a structured assessment of schedule data, network logic, calculation behavior, status integrity, and supporting controls. It identifies conditions that may prevent the schedule from producing credible dates, float, critical paths, trends, or management information.
The health check does not ask only whether the schedule file opens or whether every row contains a date. It asks whether the dates are generated by a coherent model of work. A schedule can look complete while containing disconnected activities, unjustified constraints, hidden calendar exceptions, excessive lags, incomplete work in the past, or a critical path that does not represent the actual route to completion.
Automated tools can count potential exceptions quickly, but they cannot determine every exception’s operational meaning. An activity with no predecessor may be a legitimate project-start event or a missing dependency. A hard constraint may reflect a binding external commitment or may have been used to force an unsupported date. The assessment must combine data checks with informed review.
Detect
Identify structural and status conditions that could weaken calculation, traceability, analysis, or controlled reporting.
Interpret
Determine whether each flagged condition is an error, a justified exception, an accepted limitation, or a symptom of a larger issue.
Correct
Assign severity, ownership, corrective action, target date, validation evidence, and controlled closure to confirmed findings.
Assessment dimensions
What a complete health check should examine
| Assessment area | Condition examined | Possible consequence | Interpretation question |
|---|---|---|---|
| Scope structure | Activities map to approved scope and deliverables | Required work may be absent or duplicated | Can every material deliverable be traced? |
| Missing predecessors | Remaining activities have no valid incoming logic | Starts may not respond to upstream delay | Is this an authorized project-start point? |
| Missing successors | Remaining activities have no valid outgoing logic | Delay may not reach completion milestones | Is this a genuine terminal activity? |
| Constraints | Hard or soft dates override normal calculation | Float and critical paths may be distorted | Is the restriction real and documented? |
| Lags and leads | Elapsed time is hidden inside relationships | Work, ownership, and resources may be invisible | Should this be a measurable activity? |
| Durations | Very long, very short, zero, or unsupported durations | Progress or uncertainty may be hidden | Does the duration support useful control? |
| Calendars | Incorrect assignments or undocumented exceptions | Dates may fall on unavailable periods | Does the calendar reflect actual conditions? |
| Status integrity | Actual and remaining work conflict with the status date | Forecast dates and progress become unreliable | Is past work actual and future work forecast? |
| Float | Extreme positive or negative values | Logic, constraints, or commitments may be problematic | Can the amount of flexibility be explained? |
| Critical path | Path is broken, constrained, inactive, or implausible | Management may focus on the wrong work | Does the path truly drive the selected milestone? |
| Resources | Availability or allocation conflicts with the plan | Calculated dates may be operationally impossible | Are critical resources available when planned? |
| Baseline and changes | Missing baseline dates or undocumented modifications | Performance and history cannot be explained | Can movement be traced to approved decisions? |
Preparation
Establish a reproducible assessment before reviewing results
Freeze the assessed version
Record the schedule file, version, status date, extraction date, baseline, project calendar, tool version, and applied filters. Do not assess a moving working file while contributors continue editing it.
Define the population
Decide whether metrics apply to remaining detailed activities, milestones, completed work, summary rows, planning packages, external activities, or specific workstreams. Denominators must be consistent for trend comparison.
Define the criteria
Document thresholds, exclusions, severity rules, accepted conventions, schedule-tool behavior, and evidence required to justify an exception.
Preserve the raw findings before corrections begin. If a team repairs activities during the assessment without retaining the original result, the final report cannot show what was found, what changed, or whether corrections introduced new issues.
Step-by-step audit
Perform the Schedule Health Check in fourteen stages
Record schedule control information
Capture project name, schedule name, version, status date, baseline version, current forecast finish, total activity count, completed activity count, remaining activity count, schedule tool, assessor, assessment date, and assessment scope.
These details make the result reproducible and prevent metrics from different files or status periods being compared as though they described the same schedule.
Verify scope and structural traceability
Confirm that detailed activities map to the approved work structure and that major deliverables contain the work necessary to complete them. Look for unclassified activities, empty summary branches, duplicate scope, and deliverables supported only by manually entered milestone dates.
Structural completeness normally requires comparison with the controlled WBS, deliverable register, contract, scope statement, or another authoritative source. A schedule cannot prove its own scope completeness.
Find missing predecessors
Filter remaining detailed activities and milestones that have no valid predecessor. Exclude only authorized project-start points and documented external starts.
For each item, ask what event, input, approval, material, decision, or completed work permits it to begin. Add the real relationship rather than a convenient link that merely removes the exception.
Find missing successors
Identify remaining detailed activities and milestones that do not drive another activity or recognized completion point. Exclude legitimate terminal milestones.
Ask which downstream work, delivery, acceptance, or outcome uses the activity’s result. Without outgoing logic, delay may not propagate to the project milestone it should affect.
Review relationship types and network logic
Inspect finish-to-start, start-to-start, finish-to-finish, and any unusual relationship types. Confirm that every relationship models a real dependency and points in the correct direction.
Investigate circular logic, links attached to summary activities, duplicate relationships, unnecessary complexity, and logic created solely to manipulate dates. Review representative end-to-end paths with activity owners.
Assess lags and leads
List all nonzero lag or lead values, their units, relationship types, owners, and justification. Long or numerous lags can hide waiting periods that cannot be assigned, statused, resourced, or analyzed independently.
Replace a lag with a named activity when the interval represents meaningful work, review, curing, delivery, approval, queue time, or another controllable event. Retain justified lag only when it accurately represents the scheduling method.
Review date constraints
Extract every hard and soft constraint, its date, type, source, owner, reason, approval, and effect. Determine whether logic, calendars, resource availability, or a milestone could model the condition more accurately.
A valid external commitment may justify a constraint. A date entered only to keep an activity on the desired side of a report should be corrected because it can distort float and path calculations.
Test activity durations
Review zero-duration items that are not genuine milestones, negative or invalid values, inconsistent units, unusually long activities, very short activities below practical status resolution, and durations lacking estimating support.
Long activities are not automatically wrong. Determine whether decomposition would reveal measurable progress, ownership, dependencies, decision points, resource demand, or risk exposure.
Inspect calendar assignments
List calendars, working patterns, exceptions, owners, and assigned activities or resources. Search for weekend or holiday dates, unexpected continuous calendars, obsolete calendars, and activities using an incorrect location or shift calendar.
Test a sample of date calculations. A structurally correct activity can still produce an unreliable forecast when assigned to the wrong calendar.
Validate status against the data date
Confirm that actual starts and finishes do not occur after the status date, incomplete work is not left before it, and remaining forecasts are scheduled in the future. Review activities marked complete without required completion evidence.
Investigate out-of-sequence progress and understand how the scheduling tool handles remaining logic. Status corrections should reflect reality rather than simply moving every incomplete task forward.
Analyze total float
Examine negative float, zero or low float, extreme positive float, sudden changes from the previous period, and inconsistent values on related paths.
Negative float may indicate an unresolved conflict with a constraint or required date. Very high float can indicate missing downstream logic, distant constraints, calendar anomalies, or a genuinely flexible path. Interpret the network before acting.
Validate critical and driving paths
Trace the path to final completion and other decision-critical milestones. Confirm that it is continuous, contains remaining executable work, follows credible technical sequence, and is not artificially created by constraints, long lags, or calendar anomalies.
Review near-critical paths and path convergence. A single reported critical path may not reveal another sequence with very little flexibility or significant uncertainty.
Review resources, coding, and baseline integrity
Check missing owners, invalid codes, inconsistent WBS mapping, critical-resource over-allocation, baseline gaps, unauthorized baseline changes, and forecasts that conflict with approved staffing or cost assumptions.
These findings may not be pure network-logic errors, but they affect whether the schedule can support management decisions and controlled reporting.
Prioritize, correct, retest, and close
Assign every confirmed finding an identifier, affected activity, category, severity, explanation, consequence, owner, corrective action, due date, status, and closure evidence.
Correct high-impact issues first, recalculate the schedule, and rerun the complete assessment. One repair may change float, critical paths, dates, or create a different exception elsewhere. Close findings only after validation.
Interactive diagnostic
Schedule Health Indicator Calculator
Enter high-level counts from the remaining detailed activity population. The tool produces a prioritization aid, not a certification or universal pass/fail judgment.
Health-check diagnostic
Assessment pending
Severity model
Prioritize findings by decision impact—not count alone
| Severity | Typical condition | Management consequence | Expected response |
|---|---|---|---|
| Critical | Completion path is broken or status materially false | Key forecast or commitment cannot be relied upon | Correct before controlled publication where feasible |
| High | Defect affects a major milestone, critical path, or baseline | Important decision may use misleading information | Named owner and prompt corrective action |
| Moderate | Localized defect affects analysis or maintainability | Schedule remains usable with stated limitation | Correct through planned update cycle |
| Low | Formatting, coding, or isolated documentation weakness | Limited immediate effect but recurring quality cost | Batch correction or process improvement |
| Accepted exception | Condition is valid and supported by evidence | No correction required while basis remains valid | Document reason, owner, review date, and expiry trigger |
One missing relationship on a completion-driving milestone may matter more than fifty minor coding gaps. Report both counts and consequence. Avoid declaring a schedule healthy because its overall exception percentage is low when the remaining exceptions affect decisive paths.
Corrective-action workflow
Turn findings into controlled improvements
Confirm the condition
Review the flagged activity, governing rule, related logic, owner explanation, schedule-tool behavior, and supporting records. Remove false positives from the correction queue but retain their justification.
Correct the root cause
Repair the underlying logic, status process, calendar ownership, estimation practice, training gap, integration failure, or control weakness—not merely the visible field.
Retest the network
Recalculate dates and rerun all relevant checks. Review changed milestones, float, paths, resource demand, and new exceptions before accepting closure.
Corrective-action register fields
- Unique finding identifier
- Schedule version and status date
- Affected activity or milestone identifiers
- Finding category and assessment rule
- Observed condition and supporting evidence
- Potential effect on dates, paths, float, or decisions
- Severity and prioritization basis
- Responsible correction owner
- Agreed corrective action and target date
- Disposition: correct, accept, defer, or not applicable
- Retest result and closure evidence
- Reviewer, closure date, and resulting schedule version
Trend management
Compare health consistently across update periods
A single health check provides a snapshot. Repeated assessments show whether schedule discipline is improving, stable, or deteriorating. Use the same criteria and comparable activity population when creating a trend.
Track counts with denominators
“Ten missing predecessors” means something different in a schedule with 100 remaining activities than one with 20,000. Report the count, assessed population, percentage, exclusions, and materiality.
Track closure and recurrence
Measure findings opened, corrected, accepted, overdue, reopened, and repeated. Recurrence may indicate a process or training problem even when each instance is repaired quickly.
Track schedule characteristics
Compare activity count, completed work, current finish, status date, critical path length, negative float, calendar count, and major constraints to understand structural change.
Preserve narrative context
Explain scope additions, re-planning, supplier integration, tool migration, baseline change, or criterion changes that affect the trend. Numbers without context can create false conclusions.
Common audit failures
Mistakes that weaken a Schedule Health Check
Applying one universal threshold
A threshold copied from another project may not fit the schedule’s size, reporting cycle, activity maturity, tool, or operating model.
Correction: define criteria deliberately and retain enough consistency for valid trend comparison.
Counting summary rows as detailed work
Metrics become distorted because summary activities follow different structural rules.
Correction: define the assessed population and separate detailed activities, milestones, summaries, completed work, and planning packages.
Fixing exceptions with artificial links
Users add relationships only to satisfy the tool, not because the work is dependent.
Correction: ask what real input or output connects the activities and model that dependency.
Reporting percentages without impact
Leadership sees a green score while a small number of serious defects affects the project finish.
Correction: report severity, affected commitments, path location, and management consequence alongside metrics.
Deleting justified exceptions
A valid external constraint or terminal activity is changed solely to improve the score.
Correction: document accepted exceptions with their basis and review trigger.
Auditing an uncontrolled file
Results cannot be reproduced because the schedule changes during the assessment.
Correction: retain the exact assessed version, status date, filters, criteria, and output.
Closing findings without recalculation
Corrections create new date, float, path, or status problems that are not detected.
Correction: rerun the complete assessment after material changes and verify forecast consequences.
Using health checks as punishment
Contributors hide issues because findings are treated as personal failures.
Correction: use the process to improve schedule information, controls, training, and decisions while maintaining clear accountability.
Final verification
Schedule Health Check checklist
0 of 14 health-check items completed.
Questions answered
Schedule Health Check FAQs
How often should a Schedule Health Check be performed?
Run structural checks during schedule development, before baseline approval, after major integration or change, and on a recurring cadence aligned with schedule updates. High-risk schedules may need checks during every controlled update.
Does a high health score prove the completion date is achievable?
No. A structurally clean schedule can still contain incomplete scope, optimistic durations, unavailable resources, or untreated risks. Health results must be combined with scope, technical, resource, cost, and risk review.
Should every activity have a predecessor and successor?
Most remaining detailed activities should. Authorized project-start points and genuine terminal milestones can be valid exceptions. Every open end should be reviewed and documented.
Are date constraints always bad?
No. A contractual, regulatory, operational, or external date may justify a constraint. The issue is excessive, unsupported, or calculation-distorting use when logic or calendars would represent the condition better.
Should all lags be converted into activities?
Not automatically. Convert intervals representing measurable work, ownership, cost, resources, risk, or status. Retain a lag where it accurately models the approved method and is properly documented.
What does negative float mean?
Negative float commonly indicates that calculated work cannot meet a constrained or required date under current assumptions. Review the logic, calendars, durations, constraints, status, and commitment before selecting corrective action.
Can a spreadsheet perform a health check?
Exported data and spreadsheet filters can support many checks, but tool-specific schedule calculations, relationship behavior, calendars, float, and critical paths should be validated in the scheduling system. Preserve the exact assessed dataset.
How does a health check support an Integrated Master Schedule?
It helps determine whether the Integrated Master Schedule can calculate and communicate reliable dates, paths, float, status, and milestone information after that guide URL is published.
Where can smaller operational schedules be prepared?
Teams can prepare working plans using the Weekly Schedule Builder , Monthly Schedule Builder , or other verified ScheduleFlowLab tools .