One of the most common questions I get from clients is: “How long does it take to develop an eLearning course?” It sounds simple. It isn’t. eLearning development time depends on complexity, interactivity, media richness, and the review process, but there are solid benchmarks that can guide your planning and budgeting.
Whether you’re an L&D manager trying to scope an eLearning development project, a stakeholder setting expectations, or a fellow designer building a project proposal, this post will give you the real numbers, drawn from industry research, practitioner surveys, and a decade of lived experience shipping courses that actually get used.
We’ll also walk through a concrete example: estimating the eLearning course development hours for a 20-hour bank branch training on improving customer experiences, broken down phase by phase.
The Industry Benchmark: Hours Per Finished Minute
The most cited framework in eLearning project planning and eLearning production estimate comes from the ATD (Association for Talent Development) State of the Industry report and research by Karl Kapp and Robyn Defelice. Their landmark study establishes one of the most useful ratios in instructional design:
📊 Research Finding: 49 hrs
Average eLearning development time estimates per one hour of finished eLearning for a course of moderate interactivity, according to Kapp & Defelice’s 2017 ATD research. This is the most broadly referenced benchmark in the field, and it’s probably lower than you think an hour of polished eLearning actually costs to build.
But 49 hours is a midpoint, not a ceiling for eLearning production estimate. The same research breaks the range down by complexity level:
| Complexity Level | eLearning Course Development Hours per 1 Finished Hour | What It Looks Like |
|---|---|---|
| Level 1 – Low | ~34 hrs | Slides, text, basic narration, simple quizzes |
| Level 2 – Moderate | ~49 hrs | Custom graphics, branching, some interactivity |
| Level 3 – High | ~116 hrs | Video production, simulations, heavy custom animation |
| Level 4 – Very High | ~217 hrs | Full simulations, game-based learning, custom dev |
| Weighted Average | ~49 hrs | Across all projects in the ATD dataset |
Source: Kapp, K. & Defelice, R. (2009, updated 2017). “Time to Develop One Hour of Training.” ATD Research.
Christy Tucker’s popular analysis of this data adds important nuance: these ratios assume a finished hour includes narrated audio, at least some custom visuals, and functional interactivity. Pure text-and-click “page-turners” can come in at the low end; anything with video shoots, realistic scenario simulations, or custom software demos can blow past 100 hours per finished hour of content.
“The hours required to develop one hour of eLearning vary widely based on the type of content, the level of interactivity, and the number of review cycles.”— Christy Tucker, Experiencing eLearning
Breaking Down the eLearning Design Process: Time by Phase
The eLearning production estimate doesn’t live in one phase. It’s the sum of every stage of the ADDIE or SAM workflow. Here’s how I’ve seen the time distribute over more than a decade of client projects, and what the research supports.
Phase 01
Analysis
6–15% of total hours
Needs analysis, audience profiling, gap analysis, LMS scoping, and stakeholder alignment. Often underestimated but sets up, or derails, everything downstream.
Phase 02
Design
18–25% of total hours
Writing learning objectives, building the design document, mapping the content architecture, scripting treatment, and storyboarding. This is the intellectual core of the project.
Phase 03
Development
40–60% of total hours
Authoring in Articulate Storyline/Rise or equivalent, producing audio/video, creating visuals, building interactions and assessments. The heavy lift.
Phase 04
Review & Revision
15–30% of total hours
SME reviews, client feedback rounds, QA/accessibility testing, and revision cycles. This phase is the most variable, and most commonly underscoped in proposals.
Phase 05
Implementation
5–10% of total hours
SCORM/xAPI packaging, LMS upload, testing across browsers and devices, user enrollment, and launch communication.
Phase-by-Phase Time Deep Dive of eLearning Development Time
1. Analysis: The Hidden Time Cost
Analysis is the phase that clients most often want to skip or compress. That’s understandable, there’s nothing to “see” at the end of it. But in the instructional design timeline, poorly scoped analysis means misaligned content, bloated scope, and expensive rework later. For a 20-hour course, expect 8–20 hours of analysis work: stakeholder interviews, reviewing existing materials, writing the training brief, and aligning on measurable outcomes.
💡 Pro Tip
Always document your analysis findings in a formal Training Needs Analysis (TNA) or Project Brief. This protects you from scope creep and gives stakeholders a reference point before you write a single learning objective. This will help you when estimating the eLearning course development hours.
2. Design: Where the Real Work Begins
The design phase is where the instructional design timeline gets shaped. This includes writing SMART learning objectives, mapping content to performance outcomes, building a detailed storyboard or design document, and scripting the course narrative. Plan for roughly 1 hour of design work per 2–3 minutes of finished content for moderate-complexity courses. For a 60-minute course, that’s 20–30 hours of design time, this will produce a good eLearning production estimate.
3. Development: The Time Hog
No phase consumes more hours than development, and rightly so. Building slides, recording and editing audio, sourcing or creating visuals, coding interactions, and authoring assessments are all time-intensive tasks. Using an authoring tool like Articulate 360 speeds eLearning development time significantly over custom HTML/CSS builds, but even with rapid-development tools, a one-hour moderate-complexity course will average 34–49 hours of development time.
📊 Key Statistic
According to Chapman Alliance research, a single hour of basic eLearning (text, graphics, audio, quiz) takes on average 79 hours to develop when all phases are included. Rapid eLearning tools can bring this down to as few as 33–40 hours total. Not a bad eLearning production estimate.
4. Review & Revision: Budget for the Unexpected
The single biggest cause of blown timelines in eLearning development time estimates is an underestimated review cycle. Clients often envision one quick pass. Reality: two to three rounds of SME review, a leadership approval round, and an accessibility/QA pass. Each round can take 4–8 hours of designer time per hour of content. Protect yourself: cap rounds in your contract and charge for additional cycles.
5. Implementation: The Final Mile
SCORM packaging, LMS uploads, and pilot testing are rarely glamorous, but errors here torpedo an otherwise great course. Budget 4–8 hours for a standalone course and 10–16 hours for a multi-module program. AICC or xAPI integration with third-party platforms can add significant time.
Quick-Reference: eLearning Development Time Estimates by Course Type
| Course Type | Finished Duration | Dev Hours (Low) | Dev Hours (High) | Notes |
|---|---|---|---|---|
| Rapid / Compliance | 30 min | 40 hrs | 80 hrs | Template-heavy, basic interactions |
| Standard eLearning | 1 hour | 100 hrs | 160 hrs | Custom graphics, branching, audio |
| Scenario-Based | 1 hour | 150 hrs | 250 hrs | Decision trees, character dialogue |
| Video-Led Course | 1 hour | 180 hrs | 320 hrs | Shoot, edit, integrate, caption |
| Software Simulation | 1 hour | 200 hrs | 400 hrs | Screen capture, try-mode layers |
| Full Gamification | 1 hour | 300 hrs | 600+ hrs | Custom dev, game logic, UX design |
Case Study: 20-Hour Bank Branch Customer Experience Training
Let’s make these estimates concrete. A regional bank wants to develop a 20-hour blended eLearning program to help branch staff: tellers, personal bankers, and branch managers, deliver exceptional customer experiences. The program includes customer service scenarios, regulatory context, and CRM software walkthroughs. Here’s how I’d scope it.
Program Overview
Total Finished Content: 20 hours (12 hrs eLearning modules + 4 hrs branching scenarios + 4 hrs software simulations)
Target Learners: ~1,200 branch staff across 60 locations
Complexity Level: Mixed — Moderate to High
Delivery: Articulate 360 (Rise + Storyline), hosted on existing LMS
Assumed Ratios: 49 hrs/hr for eLearning, 80 hrs/hr for scenarios, 120 hrs/hr for software simulations
| Module / Component | Content Type | Finished Hours | Dev Ratio | Est. Dev Hours |
|---|---|---|---|---|
| Module 1–4: CX Fundamentals | Standard eLearning | 6 hrs | 49 hrs/hr | 294 hrs |
| Module 5–7: Difficult Conversations | Scenario-Based | 3 hrs | 80 hrs/hr | 240 hrs |
| Module 8–9: Regulatory & Compliance | Rapid eLearning | 3 hrs | 35 hrs/hr | 105 hrs |
| Module 10–11: Branch Scenarios | Scenario-Based | 4 hrs | 80 hrs/hr | 320 hrs |
| Module 12: CRM Software Walkthroughs | Software Simulation | 4 hrs | 120 hrs/hr | 480 hrs |
| SUBTOTAL — Content Development | 20 hrs | 1,439 hrs |
Adding the Full Project Hours
| Phase | Activities | Estimated Hours |
|---|---|---|
| Analysis | SME interviews, job task analysis, LMS audit, audience profiles, TNA report | 60–80 hrs |
| Design | Learning objectives (all modules), design document, storyboards, script drafts, visual style guide | 160–200 hrs |
| Development | Authoring, audio recording/editing, graphic production, interaction coding, assessment build | 1,439 hrs |
| Review & Revision (3 rounds) | SME review, L&D manager review, legal/compliance review, QA, accessibility pass | 300–400 hrs |
| Implementation | SCORM packaging, LMS upload × 12 modules, pilot testing, launch comms | 40–60 hrs |
| Project Management | Client calls, scheduling, status updates, file management (typically 10–15% of total) | 200–240 hrs |
| TOTAL PROJECT ESTIMATE | 2,199–2,419 hrs |
💼 What This Means in Practice
At a solo freelancer rate of $75–$110/hr, this project represents a $165,000–$266,000 investment, consistent with enterprise eLearning program pricing. At a typical instructional design agency day rate, the calendar timeline for a team of two designers and one media producer would be approximately 12–18 months, depending on SME availability and review cycle speed.
If the bank needs this in 6 months, the solution isn’t to cut scope, it’s to scale the team.
The 7 Factors That Shift Your eLearning Production Estimate
No two projects are the same. These are the variables I track in every eLearning development project estimate:
1. Subject matter complexity. Technical content, compliance law, clinical procedures, financial regulations, requires more research, more SME time, and more iteration. Plan for 20–30% additional design hours on complex subject matter.
2. SME availability and responsiveness. The fastest I’ve seen a review cycle take is 3 days. The slowest: 11 weeks. Build review deadlines into your contract with escalation terms.
3. Media richness. Every original illustration, custom character, or location-specific photo adds hours. Stock imagery can cut visual production time by 60–70%. Video production introduces an entirely separate workflow.
4. Number of revisions allowed. The Chapman Alliance found that design revisions add an average of 40% to total development time when not explicitly controlled. Limit rounds in your proposal.
5. Authoring tool experience. A seasoned Storyline developer works 2–3× faster than someone new to the tool. Accurately estimate based on actual proficiency, not theoretical capability.
6. Client content readiness. If the client has a polished existing curriculum, your analysis and design phases can drop by 30–40%. If you’re starting from zero, expect to add significant time.
7. Accessibility requirements. WCAG 2.1 AA compliance: closed captions, keyboard navigation, screen reader testing, typically adds 8–15% to development and QA time. Budget for it up front.
What About “Rapid eLearning”?
The rise of tools like Articulate Rise, Adobe Captivate, and iSpring has driven the promise of rapid eLearning development. These tools are genuinely faster, particularly for content-heavy, low-interaction modules. But “rapid” is relative:
📊 Rapid eLearning Benchmark
Rapid eLearning tools can reduce online course development time by 40–60% compared to custom-built solutions, but only when the content is well-defined, the SME is available, and the design follows template-based patterns. Expect 33–50 hours per finished hour for rapid approaches vs. 79–160+ for custom builds.
The trap I see newer instructional designers fall into: promising “rapid” delivery because the authoring tool is fast, without accounting for all the phases around development. A Rise course can be built quickly, but analysis, storyboarding, review cycles, and LMS implementation take roughly the same time regardless of the authoring tool used.
Team Composition and How It Affects Timeline
Solo freelancer or full team? This is one of the biggest levers in eLearning project planning. Here’s a rough guide:
| Team Configuration | Best For | Timeline Multiplier |
|---|---|---|
| Solo ID/Developer | Projects under 5 hrs content, tight budgets | Baseline (1×) |
| ID + Graphic Designer | Visually rich courses, shorter timelines | 0.65–0.75× |
| ID + Developer + Media | Programs 10+ hrs, video, simulation | 0.4–0.55× |
| Full Agency Team | Enterprise rollouts, 20+ hrs, multilingual | 0.25–0.4× |
The Bottom Line
eLearning development time is real, measurable, and, with the right framework, predictable. The ATD/Kapp benchmarks of 34–217 hours of development per finished hour of content aren’t arbitrary; they reflect the genuine complexity of the work. When your eLearning project planning is grounded in phase-by-phase estimates rather than a single top-level number, you’ll quote more accurately, manage clients more effectively, and deliver work you’re proud of.
For our 20-hour bank training example, 2,200+ hours is not a bloated number, it’s the honest cost of building a program that will train 1,200 people to change how customers feel about their bank. That’s not overhead; that’s investment.
Use the benchmarks in this post as your starting point. Adjust for your team’s experience, the client’s content readiness, and the complexity level you’re committing to. Document your assumptions. And never, ever quote a project before you’ve mapped out all five phases.
Your future self, and your client relationship, will thank you.
As always, thank you for reading this post. If you would like to receive exclusive content, use the form on this page to sign up to our mail list. Please, share this post. Like this post. If you have questions, reach out to us. Leave a comment below. All estimates based on ATD, Chapman Alliance, and Kapp & Defelice research.