How to Split an Activity in P6: Step-by-Step Guide

How-to basics · Updated November 22, 2026

In Primavera P6 Professional, select the activity and use Edit > Split Activity to represent a planned interruption and later restart. Enter the split or restart date requested by your version, then review the resulting activity segments and schedule. Before you begin, confirm the activity’s status, remaining work, calendar, and relationships: splitting changes schedule logic, so it should reflect a real work break rather than simply divide an activity for display.

This guide focuses on P6 Professional for Windows. Menu wording and the split dialog can vary by release, and P6 EPPM may present the operation differently. Check the date field’s label in your version; the intent is to mark where work is interrupted and the continuation is to resume.

What You’ll Need

  • Access to the correct P6 project with permission to edit activities.
  • The activity’s ID and a clear understanding of its status, actual dates, remaining duration, and work calendar.
  • The planned interruption and restart dates, plus the reason for the break.
  • A recent project copy or other approved recovery point if your organization requires one.
  • Knowledge of the activity’s predecessors, successors, constraints, and resource assignments so you can check the effects after the split.

Step-by-Step

  1. Open the right project and confirm the schedule context. In P6 Professional, open the project you intend to update. Check that you are working in the correct project, not a reflection or copy, and confirm the current data date and layout. If your team follows a status-update or change-control process, complete the required checks before making the edit. Splitting an activity in a live schedule can affect forecast dates and should be coordinated with the scheduler or project controls lead.
  2. Find and inspect the activity. In the Activities window, locate the activity by Activity ID or name. Confirm the row is the correct work item and review its status, start and finish dates, original and remaining duration, calendar, and assigned resources. In the Activity Details pane, inspect the Relationships and Resources tabs as needed. Note which successors depend on it and whether any dates are driven by constraints. A split is not a substitute for correcting inaccurate progress or an incorrect activity calendar.
  3. Record the interruption and restart plan. Identify the last date work will occur before the break and the planned date work will resume. Distinguish calendar days from working days: a calendar may exclude weekends, holidays, or shift hours. The date entered in the split dialog determines the boundary or restart point, depending on the dialog wording in your release. If you are unsure which date the field expects, consult the dialog help or test the operation in a copy of the project first. Do not guess and then accept a changed forecast without checking it.
  4. Select the activity and open the split command. Click the activity row so it is selected, then choose Edit > Split Activity. If the command is unavailable, confirm that an activity—not a WBS row or blank area—is selected and that you have edit access. Some releases or project configurations may impose status or other eligibility conditions. If P6 presents a message explaining that the selected activity cannot be split, read it rather than trying to bypass the restriction.
  5. Enter the split date or restart date. In the Split Activity dialog, enter the planned date and, if available, time for the interruption boundary or continuation. Use the date format shown in P6 and verify the year as well as the day and month. For example, if work is expected to stop after a period of installation and resume after a delivery delay, use the planned restart point to represent the interruption. The break should not be counted as productive duration. If the dialog offers an activity ID or continuation details, use your project’s naming rules and choose a distinct, meaningful ID where prompted.
  6. Review and accept the resulting segments. Confirm the dialog and inspect the Activities table. P6 represents the work as an original segment and a continuation segment; the continuation may receive a new ID or require one, depending on the release and settings. Check that names make the relationship clear, such as retaining the original description and identifying the later portion as a continuation. Verify that the interruption appears in the expected place and that neither segment has an unintended duration or date. Do not assume the split preserved every detail exactly as you intended.
  7. Check logic, resources, and progress. Review relationships for both segments and confirm that the continuation follows the first portion in a sensible sequence. Check whether successors still reference the correct portion of the work. Review resource assignments, calendars, activity type, remaining duration, and any constraints or codes that matter to your schedule. If P6 copied assignments or relationships to the continuation, decide whether they should remain; an assignment spanning the break may not represent how the crew or equipment will actually be used. Update the records according to your project’s progress rules.
  8. Reschedule and validate the forecast. Use Tools > Schedule (or press F9 in P6 Professional for Windows) to recalculate the project, following your team’s scheduling settings and data-date procedure. Inspect the activity dates, total float, critical path, and affected successors before saving or publishing. Compare the updated dates with the intended restart and downstream plan. If results are unexpected, undo the edit if available or restore the approved copy, correct the inputs, and reschedule again. Record the reason for the split and communicate material forecast changes to the appropriate reviewers.

Common Mistakes

Using a split to show two scopes of work. A split is intended to represent an interruption in one activity, not to conceal that the work has separate deliverables or different logic. If the portions have independent scope, responsibility, or acceptance criteria, create separate activities and connect them with appropriate relationships instead.

Entering the stop date when the field expects the restart point. Read the dialog label and help carefully. A one-day error—or a date entered in the wrong month/day format—can shift the continuation and every dependent forecast. Check the displayed dates after the operation.

Ignoring status and actuals. Do not split an activity to make progress appear better or to overwrite actual dates. Confirm that actual start and completed work are recorded correctly, and follow your organization’s rules for updating remaining duration and the data date.

Leaving copied logic or resources unchecked. The new segment may have relationships or assignments that do not fit the restart plan. Verify them instead of assuming that copied data is correct. Also check constraints, since a hard date constraint can mask the effect of the split.

Forgetting to reschedule. The visible dates immediately after editing may not reflect the final calculated forecast. Run the schedule and review downstream effects before reporting dates.

Tips

  • Make a note of the original dates and relationships before editing, especially in a shared or statused project.
  • Use the activity notebook, a project change log, or your team’s approved documentation field to record why the work stopped and when it is expected to restart.
  • Choose a continuation name that is recognizable in reports, but retain a clear link to the original activity ID. Follow the project’s established ID convention rather than inventing one-off patterns.
  • Check the activity calendar before choosing dates. A restart on a holiday or nonworking shift may schedule to a different working time than you expect.
  • Test a complex or high-impact change in a project copy first. This is especially useful when the activity is in progress, has many successors, or sits on the critical path.
  • After scheduling, compare more than the split activity itself. Review milestones and key successor dates, and explain any change that affects the project’s published forecast.

Troubleshooting

The Split Activity command is disabled. Select an activity row in the Activities window, not a WBS summary row or an empty part of the table. Check that the project is open for editing and that your access rights allow changes. If the activity’s status or configuration is not eligible in your P6 release, read the on-screen message and consult your project administrator or the relevant version’s help. Avoid changing status merely to force the command to work.

The continuation starts on the wrong date. Verify the entered date, date format, time, activity calendar, and scheduling settings. Check whether the field represented the split boundary or the resumption date in your version. Then reschedule and inspect the result. If the intended date is nonworking, P6 may place work at the next permitted working time; adjust the plan or calendar only when that reflects the approved schedule.

Successor dates or float change unexpectedly. Review the relationships attached to both segments, any constraints, and the project’s scheduling options. Determine which segment should drive each successor. Remove or revise a relationship only when the logic is genuinely wrong and the change is authorized. If the activity affects a milestone or critical path, review the impact with the scheduler before publishing the forecast.

Resources appear on both portions or the remaining duration looks wrong. Inspect assignments and remaining duration on each segment, then compare them with the actual work plan and progress records. Correct assignments and duration using your normal update procedure; do not simply reduce duration to force a desired finish. If the operation produced a result you cannot safely correct, stop, restore the saved project copy or use your organization’s recovery process, and repeat the change with the right inputs.

You cannot tell whether the split worked. Reschedule the project, widen the date columns or view the activity in a Gantt chart, and inspect the gap and continuation. Confirm the two activity IDs, dates, durations, and logic. If the visual display is compressed, adjust the timescale rather than concluding that the break is missing.

Frequently Asked Questions

What does splitting an activity in P6 do?
It represents one activity’s work as portions separated by an interruption, with a continuation after the break. It can affect dates and logic, so inspect both portions after splitting.

Does splitting an activity create a new activity?
P6 represents the continuation separately, commonly with a new activity ID. The exact prompt and ID behavior can vary by release and settings; review the resulting rows and follow your project’s ID conventions.

Can I split a completed or not-started activity?
Eligibility can depend on the P6 release, activity status, and project configuration. If the command is unavailable or P6 displays a warning, follow that guidance rather than changing status to force a split. For separate future work, two linked activities may be more appropriate.

Will the split automatically update successors?
It can change the schedule calculation, but you must verify relationships and resulting dates. Check which portion should control each successor, then run the scheduler and review the forecast.

Should I split an activity or create two activities?
Use a split when the same work is interrupted and later resumes. Create separate activities when the work portions have different scopes, owners, deliverables, or independent logic. Clear activity structure makes updates and reports easier to interpret.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.