Google Docs Now Talks Back. Your AI Policy Still Names a Website.

The AI stopped being a website this week. Your syllabus policy still has its address.

Almost every AI policy in almost every syllabus is written as a place. It names a product. It names a category of site. It tells a student where not to go, on the quiet assumption that using AI is a trip the student takes, out of the document and back into it, and that the trip is the thing you are regulating.

On Wednesday, September 3, Google removed the trip.

What actually shipped

Google announced three voice features for its Workspace apps: Gmail Live, Docs Live, and Keep Live. They are conversational. You talk, the app answers, and the answer arrives inside the app you were already in. Google’s VP of Product for Workspace, Yulie Kwon Kim, describes Docs Live as a “thought partner and co writer” that handles “organizing your thoughts, structuring your document,” and, with the user’s permission, “pulling relevant details directly from your Gmail, Drive, Chat, and the broader web.”

Read that last part twice, because it is the part a policy has to survive. A student drafting an assignment in Docs can now, by speaking, have the document assemble structure and pull in material from their own mail, their own files, and the open web, without opening a second tab.

Here is the availability, in Google’s own words from its announcement: the features “are available in Gmail and Keep for Google AI Plus, Pro, and Ultra subscribers, and in Docs for Pro and Ultra subscribers. All of these features are coming soon for Google Workspace business customers.”

That final sentence is the one that matters on a campus, and almost nobody is going to read it.

Your AI policy assumed a door that is no longer the only one

Colleges run Workspace as business or education customers. So on the day this shipped, the campus account did not get it. The consumer accounts did.

The practical shape of your fall term is therefore an asymmetry. A student paying for a Google AI plan on their own phone has a conversational co writer inside Docs today. A student using only what the institution provides does not have it yet, and will get it at a date nobody has announced. Both of those students are in your section, submitting against the same rubric, reading the same syllabus paragraph.

This is not a reason to panic and it is not a reason to ban anything. It is a reason to notice that your AI policy is now describing a world with one door when the building has four, and that the doors opened at different times for different students.

Two things the coverage got slightly wrong, and why that matters more than the feature

When this landed, the trade coverage reported that Keep Live was arriving for the Pro and Ultra tiers. Google’s own announcement puts Keep alongside Gmail, for Plus, Pro, and Ultra. Those are different sets of students. It is a small discrepancy and it changes who on your roster has the thing.

The second one is stranger, and it is sitting on Google’s own page. Above the announcement, Google publishes a machine written summary of the announcement. That summary says the features are “rolling out this week for specific Google Workspace subscribers and business customers.” The article underneath it says business customers get them soon. The summary is labeled, in Google’s words, “Summaries were generated by Google AI. Generative AI is experimental.”

So the generated summary of the announcement contradicts the announcement, on the vendor’s own site, about the vendor’s own product, on the single fact a university most needs.

Nobody was careless here. This is just what generated summaries do at the edges, and it is a better argument for review first than anything we could put on a slide. If a summary can misstate availability with the source directly beneath it, then a student’s summary of a reading can misstate the reading, and your own summary of a policy document can misstate the policy. The lesson is not that the tools are bad. It is that the summary and the source are two different objects, and only one of them is evidence.

Rewrite your AI policy once, and name a behavior

A policy that names an address has to be rewritten every time a vendor ships. A policy that names a behavior does not. Three moves, and the whole job is one sentence.

Name the act, not the app. “Work you submit has to be work you can explain” is enforceable in a hallway, survives every product launch, and does not require you to keep a list of software. A student can tell whether they broke it. You can tell whether they broke it. Neither of you has to know what the assistant is called this month.

Put the line inside the document, not outside it. The interesting distinction is no longer whether AI was involved. It is which act it performed. Talking through an idea aloud and having the file catch it is closer to a writing center session than to plagiarism. Having the file produce the analysis is a different act, in the same file, in the same five minutes. Your sentence should be able to tell those apart, because the software will not.

Assume the asymmetry and write for both students. Do not write a rule whose fairness depends on everyone having the same tools, because as of last Wednesday they do not. Write the rule around what the student has to be able to do at the end, which is the only thing that was ever equal.

The part that compounds

Doing this once is an afternoon. Doing it for every section you teach is the actual job, and it is where most faculty quietly give up, because the fourth syllabus is written by a more tired person than the first one and the sentences stop agreeing with each other. The first student who reads two of your syllabi side by side will find the seam.

That is what a Course Record is for: your policy, your voice, and your course written down once in a place that can carry them into everything else you build. It is the difference between rewriting a sentence and changing a standard.

The Syllabus Generator in the Faculty Toolkit builds student centered, accessibility first syllabi in 19 languages from that record, so the sentence you fix today is the sentence every section gets. See the Syllabus Generator. If you would rather watch other instructors work this out first, the free Harvest Kernel community is where that conversation happens.

Do the first one by hand anyway. You need to feel where your own line sits before anything can carry it for you.

One more thing

Google did not send your provost a memo. There was no procurement cycle, no committee, no pilot, and no vote. A capability appeared inside a document your students were already writing in, on a Wednesday, and the announcement was aimed at consumers.

The next one will arrive the same way. The only question worth answering this week is whether your policy will need rewriting when it does.

Sources

• Yulie Kwon Kim, VP Product, Google Workspace. “Use your voice to get more done in Gmail, Docs, and Keep.” Google, September 3, 2026. blog.google
• Jess Weatherbed. “Google now lets you chat with Gmail, Docs, and Keep.” The Verge, September 3, 2026. theverge.com