Going from Google Docs to course has one problem the other conversions don’t, and it isn’t technical.
Drive doesn’t have a canonical version of anything. Your support handbook exists as Support Handbook, Support Handbook (1), Support Handbook FINAL, Copy of Support Handbook FINAL, and a doc called notes that somebody has been editing weekly since April and is actually the current one.
Confluence and Notion at least have opinions about hierarchy. Drive is a filing cabinet somebody tipped over. So the recipe is the same as the others, plus one step that matters more than the rest of it combined.
Try Mini Course Generator free – turn the handbook nobody reads into a course people finish.
Key Takeaways
– The hard part isn’t conversion, it’s provenance. Pick the file by hand and name it explicitly. Never let an assistant search Drive and choose.
– Ask forLast modifiedand the edit history before you generate anything – the most recently edited file beats the one called FINAL roughly every time.
– Handbooks convert into good courses because they’re already written in a teaching register, unlike specs and runbooks.
– Strip the parts that aren’t training: contact tables, org charts, form links. They belong in a reference page, not a lesson.
– Long documents need a section list first. A 60-page handbook asked for wholesale returns a shallow course that flattens the important parts.
Step Zero: Find the Real File
Do this before anything else, and do it deliberately.
“List every file in the People Ops folder with ‘handbook’ in the name. For each, show the last modified date, the last editor, and the length. Don’t open them yet.”
Then read the output and pick one by hand. The heuristics that work:
Most recently modified usually wins. A document called FINAL from March 2025 is losing to an untitled doc edited last Tuesday. Naming conventions record intentions; timestamps record behaviour.
Check who edited it last. A handbook whose last editor owns the process is the live one. A handbook whose last editor was a departing employee tidying up is an archive.
Length is a tiebreaker, not a signal. The longest version is often an old comprehensive one that got superseded by a shorter rewrite.
Then name that file explicitly in every subsequent prompt. Do not say “the support handbook in Drive”. Say the file. An assistant asked to find a document in a folder with five plausible candidates will pick one, and it won’t tell you it was a coin toss.
The Prompt
This assumes an assistant connected to Drive and to a course platform over an MCP server. The setup takes four steps – see the ChatGPT Developer Mode walkthrough or the Claude connectors one.
“Read the document ‘Support Handbook v3’ in the People Ops folder. List its sections and how long each one is. Don’t build anything yet.”
Then, once you’ve seen the sections and chosen which ones matter:
“Build a course in Mini Course Generator from sections 2, 3, 5 and 8 of that document. One lesson per section, in that order. Skip the contact tables and the form links – those belong in a reference page, not a lesson. After each lesson add a quiz question that presents a realistic situation and asks what the person should do. Publish it and give me the link.”
Splitting it into two prompts is deliberate. A 60-page handbook asked for in one go comes back as a course that treats a two-paragraph section and a twelve-page section as equals, because nothing told it which parts carry weight.
Why Handbooks Convert Better Than Runbooks
Worth knowing when you’re choosing a source, because it’s counterintuitive.
A runbook is written for someone who already has the job and needs the steps. It’s compressed, assumes context, and uses internal shorthand. Converting it produces a course that’s accurate and reads like a reference card.
A handbook was already written to teach. It explains why before what, defines terms, and assumes the reader is new. That’s a training register, and it survives conversion far better because the hardest part was already done by a human who was thinking about a newcomer.
Which suggests an ordering when you have both. Build from the handbook and use the runbook to check the details, rather than the reverse.
What to Strip
Handbooks accumulate material that isn’t training, and it drags the course down if it comes along.
| Strip it | Why |
|---|---|
| Contact tables and org charts | Out of date within a quarter, and it’s reference, not learning |
| Links to forms and systems | A course full of links is a directory |
| Legal boilerplate | Belongs in the document people sign, not the course they take |
| “As of January 2025” preambles | Dates a course that should read as current |
| Long appendices | Reference material by definition |
| Anything with a signature line | That’s a document, not a lesson |
The test: if the reader needs it while doing the job rather than before doing the job, it’s reference. Keep the document for reference and let the course be the training.
The Version Problem Doesn’t Go Away
Once the course exists, you’ve created a second thing that can drift, and Drive has no mechanism to tell you the source changed.
Two habits handle it.
Name the source in the course. Put the exact filename in the course description. In eight months, when somebody asks where a lesson came from, that line saves an afternoon.
Ask on a cycle.
“Has ‘Support Handbook v3’ changed since 12 June? If so, summarise what changed and tell me which lessons in the onboarding course are affected.”
Quarterly is enough for most handbooks. The point isn’t to catch every edit; it’s to make sure a rewritten section doesn’t sit contradicting a live course for a year. That whole class of work has its own piece in what an agent does after publish.
Where the training is required rather than useful, track the requirement itself rather than course completion – a training matrix answers who is currently compliant, which a completion report can’t.
When Drive Is the Wrong Source
Two situations where converting a Doc is the wrong move.
When the document is a transcript of a meeting or a workshop. It reads like content and it isn’t – it’s a record of a discussion, with no sequence and no conclusions marked as conclusions. The course produced from it is confidently structured and mostly wrong about what mattered.
When five people disagree in the comments. An unresolved comment thread in a handbook means the process isn’t settled. Generating a course from it publishes one side of an internal argument to your whole team. Resolve first, convert second.
The Short Version
Google Docs to course is the same conversion as any other, with one extra step that carries most of the risk: choosing the file. Drive has no canonical version, so list the candidates with their modified dates and last editors, and pick one by hand. Then name that exact file in every prompt.
List the sections before generating, and choose which ones matter, or a long handbook comes back as a course that flattens the important parts into the trivial ones.
Handbooks convert better than runbooks because they were already written to teach. Strip the contact tables, form links and appendices – if the reader needs it while doing the job rather than before, it’s reference.
Then record the source filename in the course description and check quarterly whether it changed. If your handbook is thorough and your onboarding training doesn’t exist, that’s a conversion problem rather than a content one, and it’s what an onboarding LMS with a connected assistant is for.
Frequently Asked Questions
Can AI turn a Google Doc into a course?
Yes, with an assistant connected to Drive and to a course platform. It reads the document you name, structures it into sequenced lessons with quizzes, and publishes. The step that matters most is naming the right document, because Drive usually holds several plausible versions.
How do I make sure it uses the right file?
Ask for a list of matching files with their last-modified dates and last editors, then choose one yourself and reference it by exact filename in every prompt. Last-modified date beats a filename containing “FINAL” almost every time.
Should I convert a handbook or a runbook?
A handbook, when you have both. Handbooks are already written to teach someone new, so they convert into training cleanly. Runbooks are compressed reference material for people who already have the job, and they produce accurate courses that read like reference cards.
What should I leave out of the course?
Contact tables, org charts, links to forms, legal boilerplate, appendices and anything with a signature line. The test is whether the reader needs it while doing the job or before doing it – the first is reference and belongs in the document.
How do I keep the course in sync with the document?
Record the exact source filename in the course description, then ask quarterly whether that file has changed and which lessons are affected. Drive won’t tell you on its own, and the alternative is a course quietly contradicting a rewritten handbook for a year.
Can I convert a whole Drive folder at once?
You can, and the result is usually poor. Folders contain drafts, superseded versions and meeting notes alongside the real document. Pick one source file, list its sections, and choose the sections that matter.
