--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Schedule conflicts between project tasks # Schedule conflicts between project tasks {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Schedule conflicts between project tasks Scheduling conflicts arise in project tasks when dependencies or constraint types cause a task's start date to violate the project's constraint date. These conflicts occur when actions---such as adding dependencies or changing constraint types---result in task start dates that do not honor specified constraints, impacting the project schedule. Show full answer Show less ## Key Features * **Conflict Detection:** The system automatically detects scheduling conflicts when task start dates cannot comply with constraints due to dependencies. * **User Notification:** When a conflict is identified, the planning console (both client-side and server-side) alerts users with a pop-up message and highlights the conflict by changing the calendar icon to red. * **User Decision Options:** Users can choose to cancel the conflicting action or proceed despite the conflict. * **Constraint Precedence:** If the user proceeds, the constraint date takes highest precedence. The task start date is adjusted to the constraint, but dependencies may not be honored. * **Task Constraint Types:** Conflicts are primarily associated with tasks using "Start no later than" or "Start on specific date" constraints. Changing to "Start as soon as possible" (ASAP) allows dependencies to be honored and avoids conflicts. ## Practical Implications for ServiceNow Customers ServiceNow customers managing projects should be aware that scheduling conflicts can affect task sequencing and deadlines when constraints and dependencies clash. The system provides clear warnings and visual indicators, enabling project managers to make informed decisions---either to maintain constraints or to adjust dependencies. To minimize conflicts, consider setting task constraints to "Start ASAP" where flexibility is possible. During planning, use the planning console notifications and icons to quickly identify and resolve conflicts, ensuring your project schedule remains both feasible and aligned with business requirements. Scheduling conflict helps you to identify project tasks that are not honoring dependencies. A scheduling conflict occurs when one project task prevents other task from starting on the specified date because of dependencies or constraint types. A scheduling conflict occurs when any action such as applying a dependency, changing constraint type, or constraint date causes the task start date to violate the project's constraint date. When a scheduling conflict occurs, the system warns you about the conflict. You can choose to cancel the action that is causing the conflict or continue with the conflict. If you choose to continue with the conflict, the constraint date is given highest precedence and dates are recalculated. The start date is moved till allowed by the task constraint date, but dependency is not honored. For example, consider the following scenario: For a project with project task's Constraint date set as 20 January, there are two tasks: * T1 with constraint type set to As soon as possible and start date of 20 January. * T2 with constraint type set to Start no later than and start date of 20 January. {#scheduling-conflicts__ul_vwr_r5d_4lb} If you add an FS dependency between tasks T1 and T2, the task T2 should start on 21 January, but due to Start no later than constraint, task T2 cannot start on 21 January. This inability of starting task T2 on the specified date is an example of conflict. In this example, if you choose to proceed with the conflict, the start date of task T2 is moved to 20 January which is the constraint date. Scheduling conflict between tasks is shown for tasks with Start no later than and Start on specific date time constraints. If you want the task to honor the dependency and adjust the start accordingly, change the constraint type of the task to Start ASAP. When a scheduling conflict is identified, you can identify such tasks in the planning console. * The client-side planning console displays a pop-up message with an option to proceed with the conflict or cancel the action. If you proceed with the conflict, the constraint type is applied or date is changed appropriately to the next feasible date. * The calendar icon (![Calendar icon]()) on the client side planning console changes to red (![Conflict icon]()) to indicate the conflict. * The calendar icon on the server side planning console changes to red (![Conflict icon]()) to indicate the conflict. {#scheduling-conflicts__ul_znk_kqd_4lb} **Related concepts** * [Parent-child rollup task calculations](https://www.servicenow.com/docs/yicBJqzueBAurJzjgsPLAw "Date changes, stage changes, and value calculations roll up from child tasks to parent tasks.") * [Change requests and project tasks](https://www.servicenow.com/docs/bmbRe~LMrlxkAeEPPkNR3w "Large-scale changes approved by your change approval board (CAB) require new or existing projects to be implemented.") * [Project task checklists](https://www.servicenow.com/docs/fAhSJrFn7Fxx_aFoEcH2zA "A project task checklist gives you the ability to track activities that must be completed on a task.") * [Task resources](https://www.servicenow.com/docs/DDYc8Kvical0nqUKjhtoog "Resources are the individuals or groups assigned to perform tasks and subtasks in Project Management.") * [Project and project task states](https://www.servicenow.com/docs/c9RS0oEzIVbECWV6RnHzmw "In the base system, the states in project and project task inherit the states in Task table.") * [Composite Fields](https://www.servicenow.com/docs/CRJCsO1yPCKmdzCQvc_tbQ "A composite field combines information from two fields in a table to form a single field.") * [Cost plan breakdown](https://www.servicenow.com/docs/uixGFtQqBVrNm_UVdKPxSg#cost-plan-breakdown "A cost plan breakdown captures the estimated cost and actual cost for every fiscal period. Cost plan, project, demand, program, and portfolio are the breakdowns types that are available.") * [Actual project costs](https://www.servicenow.com/docs/b1~zhiExT5R8Pz_Et_P47Q "Actual project costs come after you create expense lines for cost plans or after human resources use time cards to create expense lines.") * [Types of external dependencies](https://www.servicenow.com/docs/6~Sy0tVsTxXSF1tkjHkBrw "The Project management application supports two types of external dependencies - hard and soft.") * [Project and portfolio funding](https://www.servicenow.com/docs/lemfmgoMwVN7Duy~wk3Otw "Specify the amount of money that projects and portfolios are allowed to have.") * [Project scheduling in Project Management](https://www.servicenow.com/docs/3dnQztbobmF5NVLuL1kSjg "Define how tasks are sequenced, timed, and connected to determine when a project starts and finishes with Project scheduling. Project scheduling calculates task start and finish dates based on the project start date, task dependencies, constraints, and task duration in forward scheduling mode.") **Related tasks** * [Project tasks](https://www.servicenow.com/docs/tCXf5iJm8J9lqdD4fy8nsg "Create project tasks in several ways, even from other applications in the instance.")