When a task is dependent on a different task, you can set a task dependency.
Deciding When Tasks Are Due
There are many ways you might define when tasks are due, including:
- Tasks that all depend on the opening date: "14 days before opening, do this" or the project kickoff date: "week 1, do these tasks."
- Groups of similar tasks that depend on milestones: "after lease signing, construction tasks begin."
- Tasks that depend on other individual tasks: "after truck and vinyl wrap arrive, upfit truck."
- A combination of different types
When in doubt, we recommend that you start with the simplest option and upgrade your checklists as you identify the need for more complex solutions.
Compare the Use Cases of Each Method of Dependency
| Tasks that depend on opening date | Best for well-defined checklists that usually run on a repeatable timeline. |
| Tasks that depend on other tasks | Best for complex processes, where one task kicks another by a different owner. |
| Groups of tasks that depend on milestones | Best for moving whole phases back or up based on prerequisites. |
Example
We cannot upfit a truck until we have one, so the "Install Up-fic Kit in Truck" task is dependent on the purchase and arrival of the truck.
You can now set the task schedule based off the dependency. By default, FranConnect sends an email on the start date and the end date of each task (shown in orange).
Note: for information on scheduling additional email reminders, please see Sending Email Reminders to Task Contacts