The Clarifier Workshop

Your district adopted the tools. The Clarifier is where your team learns what those tools actually require, what your documentation actually proves, and what to do about the gaps.

The earliest Clarifier Workshop can be scheduled for May 25, 2026. Cohorts are scheduled on a first-come, first-served basis until capacity is reached.

Explore the Workshop
Explore the Workshop

The Clarifier Workshop

Learn More
Learn More

Clarity and trust in your AI governance strategy begin here.

    • Superintendents, assistant superintendents, deputy superintendents

    • Principals and assistant principals

    • Curriculum leads

    • Building-level IT leads

    • Data privacy officers

    • Educators identified by district leadership as having practical use for the methodology

    • ESA, BOCES, and consortium leads booking on behalf of member districts

    • A list of your AI and edtech tools (any format; vendor name and tool name)

    • Your DPAs, accessible during sessions

    • That is it

    No orientation packets. No pre-collected questionnaires. No structured submissions. The Clarifier meets your team where you are, not where a pre-work checklist assumes you should be.

  • The Clarifier Reference Guide, sent before Session 1

    • The TLF Integrity Cycle overview

    • The Forensic Read methodology with a worked example

    • EWA Lexicon terms covered in your sessions

    • The Educator Pedagogy Protocol template

    • Structural overview of the Upstream Vendor Risk Evaluation Protocol

      • Referenced throughout the engagement, kept for in-house use afterward

      • Yours to keep, adapt, and revise to fit how your team actually works

    • A facilitated three-session engagement where district leadership teams learn to read vendor language forensically, evaluate AI and edtech tools against actual pedagogical needs, and identify the governance gaps in their current documentation.

    • The Clarifier teaches your team to see what your vendors are telling you, what your documentation actually proves, and where the distance between the two creates exposure.

    • Each session applies TLF methodology to your district's own tools, documents, and context.

    • Five months of office hours & a 30—day free trial of the Watchlist Subscription tier of your choice are included for ongoing support as your team puts the methodology into practice.

    • The ability to read your vendor agreements and know what they actually commit to, where responsibility stops, and what the language leaves out

    • A reference guide for repeating the methodology in-house on every future vendor document, tool evaluation, and DPA review

    • A structured protocol for asking your teachers what their students need from a tool before your district approves it

    • Five months of office hours for facilitated support as your team puts the methodology into practice

    • A 30-day complimentary Watchlist monitoring trial on up to 10 of your district's tools

    • Your district is adopting AI tools faster than anyone is documenting them

    • Some tools are on file, some are missing key paperwork, and some are being used with no formal record at all

    • Your vendors are writing contracts in language your team may not fully parse

    • Nobody has systematically asked your teachers what their students actually need from these tools, especially the students edtech routinely overlooks

    • The Clarifier closes that gap so your leadership team can govern its own tool environment with confidence

  • The Clarifier runs three sessions, one per week, 90 minutes each, delivered virtually.

    Virtual delivery removes travel costs, accommodates districts across time zones, and keeps the engagement accessible to consortium bookings where participating districts are not geographically close. Sessions run on a secure video platform.

    1. Submit your enrollment form. It takes a few minutes, collects your district and organization info and intended participants, and starts the conversation. No payment, no commitment.

    2. Schedule your fit call. Within 24 hours, The Language Firm schedules a 15-minute call to confirm participant count, tool inventory scope, and scheduling needs.

    3. Review and sign your Statement of Work. Within three business days of the fit call, the Statement of Work goes to your designated signatory. It details the schedule, roster, deliverables, and total fee. Sign and return when ready.

    4. Receive your invoice and arrange payment. Net-30 terms. Purchase orders accepted.

    5. Receive your Clarifier Reference Guide and session preparation instructions. Your team's only preparation: bring a list of your AI and edtech tools (any format, vendor name and tool name) and have your DPAs accessible during sessions.

  • Timeline & Billing

    • Three live 90-minute sessions, one per week, exclusively for your cohort

    • Five months of scheduled office hours following the final session

    • 30-day complimentary Watchlist Signal trial on up to 10 of your district's tools

    • $2,500 per cohort

    • Session times and office hour windows are customizable in the Statement of Work

    • ESA, BOCES, and consortium bookings welcome

Have more questions?

Ask Before You Enroll
Ask Before You Enroll

Inside the Workshop

  • 1) Ground the Framework

    We open with the TLF Integrity Cycle: Document, Assess, Build, Maintain, Inform. This is the operating logic behind everything TLF produces, and the lens your team will use for the rest of the engagement.

  • 2) Surface Your Tool Landscape

    Your team works through three categories in real time: tools on file with current documentation, tools believed to be on file but missing key paperwork, and tools in active use with no formal record. You bring what you have. The gaps are the point.

  • 3) Learn the Language Vendors Speak

    We walk through the EWA Lexicon terms that show up in the contracts your district signs: upstream vendor risk, foundation model dependency, definition drift, supply chain visibility. Your vendors are already using this language in their DPAs and terms of service. Your team needs to recognize it before the next signature.

  • 4) Unpack the Forensic Read

    We walk through a real example of how vendor language distributes, obscures, and shifts responsibility across documents. The Forensic Read is TLF's applied methodology for reading DPAs, terms of service, and vendor disclosures as evidence. Your team watches the four stages (Read, Trace, Surface, Build) applied to an anonymized case before applying the method themselves.

  • 5) Read Your Own Documentation

    Your team picks a DPA or vendor agreement from your own files and reads it forensically, live, with TLF facilitating. Where does the vendor's responsibility stop? Does the notification clause cover upstream incidents? Does the agreement name the foundation model? This is the session that changes how your team reads every agreement that comes next.

  • 6) Connect Gaps to Governance Infrastructure

    The gaps your team surfaced in the DPA are the same gaps the Upstream Vendor Risk Evaluation Protocol is designed to document. We show how the protocol maps to what you found, so your team understands what a complete vendor evaluation looks like and where their current documentation falls short.

  • 7) Engage the Educators Perspectives

    We introduce the Educator Pedagogy Protocol: the structured method for capturing what your teachers' students actually need from a tool based on the observation and teaching actions of educators in the organization, including English learners, students with IEPs and 504 plans, and twice-exceptional learners. A tool evaluation that only examines features and data privacy misses the students with the most legal protection.

  • 8) Test a Tool Against Pedagogical Reality

    Your team applies the Educator Pedagogy Protocol to one or two tools from your own inventory. Does the tool's assumed pedagogical approach match what your teachers do in the classroom? Does it accommodate differentiation, multilingual learners, and accessibility needs? What does the vendor claim about evidence, and does the claim survive scrutiny?

  • 9) Bring Everthing Together

    Three sessions. Your team now has a picture of its tool landscape, knows how to read vendor documentation forensically, and understands how to evaluate whether the tools serve the students and teachers they are supposed to serve.

  • 10) Choose Your Next Step

    Govern independently with five included months of office hours: bring your documents, your protocols, your questions. The Clarifier Reference Guide and the Educator Pedagogy Protocol template are yours to run in-house. If you want ongoing weekly monitoring on the tools you just reviewed, activate your complimentary 30-day Watchlist Signal trial and see what it looks like when someone is watching your vendors for you every week.

Begin Enrollment

The Education Workflow Automation Lexicon. Operational language for K-12 education in a shifting accountability climate.

  • EWA is the practice of identifying and documenting the administrative workflows that consume K-12 time and create compliance exposure. It includes building the governance literacy schools need to evaluate, adopt, and oversee the AI tools now embedded in those workflows. The EWA framework names the federal statute governing each workflow, measures the documentation gaps, and produces the evidence infrastructure that holds up when someone asks to see the file.

  • The edtech vendors, SIS platforms, and AI tool providers your school does business with are already using AI governance language in their terms of service, their data privacy agreements, and their product documentation. Terms like upstream vendor risk, foundation model dependency, and definition drift are shaping the contracts schools sign, whether the person signing them recognizes the terms or not. The EWA Lexicon makes sure your building speaks the same language as the industries selling to it, and understands what that language commits the district to.

Access the EWA Lexicon
Access the EWA Lexicon

  • When a vendor agreement uses terms your team does not share a definition for, decisions get made around the language instead of through it. The Lexicon closes that gap. When someone in your building can name the upstream vendor risk, identify a definition drift between the DPA and the terms of service, or explain why a missing SBOM matters, the conversation moves from "should we use this tool?" to "does this vendor's documentation meet our obligations?"

  • Federal and state oversight increasingly expects schools to demonstrate AI governance, not just that tools are in use, but that the district understands what those tools are built on, what data flows where, and what the documentation proves. The Lexicon gives your team the working vocabulary to document that understanding in language that maps to FERPA, COPPA, NIST, and the vendor accountability frameworks auditors reference.

  • Logging an AI incident requires knowing what you are describing. A supply chain compromise requires knowing the difference between a vendor breach and an upstream dependency failure. A data exposure entry requires knowing whether the DPA covered the actual data path or only the vendor's front door. Without shared vocabulary, incident logs stay vague, and vague entries do not hold up under review.