> For the complete documentation index, see [llms.txt](https://docs.introist.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.introist.com/knowledge-base/learn/deep-dive/understanding-target-dates-in-workflows.md).

# Understanding Target Dates in Workflows

The target date is a crucial element of every workflow, guiding the timing of automated steps. Here’s what you need to know about target dates:

### What is a Target Date?

Each workflow includes a target date, which can be either "*when enrolled*" (the date when the workflow starts for an employee) or an employee-related date (an [Employee Field](/knowledge-base/build/employees/employee-fields.md), such as *start date* or *termination date*).

### Importance of the Target Date?

The target date is essential because it dictates when automation steps are executed. When configuring a workflow, you always set actions relative to the target date. For instance, you might schedule an email to be sent three weeks before the start date. This ensures that all automated tasks are perfectly timed.

### How Target Dates Work

When Introist launches an automation for an employee, it checks the workflow’s target date configuration and assigns the appropriate date to the employee's Automation. This seamless integration ensures that all actions within the workflow are executed as planned for each employee.

Understanding and correctly setting the target date is vital for the smooth operation of your workflows. By aligning automation steps with the target date, you can ensure timely and efficient task execution.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.introist.com/knowledge-base/learn/deep-dive/understanding-target-dates-in-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.