Overview
Dependencies and durations work together to automate project scheduling in GUIDEcx 2.0.
By configuring task dependencies, you can control when project team members — both internal and external — receive task assignment notifications. Durations determine how long a task should take and help GUIDEcx calculate due dates and forecast project completion.
When dependencies and durations are used together:
Tasks automatically shift if earlier tasks are completed late or ahead of schedule
Assigned durations remain intact
Project timelines stay aligned
Forecasted End Dates become more accurate
This helps teams maintain realistic timelines while improving customer visibility and confidence in the onboarding process.
Permissions: Who can do what with dependencies?
Admin and Managers can create, edit, and remove dependencies on templates and projects.
Guides can create, edit, and remove dependencies on projects they are invited to.
Task Owners can create, edit, and remove dependencies for regular tasks within existing milestones.
Understanding Dependencies
Dependencies determine when a task can begin based on the completion of another task.
For example:
Task B cannot start until Task A is completed
Once Task A is marked complete, Task B becomes available and assignment notifications are triggered
Dependencies help ensure work happens in the correct order and prevents tasks from being started too early.
How to Set Up Dependencies on the Template Level
The benefit to adding dependencies on the template level is that it will save that flow for all new projects that use that template.
1. Determine Which Tasks Need Dependencies
Review your templates and identify:
Tasks that must happen sequentially
Approval steps
Handoffs between teams
Customer actions that block future work
2. Add Dependencies
Click on the + Add button and select another unit for that task to be dependent on!
3. Review Dependency Logic
After building your project plan:
Verify task order
Confirm there are no unnecessary blockers
Ensure assignment timing aligns with your onboarding process
How to Set Up Dependencies on the Project Level
Sometimes dependencies change and you need to add them in-flight!
Click on the 3 dot menu on a task
Select
+ Blocked BySelect the object you want that task to be dependent on
Did You Know? You can make subtasks, tasks, milestones, and even inter-phase dependencies! PS Milestones and Phases cannot have dependencies, however the tasks within them will keep the object aligned with changing dates.
How to Remove Dependencies on the Project Level
Sometimes dependencies change and you need to adjust them mid-flight! Here's how to do that:
Click on the Task's dependency icon
Click the "
Remove Dependency Connection" buttonConfirm the action
Watch as the dependency is removed.
Permissions: Who can create, update, and delete dependencies on the project level?
Admin and Managers can create, update, and delete dependencies on any project even if they aren't on the project team.
Guides and Task Owners can create, update, and delete dependencies on projects that they are invited to.
Contributors cannot create, update, or delete dependencies on projects they are invited to.
Customers and Third-parties cannot create, update, or delete dependencies on projects they are invited to.
Understanding Durations
A task duration is the number of days a task should take to complete. In Legacy weekends are NOT counted, but in 2.0 all calendar days are counted.
GUIDEcx uses durations to calculate task due dates based on:
The task start date
The completion date of the dependent task
The overall project schedule
How Due Dates Are Calculated
Tasks Without Dependencies
If a task has no dependency:
The task start date is based on the project start date (you can always manually edit this)
The due date is calculated using the task duration
Tasks With Dependencies
If a task has a dependency:
The task start date is based on the due date or completion date of the dependent task (whichever comes first)
GUIDEcx then applies the duration to calculate the due date
Duration Availability
Durations are configured at the template level.
At the project level:
Duration is reflected through the task’s calculated start and due dates
Completed tasks use the done date instead of the due date
Forecasted End Dates
A Forecasted End Date is automatically calculated using:
Task durations
Dependencies
Due dates
Task completion progress
This forecast helps predict when a project is expected to finish.
Why Forecasted End Dates Matter
Forecasted End Dates help:
Set customer expectations
Improve project transparency
Increase customer confidence and trust
Identify timeline risks earlier
Where Forecasted End Dates Appear
Forecasted End Dates are visible in:
Project Overview
Plan View
Weekly Project Overview Emails
Best Practices
Use Template Analysis Reports
Review Template Analysis reports regularly to identify:
Tasks consistently completed early
Tasks frequently overdue
Duration estimates that may need adjustment
Example:
If a task is often completed several days late, consider increasing the duration in the template.
Remember That Weekends Are Excluded
Task durations only count weekdays.
Example:
A 1-day task starting on Friday will be due on Monday, not Saturday.
Test Your Templates
After configuring durations and dependencies:
Create a test project from the template
Review the generated dates
Confirm dependencies behave as expected
Testing helps identify scheduling issues before templates are used in live projects.
FAQs
Can I set a task due date to a weekend?
No. Regular task due dates cannot be scheduled on weekends.
However, Event Tasks can be scheduled to occur on weekends.
Can a task depend on more than one task?
Yes. This can be accomplished using task groups.
Does GUIDEcx support backward dependencies?
Not currently, but this functionality is on the product roadmap.
Can I see a task dependency without opening the task?
Yes.
You can:
Hover over the dependency icon on the task card to view dependency details
View dependencies directly from the Tasks tab in the left panel
What happens if a task is marked “Not Applicable”?
When a task is marked as Not Applicable:
Its dependency is removed
If the task is later moved back to Not Started:
The dependency must be manually re-added again