Due Dates: Before or After the Start Date, End Date or Another Task's Completion
- Dependent Tasks vs a Primary Task due AFTER another Task
A task can be due before or after the Start Date or End Date, or after another task is completed.
Some steps in a transaction can't be dated ahead of time. You don't schedule the appraisal until inspections are resolved, and if inspections drag on, that task shouldn't be sitting on your calendar with a guessed date. With the After… option, the task waits with no due date until the other task is marked complete. That completion triggers the due date, the number of days later that you chose.
Dependent Task or due after another task: which should I use?
Both wait on another task, so here's the simple way to choose.
Make it a Dependent Task when it truly belongs to its Primary Task. Dependent and Preceding Tasks are part of the Primary Task's family. They sit in the same group, show an estimated "approx." date from day one, and if the Primary Task is deleted, they go with it.
Make it due after another task when either of these is true:
- You want it in a different group than the task it waits on. For example, "Schedule Appraisal" belongs in your Financing group even though it waits on "Inspections are resolved" in your Inspections group. See How to Use Task Groups.
- You want to keep it even if the other task is deleted. If that task is deleted, or isn't applied (because inspections are waived) when the workflow is launched, your task stays on the transaction. You'll find it in the No Due Date list, ready for you to give it a date.
What else to know
- It has no due date until the other task is completed, and it sits with your No Due Date tasks until then.
- It can be completed at any time. Waiting only decides when the task is due, never whether you can complete it.
- It can have its own Dependent and Preceding Tasks, just like any other task.
- You can change its due date whenever you like, right from the task's form. No drag and drop needed.
Set it up in a workflow
- Open the workflow and create a new task, or open an existing one.
- Next to Due, enter the number of days. 0 means the same day the other task is completed.
- Open the Days dropdown and pick After…, below Before Start Date, After Start Date, Before End Date and After End Date.
- A Task field appears. Start typing the name of the task it should wait for (for example "inspec") and pick it from the list.
- Tick Business Days to count business days only, or use If weekend, shift to to move a weekend due date to the Friday before or the Monday after. (When Business Days is ticked, the weekend shift doesn't apply.)
- Click Save task.


The list won't let you choose a task that would create a loop, like a task waiting on itself directly or through a chain of other tasks.
In the workflow, the task shows 1 day after Inspections are resolved (or whatever you set) in place of a date, and it sorts to the bottom of its group with the other tasks that have no due date.

For everything else in the task form, see Standard Task Box Overview.
Change it anytime
Open the task and use the Days dropdown:
- Pick Before Start Date, After Start Date, Before End Date or After End Date to give it a regular due date, using the number of days next to Due.
- Clear the dropdown with the × to leave the task with no due date at all.
- Pick After… again and choose a different task to wait for a different one.
There's nothing to drag, and nothing else in the workflow moves when you change it.
What you'll see on a transaction
- While it's waiting: the task is on the No Due Date tab of your Tasks page, and where the date would normally be it reads something like 1 day after Inspections are resolved. Long task names are cut short with "…", and you can hover to see the full name.
- When the task it's waiting for is completed: the label flips to the real due date and the task moves out of No Due Date. That flip is your sign the clock has started.
- If that task is reopened: the date goes away and the task waits again.
- If you change that task's completion date: the due date moves to match.
- If that task is deleted: your task stays on the transaction in the No Due Date list until you give it a date.
The reopen and completion date changes only happen if nobody has changed the task's due date by hand in the meantime.

On the Nekst mobile app, waiting tasks show under No Due Date with the same "# days after" label.
Give a waiting task a date by hand
Plans change. To date a waiting task yourself, click its # days after… label to open the date picker. You'll see a note that setting a date stops the task waiting. Pick a date, and it becomes a regular dated task.
You can also do this from the task's edit form by switching the due date from After… to a date. Setting a date through Nexi works the same way.
Launching and copying workflows
- Launch with both tasks: the task waits on the transaction's copy of the task it's waiting for, with the same day count and settings.
- Other task not applied at launch: your task is still added and waits in the No Due Date list. Nekst doesn't add the other task back for it.
- Copy or share a workflow: the setting comes along as long as the task it waits for is copied too. Copy the waiting task into another workflow on its own and it arrives with no due date rule, so give it one there.
Updated on: 11/18/2026
Thank you!
