Functional AI · 1.5 days · reviewed outline

Operations

Route the work and keep approval visible. Turn a sample request into an inspectable route, exception and approval workflow.

For
Operations managers, process owners and procurement operations
Duration
1.5 days
Selected output
Sample request-to-approval flow and SOP
Commercial state
Register interest · dates unreleased

Representative work

A bounded artifact, with the checks still visible.

Illustrative workshop artifact

What a participant might build

  1. Request triage and extractionSource, method and a human verification step remain attached.
  2. SOP draftingSource, method and a human verification step remain attached.
  3. Approvals and exceptionsSource, method and a human verification step remain attached.

Who this is—and is not—for

Designed for: Operations managers, process owners and procurement operations.

Not designed for: Teams expecting live system integration or approval bypass.

Starting requirement: Approved assistant and fictional sample requests.

What participants leave with

Sample request-to-approval flow and SOP. The work remains accompanied by the method, evidence and limitations needed for someone else to review it.

Representative curriculum

  • Request triage and extraction
  • SOP drafting
  • Approvals and exceptions
Workshop boundary. The workspace is a disclosed sandbox; no company system is updated.

Standard 1.5 days agenda

WhenWhat happens
Before eventDevice, account, network, permissions and safe-data preflight
Day 1 · 09:30–12:30Orientation, working examples, workflow choices, safety and capstone selection; includes a short break
12:30–13:30Lunch
13:30–14:45Guided build
14:45–15:00Break
15:00–16:45Individual or team application with a fallback starter
16:45–17:30Verify, document limits and prepare the presentation
Day 2 · 09:00–12:30Showcase, feedback, recognition and next commitments

Tools and preparation

The final toolchain is approved before delivery. Participants need a laptop, working accounts, permitted browser and network access, and either safe data or the supplied synthetic fallback. Product names are not guessed before the buyer and faculty approve them.

Showcase and assessment

For the standard 1.5-day format, each presenting unit receives ten minutes plus two minutes for feedback and changeover. Assessment covers usefulness, correctness and evidence, repeatability, safe handling and explanation. A critical factual or data error requires rework.

Price and dates

No exact rate or delivery window has been approved. This outline therefore shows Register interest and Dates not released. A preference is reviewed by staff against the complete external calendar; it never reserves a slot.

Possible alternative: Native may fit when the audience or intended output differs.