Free Tool

L&D Project Complexity Calculator

Work out how complex your learning project actually is — and get a realistic delivery timeline before anyone commits to a date.

1 · Deliverables
2 · Complexity
3 · Results
Step 1 of 3
What are you building?
Select everything this project produces. If a deliverable is embedded inside another (e.g. a Vyond video inside a Rise module), select the parent first — you’ll get to specify what’s inside below.
Deliverable type — select all that apply
📱
eLearning module
Rise, Storyline — any platform
base: 2 pts
🎬
Animated / explainer video
Vyond or equivalent
base: 3 pts
🎥
Filmed / real-life video
Location shoot, people on camera
base: 3 pts
🖥️
Screen recording / tutorial
System or software walkthrough
base: 1 pt
📄
Job aid / one-pager / PDF
Reference card, poster, checklist
base: 1 pt
📋
Facilitator guide / workbook
Trainer materials, slide decks
base: 1 pt
🙌
Face-to-face / workshop
In-room or virtual delivery
base: 2 pts
🔀
Blended programme
Multiple formats, one programme
base: 3 pts
Standalone assessment
Quiz or test, no accompanying content
base: 1 pt
📊
Infographic / visual asset
Branded visual content
base: 1 pt
⬆️
LMS admin / upload only
No new content — config only
base: 0 pts
📱 What does this eLearning module contain?
Embedded Vyond animation
A video produced in Vyond, published inside the Rise module
+2 pts
Embedded filmed / real-life video
Location or talking-head footage embedded in Rise
+2 pts
Embedded screen recordings
Camtasia or Storyline screen capture inside a Rise block
+1 pt
Custom HTML / JS interactions
Rise code block — bespoke tools, games, or apps built in-module
+2 pts
Branching / scenarios
Decision trees, consequence paths — more than 3 branches
+1 pt
Narration / voiceover
Scripted audio on most or all screens
+1 pt
Content volume
Total word count (on-screen text + narration script)
~500
1505007501k1.5k2k3k4.5k6k+
~3 minutes of learning. Fine for a focused low-complexity deliverable or supporting resource.
Number of distinct learning objectives
2
12345678+
Woah there. That’s a lot of objectives for a single piece of learning — and in our experience, it never really works. Learners remember one or two things from a course, not six. More objectives means more content, more screens, more review rounds, and a higher chance people zone out before the end. Consider splitting this into focused modules — three tight objectives that land beats eight that don’t.
Step 2 of 3
How complex is it?
These factors increase build and review time regardless of format. Toggle anything that applies.
Interaction complexity
Level of learner interactivity required
Simple
NoneSimpleModerateAdvancedImmersive
Simple: Multiple choice questions, image reveals, accordions, basic hotspots. Standard Rise blocks — no custom behaviour.
Content factors
No source content exists yet
Content needs creating from scratch — no policy docs, process guides, or existing materials to work from
+2 pts
Sensitive or high-stakes content
Safeguarding, HR policy, colleague wellbeing, legal implications — needs extra care and sign-off
+1 pt
Updating or replacing existing content
Rebrand, refresh, or significant update to a module already live — requires unpicking existing structure
+1 pt
Stakeholder and process factors
Legal or compliance review required
Content needs sign-off from Legal, Compliance, or an external regulatory body before launch
+2 pts
Multiple stakeholder groups with sign-off
More than one team or department needs to review and approve — not just the requestor
+1 pt
Large or dispersed audience (500+)
Whole-business rollout — affects comms planning, LMS setup, and reporting requirements
+1 pt
SME not yet identified
No confirmed subject matter expert — adds time to scoping and increases storyboard risk
+1 pt
Step 3 of 3
Results
Set Day 0 to generate real milestone dates.

What is this?

L&D projects have a way of looking deceptively simple at the brief stage and revealing their true complexity about three weeks into development. This calculator is an attempt to get ahead of that — to surface the factors that drive build time before anyone’s committed to a delivery date.

It works by scoring your project against a set of deliverable types and complexity factors, then estimating a realistic timeline and breaking it into milestones. It won’t give you a precise date — every project is different — but it will give you a defensible starting point for the planning conversation.

I built it for L&D teams who regularly field requests with optimistic deadlines and want a structured way to push back, or to set expectations early. The scoring system is based on common industry benchmarks for eLearning development, adapted for the full range of L&D deliverable types.

How to use it

  1. Select everything the project needs to produce. If deliverables are embedded inside others, select the parent and then pick the embedded content in the sub-options.
  2. Set the word count and number of learning objectives to reflect the actual scope — not the hoped-for scope.
  3. On the second screen, toggle any complexity factors that apply. These are the things that silently eat into timelines without showing up in a word count.
  4. Review the results. If guardrail warnings appear, take them seriously — they’re flagging things that commonly cause projects to run late or underdeliver.
  5. Set a Day 0 (scoping meeting date) to generate actual milestone dates you can paste into a project plan or LDD.

About the scoring

Each deliverable type has a base complexity score. Embedded content, high word counts, interaction complexity, and stakeholder factors each add to that total. The final score maps to one of three complexity levels: low (0–4 pts), medium (5–9 pts), and high (10+ pts). Each level has a corresponding total timeline, which is then divided proportionally across standard L&D project phases.

The milestone splits are based on a typical eLearning development model — scoping, storyboard, first draft, amends, SME review, QA, sign-off, and publish — weighted to reflect where time actually goes in practice. The storyboard phase is front-loaded because it’s almost always the critical path. Build can’t start until it lands.

Timelines are expressed in business days. The date calculator skips weekends and gives you calendar-friendly milestone dates assuming a straight run with no unplanned interruptions — which, in practice, never quite happens, but is the right baseline to plan against.

Privacy

Everything runs entirely in your browser. Nothing you enter is sent anywhere — there’s no server, no analytics on what you select, and nothing stored between sessions. Closing the tab clears everything.

Built by Shane Ivers. I also run Silverman Sound Studios — a royalty-free music library for content creators.