AI Literacy Lab

For Teams

Use the lab as practice, then connect it to local policy.

AI Literacy Lab can support office training, team discussion, and workshop facilitation. It should be paired with the organization's approved tools, data rules, escalation contacts, and role-specific obligations.

Good fit

  • Self-guided AI literacy practice.
  • Pre-work before a policy or tool rollout.
  • Team discussion about judgment, review, and escalation.
  • Workshop backbone for general office audiences.

Not a substitute for

  • Legal, privacy, security, HR, or procurement review.
  • Identity-verified credentialing or proctored assessment.
  • Approval to use a specific AI tool or data source.
  • Organization-specific compliance evidence.

Add locally

  • Approved AI tools and prohibited data types.
  • Examples of high-risk uses in your environment.
  • Escalation contacts and review thresholds.
  • How the learning record should be handled internally.
  • A short policy addendum for the audience and workflow.

Regulated-setting adoption note

In regulated or professional settings, use the lab as judgment practice only. It does not establish legal authority, clinical appropriateness, financial suitability, HR compliance, procurement approval, audit evidence, or permission to use a specific AI system.

Before assigning the lab, map each audience to approved tools, prohibited inputs, recordkeeping expectations, review owners, escalation contacts, and role-specific duties. Treat any required completion process as an internal training decision governed by local policy.

Scenario overlay prompts

The public lab uses generic and public-office scenarios. For a sector-specific rollout, keep the same judgment pattern and swap in local examples that are fictionalized, policy-aligned, and free of sensitive details.

  • Finance: customer hardship notes, adverse-action drafts, fraud triage, vendor-risk summaries, or audit finding memos.
  • Healthcare: patient-access complaints, prior-authorization correspondence, appointment access themes, clinical admin summaries, or vendor intake notes.
  • Government: public-records requests, benefits correspondence, accessibility requests, procurement notes, grant monitoring, or resident-service themes.
  • HR or operations: hiring rubrics, performance notes, accommodations, workforce surveys, payroll exceptions, or internal policy drafts.

Recommended deployment pattern

  1. Ask learners to complete the sequenced public lab.
  2. Discuss one or two modules in a team meeting or workshop.
  3. Translate the generic scenarios and Before You Act prompts into local examples.
  4. Ask learners where they revised, defended, or documented their judgment.
  5. Clarify where employees should escalate uncertainty.
  6. Treat the learning record as self-attested practice, not compliance evidence.

For workshops, use the facilitator run sheets to choose a 60-, 90-, 180-minute, or half-day format before sending the learner link.

Office AI quick check

  • Before acting on AI output: pause, broaden the context, and name what would change your mind.
  • Before pasting text: remove names, account numbers, confidential facts, and regulated data.
  • Before sending AI-assisted work: verify dates, policy links, numbers, names, and commitments.
  • If it affects pay, hiring, access, complaints, discipline, safety, or legal rights: escalate first.
  • Name the human owner for the final decision before using the output.
  • Stop when the tool, data, policy, or review owner is unclear.