How to Use Date Fields Correctly in a Process

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

Set the time zone in Jestor before anyone records dates against it.
Use date fields rather than text, so date-based automations can act.
Store due and completion dates separately from the creation date.
Configure reminders on the due date, and expiry warnings five days ahead.
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.

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 and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,