# A functional test of a Righthand local deadline for a dated task

Test: Supply a dated London deadline and give instructions for Pacific reporting. Include a second deadline without a zone.

By Righthand Team · 2026-10-24

Source: https://www.righthand.ai/blog/test-a-righthand-local-deadline-for-a-dated-task

An owner wants a deadline converted only with a complete date and time-zone basis.

This article is from Righthand. The test inputs and example result are illustrative. No test in this article has an executed result.

## Prepare the test case

Supply a dated London deadline and give instructions for Pacific reporting. Include a second deadline without a zone.

A Righthand has its own phone number and email address, with text, email, phone, and Slack communication. [Introduction](https://docs.righthand.ai/introduction).

The initial test uses supplied information and the Righthand's own email. For direct account work, a separate available connection operation is necessary. [Connections](https://docs.righthand.ai/guides/adding-your-first-connection).

## Give the task instructions

> Send both local times for the complete deadline.
>
> Keep the second zone as an unanswered question.
>
> Keep its time basis as an unanswered question.
>
> Send the owner the result in this conversation.
>
> Use Pacific time for the supplied deadline.

Identify any permitted outward action explicitly. With **Ask**, the instruction or approval must identify its recipient and task. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## Examine an illustrative result

> The complete deadline has two named local times. The other deadline still has no zone.

The owner supplies the missing zone before scheduling a reminder.

## The acceptance conditions

The result must keep the actual date and missing zone condition.

Compare the result with the original case information. Examine the teammate's received message when contact is part of the task. A send record and recipient-visible receipt are different observations.

Using one assumed offset for every deadline fails the test.

If the result fails an acceptance condition, stop that responsibility at this scope. Examine [Activity](https://docs.righthand.ai/guides/working-with-your-righthand) for questions, account problems, or the actual communication.

Give the missing source or owner decision before another attempt. If sending has an uncertain result, establish what occurred before repeating it.

## Keep a small test record

Record the task instructions, source information, received result, and owner decision. Record the configured communication policy and applicable connection permissions.

## Select the next task

A direct record, existing app function, or human teammate can be sufficient when no continuing conversation or coordination is necessary. A Righthand is an alternative when the owner wants responsibility for the next steps and decision handoff.

[Compare plans](https://www.righthand.ai/pricing). [Get a Righthand](https://teams.righthand.ai).