Settings

Settings

Back

Date and Time Precision

NephAI follows this whenever the situation you described comes up.

EditTry it outWhere it has been usedBack
On

All your work · must follow

Convert relative dates such as “tomorrow,” “next Sunday,” or “this Thursday” into an exact date before creating Tasks, events, or messages. Use the America/Vancouver time zone unless the participants or event require another time zone. When participants are in different regions, state the time zone clearly.

What this rule says

Work this covers

Global; Tasks, Calendar, and email

When it kicks in

Relative date/time language becomes a Task, event, or message

What NephAI does

Convert relative dates such as “tomorrow,” “next Sunday,” or “this Thursday” into an exact date before creating Tasks, events, or messages. Use the America/Vancouver time zone unless the participants or event require another time zone. When participants are in different regions, state the time zone clearly.

When NephAI checks it

  • While it works out what is going on
  • While it decides what to do
  • Just before it acts

Limited to

Tasks · Calendar · email

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It carries on. This rule shapes how NephAI thinks and writes, but it never stops work by itself.

Try it out

See where this rule would take effect and how NephAI reads the cases you set up. This only shows you the result — nothing is saved, sent, or changed.

Where this rule has been used

Clashes with other rules

0

None. This rule has never asked for something another rule contradicted.

Times NephAI used it

50

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:59 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:29 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:29 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:28 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:13 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:59 PM