Dependent and Proceeding Tasks

Nekst lets you base a task's due date on the Start Date, the End Date, or another task. Chaining tasks this way keeps a whole sequence of deadlines accurate even when one date moves.

• A task set to occur a number of days before another task is a Proceeding Task.
• A task set to occur a number of days after another task is a Dependent Task.

The task they're built around is the Parent Task.

Proceeding Tasks

Open any task and click Proceeding/Dependent Task at the bottom to add one before it.

Choose the type of proceeding task to create.

On an active transaction, a proceeding task gets a calendar due date right away and sorts into your to-do list. It shows "approx." before the date because it moves with the Parent Task if the parent's date changes.

In a workflow, a proceeding task nests under its Parent Task so the relationship is clear.

Dependent Tasks

Dependent tasks come due a number of days after another task. You can build a stair-step sequence from any mix of Standard, Email, and SMS tasks — and unlike proceeding tasks, a dependent task can be built off another dependent task.

Example, built around the inspection contingency:

• Standard Task: Inspection Due Date (due 10 days after Start Date) — the Parent Task
• Dependent Task: Sellers Response to Inspection Due (due 3 days after Inspection Due Date)
• Dependent's Dependent Task: Buyers Response to Inspections Due (due 3 days after Sellers Response to Inspections Due)

A dependent task has no formalized due date until the task it's linked to (dependent upon) is marked complete.

Hiding or showing dependent tasks

You can choose whether you want dependent tasks minimized under their parent, or have them expanded by default. It depends on how "clean" a task list you want to see.

Set your preference on the Settings / Preferences page.

Updated on: 06/11/2026