Your first task: turn one document into a checkable summary

Know what you want to receive

For a meeting note, event brief or product document, “handle this for me” leaves too much unstated. Start with one small outcome: a summary whose claims you can trace back to the text. Practise specifying the deliverable, requesting evidence and recognizing gaps.

This is a documentation-based tutorial, not our test report. The task brief and exercise are original editorial material. No actual Bot run or successful output is claimed here.

Prepare the material and check the context

This lesson covers one document in a personal Bot. The official getting-started guide describes submitting a task with an attached document. For installation and account eligibility, consult the official guide. [Source 1]

Choose a short document you are entitled to provide. Remove personal contact details, customer data and internal access links. Your own public introduction is a reasonable first material. This exercise needs no connected email or team drive; a request for those permissions is a reason to check the scope.

Shared Bots have different account and collaboration rules. This lesson does not cover shared setup; read the official shared-Bot guide before adapting it for a team. [Source 3]

1. Give a complete task brief

Attach the material in your personal Bot chat and adapt the task brief below. Four main points are an exercise choice, not a product limit.

Check whether the Bot can identify the input, the expected output and the stopping point. For a long document, start with one chapter. If paragraphs have no numbers, ask for a heading or a short source phrase. Do not ask it to invent references.

2. Review permissions before continuing

“Do not change files” is a task instruction; it does not replace actual approval controls. Official guidance recommends explicit boundaries. When an approval card appears, review its target, scope and effect before deciding. [Source 2]

This exercise only needs a summary in the chat. If it proposes email, a public link, shared access changes or edits to the source, stop and narrow the request. Avoid expanding lasting permissions for a single summary.

3. Check individual claims against the text

Pick one date, one conclusion and one unresolved question. Locate the supporting passages. Pay attention to negation, qualifications and “to be confirmed,” rather than just polished prose.

For example, if your practice text says “The proposal is still under discussion; the submission date will follow,” the summary should not call it approved or invent a date. That sentence is our fictional exercise material, not a real case or Bot output.

4. Correct problems and finish deliberately

When a claim has no clear support, ask for its exact supporting passage. If none exists, move the claim to unresolved questions. If an attachment cannot be read, check that it opens and is accepted by the current client, then try shorter non-sensitive material. Repeated permission grants are not a fix for a file-reading failure.

Decide yourself whether to save the summary. Handle unneeded uploads through the client you actually use. We have not verified server-side retention after deletion and do not promise that deleting an item immediately removes every copy.

Practise again

Repeat the brief with another document and compare what you still need to correct. Stabilize your instructions and checking method before team use or connected apps. This lesson requires no routine, skill or automated publishing setup.

Read only the one document I attached; do not search other sources.
Return four sections: up to four main points; dates and confirmed decisions; unresolved questions; and the paragraph or heading supporting each conclusion.
Separate source facts from your inferences. Write “not stated in the document” when evidence is missing.
Keep the result in this chat. Do not change the source, send messages or create a sharing link. If another account, permission or paid action is needed, explain why and stop first.