Righthand
← All posts

Use Google Docs for a grant attachment narrative gap

Example: A grant narrative names three activities. The approved supporting material has evidence for only two.

Keep Google Docs as the source for its records. A Righthand can use available information for the decision below.

This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.

The customer task

A grant narrative names three activities. The approved supporting material has evidence for only two.

Provider documentation. The documentation gives information about creation and modification of documents through its API. Document operations and account authorization remain distinct requirements.

Make account access explicit

If Google Docs is available in Connections, connect the intended account. Give the Righthand access to that connection.

Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.

For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.

Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.

The request to the Righthand

Read the supplied narrative and supporting material.

>

Record activity statements without supporting evidence.

>

Prepare questions for the program owner.

>

Keep existing evidence references with their claims.

>

Send the owner the result before 3 PM Friday.

>

Use Pacific time.

Use the provider records for the result

Identify the exact document before the task. Give the assistant the approved text source. Use a copy for the first edit test and compare the resulting content.

The program owner must supply impact evidence. Grant eligibility remains outside this document task.

For a permitted write, examine the resulting account record. A proposal does not establish a completed change.

For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.

An illustrative result and next step

Two activities have supplied support. The third has no supporting material in the task information.

The program owner supplies evidence or changes the narrative before submission.

Try one account task

  1. Give the Righthand one identified source record.
  2. Compare its result with that source.
  3. Examine the account record after a permitted write.
  4. Examine the work in Activity.

If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.

When the account tools are sufficient

Use Google Docs directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.

Compare plans. Get a Righthand.