From the Campus Operations edition of September 18, 2026
AAUP/AFT AI/Tech Audit Guide equips campus workers to independently audit GenAI and edtech contracts
American Association of University Professors (with AFT Higher Ed) · Higher education labor / shared governance · United States (national faculty/staff association guidance)
- Publisher
- AAUP ad hoc Committee on AI and Academic Professions
- Original publication
- September 2026 (toolkit webinar September 9, 2026; PDF under /2026-09/)
- Source retrieved
- 2026-09-19
- Event date
- 2026-09-09
What happened
AAUP's September 2026 AI/Tech Audit Guide (ad hoc Committee on AI and Academic Professions; introduced in the September 9 toolkit webinar) argues that ongoing independent audits of campus technologies—from LMS platforms to generative AI partnerships—minimize harms before they occur. It instructs members to obtain vendor contracts (via FOIA/open records where needed), triangulate vendor claims with worker experience across job types, and complete structured worksheets on data privacy (including FERPA/COPPA/HIPAA handling), opt-in/out control, intellectual property, technical methods, institutional resource costs (compute, water, electricity), social impacts (accessibility, surveillance, differential effects by job category), and economic/labor impacts (cost, affiliate relationships, unseen labor, precarity, deskilling, shared-governance gaps). The guide is designed to surface disparities between administrator/vendor claims and grounded outcomes.
Why it matters
Direct campus-operations labor and governance constraint: procurement and GenAI rollouts face organized demands for independent contract/labor/privacy audits—not only CIO architecture checklists. Why now: September 2026 toolkit materials were not archived; prior campus-operations run could not open the related AAUP topical report (timeout).
Evidence and measured results
Official AAUP PDF practice guide plus toolkit/webinar context (slides dated September 9, 2026). Prescriptive methodology without publishing results of a completed campus audit in this document.
Limitations and uncertainty
Advocacy toolkit, not an empirical multi-campus study. Effectiveness depends on local open-records rights and bargaining power. International transfer requires local labour-law mapping.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Administrations face organized demands for independent audits of AI/edtech costs, contracts, privacy, and labor impacts before or during adoption.
- Stakeholders
- Faculty senate / AAUP chapter
- Unions / staff associations
- CIO and procurement
- General counsel
- HR / academic affairs
- Discovery questions
- Can the institution produce AI/edtech contracts and correspondence on request?
- Has a labor-impact assessment been done for the proposed tool?
- Who can opt out, and where is that documented?
- Are compute/energy/water cost questions part of procurement?
- Value hypothesis
- Audit-ready documentation and participatory review can reduce later bargaining conflicts and FOIA surprises—without guaranteeing smoother ratification in this source.
- Potential engagement
- Four-week AI procurement audit-readiness sprint producing filled AAUP-style worksheets for one priority platform.
- Unsupported claims
- Union endorsement of a specific AI product
- Guaranteed avoidance of labor disputes
- Measured productivity benefits from auditing alone
Pre-sales engineering
Role takeaway
- Fit
- Institutional GenAI/edtech systems subject to shared-governance and labor scrutiny.
- Architecture and integration
- Systems should expose data flows, retention, training-use flags, access controls, and human-in-the-loop points that map to audit worksheet fields.
- Prerequisites
- Searchable contract repository
- Data classification and FERPA/HIPAA mappings
- Named human decision owners for consequential outputs
- Constraints
- Guide is procedural, not a technical standard
- Public-records scope varies by state
- Vendor NDAs may conflict with transparency demands
- Security
- Clarify school-official designations, subprocessors, and enforcement remedies in contracts; avoid opaque model training on campus data.
- Proof of value
- Completed audit spreadsheet for one live AI use case
- Documented opt-out and human-authority paths
- Resource-cost estimate (compute/energy) attached to the buy
Delivery
Role takeaway
- Work
- Assemble contract packs, run participatory audit sessions, document labor/privacy findings, and feed results into go/no-go decisions.
- Dependencies
- Open-records/FOIA process
- Vendor cooperation
- Union/senate calendars
- Security and privacy offices
- Ownership
- Joint ownership: procurement/CIO for documentation; governance/labor bodies for independent review findings.
- Skills and adoption
- Train chapter/senate volunteers and IT staff on worksheet methods and FOIA request hygiene.
- Governance checkpoints
- Pre-procurement audit kickoff
- Mid-implementation labor/privacy review
- Annual re-audit when vendor capabilities change
- Acceptance criteria
- Worksheet domains completed with cited sources
- Published summary of unsupported vendor claims found
- Human final-authority statement for employment/academic decisions
- Risks
- Polarized campus conflict without facilitation
- Incomplete vendor disclosures
- Deployment delays that push shadow IT
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Expect audit requests for logging, training-data use, resource-cost disclosure, and human-oversight paths; design GenAI platforms so contract terms and technical controls are inspectable by non-vendor parties.
Governance
Who approves, reviews and stays accountable for outcomes?
Shared-governance and bargaining actors are being equipped to challenge top-down tech adoption; institutions should plan participatory review of AI/edtech procurement rather than post-hoc justification.
Security and privacy
What data, permissions and controls need testing?
Guide highlights school-official exceptions and weak enforcement language in edtech contracts—campuses should clarify data ownership, access, and FERPA/HIPAA boundaries in AI agreements.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Worksheets explicitly ask about accessibility, differential harms by job category, unseen labor, precarity, and deskilling—centering workforce impacts that platform rollouts often omit.
Procurement
What should contracts, pricing and exit terms secure?
Treat FOIA-ready contracts, privacy clauses, cost disclosures, and labor-impact questions as first-class procurement artifacts for AI/edtech, not post-signature afterthoughts.
Operating model
Which teams own the service once it runs?
Shifts AI adoption from admin-led enablement toward contested, auditable shared-governance processes with member-led verification.
Publication history
- 2026-09-18Campus Operations · Issue 134 resources
Stable resource ID: aaup-aft-ai-tech-audit-guide-202609