Before this level
L1 first
In practice most teams do L1 first, because L1 gives them the ground this level builds on. If your team already has it, the assessment will say so and we will start you here.
Level 2 of three · 16 hours · online, own pace
Your staff research the use case, agree what data may be used, then build and test the company's own AI colleague on one piece of real work.
L2 is level 2 of the OwnYourAI corporate AI training path. It is 16 hours of online, own-pace learning delivered as 8 online sessions, and it is the point where your company builds its own AI colleague on a real task.
L2 · 8 online sessions · part of a 48-hour path
What this level is for
Before this level
In practice most teams do L1 first, because L1 gives them the ground this level builds on. If your team already has it, the assessment will say so and we will start you here.
After this level
L3 — Run and Guard It. Most teams take a short break between levels so the first one settles into daily work.
Session by session
Every session is 2 hours of online learning at the person's own pace, with a scheduled live touchpoint inside it and a trainer present. Each one ends with something your company keeps: 16 hours in total for L2.
| # | Session | The one thing it settles | What your company keeps |
|---|---|---|---|
| 1 | Choosing the right job for an agent | Which workflow is worth automating first, and which must not be | A scored shortlist of three workflows, and the one chosen, with the reason |
| 2 | Mapping the workflow and the data | Where the information lives, who owns it, and what may not be touched | A one-page workflow map plus the data rules for this agent |
| 3 | Writing the agent's brief | What it is told to do, and the three limits it may never cross | The agent's written brief, including the three limits |
| 4 | Building it | A first working version connected to your own information | A first build that answers correctly on three real inputs from your work |
| 5 | Testing it against real work | What breaks, and how you know | A failure log built from your own documents, with the fix for each failure |
| 6 | Guarding it | Who may ask it what, what needs a human, and what gets logged | The guardrail document, plus the corrected rule from the incident drill |
| 7 | Putting it into the daily routine | Who operates it, and what working means on a Monday morning | A one-page operating routine with a named owner and a reviewer |
| 8 | The build assessment | Whether your company actually has a running agent | A live demonstration on fresh inputs, and your company agent record |
The standard every build is held to
A brief that does not name these three is sent back before any building starts. The limits are written by your own staff, in your own words, for your own workflow.
It may do alone
The documented, repeating part of the workflow: reading the same kind of document, drafting from the same template, pulling the same figures together. If a task needs judgement about a person, it is not this.
It must ask a person first
Nothing goes out of the company on its own: not a client letter, not a filing, not a payment instruction. The routine written in Session 7 names who approves, and the approval is recorded.
It never does
Four hard lines, configured as rules rather than left to memory: no sending to a client, no payment, no deletion, and never entering a client's personal data. Session 6 includes an incident drill, so the team has caught it once before it matters.
The assessment
The assessment is delivered live online with a trainer present. It is not a multiple-choice quiz, and it does not test whether someone remembers AI theory: it tests whether they can do the thing on their own desk.
| Part | What the person does | Time | Marked by |
|---|---|---|---|
| A. The agent runs | Runs the agent live on the company workflow, on inputs the assessor supplies fresh at the assessment | 20 min | Trainer |
| B. The failure log | Explains three failures from the log, what caused each one, and what changed as a result | 10 min | Trainer |
| C. The guardrails | Says what the agent may do alone, what needs a human, what it never does, and where the log is | 10 min | Trainer |
| D. The routine | Names the owner, the reviewer, and the three checks that show it is still working | 10 min | Trainer |
A. must succeed on inputs supplied fresh at the assessment: a prepared demonstration does not pass. B., C. and D. must each be answered correctly. Anyone who misses a part is assessed again on that part at no extra cost, and that re-assessment is recorded as such. The assessor is named on the record, with the date.
Per person, kept together and retrievable on its own: the identity record, attendance at each session, progress at each session with the work produced, the assessment result part by part, the artefact that was demonstrated, and the name of the assessor with the date. Everything on that list is written by a named trainer, not by the learner. What we keep, and who can read it is set out on its own page.
Written to the SSG funding requirements as published. Course funding application status: pending.
What your team can do afterwards
These are the skills that travel between companies, which is why the level is written around them. About 70% of every level is that shared skill; about 30% is your own workflows.
| What | Detail |
|---|---|
| Level | L2 of three — Build Your Company's Own AI Agent |
| Hours | 16 hours |
| Delivered as | 8 online sessions, online and own pace |
| Scheduled touchpoints | Yes — online, booked in advance inside the level |
| Working language | Plain English. No technical background needed. |
| What you keep | The work produced, the written record, and the skill in your own staff. |
A result, how it is measured, when it lands, and what happens if it does not.
L2 — questions
Previous: L1 — Get Your Company AI-Ready · Next: L3 — Run and Guard It
Next step
The assessment tells you whether L2 is the right place to start, and what it would cost for the seats you actually need.
Corporate pricing on request. Course funding application status: pending.