How to Run the Schedule Analyzer

By XER Reader Team • September 13, 2026 • 12 min read
How to Run the Schedule Analyzer

The Schedule Analyzer runs 19 checks against an open schedule and reports each one as a pass or a fail against a configurable limit. It is on the Tools tab, under Schedule Analyzer.

Tools tab of the XER Reader ribbon showing Querying, Settings, Column Setting, Manage Baseline and Schedule Analyzer
Schedule Analyzer sits on the Tools tab alongside Querying, Settings, Column Setting and Manage Baseline.

The analysis starts on its own

Clicking Schedule Analyzer opens a full window view titled Schedule Health Assessment and immediately runs the analysis against every project in the file. There is no separate step to start it the first time.

Schedule Health Assessment view in XER Reader showing an overall score of 65 percent, the Baseline list in the title bar, the left panel and the first twelve check cards, each with an info button after its name
The result. Overall Score on the left, one card per check on the right.

Reading the left panel

EntryMeaning
Overall ScoreThe percentage of checks that passed. Green at 90 and above, amber from 70, red below 70
ProjectThe project name the figures relate to
Data DateThe project data date the checks are measured against. For a file that has none, its planned start or its latest progress, followed by (planned start) or (estimated)
ActivitiesTotal activity count
CompletedActivities already finished
PassedChecks passed out of checks run

Overall Score is a count, not a weighting. It is passed checks divided by checks run. A schedule failing four minor checks scores the same as one failing four severe checks, so read the cards rather than stopping at the number.

Reading a metric card

Every check draws the same card: a numbered badge, the check name with an info button after it, what it looks for, the measured value, the count it came from, the limit, and a pass or fail badge on the right.

ElementMeaning
ValueThe measured result, as a percentage or as a ratio
Count / totalThe offending items over the population the check divided by
limitThe configured threshold the value is compared against
minUsed instead of limit where the value must reach the figure rather than stay under it: Relationship Types, CPLI and BEI
Green tickPass
Red crossFail
Grey, --, not measuredThe check could not be made, and the card says why: Needs a baseline: pick one above, Needs a baseline: the schedule has none, Needs a data date: the schedule has none or, for CPLI when no activity is critical, Needs critical activities: the critical rule finds none. It is left out of the score and of Passed
Data date estimated from the latest progressThe check was measured as of an estimated data date, for a file that has none

Relationship Types is the check that reads backwards. It is higher is better: the card shows the percentage of Finish to Start relationships and a minimum of 95 percent, labelled min, and it fails when the value is below that figure. Every other percentage check fails when the value is above its limit. CPLI and BEI work the same way.

The 19 checks

#CheckWhat it counts
1Missing LogicIncomplete activities missing a predecessor or successor, excluding the project's start and finish. A relationship to a project not in the file counts
2LeadsFinish to Start relationships with negative lag
3LagsRelationships with positive lag
4Long LagsRelationships with lag above the configured day count
5Relationship TypesFinish to Start relationships, as a share of all of them. Higher is better
6Hard ConstraintsActivities with Start On, Finish On, Mandatory Start or Mandatory Finish
7Soft ConstraintsActivities with a constraint that limits dates without fixing them
8High FloatIncomplete activities with total float above the configured day count
9Negative FloatIncomplete activities with total float below zero
10High DurationIncomplete non milestone activities with remaining duration above the configured day count
11Invalid Progress BeforeIncomplete activities whose remaining work starts before the data date
12Invalid Progress AfterActivities with actual dates after the data date
13ResourcesNon milestone activities with no resource assignment
14Late ActivitiesActive activities whose early finish is later than their finish in the baseline
15CPLICritical Path Length Index, a ratio. Higher is better
16BEIBaseline Execution Index, a ratio. Higher is better
17Dangling Start ActivitiesActivities with predecessors but no FS or SS link driving their start
18Dangling Finish ActivitiesActivities with successors but no FS or FF link driven by their finish
19Out of SequenceActivities progressed before the predecessor reached the state its relationship requires

Missing Logic and checks 6 to 12 exclude Level of Effort and WBS summary rows, and High Duration, Resources, Late Activities and BEI also exclude milestones. That is why the count / total denominator differs between cards on the same schedule. A denominator that looks wrong is usually one of these exclusions rather than a fault.

What the checks measure against

DenominatorUsed by
Incomplete relationshipsLeads, Lags, Long Lags, Relationship Types
Incomplete activitiesMissing Logic, Hard and Soft Constraints, High Float, Negative Float
Incomplete non milestone activitiesHigh Duration, Late Activities
All non milestone activitiesResources
All activitiesDangling Start, Dangling Finish, Out of Sequence

BEI divides completed non milestone activities by the activities the baseline says should have finished by the data date. An activity the baseline does not have was added after it and is not counted as due.

The baseline BEI and Late Activities are measured against

The title bar shows it as Baseline: followed by its name. Click it to pick another: None (current schedule), the four baseline slots by their names, then the baselines saved inside a Microsoft Project file, MS Project Baseline and MS Project Baseline 1 to 10. A slot that none of the ticked projects has is greyed. Picking one runs the analysis again.

Schedule Health Assessment in XER Reader with the Baseline list open in the title bar, None (current schedule) ticked, the four baseline slots greyed and the BEI card not measured
No baseline is assigned, so the four slots are greyed and BEI is not measured.

Left alone, it takes the first slot that holds a baseline, then the first baseline saved inside the file. A pick is kept for next time; when the ticked projects do not have it, the same rule picks one, and the title bar says which. Projects that do not have the baseline in use are left out of BEI and Late Activities.

With no baseline, BEI and Late Activities are not measured. Their cards turn grey with Needs a baseline: pick one above, or Needs a baseline: the schedule has none when no project has one, and they are left out of the score. Assign one under Manage Baseline on the same Tools tab, or pick one in the title bar.

A file with no data date

A Microsoft Project file whose status date was never set has no data date. The checks that compare with one then go by the schedule itself: when nothing has started, its planned start, shown in the left panel followed by (planned start); when work has started, the latest progress it records, an estimate, shown followed by (estimated).

On an estimate, Invalid Progress Before, CPLI and BEI are measured and their cards say Data date estimated from the latest progress. Invalid Progress After is not measured, since no actual date can be later than the latest progress. With nothing to go by, the four are not measured and say Needs a data date: the schedule has none.

The charts

Below the cards, seven charts break the same data down by distribution rather than by pass and fail.

Charts section of the Schedule Health Assessment in XER Reader showing Relationship Types, Activity Status, Criticality, Open Ends, Total Float, Remaining Duration and Schedule Density
The charts sit at the bottom of the metric list and cover the same population as the cards above them.
ChartBreakdown
Relationship TypesFS, SS, FF and SF counts, with the FS share in the centre
Activity StatusNot Started, In Progress and Complete
CriticalityCritical by the rule under Critical Activities in Preferences, by default as each project defines it; Near critical, the rest with total float up to the near critical limit in Parameters, 10 days by default; Non critical, beyond it. The chart says both rules under its title
Open EndsOpen Start, Open Finish and Linked, Level of Effort and WBS summary rows left out. A relationship to a project not in the file counts
Total FloatNeg, 0, 1 to 5d, 6 to 20d, 21 to 44d and above 44d
Remaining Duration0 to 5d, 6 to 20d, 21 to 44d, 45 to 90d and above 90d
Schedule DensityActivities starting each month, annotated with the peak. Grey for those already started, in the month they actually started; blue for those still to start, in the month planned. A dashed line marks the data date

Total Float is the chart to read alongside the High Float card. The card gives one percentage; the chart shows whether the float is spread across the schedule or piled into a single bucket above 44 days, which points at a specific missing link rather than a general logic problem.

Days, in the charts, the day counts and the lists, are the project's working days: its calendar's hours a day, or Hours/Day in Preferences when the calendar is not used.

What each check means and how it is worked out

Put the pointer on the info button after a check's name. Its tooltip says What it tells and How calculated, with the exact numerator and denominator, which is what to quote when a result is challenged.

Schedule Health Assessment in XER Reader with the tooltip of the Out of Sequence check open, showing What it tells and How calculated
The tooltip of the info button by Out of Sequence: what the check tells and how it is calculated.

The title bar buttons

ButtonEffect
BaselineThe baseline BEI and Late Activities are measured against. Click it to pick another
RunRe runs the analysis. Disabled while a run is in progress
Export PDFWrites the full assessment report. Disabled until an analysis has completed
ParametersOpens the threshold settings
CloseReturns to the activity view

The buttons carry no captions. Hover one to see its name.

Changing the thresholds

Parameters opens Maximum % Allowed (lower = stricter), one row per check.

Parameters dialog in XER Reader showing the maximum percentage allowed for each schedule check with Reset Defaults, Close and Save
Every check has its own limit. Long Lags, High Float and High Duration take a day count as well as a percentage.
Row typeFields
SingleOne percentage limit
Long Lags, High Float, High DurationA day count and a percentage. The day count defines what counts as long, high or excessive, in the project's working days; the percentage is how many of those the schedule may contain
11/12Invalid Progress Before and Invalid Progress After share one limit
CPLI, BEIA minimum rather than a maximum
ChartsHow far near critical runs on the Criticality chart, in days
DefaultValue
Most percentage limits5%
Negative Float, Invalid Progress, Late Activities, Dangling Start, Dangling Finish0%
Out of Sequence2%
Long lag, high float and high duration day counts44 days
CPLI and BEI minimum0.95
Near critical limit10 days

Saving parameters runs the analysis again with the new limits. After ticking other projects or changing Preferences, press Run to see the result of the change.

Reset Defaults opens a list of two. Application Default puts back the thresholds above. DCMA puts back the same with DCMA's figures for four of them: Leads 0%, Relationship Types at most 10% other than Finish to Start, Late Activities 5% and Resources 0%. Save keeps them, Close leaves without saving.

Analysing one project out of several

When the file holds more than one project, a project selector appears in the title bar to the left of Run. It is a checklist, not a single choice: tick the projects to include and the button label reports the selection as All Projects, a project name, or a count.

On a file with a single project the selector is hidden, because there is nothing to choose. Every project is ticked when the view opens, so the first run always covers the whole file.

Unticking the last remaining project is refused. The analyzer keeps at least one project selected, so you cannot arrive at an empty run.

The PDF report holds more than the screen

Export PDF writes a report named ScheduleAssessment.pdf by default, in these sections.

SectionContent
Executive SummaryScore and headline figures, with the baseline
Schedule Logic QualityThe logic checks grouped together
Detailed MetricsEvery check with its value, limit and status. A check not measured shows N/A and why
ChartsThe same seven charts
RecommendationsThe failing checks only, ordered by severity, each with the corrective action
Check MethodologyThe calculation behind each check
Analysis ParametersThe baseline and the thresholds the run used
Activity DetailsThe activities that failed each check, listed by ID

Activity Details is the reason to export. The on screen cards give you a count; the report names the activities behind it, plus a table of external cross project relationships; those to projects not in the file are counted in Schedule Logic Quality but cannot be listed. Out of sequence progress is listed once: under check 19 when it fails, in a table of its own when it passes. Each table stops at 200 rows, and a heading ending in a plus sign means the check found more than were printed.

Recommendation severity is worked out from how far the value sits from its limit: at or beyond twice the limit, or below 80 percent of the minimum on the higher is better checks, a failure is ranked above the rest and printed first.

Requirements

Requires an open schedule with data and a signed in account. Clicking Schedule Analyzer while signed out opens the sign in dialog instead.

Home Pricing Downloads Articles Blog FAQ Contact