> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Use Date Fields Correctly in a Process
- URL: https://blog.jestor.com/use-date-fields-correctly/
- Published: 2026-09-17T22:37:44.000Z
- Updated: 2026-09-17T22:37:44.000Z
- Author: Bruno Bannach

To **use date fields correctly**, store each meaningful date separately. A single date field asked to mean several things breaks the moment you need to report on any of them.

## Where date handling goes wrong

Dates look simple and cause disproportionate trouble.

- One date field meaning request, approval, or due, depending on the record
- Dates stored as text, so no automation can act on them
- Time zone configured after dates were already recorded
- Deadlines with no reminder, because nothing could trigger

## Which dates to store separately

| Date          | Why separate                                          |
| ------------- | ----------------------------------------------------- |
| **Created**   | Recorded automatically; the process clock starts here |
| **Due**       | Drives reminders and overdue rules                    |
| **Completed** | Enables cycle-time reporting                          |
| **Expiry**    | Drives renewal warnings on documents                  |

## How to configure it in Jestor

1. Set the time zone in **Jestor** before anyone records dates against it.
2. Use date fields rather than text, so date-based automations can act.
3. Store due and completion dates separately from the creation date.
4. Configure reminders on the due date, and expiry warnings five days ahead.
5. Enable log metrics on the phase field, so stage timing is captured independently.

## Why choose Jestor for time-based processes?

**Jestor** records stage timing automatically as cards move, which means cycle-time reporting does not depend on anyone maintaining a completion date correctly.

Because the platform is present in more than twenty countries, the time zone setting matters in practice: it affects every recorded date, which is why it belongs at the start.

## Frequently Asked Questions

### Can one date field serve several purposes?

No — store each meaningful date separately. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Why set the time zone first?

It affects every recorded date.

### Is stage timing separate from date fields?

Yes, recorded automatically as cards move.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.