How to Turn a Google Doc Into a SCORM Course

A great deal of training content is written in Google Docs, shared by link, and never becomes anything else. It is collaborative, it is where the subject-matter experts already are, and it is a completely reasonable place to write. It is just not a place you can assign from, track, or put in an LMS.

How do I get a Google Doc into a course?

Export it as Word and import that. In Google Docs, choose File, then Download, then Microsoft Word (.docx), and import the resulting file. There is no separate Google Docs connector and you do not need one — the .docx export is faithful enough that the round trip costs you nothing.

What formatting survives the trip?

The things that matter, if you have used real styles rather than manual formatting:

• Heading styles — Heading 1, Heading 2 and Heading 3 come through and become the course structure.
• Bulleted and numbered lists, including nesting one level deep.
• Bold and italic within paragraphs.
• Images, in position, which are carried into the course near the content they illustrate.
• Simple tables, though complex ones with merged cells are unreliable.

What does not survive?

Comments, suggestions and revision history — none of which you want in a course anyway. More importantly, text that only looks like a heading does not become a heading. If your section titles are just bold 16pt text rather than the Heading 2 style, the structure is invisible to everything downstream and your course will be one long module.

This is the single highest-value thing to fix before exporting, and in Google Docs it is quick: click into a section title and choose the heading style from the styles dropdown rather than the font size box.

What about Google Slides?

Different path. Export slides as PowerPoint and use the PowerPoint import, which handles slide content and images. Be aware that decks and courses want different things — a slide is a prompt for someone speaking, and a course has to stand alone, so expect to add the connective writing that the presenter was going to supply out loud.

Should I restructure before or after importing?

Before, if the problem is structural. After, if the problem is wording.

Structure is much easier to fix in the document, where you can see the whole thing at once and drag sections around. Wording is easier to fix in the course editor, where you can see it in context and know how much text is actually sitting on a screen.

Does collaboration still work afterwards?

This is worth thinking about before you commit. Once the content is a course, the Google Doc stops being the source of truth, and if your subject-matter experts keep editing the doc you will end up with two diverging versions.

Two workable patterns:

• Doc as source. Keep writing in Google Docs and re-import when there is a substantial change, accepting that you redo the course-side edits each time. Fine for content that changes rarely.
• Course as source. Import once, then make the course the master and archive the doc. Better for anything that will be maintained, and it is the pattern most teams settle on.

The failure mode is not choosing, which is how you end up with a course that contradicts the document three months later.

What if several people wrote it?

Documents written collaboratively arrive with the seams showing — three registers, inconsistent terminology for the same thing, and headings at different levels of specificity. None of it is visible while you are editing in the doc, and all of it is obvious once the sections become modules.

The cheapest fix is a terminology pass before exporting: pick one term for each concept and find-and-replace the others. Register is harder and usually easier to fix after import, section by section, where you can see how jarring the shift actually is.

Getting it into your LMS

Once the course is built, export to SCORM 1.2 and upload the package. SCORM 1.2 has the broadest platform support and is what most LMSs expect by default. If there is no LMS in the picture, standalone HTML export gives you a self-contained folder you can host anywhere.

The short version

Download as .docx, check your headings are real heading styles, import. Then decide which version is the master before anyone edits the doc again.