How long does it take to build an eLearning course?

The most frequent source of frustration in eLearning projects is the gap between how long a client thinks a course will take to build and how long it actually takes. The honest answer is: longer than most people expect. Here is why, and what the realistic numbers look like.

The most common expectation gap in eLearning development is the timeline. Let's outline how a standard project unfolds.

The typical timeline for a single module

A single eLearning module of around 20 minutes in learner time typically takes between four and six weeks from storyboard approval to delivery of a tested SCORM package. This assumes:

1. 1

   All course content has been gathered and approved before storyboarding begins.

2. 2

   One named decision-maker is providing feedback at each review stage.

3. 3

   Feedback is provided within the agreed timeframe at each stage.

Projects where content arrives late, where multiple stakeholders are providing conflicting feedback, or where the scope changes mid-build regularly take significantly longer.

Where the time goes

A common misconception is that most of the time is spent building the course. In practice, the development itself is often the faster part. The time goes into:

1. 1

   Learning needs analysis and objective setting.

2. 2

   Gathering and reviewing subject matter content.

3. 3

   Writing and getting approval on the storyboard.

4. 4

   Visual design and brand alignment.

5. 5

   Review cycles and incorporating feedback.

6. 6

   SCORM testing and LMS upload.

The single biggest variable

Content. The most common cause of delays on eLearning projects is subject matter content arriving late, being incomplete, or changing after the storyboard has been signed off. The content deadline is the most important deadline in any eLearning project, and it almost always sits with the client rather than the developer.

Set a firm content deadline at the beginning of every project and hold to it. Everything else in the development schedule depends on it. A two-week delay in content delivery typically means a two-week delay at the end.

For larger programmes

A programme of three or four modules should not simply be multiplied: three modules do not take three times as long as one. There is shared design work, shared storyboarding patterns, and a review process that becomes more efficient as stakeholders become familiar with the format. But a three-module programme still typically takes eight to twelve weeks from start to delivery.

About the Author

Dan Deveney is a digital designer, educational specialist, and developer based near Dartmoor in Devon. Through Granite & Glitch, he works with small businesses, charities, and community groups to create accessible, high-performance digital projects, drawing on more than 15 years of experience across design, education, and development.