How to Write a Course in Word So It Converts Cleanly

Word is a genuinely good place to write a course. It is where most subject-matter experts already are, it handles review and comments well, and nobody needs training to use it. The problem is not Word. The problem is that most people format documents to look structured rather than be structured, and only the second one survives conversion.

What is the single most important thing to get right?

Use real heading styles. Click into a section title and choose Heading 1 or Heading 2 from the styles gallery, rather than making the text bigger and bold.

This is not a stylistic preference. A heading style is a machine-readable statement that says "this is a section title". Bold 16pt text is a statement that says "this text is bold and 16 points". Everything downstream — the course structure, the module breaks, the navigation, the contents — is built from the first kind and cannot see the second.

If you do nothing else from this post, do this. It accounts for more bad conversions than every other cause combined.

How should I use the heading levels?

Consistently, and shallowly. A workable convention:

• Heading 1 for the things that should become modules.
• Heading 2 for sections within a module.
• Heading 3 sparingly, where a section genuinely has sub-parts.

Deeper than three levels usually means the content wants to be split into more modules rather than nested further. A learner working through a course on a phone has no sense of where they are in a hierarchy, so depth that reads clearly in a printed document reads as an undifferentiated sequence on screen.

What should I do about tables?

Use them for data and avoid them for layout. A table comparing three options across four attributes is a table. A two-column arrangement used to put a picture next to some text is a layout hack, and it converts badly because the structure implies a relationship the content does not have.

Simple tables come through. Merged cells, nested tables and tables spanning pages are unreliable, and the honest advice is to restructure them into lists before importing rather than to import and repair.

Where should images go?

Inline, next to the content they illustrate, and anchored to a paragraph rather than floating. Images are extracted at the position they occupy, so an image that floats freely near the right margin may attach itself to a different paragraph than the one it belongs with.

Avoid using images of text. A screenshot of a table, a diagram containing the only copy of a definition, a scanned form — all of these are invisible to search, to screen readers, and to the conversion. If the words matter, they need to be words.

What about the writing itself?

Write for a screen, not a page. Three specific habits carry most of the improvement:

• Shorter paragraphs. Three or four sentences. What reads as a well-developed paragraph on A4 reads as a wall on a phone.
• No internal cross-references. "As discussed in section 4.2" is meaningless once the document is a sequence of screens. Say the thing again, briefly.
• Front-load each section. Say what the section is about in its first sentence, because that first sentence is often all a scanning learner reads.

What should I leave out entirely?

Everything that exists because the document was a document. Cover pages, tables of contents, document control tables, version history, page headers and footers, and the "purpose and scope" section that no reader has ever needed. All of it converts into content and all of it has to be deleted afterwards.

Also worth cutting: introductory paragraphs that explain what the following section will explain. They are a printing convention that helps a reader decide whether to keep reading a chapter. In a course, the learner has already committed.

Do I need to mark up the interactive parts?

Only if you want precise control. AI import reads an ordinary document and decides where knowledge checks, flip cards and process blocks belong. If you would rather specify exactly where they go, the tagged import path lets you write markers directly in the document — useful when you know the content well enough to know which points deserve a check.

Most people start with AI import and move to tags for the courses they maintain long-term, where the extra control pays back over multiple revisions.

A five-minute pre-flight

Before importing anything, open the navigation pane in Word — View, then Navigation Pane. If your document's structure appears there as a tidy outline, the conversion will go well. If the pane is empty or shows one entry, your headings are not real headings, and twenty minutes fixing that will save an hour of editing afterwards.