{"id":21471,"date":"2025-07-15T11:50:49","date_gmt":"2025-07-15T06:20:49","guid":{"rendered":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/?post_type=article&#038;p=21471"},"modified":"2025-07-29T15:55:56","modified_gmt":"2025-07-29T10:25:56","slug":"automatic-task-rescheduling-based-on-actual-progress","status":"publish","type":"article","link":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/automatic-task-rescheduling-based-on-actual-progress\/","title":{"rendered":"Automatic Task Rescheduling Based on Actual Progress"},"content":{"rendered":"<h2 style=\"background-color: #fcf9ed; padding: 10px; border-radius: 6px; font-size: 1.5em;\">Overview<\/h2>\n<p>When a task(s) is falling behind schedule based on actual progress, Nimble takes action to adjust the <strong>Planned Finish Date<\/strong> based on the task type. This helps project managers by:<\/p>\n<ul data-spread=\"false\">\n<li>Automatically flagging delays without requiring manual tracking.<\/li>\n<li>Saving effort in identifying and rescheduling tasks manually.<\/li>\n<li>Keeping plans dynamically updated based on actual progress.<\/li>\n<\/ul>\n<h2 style=\"background-color: #fcf9ed; padding: 10px; border-radius: 6px; font-size: 1.5em;\">Criteria to Identify Tasks Behind Schedule<\/h2>\n<p>Nimble automatically identifies a task as behind schedule if:<\/p>\n<ul data-spread=\"false\">\n<li>The <strong>Planned Finish Date<\/strong> is in the past and % Work Complete is less than 100%, or<\/li>\n<li>Planned Start Date &lt; Today AND Actual % Complete &lt; Expected % Complete<\/li>\n<\/ul>\n<blockquote><p><em>Expected % Complete is based on working days from Planned Start to the last working day (i.e., yesterday).<\/em><\/p><\/blockquote>\n<table>\n<tbody>\n<tr>\n<th>Task Type<\/th>\n<th>System Action<\/th>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Fixed Work<\/strong><\/td>\n<td style=\"text-align: left;\">Auto-update Planned Finish Date based on remaining effort and resource allocation<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Fixed Unit<\/strong><\/td>\n<td style=\"text-align: left;\">Auto-update Planned Finish Date based on remaining effort and resource allocation<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Fixed Duration<\/strong><\/td>\n<td style=\"text-align: left;\">Show warning icon; no date changes<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Fixed Date<\/strong><\/td>\n<td style=\"text-align: left;\">Show warning icon; no date changes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Tasks with <strong>zero duration<\/strong> (e.g., milestones) are excluded from this behavior.<\/p>\n<h2 style=\"background-color: #fcf9ed; padding: 10px; border-radius: 6px; font-size: 1.5em;\">How Remaining Hours Drives Task Rescheduling<\/h2>\n<p data-pm-slice=\"1 1 []\">For <strong>Fixed Work<\/strong> and <strong>Fixed Unit<\/strong>\u00a0type of tasks, Nimble calculates whether the Remaining Hours can still be completed within the Planned Finish date:<\/p>\n<ul>\n<li data-pm-slice=\"1 1 []\">If <strong>Remaining Hours &gt; available time<\/strong> (based on resource allocation and working hours), the <strong>Planned Finish date is pushed<\/strong> forward accordingly.<\/li>\n<li data-pm-slice=\"1 1 []\">If <strong>today is the last planned day<\/strong> and the task is <strong>not yet complete<\/strong>, the system <strong>waits until the day ends<\/strong> before changing dates.<\/li>\n<li data-pm-slice=\"1 1 []\">Weekend and non-working days are intelligently skipped during this recalculation.<\/li>\n<\/ul>\n<p>When the user opens the Task Plan, the system evaluates actual progress and calculates how many working days required to complete the Remaining Hours based on resource allocation. If needed, it automatically updates the <strong data-start=\"428\" data-end=\"451\">Planned Finish Date<\/strong>. The updated date appears directly in the cell, marked with a red triangle in the top-right corner to indicate it was modified.<\/p>\n<h3 style=\"background-color: #e6f4f1; padding: 6px; border-radius: 6px; font-weight: bold;\"><span style=\"font-size: 14pt;\">Examples:<\/span><\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21869 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-scaled.jpg\" alt=\"Task Plan\" width=\"2560\" height=\"639\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-scaled.jpg 2560w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-300x75.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-1024x255.jpg 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-768x192.jpg 768w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-1536x383.jpg 1536w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Task-1-1-2048x511.jpg 2048w\" sizes=\"(max-width: 2560px) 100vw, 2560px\" \/><\/p>\n<div style=\"background-color: #f0f8ff; padding: 10px; border-radius: 8px;\"><strong>\u00a0Example 1: Insufficient Time Left<\/strong><\/div>\n<ul data-spread=\"false\" data-pm-slice=\"3 1 []\">\n<li><strong>Task TSK1-Develop Login Module<\/strong> (Fixed Units)<\/li>\n<li>Planned Start \u2013 Finish: 28-Jul-2025 to 31-Jul-2025<\/li>\n<li>Planned Hours: 26 hrs | Remaining Hours: 10 hrs<\/li>\n<li>Resource: Emma Dates (100%)<\/li>\n<li>Today&#8217;s Date: 31-Jul-2025 (working day)<\/li>\n<\/ul>\n<p>\ud83d\udccc The task is scheduled to finish today, but it still has 10 hours of pending work. Since Emma is allocated at 100%, she can contribute only 8 hours in a working day. This leaves a shortfall of 2 hours, which cannot be accommodated within today&#8217;s schedule.<\/p>\n<p>Nimble evaluates this mismatch and determines that the task cannot be completed by the current finish date. As a result, it automatically extends the <strong>Planned Finish <\/strong>date\u00a0to <strong>01-Aug-2025<\/strong> to cover the remaining effort. The system marks this change with a red triangle in the date cell, clearly indicating that it was system-modified based on actual progress and allocation. This proactive adjustment helps avoid last-minute surprises for project managers.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21870 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1-.png\" alt=\"Task Plan\" width=\"2854\" height=\"462\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1-.png 2854w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1--300x49.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1--1024x166.png 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1--768x124.png 768w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1--1536x249.png 1536w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-1--2048x332.png 2048w\" sizes=\"(max-width: 2854px) 100vw, 2854px\" \/><\/p>\n<div style=\"background-color: #f0f8ff; padding: 10px; border-radius: 8px;\"><strong>\u00a0Example 2: Progress Possible Within Today<\/strong><\/div>\n<ul data-spread=\"false\" data-pm-slice=\"3 1 []\">\n<li><strong>TSK2 \u2013 Develop User Profile Module<\/strong> (Fixed Work)<\/li>\n<li>Planned Start \u2013 Finish: 15-Jul-2025 to 31-Jul-2025<\/li>\n<li>Planned Hours: 94 hrs | Remaining Hours: 8 hrs<\/li>\n<li>Resources: Emma Dates (45%), Mark Jones (45%)<\/li>\n<li>Today&#8217;s Date: 31-Jul-2025 (working day)<\/li>\n<\/ul>\n<p>\ud83d\udccc Two partially allocated resources offer a combined ~8 hrs\/day. Since 8 hrs remain, the system assumes the task can be completed today. It waits until the end of the day to verify actual completion. As long as the task completes by the end of today, <strong>no date changes<\/strong> are applied.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21871 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2.png\" alt=\"Task Plan Example\" width=\"2854\" height=\"535\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2.png 2854w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2-300x56.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2-1024x192.png 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2-768x144.png 768w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2-1536x288.png 1536w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-2-2048x384.png 2048w\" sizes=\"(max-width: 2854px) 100vw, 2854px\" \/><\/p>\n<div style=\"background-color: #f0f8ff; padding: 10px; border-radius: 8px;\"><strong>Example 3: No Rescheduling for Fixed Duration and Fixed Date Tasks<\/strong><\/div>\n<ul>\n<li><strong>TSK3 \u2013 Develop Notifications Module<\/strong> (Fixed Dates)<\/li>\n<li><strong>TSK4 \u2013 Develop Reports Module<\/strong> (Fixed Duration)<\/li>\n<\/ul>\n<p data-pm-slice=\"1 1 []\">\ud83d\udccc For Tasks TSK3 and TSK4 are <strong>Fixed Dates<\/strong>\u00a0and <strong>Fixed Duration<\/strong> task types are intentionally excluded from automatic date adjustments. This is because the start and finish dates for these task types are usually set <strong>deliberately by the project manager<\/strong> to reflect business constraints, external deadlines, or strict delivery windows. And, changing these dates automatically would defeat the purpose of defining them as &#8220;fixed.&#8221;<\/p>\n<p>Instead, the system displays a \u26a0\ufe0f warning icon in the <strong>Info<\/strong> column to alert the project manager. This indicates that the task is delay or off track and needs attention. On hovering over the icon, the following tooltip is shown: <em>&#8220;This task is behind schedule. Consider adjusting resources or updating progress.&#8221; <\/em>Since Fixed Duration and Fixed Date tasks cannot be rescheduled automatically, this approach ensures the project manager remains fully in control of any required date changes for time-sensitive tasks.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21872 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1.png\" alt=\"Task Plan Example\" width=\"2854\" height=\"712\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1.png 2854w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1-300x75.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1-1024x255.png 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1-768x192.png 768w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1-1536x383.png 1536w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/07\/Example-3-and-4-1-2048x511.png 2048w\" sizes=\"(max-width: 2854px) 100vw, 2854px\" \/><\/p>\n<h2 style=\"background-color: #fcf9ed; padding: 10px; border-radius: 6px; font-size: 1.5em;\">Important Notes<\/h2>\n<ul data-spread=\"false\">\n<li>This applies to both Simple and Advanced Scheduling types.<\/li>\n<li>Automatic changes to a task (such as updates to the Planned Finish Date) occur only when the user checks in the task and has to edit it.<\/li>\n<li>When <strong>Planned Finish<\/strong> changes, <strong>Planned Duration<\/strong> is also recalculated automatically to reflect the new date range. This ensures duration is based on updated working dates while maintaining effort realism.<\/li>\n<li>The system recalculates dates automatically whenever the user opens the Task Plan or modifies a task.<\/li>\n<li>Changes made by the system (like new Planned Finish Dates) are currently indicated with a red triangle in the cell.<\/li>\n<\/ul>\n<blockquote><p>It is recommended that Project Managers periodically review their task plans to understand automated changes and take informed actions.<\/p><\/blockquote>\n<div class=\"helpful-block-content wth-theme-thumbs\" data-title=\"\" >\n<ul>\n<li><span class=\"wth-title\">Was this helpful?<\/span><\/li>\n<li><a data-post=\"21471\" data-post-url=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/automatic-task-rescheduling-based-on-actual-progress\/\" data-post-title=\"Automatic Task Rescheduling Based on Actual Progress\" data-response=\"1\" href=\"#\" class=\"wth-green-btn icon-thumbsup\">Yes<\/a>&nbsp; &nbsp;<a data-response=\"0\" data-post=\"21471\" data-post-url=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/automatic-task-rescheduling-based-on-actual-progress\/\" data-post-title=\"Automatic Task Rescheduling Based on Actual Progress\" href=\"#\" class=\"wth-red-btn icon-thumbsdown\">No<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"author":4,"featured_media":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","multi-rating":{"mr_rating_results":[]},"_links":{"self":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/21471"}],"collection":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/types\/article"}],"author":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/comments?post=21471"}],"version-history":[{"count":9,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/21471\/revisions"}],"predecessor-version":[{"id":21866,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/21471\/revisions\/21866"}],"wp:attachment":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/media?parent=21471"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}