Astra Via

Academy / Level 2

Level 2 of 3

AI Practitioner.

One day for people who already use AI every week. Participants decide which work to hand over, give AI the team's context once, save the procedures they repeat, and set up work that runs on its own.

Book AI PractitionerAll levels
Duration
7 hours, one day
Group size
Up to 10 per group
For
People who use AI every week
Before joining
AI Essentials, or regular use
Tools
Copilot, ChatGPT, Claude or Gemini, in the client's tenant
Method
Build on own tasks, test, share
Colleagues working on laptops in an open office
Hand over the repeat. Keep the judgment.

Taught by capability, so the skill carries across tools and survives the next product update.

Three rules for handing work to AI.

Hand over the repeat, keep the judgment.Volume and rules go to AI. Decisions, relationships and taste stay with people.
Test on known answers first.A new procedure runs on cases the team has already solved before it runs on new ones.
A person approves what leaves.Nothing goes to a client, a supplier or a system without a named person checking it.

The day, module by module.

Taught by capability, so the skill carries across tools and survives the next product update. Every exercise uses the team's own tasks and files.

  1. 1
    9:00 to 10:30

    Decide what to hand over

    Pick the tasks worth handing to AI, and the ones that stay with people.

    What it covers

    • What changed since Essentials: new features, and which model for which task
    • Mapping a week: repeat work, judgment work, risky work
    • The hand-over test: volume, clear rules, an output someone can check
    • Testing AI on work whose answer is already known

    Practice, on their own cases

    Each participant maps one real week and tests AI on a task they have already done.

    They leave with

    A shortlist of three tasks to hand over, and what stays human.

  2. 2
    10:45 to 12:15

    Give AI the context once

    A workspace that answers like a colleague who knows the team's files.

    What it covers

    • What goes in: templates, past examples, standards, glossary
    • Instructions that set the role, tone, rules and what to refuse
    • Long documents: contracts, specifications, reports and policies
    • Who owns the workspace, keeps it current, and can see it

    Practice, on their own cases

    Build the team workspace from real templates and five past examples.

    They leave with

    One team workspace, tested on three real requests.

  3. 3
    13:30 to 15:30

    Save procedures, get finished files

    A recurring task written once, delivered as a finished file every time.

    What it covers

    • Writing a task as steps, inputs, checks and output
    • Saving it as a skill, custom GPT, agent or Gem
    • Spreadsheets in and out, charts, slides and formatted documents
    • Checking every number against its source

    Practice, on their own cases

    Turn one recurring report or proposal into a saved procedure that produces the finished file.

    They leave with

    One saved procedure per person, run once by a colleague.

  4. 4
    15:45 to 17:15

    Let work run on its own

    Repeat work scheduled, connected to email, calendar and shared drives.

    What it covers

    • Agents that act on the team's behalf: what they do well today, and where they stop
    • Scheduled tasks: what to automate first
    • Connectors and the permissions they need
    • When to stop and hand over to IT

    Practice, on their own cases

    Schedule one task on real inputs, such as a Monday briefing built from last week's emails.

    They leave with

    One scheduled task running, with an owner and a check.

Around the sessions.

  1. Before

    One interview per team to list the tasks worth handing over, and a check with IT on tools and connectors.

  2. After

    Weekly usage reports for four weeks. Saved procedures go into a shared team library.

  3. Adaptation

    Tool names change with the client. The four capabilities and the rules stay the same.

Safe use at this level.

  • What a shared workspace exposes, and to whom
  • Permissions on connectors to email, calendar and drives
  • A person in the loop before anything leaves the company

Safe use across the Academy

Next

AI Builder: build internal tools safely

AI Builder

Start with one team.

A short call to understand the team and its tools, then a proposed level, format and date.

Book a call