# A functional test of a Righthand accepted source versus newer draft

Test: Supply approved revision two and proposed revision three. Clearly identify revision two as accepted.

By Righthand Team · 2026-10-24

Source: https://www.righthand.ai/blog/test-a-righthand-accepted-source-versus-newer-draft

A production owner wants approved instructions used even when a newer unapproved draft exists.

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 approved revision two and proposed revision three. Clearly identify revision two as accepted.

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

> Compare the supplied versions.
>
> Use revision two for accepted instructions.
>
> Send revision three as a proposal.
>
> 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

> Revision two is the accepted work source. Revision three remains unapproved.

The owner gives a decision about whether to accept revision three.

## The acceptance conditions

The result must keep authority independently from version order.

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 the newest draft as approved merely because it is newer 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).