Every college in the system now has Gemini for Education and Gemini Notebook through the systemwide Google agreement. The licenses are in place.
The training to actually use them, in the roles your people actually work in, mostly isn't.
What's left is harder. The systemwide agreement is opt-in and managed locally, which means adoption happens college by college, on your timeline, with your IT team, and your faculty. The systemwide training that came with it is a general tool walkthrough. It shows people what the buttons do. It doesn't show a program review coordinator how to turn three years of data into a first-draft narrative, or show a counselor how to draft student outreach without putting student records anywhere near a prompt.
That gap is where most campuses are stuck right now: licensed, technically ready, and barely using it.
WHAT I DO:
Three ways to work together. All of them use the Google tools your college already has, so there's nothing new to buy, procure, or route through IT for approval.
That matters here for one reason: I've done the jobs I'm training people to do. I've scrambled my way through program review. I've written the board report. I've been in the flex day session that everybody attended and nobody used afterward.
I'm not a technologist selling colleges on AI. I'm a former administrator showing colleagues how to use tools their institution already pays for, on the work that's already on their desk. That includes being straight about what these tools do badly, where they produce confident nonsense, and which decisions have to stay with a person.
This comes up in every session, and it should.
Under the systemwide agreement, Gemini and Gemini Notebook are designated Core Services, which means institutional prompts and files are not used to train Google's models and not used for advertising, and the tools operate under FERPA and COPPA. There are also limits worth knowing: Gemini Notebook is not HIPAA-certified, which matters for health-adjacent offices like DSPS, health centers, and veterans services.
Every engagement includes a written one-page student data standard: what never goes into a prompt, what the Core Services designation actually means in plain language, and a short checklist to confirm with your own IT team. You keep it whether or not we work together again.
Verify anything here against your district's current agreements and your IT department's provisioning decisions. I'll tell you the same thing in the room.
Sixteen prompts written for community college work. Eight for faculty (syllabi, readings, rubrics, discussion questions) and eight for staff (meeting notes, program data, policy manuals, survey responses). Each one includes what to use it for, the exact prompt to copy, and a caution about where it can go wrong.
Free, no cost, no pitch attached.