Schedule Options
Applies to: Pro · Enterprise Last updated: 27-Feb-2026
Overview
The Schedule Options dialog configures how the CPM engine calculates your schedule. Options are organised in three tabs: General, Calculation, and Advanced. You can run the schedule calculation directly from this dialog.
Prerequisites
- Active Pro or Enterprise subscription
- Editor Mode enabled
- At least one project loaded
Opening Schedule Options
Open from:
- Editor Toolbar → Schedule Settings button
- Grid Toolbar → Project menu → Schedule Options
- Press F9 to open the dialog and calculate in one step
General Tab
| Option | Type | Default | Description |
|---|---|---|---|
| Data Date | Date picker | Current project data date | The status date for scheduling |
| Retained Logic | Toggle | On | Respect predecessor logic for in-progress activities |
| Progress Override | Toggle | Off | Allow progress to override logic constraints |
Retained Logic vs Progress Override
- Retained Logic (recommended): In-progress activities still respect predecessor relationships. If a predecessor is delayed, the remaining work on in-progress successors adjusts accordingly.
- Progress Override: In-progress activities ignore predecessor logic. Useful when actual progress has moved ahead of the planned logic.
Only one of these options should be enabled at a time.
Calculation Tab
| Option | Type | Default | Description |
|---|---|---|---|
| Total Float Calculation | Select | Finish Float | How total float is computed |
| Lag Calendar | Select | Predecessor | Which calendar to use for lag duration |
| Connect Open Ends | Toggle | On | Create implicit links from open-ended activities to the project finish |
| Longest Path Critical | Toggle | Off | Identify the longest path through the network |
Total Float Calculation
| Method | Formula |
|---|---|
| Finish Float | Late Finish − Early Finish |
| Start Float | Late Start − Early Start |
Most practitioners use Finish Float (the default).
Lag Calendar
| Option | Description |
|---|---|
| Predecessor | Lag is measured using the predecessor's calendar |
| Successor | Lag is measured using the successor's calendar |
| Longest | Uses whichever calendar produces the longer duration |
Advanced Tab
| Option | Type | Default | Description |
|---|---|---|---|
| Ignore Completed | Toggle | Off | Exclude completed activities from the calculation |
| Near-Critical Threshold | Number (days) | 10 | Activities with total float at or below this value are flagged as near-critical (range: 0–365 days) |
Defaults
Options initialise in a three-layer merge:
- System defaults — built-in Kazinex defaults
- XER-embedded options — options imported from the P6 schedule file
- User-saved options — your last saved configuration for this project
Your manual changes override all previous layers.
Running the Schedule
Click the "Schedule (F9)" button at the bottom of the dialog to execute the CPM engine immediately. The calculation runs with the current options, and results appear in the Schedule Results Panel.
Tips & Best Practices
- Leave Retained Logic enabled for most projects — it produces the most accurate dates
- Enable Connect Open Ends to prevent open-ended activities from having infinite float
- Enable Longest Path Critical for multi-calendar projects where the traditional critical path may not correctly identify the longest duration chain
- The Near-Critical Threshold of 10 working days is a good starting point; adjust based on project risk tolerance
Related Documentation
- Schedule Calculation — Full CPM pipeline documentation
- Project Properties — Project-level settings
- Critical Path Checks — CPLI and BEI quality checks