Harnessing the Power of Document to Course

To simplify the process and ensure you produce the most suitable source documents for the Document to course build option, we’ve put together this list of guidelines:

Ensure the document file name is the name of the course. Doing this will prevent you having to manually type and correct each course name as you upload the document.

We strongly suggest deciding on a naming convention early on for your course build process. For example, if you have 10 courses that make up a certification, including the code for that certification at the start or end of each course name will ultimately help with organizing (and being able to readily search for your course in your workspace).

We suggest selecting Comprehensive, as this will give you the most screens for your material and stay as true to the source document as possible, whilst also summarizing the content to fit within a microloearning course.

When converting your document to a course in our course builder, you’ll be presented with the option to download your images. This will be extremely helpful, as it will put them all in folder for easy access.

Tables are omitted from the conversion process as they generally can’t be easily summarized. If these tables are complex or extensive, we'd suggest including these as a PDF to be embedded into the course. We would suggest creating a document template (with your branding etc.) that can be repeatedly used for creation of longform assets such as extensive tables, that can be embedded using our Document screen.

This information would be best manually added, for two key reasons. If it's consumed by AI, it may be summarized; there is also the chance that in summarizing the material, some of the outcomes may have not been fully covered, so we would suggest making this step a final one, where a screen is added at the start of the course with outcomes and an introduction. Additionally, the course outcomes or information about the structure will contribute to the 12 screens (which isn’t the best use of them necessarily).

Hyperlinked resources won’t necessarily be brought in, so these will need to be flagged in the source document and added to the course after the conversion.

Generally, we recommend a source document be around the 20 page mark to avoid over-summarization. Use headings within your source document. If bulletpoint lists are used, please keep these to 8 items or less if possible. Avoid shorthand text and aim for full sentences. Remove any bulky information from the document that isn’t truly necessary for the summarization process (e.g. version numbers, extra notes etc.)

We would suggest relying on using Comments (e.g. in a Word Doc) to identify where extra assets will need to be built out after the process. As the source document is produced, leave comments as a checklist as a way of identifying where key hyperlinks are that might need to be added, where tables will need to be created or PDF resources.

Where possible, source higher resolution images for your course. This provides more options in terms of layouts without the risk of images appearing poorly.