Overview

Updating an ongoing project in LYNX should be done in a way that keeps the project logic clear, minimizes manual work, and makes the impact of changes visible before you commit them. In practice, most updates fall into one of two categories: small changes that can be made directly in the target project, and medium or large changes that are safer to prepare in a temporary project first. The recommended process also includes reviewing the effect on the critical chain, due date, and buffer consumption, and comparing versions when you want to simulate changes before applying them.

Choose the right update method

Before you start, decide whether the change is small or more substantial.

A small change usually means one or a few tasks with local connections. In that case, the most efficient method is to insert the task directly into the ongoing target project, add or confirm the dependencies, and review the logic. 

A medium or large change usually means a section of tasks that would take too long to build manually or would be easier to prepare from structured source data such as Excel. In that case, the recommended method is to import the work into a temporary project first and then move the prepared section into the target project.

Updating an ongoing project with small changes

For smaller updates, you can work directly in the target project. This method is best when the change is limited in scope and the new work can be connected to the surrounding tasks without major restructuring. The goal is to make the update quickly, while still checking that the project network remains correct.

Step 1: Open the target project

Open the ongoing project where the new task or small update should be added. Make sure you know where the change belongs in the existing task flow before inserting anything.

Step 2: Insert the new task inline

Use the inline insert option to place the new task directly in the target project. This is the recommended approach for a small change because it keeps the update close to the existing work and avoids unnecessary extra setup.

Step 3: Review automatically created dependencies

When a task is inserted inline, LYNX can automatically create dependencies. Review those links carefully to make sure the task is attached to the correct predecessor and successor tasks. Even when the software creates the first logic automatically, you should still confirm that the sequence matches the intended project flow.

Step 4: Review the project in holistic view

After the new task is in place, review the network logic and add additional changes if needed.

Updating an ongoing project with medium or large changes

When the update affects a whole section of tasks, the recommended process is to use a temporary project first. This reduces manual data entry, gives you a safer place to prepare the update, and makes it easier to review the imported work before moving it into the live target project. The main tools mentioned in the presentation are the Import Wizard, a temporary project, copy/paste of the task section, and a network logic review with PERT.

Step 1: Prepare the source data

If the new work already exists in Excel, use that as the base for the import. The presentation specifically notes that the attached Excel file serves as the base table, so your first check should always be whether the data is structured correctly before importing it into LYNX.

Step 2: Open the Import Wizard

Go to the Import function in LYNX and paste the prepared data from Excel into the wizard. This is the fastest way to build a larger section of work without entering each task manually.

Step 3: Check the imported fields

Before continuing, verify that the data has been inserted correctly and that each field has been defined correctly. This is one of the most important checks in the process, because incorrect field mapping at import stage can create unnecessary cleanup later.

Step 4: Complete the import into a temporary project

When the import is completed, the new imported project will appear in the Project Portfolio. This imported project acts as a temporary staging area where you can validate the new section before moving it into the actual target project.

Step 5: Review and adjust the temporary project

Open the temporary project and review the imported tasks carefully. Correct any details that need adjustment, confirm the order of work, and prepare the section exactly as it should appear before it is copied into the target project.

Step 6: Copy the prepared section into the target project

Once the temporary project looks correct, copy and paste the relevant tasks or cards into the ongoing target project. Then add the required dependencies and review the logic again in PERT to make sure the imported section is connected properly to the existing work.

Review and confirm the impact of the changes

After you add changes to the ongoing target project, the next step is to review their effect. The presentation recommends checking three things: project statistics, critical chain versus due date, and buffer consumption. These checks help you decide whether the project can keep running with the current structure or whether the changes are large enough to require a recalculation.

If the impact is limited

If the review shows that the impact is limited, you can keep the buffers as they are and save or commit the changes. This is the most straightforward outcome and is typical for smaller updates that do not materially change the overall project structure.

If the impact is significant

If the review shows that the impact is significant, the presentation recommends a more careful reset-and-review process. Switch the project to Not Started, remove or recalculate the buffers, reconsider whether the due date should be updated, release the project again, and then save or commit the changes. This helps ensure that the new project logic and schedule protection reflect the updated reality of the work.

Compare and validate changes

If you want to test changes before updating the live project, create a copy of the target project and apply the changes there. Then compare the original and updated versions using critical chain, buffer consumption, and project statistics. Recalculate the copied project if needed, and if the result is acceptable, apply the approved changes to the original project. You can also ask AI to compare both projects or run a Project Report that includes both versions.

In Lynx-X, you can also use the Portfolio View to visualize Project Statistics in the right-hand panel. By selecting different projects within this view, the key statistical values update dynamically, making it easy to identify and compare differences at a glance.

We highly recommend using Reporting or the AI Dashboard to compare information side by side and better understand the impact of the changes.

For example, this widget (WidgetShareCode-[imar-wv1c-hvij]) allows you to select the original project alongside the updated version, helping you quickly identify where to focus your attention and which tasks have been modified. It would look something like this:

You can further customize the widget to match your specific requirements or preferred way of visualizing the data.

Tips and supporting tools

For larger updates, you can pause auto scheduling while making changes and reactivate it afterward to review the impact. If the network becomes difficult to manage, set the project to Not Started, remove the buffers, connect the new task or section, and then add the buffers again. Use Undo if you need to reverse unwanted changes. Helpful related features include Project Properties, Control Feeding Chain Durations, Rescheduling Behavior for Ongoing Projects, and the LYNX Scenario Wizard for comparing projects. As a general rule, make small changes directly in the target project, use a temporary project and the Import Wizard for larger updates, and compare project versions first when you are unsure about the impact.