Where faculty agency meets student trust
his article is part of a three-part series examining how AI is reshaping trust between faculty, students, and the institutions governing them. Reading the full series is recommended.
Part 1: The Detection Default | Part 2: The Silent Loop
Here is the moment, the collision point, stated plainly. Elena Marsh, exercising the exact discipline-specific judgment Part 1 argued she should have, uses an AI-assisted feedback tool to help her manage grading load across 90 first-year essays. It’s a reasonable professional choice, made in good faith, inside a policy her department endorses. Maya Chen, sitting on the other side of that same decision, receives a grade shaped in part by a tool she was never told was involved and with no path to ask why. Both things are true in the same instant. Elena is exercising legitimate pedagogical agency. Maya is a student having a decision made about her by a system she can’t see. Neither of them did anything wrong. The institution simply never designed for the fact that its faculty-agency policy and its student-trust policy would collide in this room, over this piece of work.
Two Workstreams, One Collision Point
Most institutions treat faculty AI policy and student-facing AI transparency as two different projects, run by two different offices, and on two different timelines. Faculty policy usually lives with the Provost or a Center for Teaching and Learning. Student-facing disclosure, when it exists at all, tends to live with IT, the Registrar, or student affairs. It often doesn’t exist as a formal policy so much as an assumption that someone else is handling it. Each office can point to real progress on its own workstream. Neither has been asked to think about the moment those two workstreams meet; the instant an instructor’s tool becomes a student’s outcome.
This is the same structural blind spot The Institutional Intelligence Crisis found across university operations: departments run independently, and no one is responsible for what falls through the cracks between them. In the classroom, that crack isn’t between departments; it’s between the person given the power and the person affected by how they use it. Almost no institution has a governance table where both of them sit.
Why the Fix Isn’t Another Committee Handing Down Rules
The instinct, once an institution notices this gap, is to convene an IT-and-Provost governance committee and issue joint guidance. That instinct reproduces the exact failure both prior pieces in this series documented; policy written by the people furthest from the room, applied to the people standing in it. A governance model built to hold faculty agency and student trust together must include faculty senate representation, because faculty are the ones who must live inside whatever gets decided, and it must include actual student voices. And not just a single student representative added to satisfy an optics requirement, because students are the ones the decisions land on.
This is structurally different from the accountability-owner model that works for administrative AI. A single named owner for a workflow tool makes sense when the tool serves one office and one function. That structure doesn’t work here, because the classroom isn’t one function; it’s two people with different relationships to the same decision. A governance structure that represents only one of them will keep producing policy that only looks complete but functions incompletely.
A Standard Simple Enough to Actually Adopt
The practical version of this doesn’t need to be complicated, and it shouldn’t wait for a perfect governance model to be built before any course adopts it. Any instructor, in any discipline, can commit to two things without needing campus-wide uniformity on how AI gets used. One, tell students what AI was used for on a given piece of work, and two, give them a real, findable way to ask for a second look if they think it got something wrong.
That’s the whole standard. It doesn’t require Elena to disclose her exact tool stack or her grading workflow in granular detail. It doesn’t require the registrar to build a new system before anyone can use it. It requires the two things students in Part 2 said they wanted; to know how the decision was reached (disclosure), and to have somewhere to go to ask questions (recourse). Institutions already building agentic systems with real governance, which includes identity, oversight, and an audit trail designed in from the first sprint rather than bolted on after a trust failure, tend to treat this kind of disclose-and-recourse checkpoint as a basic architectural requirement. Classroom AI deserves the same standard the best-engineered institutional systems already hold themselves to.
Scaled up, that same logic becomes the governance table’s actual job. Which is not dictating how every course uses AI, but making sure every course, regardless of how it uses AI, meets that standard.
Designing the Relationship, Not Just the System
The thread running through all three pieces in this series is the same; human-centered agentic AI in higher education is not primarily a data architecture problem, and it’s not primarily an operations problem; it’s both. Both of those are real, and both are already being worked on elsewhere. It’s a relationship problem, between two people who are physically in the same room and structurally treated as if they’re solving two unrelated problems.
ASU’s framing for its Agentic AI and the Student Experience summit this October puts it well; the goal is designing AI systems that “enhance human agency, expand access, and strengthen learning in meaningful ways” (ASU, 2026). That framing only works if “human agency” means both humans in the room; the instructor deciding how AI belongs in her discipline, and the student who deserves to know when it’s being used on her. Institutions that get this right will avoid a trust problem, and they’ll have a classroom-level foundation solid enough to make everything already being built at the operational layer worth scaling.
The institutions that solve this well won’t simply have better AI governance. They’ll strengthen one of the most important relationships on campus: the trust between faculty, students, and the institution itself. That trust becomes the foundation for every future AI initiative.
As institutions move from AI experimentation to enterprise adoption, classroom governance will become one of the earliest indicators of whether AI can be scaled responsibly across the institution. Education leaders ready to design AI governance that faculty trust, students understand, and institutions can confidently scale can request an AI Briefing with Robots & Pencils.
Punch List
| Action | Owner | Timeframe |
| Stand up a joint governance table for classroom AI with faculty senate and student representation — not an IT/Provost committee alone | Provost’s Office / Faculty Senate | This academic year |
| Adopt a minimum disclose-and-recourse standard for any AI-assisted grading or feedback, adoptable course-by-course without waiting for campus-wide policy | Faculty Senate / Center for Teaching and Learning | This term |
| Map where faculty-facing AI tools currently touch student-facing outcomes (grading platforms, feedback tools, proctoring) and assign shared ownership at each handoff point | IT / Provost’s Office | Next two quarters |
| Build the disclosure-and-recourse checkpoint into any new AI tool’s implementation requirements before procurement, not after adoption | IT / Procurement | Ongoing |
| Publish a short annual report on how classroom AI governance is working, in plain language, for both faculty and students to read | Provost’s Office | Annually |
Note: Elena Marsh and Maya Chen are composite illustrations carried through from Parts 1 and 2, not named individuals.
Lindsay Pineda is a Senior Delivery Manager at Robots & Pencils, where she leads delivery of an AI-powered student intervention platform for a major public research university. With over 20 years of experience spanning higher education, educational technology, and program and delivery management, she has held leadership roles at a range of organizations across the higher education and edtech sectors. Lindsay spent nearly a decade as an adjunct graduate faculty member at a large online university facilitating master’s level courses in project management leadership and PMP exam preparation while contributing to curriculum and instructional design. A PMP-certified leader with master’s degrees in psychology and management, she brings a rare blend of strategic delivery expertise and firsthand experience in online course facilitation and the student learning experience.
FAQs
Q: What is “the collision point”?
A: The exact moment a faculty member’s legitimate AI-assisted grading choice becomes a student’s outcome, without the student ever knowing a tool was involved or having a way to ask why. Faculty agency and student disclosure aren’t separate problems, they meet in the same room, over the same piece of work.
Q: Why can’t a joint IT-and-Provost committee just fix this?
A: Because that reproduces the exact failure Parts 1 and 2 documented, policy written by people furthest from the classroom, applied to the people standing in it. A governance table needs faculty senate representation and real student voices, not one token student seat.
Q: What’s the actual two-part standard being proposed?
A: Any instructor, in any discipline, can commit to two things without campus-wide uniformity: tell students what AI was used for on a given piece of work, and give them a real, findable way to ask for a second look.
Q: Does this require a new system or registrar build-out?
A: No. It doesn’t require disclosing a full tool stack or grading workflow in detail, and it doesn’t require IT to build anything new before an instructor can adopt it. It’s disclosure plus recourse, nothing more.
Q: Is this a data problem or a relationship problem?
A: Both are real, but the series argues it’s primarily a relationship problem, between two people physically in the same room who are structurally treated as if they’re solving unrelated problems.
Q: How does this connect to institutional AI governance generally?
A: The same disclose-and-recourse checkpoint that well-engineered agentic systems already build in from the first sprint (identity, oversight, audit trail) should apply to classroom AI. Getting this right becomes the foundation for scaling every other AI initiative on campus.
Key Takeaways
- Faculty agency (Part 1) and student trust (Part 2) aren’t two separate governance tracks, they collide in the same classroom decision, and most institutions have never designed for that collision.
- Faculty policy and student disclosure usually live in different offices on different timelines, with nobody responsible for what falls through the gap between them.
- A single named tool-owner model works for administrative AI but fails here, because the classroom involves two people with different relationships to the same decision.
- The standard is simple enough for one instructor to adopt without campus-wide overhaul: disclose what AI was used for, and provide a real path to ask for a second look.
- Getting this right isn’t just better governance, it’s the trust foundation every future AI initiative on campus depends on.
