From Lecture Notes to Textbook: Turning Course Materials into a Book

Instructors often say they "should write the book one day", as if the book were a separate project waiting for a sabbatical. Usually it is not. A course that has been taught and refined for several years already contains most of a textbook: an outline (the syllabus), chapters in draft (the notes and slides), exercises (the problem sets), and a decade of knowledge about where students get stuck. What is missing is not the material but the shaping — and that is what this guide is about.

Step 1: Audit what you have

Before writing anything new, take inventory. Make a table with one row per week or unit of the course and columns for:

• Topic — what the unit covers.
• Notes — do you have written lecture notes, and how complete are they? (Full prose / detailed bullets / slide headings only.)
• Slides — how many, and how much of the explanation lives in what you say rather than what is on the slide?
• Exercises — problem sets, quizzes, lab work, with answers or without.
• Examples — the worked examples and cases you use in class.
• Media — videos, animations, data sets, images, and who owns them.
• Trouble spots — the places where students reliably struggle, and what you have learned to do about it.

Two things usually become obvious. First, the course is more complete than you assumed: the exercises alone may be the most valuable asset. Second, the gaps cluster in predictable places — the explanation that lives only in your voice, and the units you added recently that never got written up. Both are fixable.

Step 2: Decide what the book is

A course is designed for one institution, one term length and one instructor. A textbook has to work for many. Before you build the outline, decide:

• Which course, generically? Your "BIO 214" is somebody else's "Introduction to Genetics". Describe the course as it exists across institutions, not as your catalogue lists it.
• What level? Your students' background sets the level of your notes. If the book is for the same course elsewhere, will those students arrive with the same preparation?
• What is idiosyncratic? Every good course has the instructor's fingerprints on it: a favourite case study, a sequence that departs from the usual, an emphasis that reflects your research. Some of this is the book's reason to exist; some of it is a local habit that other instructors will not share. Be honest about which is which.
• What must be added? Textbooks usually need material a course does not: a chapter introducing the field, a glossary, more exercises than any one term uses, and enough explanation that a student can learn from the book without hearing you.

Step 3: Build the outline from the syllabus

The syllabus is your first draft of the table of contents, but it is rarely the final one. Course schedules are shaped by term length, exam dates and holidays; a book is shaped by the subject. Common adjustments:

• Merge units that are one idea taught over two weeks.
• Split the week that covers three separate things because it fell before the exam.
• Reorder where the course sequence was a compromise with the lab schedule or a co-requisite.
• Add the chapters a course never needs — an introduction that orients a reader who is not sitting in your first lecture, and the "optional" topics that other instructors will consider essential.
• Balance the chapters. Course units vary wildly in size; textbook chapters should not, or the book becomes hard to assign week by week.

Write one or two sentences for each chapter describing what it teaches. This outline is the core of the proposal you will eventually send, and it is worth showing to a colleague who teaches the same course before you go further.

Step 4: Turn notes and slides into prose

This is the real work, and it is worth understanding why it is harder than it looks. Lecture notes are written for a reader who already knows the material — you. Slides are cues for a speaker. A textbook has to carry the whole explanation without the instructor in the room. In practice that means:

• Write the transitions. In a lecture you say "so now that we can compute this, the obvious question is…"; on the slide there is just a new heading. The connective tissue between ideas is what makes a book teach.
• Restore the examples. Much of what makes a lecture work is the example you talk through at the board. Write it out, step by step, including the false start you make on purpose.
• Anticipate the questions. You know the question that comes from the third row every year. Answer it in the text before the reader asks it.
• Fix the level. Notes drift: the material you added last year is pitched differently from the material you wrote a decade ago. Reading each chapter with one imagined student in mind is the simplest corrective.
• Cut what only works live. Some things — the demonstration, the class discussion — do not translate to the page. In a printed book, replace them with a description or an exercise. In an interactive edition, this is exactly where a simulation or a self-check with feedback belongs, so keep a list.

A practical routine: draft one chapter from your notes, then teach from the draft the next time the unit comes round. Students will find every gap for you.

Step 5: Turn problem sets into exercises

Your problem sets are probably the most publishable thing you have, because they were tested on real students and refined year after year. To make them textbook exercises:

• Sort them by difficulty and by the section they belong to, and make sure every section has some.
• Add more than the course uses. Instructors assigning the book want a choice, and students want practice.
• Write answers or solutions for all of them, in a separate file (see the manuscript guide). Questions with definite answers, recorded in a structured way, are also what an interactive edition uses to give immediate feedback.
• Check ownership: exercises adapted from another textbook cannot simply be reused. Rewrite them or replace them.

Step 6: Deal with what you do not own

Courses accumulate borrowed material — a figure from a paper, a photo from the web, a data set from a colleague. In a classroom this is usually fine; in a published book it is not, unless you have permission or the material is openly licensed. Go through the audit table and mark every item you did not create. Start a permissions log now (item, where it appears, source, rights holder, status). Some items you will replace with your own; some the publisher will help clear. Either way, knowing the list early saves months later.

Step 7: Decide what the book should do that the course cannot

A course is a living thing — you adjust it every term. A printed book is fixed on the day it ships. That gap is why it is worth deciding, before you write, what kind of book you want:

• A print or eBook edition gives students a fixed, portable, affordable text.
• An interactive edition can carry the parts of your course that a page cannot — the demonstration a student can run, the check that tells them immediately whether they understood, the data behind a chart that they can explore — and it can be corrected and updated after publication. It can also tell you which sections students use and where they struggle, which is information no printed book has ever given an author.

The choice affects how you write. If interactivity is in the plan, your notes on "where students get stuck" become the design brief for the interactive elements, and the exercises with definite answers become the self-checks. Linus Learning publishes all three formats from one manuscript; the ActiveBook page shows what the interactive edition looks like.

Step 8: Propose before you finish

You do not need a complete manuscript to approach a publisher. What you need is the outline from Step 3, an honest description of the audience and the competing books, a sample chapter from Step 4, and a realistic timeline. That is a proposal, and sending it early has a practical benefit: editorial feedback and instructor review shape the book while it is still cheap to change. Our proposal template walks through the sections; our complete guide to publishing a textbook covers what happens after you send it.

A realistic picture

Turning a course into a textbook is not a sabbatical project that starts from nothing; it is a shaping project that starts from years of work already done. The audit takes an afternoon. The outline takes a week. Writing the chapters takes as long as writing takes — but you are not inventing the material, you are explaining it once more, this time to a reader who is not in the room. If you would like a second opinion on whether your course is ready, tell an editor about it in a sentence or two; that is the first conversation for most of our authors.