Illustrated cover reading "eLearning Development Time: Hours per Minute" on an apricot and teal background with a zigzag pattern

eLearning Development Time: How Long It Takes to Build a Course, in Hours per Minute

Table of Contents

Share:
Easily share intel
Summarise this page with your favorite AI assistant

eLearning development time depends mostly on how interactive the course is. For typical interactive courses, published benchmarks fall between about 1 and 3 hours of work per finished minute. Simulations and games cost far more. A 20-minute interactive module needs roughly 40 to 60 hours of team effort, before review waits and a buffer.

The trouble is that sources count different things. Some count the whole team, some count one person in one tool, and some give a rule of thumb with no method. This post puts four sources on one scale, hours per finished minute, so you can see why they disagree.

We did not run a timing study of our own, and the best-known study is old. So the post ends with a worksheet and a worked example. To turn hours into money afterward, see our course development cost calculator walkthrough.

Key takeaways

  • Cited benchmarks run from under 1 to about 3 hours per finished minute for typical interactive eLearning, with advanced simulations far higher.
  • The sources disagree most about the authoring step, and about whether they count the whole team or one role.
  • Hours are not weeks. Review rounds add calendar time that no hours-per-minute figure includes.
  • Use the benchmarks as starting ranges, then replace them with your own timesheets.

How much eLearning development time does one finished minute take?

Published figures run from under 1 hour to about 3 hours per finished minute for typical interactive eLearning. Chapman Alliance’s 2010 average for interactive courses is about 3.1 hours per minute. Newer, narrower sources land near 2 hours, and an Articulate rule of thumb lands near 1. Simulations and games run far higher.

A finished minute is one minute of learner time in the completed course, not a minute of raw video or one slide. The table converts four sources into that unit: the Chapman Alliance survey (September 2010), IconLogic’s 2019 post, Christy Tucker’s 2025 update and Articulate’s January 2025 post.

Source What it measures Hours per finished minute
Articulate rule of thumb (2025) 40 to 50 hours per finished hour; 15 to 20 hours for a 20-minute module. No method stated. 0.7 to 1.0
IconLogic (2019) About 2 hours of labor per minute of playtime in Captivate or Storyline. Excludes scripting, rehearsal and assets built outside the tool. About 2
Christy Tucker (2025) 367 hours for about 3 finished hours of interactive eLearning, converted from an existing course. One designer’s estimate. About 2.0
Chapman, Level 1 basic (2010) 79 hours per finished hour on average (range 49 to 125). Whole team. 1.3 (0.8 to 2.1)
Chapman, Level 2 interactive (2010) 184 hours per finished hour on average (range 127 to 267). Whole team. 3.1 (2.1 to 4.5)
Chapman, Level 3 advanced (2010) 490 hours per finished hour on average (range 217 to 716). Whole team. 8.2 (3.6 to 11.9)

The conversions are our arithmetic: hours per finished hour divided by 60. Chapman’s deck adds that some Level 3 respondents reported over 2,000 hours per finished hour, or over 33 per minute.

Why do eLearning development time benchmarks disagree?

They count different things. Chapman counts every team member, from designers and writers to subject-matter experts (SMEs) and project managers. IconLogic counts only the build in one tool. Articulate states a rule of thumb without a method. Compare them only after you match what each one includes.

Three differences explain most of the spread:

  • Who is counted. Chapman’s figures cover everyone on the team. Tucker notes that they are not just her role.
  • Where the clock starts. IconLogic starts timing once a project exists, so scripting, rehearsal and outside graphics sit outside its figure.
  • What interactivity means. Chapman wrote its levels to be broad. Tucker treats one interaction every two to three slides, with no branching or video, as Level 2.

The biggest gap sits in the build step. Chapman’s task shares give about 99 authoring hours for a three-hour course. IconLogic’s rate gives about 360. Tucker says she cannot fully reconcile the two, so she chose 180, between them, based on her own tracked time.

How old are these studies, and should you still use them?

Chapman’s survey ran in September 2010, so it is 16 years old as of November 2026. Tools and AI drafting have changed the work. Use the numbers as planning anchors. ATD’s 2023 research team says not to use its results as stand-alone project estimates.

Chapman’s survey drew 249 completed responses. Its deck says it assumed every task repeats for each hour of instruction and did not measure efficiency gains on longer courses. So very long courses may cost less per minute than shown. That is our inference.

The ATD article, “Want to Speed Up Training Development Time?”, reports a 2023 survey with 115 usable responses. Its hour figures appear only in charts we could not read, so we do not quote them. Its text names the top three barriers to faster development: limited resources, lack of SME and stakeholder availability, and scope creep.

Where does the time go in a typical course?

In Chapman’s task breakdown, as Christy Tucker reports it, analysis, design and storyboarding take about a third of the hours. Media takes about a quarter, and authoring in the tool about 18%. Review, testing and pilots take about 16%. Project management and other work take about 7%.

The table applies those shares to a 61-hour build, which is the Chapman Level 2 average for a 20-minute module. The source shares add up to 98%, so the hours do too.

Task group Includes Chapman share Hours in a 61-hour build
Analysis and design Front-end analysis, instructional design, storyboarding 33% 20
Media Graphics, video, audio 24% 15
Build Authoring and programming in the tool 18% 11
Review and test QA testing, SME and stakeholder review, pilot 16% 10
Management and other Project management, other tasks 7% 4

Shares shift by project. In Tucker’s own 2025 estimate, authoring is 180 of 367 hours, or 49%.

Pro tip: Time Three Courses by Task. Log your hours in the five groups above on your next three courses. Divide each group by finished minutes and average the results. You get a ratio that fits your team, tools and review habits. Tucker finds her own tracked time more accurate than industry benchmarks.

Which factors raise or lower eLearning development time?

Tool experience, templates, stable source content, branching and captions all move the estimate. Only the tool and buffer rows below come from cited sources. The rest are our judgment, so replace them with figures from your own timesheets as soon as you have them.

Factor Multiplier on total hours Basis
Team is new to the authoring tool x 2 Articulate says to double the estimate for a new tool.
Reusable template and style guide ready x 0.8 Judgment. Articulate says templates can cut development time in half.
Source content final / still changing x 0.9 / x 1.3 Judgment.
Branching scenarios x 1.25 to 1.5 Judgment.
Captions and transcripts on every module x 1.1 Judgment. Tucker now includes captions in every project.
AI help with drafting and images x 0.8 to 1.0 Judgment. No controlled study found.
Safety buffer x 1.1 to 1.3 Tucker uses 10% to 20%. Articulate suggests 30%.

Multiply the factors that apply, and stop at three or four because errors compound. Our reusable interactive blocks post shows what to build once.

How do you estimate eLearning development time step by step?

Convert the course to finished minutes, pick a low and high rate from the first table, and multiply. Apply the adjustment factors, add a buffer, then convert hours to calendar weeks. Write down each assumption so you can check it against actual hours later.

The right column fills in the worksheet for a 20-minute interactive module built from approved slides and notes, with a template ready and captions included.

Step What to do Worked example
1. Finished minutes Count learner time, not slides. 20 minutes
2. Level Basic, interactive or advanced. Interactive: an interaction every two to three screens, no branching, no video
3. Rate Pick a low and high rate. Low 2.0 (IconLogic, Tucker). High 3.1 (Chapman Level 2 average)
4. Base hours Minutes x rate. 20 x 2.0 = 40 hours. 20 x 3.1 = 61 hours
5. Adjust Multiply the factors that apply. Template x 0.8, captions x 1.1, so x 0.88: 35 to 54 hours
6. Buffer Add 10% to 30%. 20%: 42 to 65 hours
7. Calendar Hours divided by focused hours per week, plus review waits. About 3 to 5 weeks (next section)

The planning range is 42 to 65 hours. A fixed-price quote should lean high. An internal team can plan to the middle.

How many calendar weeks does that take?

Hours are not weeks. One person rarely has 40 build hours free each week, and Articulate says reviewers typically need 3 to 5 business days per round. In the example, 42 to 65 hours plus two review rounds is about 3 to 5 calendar weeks. That is our estimate, not a benchmark.

The arithmetic:

  • Build time: at 25 focused hours a week (judgment), 42 to 65 hours is about 1.7 to 2.6 weeks.
  • Review waits: two rounds at 3 to 5 business days each is 6 to 10 business days, or about 1.2 to 2 weeks.
  • Total: about 2.9 to 4.6 weeks, rounded to 3 to 5.

Review waits are not work hours, so no benchmark includes them, yet they set your launch date. Tucker adds that a full QA review takes two to three times the course length. That is 40 to 60 minutes per pass for a 20-minute module.

The ATD barriers matter here. When SME availability and scope creep are top causes of delay, your schedule depends on people outside your team. Our course development process for small training teams lays out review gates from SME draft to publish.

Pro tip: Book Review Slots Before You Build. At kickoff, put both review windows on your reviewers’ calendars, with a hand-back date for each. Booking them protects the launch date more than trimming build hours does. Ask for one consolidated set of comments per round.

What should you do next?

Run the worksheet on your next course. Apply only factors you can defend, and write a range. After launch, compare it with your logged hours. A few projects of that habit will beat any benchmark.

Then turn the hours into money. Our course development cost calculator walkthrough shows how to apply a loaded hourly rate to a range like the one above. If you quote clients, how to price eLearning development covers pricing models and margin. For regulated aviation training, the aviation eLearning development cost breakdown covers the extra review steps these general benchmarks leave out.

Frequently asked questions

How many hours does it take to build a 30-minute eLearning course?

At Chapman’s 2010 averages, a 30-minute interactive course takes about 92 hours of team effort, with a range of roughly 64 to 134. Narrower recent figures near 2 hours per minute suggest about 60 hours. Add a buffer, count review waits separately, and replace this range with your own timesheet data after a few projects.

How long does it take to build one hour of eLearning?

Published figures vary widely. Articulate cites a rule of thumb of 40 to 50 hours per finished hour. IconLogic’s tool-only rate of about 2 hours per minute equals about 120 hours. Chapman’s 2010 averages are 79, 184 and 490 hours for basic, interactive and advanced levels. Your content, team and tool decide where you land.

How long does it take to turn a PowerPoint into eLearning?

IconLogic says a PowerPoint-to-eLearning conversion should take no more than 1 hour per minute of finished playtime, counting production in the tool only. Scripting, audio, outside graphics and reviews come on top. A 20-minute conversion is therefore about 20 hours of building, plus those extra steps.

Does AI shorten eLearning development time?

Probably for drafting tasks, but we found no controlled benchmark. Christy Tucker’s April 2025 update cut her estimate for one project from 450 to 367 hours. She credits AI help with analysis, storyboards and images, along with her own experience. Treat that as one designer’s view, and keep human review time in the plan.

How many review rounds should I plan for?

We suggest at least two, with 3 to 5 business days for each, the typical turnaround Articulate describes. That is 6 to 10 business days of waiting before rework. Name one person who gathers comments per round, because ATD lists scope creep and limited SME availability among the top barriers to faster development.

What counts as a finished minute of eLearning?

A finished minute is one minute of learner time in the completed course, not a minute of raw footage or one slide. IconLogic measures against playtime of the finished output, and Chapman measured hours per finished hour of content. Check what each source counts before you compare it with your own numbers.

Want to learn more?

Reach out to us to learn more.

One Platform for
All Your Training Needs

Get a personalized demo.