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.

SAMPLE DURATION150 minutes

one 150-minute private workshop, including a 10-minute break.

TOOLS FOR THIS EXAMPLE

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.

We agree on timing, tools, and deliverables with your team before booking.

Plan this workshop →

Your starting point.

Teams that already write and refine prompts and want to delegate a defined task.

Comfort prompting AI and checking a draft.
Ability to read a simple table; spreadsheet formulas and coding are not required.

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.

Skills 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.

ILLUSTRATIVE EXERCISE · NOT A CUSTOMER RESULT

Prepare an invoice status brief

Example output

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.

Review: Every invoice appears once. Only INV-101 contributes to the $240 overdue total. The note requests verification and remains a draft.

See the input and try the exercise

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.

SAMPLE AGENDA / 150 MINUTES

What you will work on.

Define the assignment

25 min

Write a task brief with permitted inputs and explicit limits.

Take home: A task brief with acceptance checks.

Practice and review details

Practice: Use the fictional invoice table below. Specify report columns, source date and the rule that drafts stay unsent.

Example: Show a brief that separates preparing a report from sending a message.

Check: The brief names the source, required output and human approver; sending is excluded.

Before this exercise: Basic AI drafting and table reading.

Produce a source-based report

40 min

Classify each record using its due date and paid status.

Take home: A report and unsent internal note.

Practice and review details

Practice: Produce the sample invoice status report as of May 15, 2026. Draft an internal note for the reviewer.

Example: Paste a table and request a report with record IDs and evidence.

Check: All three records appear once; report distinguishes paid, overdue and not yet due.

Before this exercise: Task brief from section 1.

Break10 min

Check the deliverable

40 min

Trace each status and amount to a source row.

Take home: A checked report and one documented exception.

Practice and review details

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.

Example: Demonstrate a deliberately wrong overdue label and a missing record.

Check: Amounts and dates match; the incomplete record is escalated instead of guessed.

Before this exercise: Report and source table.

Make the workflow repeatable

35 min

Document a repeat run with a named reviewer and limited access.

Take home: Reusable instructions and access checklist.

Practice and review details

Practice: Write a manual input → report → check → approval handoff. List what an assistant would need to read and actions requiring approval.

Example: Map company account ownership, source access, review and offboarding needs without connecting systems.

Check: A colleague can repeat the sample; account owner, reviewer and access-removal responsibility are explicit.

Before this exercise: Checked report and exception example.

What to bring and how we can adapt the session

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 anonymized examples or our fictional material. Keep confidential records and credentials out of your inquiry.

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.