How long does it take to create an online course? Time a module

29 September 2026 · 6 min read

It depends on the format, the length and how polished you want it, so general ratios of working hours to finished minutes are not much use for planning. A course of slides with a voiceover and a course filmed on camera with edited demos are different projects. The dependable answer is to time one full module from outline to upload, stage by stage, and plan the rest of the course from that.

The stages that take the time

A module passes through more stages than the finished video suggests:

Outline and learning goals: what the learner should be able to do by the end.
Script or speaking notes, written out in full or as bullets.
Slides, demos and screen setups, including sample files for learners.
Recording, with retakes, audio checks and the occasional lost take.
Editing: cuts, zooms, captions, callouts, music, export.
Supporting material: worksheets, quizzes, transcripts, resource lists.
Uploading and setting up each lesson on the course platform: titles, descriptions, order, previews.

Recording is the part people picture when they estimate. The rest is easy to leave out, and it is where plans quietly slip.

Why one module is the right sample

Timing the whole course before you plan it defeats the point, and timing one lesson is too small, because a short lesson hides the setup cost. A module of several lessons is big enough to include every stage and small enough to finish in a week or two.

Expect the first module to run slow. You are choosing templates, fixing your audio, settling on an intro, and learning your editing workflow. If you can, time the second module too. The difference between the two tells you how much of the first was setup, which is exactly what you need to project the rest.

Keep two numbers at the end: total working hours, and finished minutes of video. Hours per finished minute is your ratio for this format. It is only yours, and only for this style of course, which is why it is worth measuring.

Recording it on your Mac without a timer

Course work is start and stop by nature. You script for an hour, fix a slide, record three takes, and spend twenty minutes on an audio problem. Timers get forgotten at exactly those moments.

Punchcard is a Mac menu bar app that notices which app is in front during your day, by name only, and prints a receipt at the closing time you set: the top five apps with the time on each, the rest as MISC, and a day total. There is nothing to start or stop, and it needs no macOS permissions.

Course stages map neatly onto apps, so the receipt already splits the day for you. The writing app is scripting. The slide app is slides. The recording app is recording. The video editor is editing. The browser is the course platform and research. A week of receipts gives you stage totals with very little effort.

If you switch on “Itemize websites” in Settings, browser time in the supported browsers prints as the sites you used, so the course platform gets its own line and you can see what uploading and setup really cost. Settings shows each browser and whether it is itemizing.

Some limits to plan around:

It does not know which module a day belonged to. There are no projects or tags. Note that in your own log; the CSV export lists every session with start and end times if you need to split a day.
Filming away from the Mac is not on it. If you shoot on a camera and bring the files in later, add the shoot yourself, including setup and teardown.
It cannot tell a good take from a retake. It sees that the recording app was in front, not what happened in it.

Tracking never expires and the CSV export works without a license. The first two printed receipts are free; printing after that needs a $9 one-time license.

A module log in five steps

Pick the module and write down its planned finished length in minutes.
Each evening, copy the receipt’s top lines into a note, with the date and the stage you were on.
Add off-Mac time the same day: filming, lighting setup, reading source material.
When the module is live, total the hours by stage and divide the total by finished minutes.
Repeat for the second module, and compare the two.

Planning the rest of the course

Multiply carefully. If the second module’s ratio is lower than the first’s, use the second for projections and treat the first module’s extra hours as one-time setup. Then turn hours into weeks: the week roll that prints on Sunday shows how many hours you actually gave the course, which is a better basis for a launch date than how many you meant to.

The stage totals also show where to simplify:

Editing is the long stage. Record in shorter segments so there is less to cut, or accept a plainer style. How long a video edit actually takes goes deeper on that stage.
Slides are the long stage. Settle on one template and reuse it. How long it takes to make a presentation has more on where deck time goes.
Scripting is the long stage. Try speaking from bullet notes for the lessons that do not need exact wording.
Setup on the platform is the long stage. Prepare titles, descriptions and resources for every lesson in one sitting instead of one lesson at a time.

And if the measured total is far beyond what you can give the course, you learn that before you announce a launch date rather than after.

Questions

Does Punchcard see my screen or my recordings? No. It needs no Screen Recording permission and records app names only, never window titles, file names or screen contents.

I record on one Mac and edit on another. Does that work? Each Mac keeps its own record, and a license covers two Macs. Add the two day totals together; how to track time across two Macs covers the details.

Can I post my progress while I build the course? Yes. Each receipt exports as a 1080x1350 PNG made for posting, or as plain text, and you choose what to share.