The District Filing Workshop

You bring the tools. We get your district compliance-ready and leave you with the workflow to stay that way.

The earliest District Filing 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

The District Filing Workshop

Learn More

You bring the tools. We teach you to file them.

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

    • Superintendents, assistant superintendents, deputy superintendents

    • Principals and assistant principals

    • Curriculum leads

    • Grade band-specific lead educators

    • Building-level IT leads

    • Data privacy officers

    • ESA, BOCES, and Consortium Leads booking on behalf of member districts

    Not for individual classroom teachers or classroom-level AI questions.

  • Turned in to your secure Dropbox Business shared folder, no later than one business week before your first session:

    1. The completed orientation packets. Each participant fills out their own roles worksheet and returns it to the Dropbox folder. The district's point of contact confirms all participant worksheets are in before the deadline.

    2. All completed Educator Pedagogy Protocol questionnaires. Collected from the relevant teachers in the subjects and grade bands your tools target, using the questionnaire template provided at onboarding.

    3. Your tool list. No formatting required. Just the list: vendor and tool. Include tools currently on file, tools currently in use or suspected to be in use but not on file, and prospective tools your district is considering.

    Brought to sessions and kept with your district throughout:

    • Your DPAs

    • Your paperwork

    • Your parent communication methodology and the triggers that determine which types of tools call for which types of communication

    • Any compliance documents you want layered into your build

    These materials are never shared with The Language Firm. They stay with your district from start to finish. The cataloging, filing, and utilization of those documents is the methodology we teach you in the workshop itself.

  • The Educator Pedagogy Protocol Template

    • The structured questionnaire (provided after a workshop is officially scheduled) used to collect teacher input on pedagogy, scope and sequence, and non-specified student needs.

    • Completed by your relevant teachers as pre-work and returned before the workshop date, and aggregated during workshop.

    • Kept by your team for use and revisions as time goes on for every future tool evaluation.

    The District Filing Card Build Methodology

    • The step-by-step process your team learns and builds to its specifications during workshop for constructing District Filing tool spotlight cards independently. This is the methodology that makes your team independent of outside help for tool information upkeep.

  • A facilitated engagement where district leadership teams learn the District Filing methodology, used for the Tool Vault’s weekly District Filing, to produce a complete, signed, and dated filing for every included AI and edtech tool in the school organization environment with the help of AI tools already approved by the district, along with a cadence to maintain filing upkeep of approved tools.

    • A complete set of District Filing tool spotlight cards, one per tool, signed and dated

    • A completed Educator Pedagogy Protocol per subject and grade band in your tool inventory, plus the template to refresh it in-house whenever your teachers' pedagogies shift

    • A Vendor Fit Map for every vendor represented in your tool inventory

    • A signed and dated Upstream Vendor Risk Assessment for every vendor behind every tool

    • A full accounting of which tools were on file, which were thought to be on file but were not, and which were being used off the record

    • The in-house card build methodology, so your team can produce every future District Filing tool spotlight cards without outside help

  • The gap:

    • Districts are adopting AI tools faster than anyone is documenting them

    • Some tools are on file

    • Some were thought to be on file but are missing paperwork that disqualifies them

    • Some are being used off the record entirely

    The unasked question: Educators have mandates to use these tools but have never been asked what their students actually need from them, especially the students edtech typically ignores:

    • English language learners

    • Students with IEPs and 504s

    • Twice-exceptional learners

    • Students who do not fit the "average" the tool was built for

    The District Filing Workshop closes all of these gaps in one engagement and leaves your team able to do it themselves the next time.

  • The District Filing Workshop runs four weeks and is delivered virtually.

    Virtual delivery is the default because it removes travel costs for your team, accommodates districts across time zones, and keeps the Workshop accessible to consortium bookings where participating districts are not geographically close. Sessions run on a secure video platform, with all document exchange handled through your district's Dropbox Business shared folder.

  • Five steps, typically 10 to 14 business days from first contact to your first session.

    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 makes the 15-minute call (ideal times and dates can be chosen). We confirm delivery timeline, number of participants, tool inventory scope, and any scheduling needs. Pricing is shared in full.

    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. Review it with your cabinet, legal, and business office. Sign and return when ready.

    4. Receive your invoice and arrange payment. Net-30 terms. Purchase orders accepted. Payment is due no later than two weeks before your first session, so your Dropbox access is active in time for the one-week turn-in deadline.

    5. Complete onboarding. Once payment is confirmed, the point of contact receives Dropbox folder access to the Educator Pedagogy Protocol questionnaire template and the orientation packet. Your turn-ins are due in Dropbox one business week before Session 1. Your Workshop begins on the agreed date.

  • 4-Week Cohort - $4,000:

    • Four live 90-minute sessions, one per week, exclusively for your specified cohort.

    • Followed by a two-week async tail for office hours, card build review, and filing verification.

    4-Day Condensed - $4,500:

    • Four live sessions of approximately 2 hours each, delivered across four consecutive or near-consecutive days, private to your district or consortium.

    • Followed by a four-week async window of office hours, card build review, and filing verification.

    • Ideal for ESAs, BOCES, and consortium bookings with a defined tool inventory.

    Session times, office-hour windows, and agenda pacing are customizable in the Scope of Work. Teams with larger tool inventories may require additional sessions, priced at a per-session rate defined in the Scope of Work.

Have more questions?

Ask Before You Enroll

Inside the Workshop

  • 1) Define the Filing

    We start by defining what the District Filing is and what it exists to do. Not its components. Its purpose.

  • 2) Define Our Approach

    We walk through how The Language Firm approaches the work of building a District Filing, so your team understands the methodology before we apply it.

  • 3) Set Goals for the Flow of Information

    You tell us who in your district should receive the weekly information, and how that information should be delivered to them.

  • 4) Conduct Tool Inventory

    We work through your tool list together: the tools fully on file, the tools thought to be on file but missing key paperwork, and the tools being used off the record.

  • 5) Build the Pedagogy Protocol

    We assemble the Educator Pedagogy Protocol from your pre-collected teacher questionnaires, capturing pedagogy, scope and sequence, and the non-identifiable student needs standard edtech overlooks.

  • 6) Cover the Card Components

    We walk through the components of a District Filing tool spotlight card so your team knows exactly what each finished card contains.

  • 7) Organize Card Structure

    We decide which of your tools need a one-section card and which need two sections (classroom deployment and teacher-only use). Entirely your choice and based on your needs, tool by tool.

  • 8) Learn the Build Methodology

    Your team learns the card build methodology in-house, so every future District Filing is something you produce yourselves without calling outside help.

  • 9) Build and Map the Cards

    We build a card together for one of your tools, then map its promises against the Educator Pedagogy Protocol to test how well the tool fits what your teachers need. We repeat this for every tool in your inventory.

  • 10) Run the Vendors

    Every tool's vendor is assessed through the Upstream Vendor Risk Assessment. Each vendor gets a printed, signed, and dated sheet for your records.

  • 11) Verify, Sign, File

    We verify every card, every Educator Pedagogy Protocol, and every Upstream Vendor Risk assessment is dated and signed. Then we get them filed in their appropriate areas within the organization system.

  • 12) Closing the Workshop

    The engagement closes. Your district leaves with a complete filing, the methodology to maintain it, and the pedagogy posture to evaluate everything that comes next.

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

  • 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.