A POSSIBLE SESSION FOR YOUR TEAM
Sample course outline — adapted after a planning conversation.
AI as an Assistant
Assign a bounded reporting task, check the result against its source and prepare a clear handoff. Map the access and approval rules a repeatable assistant workflow would need.
Proposed: one 150-minute private workshop, including a 10-minute break.
Proposed: a laptop and a team-approved text AI tool. Tool and access requirements agreed during planning; practice uses pasted fictional text. No connector or file-upload feature is required for this sample.
This example is a starting point. Scope, timing, tools and deliverables are agreed together before a session.
WHO IT SERVES
Is this your next step?
Teams that already write and refine prompts and want to delegate a defined task.
Before the session
- Comfort prompting AI and checking a draft.
- Ability to read a simple table; spreadsheet formulas and coding are not required.
PRACTICE & TAKEAWAYS
Work you can try.
What you will practice
- Specify inputs, output format and acceptance checks for a reporting task.
- Check an AI-generated report against every supplied record.
- Define a manual handoff and an access boundary for a repeat run.
What you can leave with
- A checked sample status report and internal follow-up draft.
- A reusable task instruction and source-check table.
- An access and approval checklist for the proposed workflow.
PROPOSED AGENDA / 150 MINUTES
From first example to review.
Open each section for the exercise, output and review check. All practice uses fictional or anonymized material.
01Define the assignment25 min
Purpose. Make completion measurable.
Learning outcome. Write a task brief with permitted inputs and explicit limits.
Explain or demonstrate. Show a brief that separates preparing a report from sending a message.
Hands-on practice. Use the fictional invoice table below. Specify report columns, source date and the rule that drafts stay unsent.
Your output. A task brief with acceptance checks.
Review check. The brief names the source, required output and human approver; sending is excluded.
Prerequisites. Basic AI drafting and table reading.
Proposed time: 25 minutes, including the explanation, practice and review.
02Produce a source-based report40 min
Purpose. Practice a complete, bounded deliverable.
Learning outcome. Classify each record using its due date and paid status.
Explain or demonstrate. Paste a table and request a report with record IDs and evidence.
Hands-on practice. Produce the sample invoice status report as of May 15, 2026. Draft an internal note for the reviewer.
Your output. A report and unsent internal note.
Review check. All three records appear once; report distinguishes paid, overdue and not yet due.
Prerequisites. Task brief from section 1.
Proposed time: 40 minutes, including the explanation, practice and review.
03Break10 min
Purpose. Pause before checking the result.
Learning outcome. Return ready to check the source.
Explain or demonstrate. No demonstration during the break.
Hands-on practice. Step away from the screen.
Your output. No course artifact.
Review check. Resume with the report and source available.
Prerequisites. Work saved.
Proposed time: 10 minutes, including the explanation, practice and review.
04Check the deliverable40 min
Purpose. Catch plausible mistakes before handoff.
Learning outcome. Trace each status and amount to a source row.
Explain or demonstrate. Demonstrate a deliberately wrong overdue label and a missing record.
Hands-on practice. Check each report row manually. Then remove a paid-status field from a copy of the sample and see whether the workflow flags the uncertainty.
Your output. A checked report and one documented exception.
Review check. Amounts and dates match; the incomplete record is escalated instead of guessed.
Prerequisites. Report and source table.
Proposed time: 40 minutes, including the explanation, practice and review.
05Make the workflow repeatable35 min
Purpose. Set rules for inputs, access and review.
Learning outcome. Document a repeat run with a named reviewer and limited access.
Explain or demonstrate. Map company account ownership, source access, review and offboarding needs without connecting systems.
Hands-on practice. Write a manual input → report → check → approval handoff. List what an assistant would need to read and actions requiring approval.
Your output. Reusable instructions and access checklist.
Review check. A colleague can repeat the sample; account owner, reviewer and access-removal responsibility are explicit.
Prerequisites. Checked report and exception example.
Proposed time: 35 minutes, including the explanation, practice and review.
TRY A REPRESENTATIVE EXERCISE
Prepare an invoice status brief
Fictional practice material
Fictional records, as of May 15, 2026: INV-101, Pine Studio, $240, due May 10, unpaid. INV-102, West Shop, $180, due May 20, unpaid. INV-103, North Works, $300, due May 5, paid. No partial payments in this sample.
Example prompt
As of May 15, 2026, classify every record as paid, overdue or not yet due. Overdue means unpaid with a due date before May 15. Include invoice ID, amount and reason. Records: INV-101 Pine Studio $240 due May 10 unpaid; INV-102 West Shop $180 due May 20 unpaid; INV-103 North Works $300 due May 5 paid. Give the total overdue amount and draft a short internal review note. Do not send anything or assume other records.
Illustrative expected output
One acceptable example, not a guaranteed AI response.
INV-101: overdue, $240; unpaid and due May 10. INV-102: not yet due, $180; unpaid and due May 20. INV-103: paid, $300; paid status takes precedence. Total overdue: $240. Internal draft: Please verify INV-101 against the latest payment record before approving any customer follow-up.
Check the result. Every invoice appears once. Only INV-101 contributes to the $240 overdue total. The note requests verification and remains a draft.
BEFORE WE MEET
What your team provides.
- Select one report or document task and its acceptance criteria.
- Identify the source owner, reviewer and company account owner.
- Confirm data rules and tool access; connector demonstrations would require separate access checks.
Use approved, anonymized examples or fictional material. Do not share confidential records or credentials in a planning inquiry.
ADAPT IT TO YOUR WORK
Choose a useful focus.
- Use a project-status table or inventory summary instead of invoices.
- Prepare presentation notes from the checked report when document skills matter more.
- Demonstrate approved file handling only after available features and permissions are confirmed.
We confirm the audience, business task, time and tool access during planning.