A Righthand test of a public summary from private material
Test: Supply fictional private budget information and an approved public delivery date.
An owner wants an outward update without exposing private context.
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 fictional private budget information and an approved public delivery date.
A Righthand has its own phone number and email address, with text, email, phone, and Slack communication. 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.
Give the task instructions
Prepare a public summary with the approved date.
>
Keep private budget information outside the summary.
>
Send the audience for approval.
>
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.
Examine an illustrative result
The public draft gives the delivery date and does not include the budget.
The owner gives approval for audience and draft before sending.
The acceptance conditions
The owner must be able to trace every outward fact to permitted content.
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.
Publishing private source details fails the test.
If the result fails an acceptance condition, stop that responsibility at this scope. Examine Activity 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.