Online Course Completion Content Production Time Estimator

Estimate the staff time required to produce a complete online course by separating recurring lesson work from media production, assessment authoring, and final quality review. The calculator converts each production component into hours and adds them into a total, while also showing the average production time per module. Instructional designers, subject-matter experts, and course producers can use the estimate when building a project schedule or checking whether a planned launch date is compatible with available capacity. Keeping the work categories separate makes it easier to see whether the schedule is driven by module development, recorded media, assessments, or review. The estimate focuses on production effort rather than elapsed calendar duration; parallel work, review queues, stakeholder availability, and revision cycles can make the actual project take more or less calendar time than the total labor hours suggest.

Inputs

Course modules

Hours per module

hours

Finished media hours

Production hours per media hour

hours

Assessment items

Hours per assessment item

hours

Final QA hours

hours

Result

—

Estimated production time

Core content hours—

Secondary production hours—

Assessment hours—

Average hours per unit—

How to use

1. Define the content scope
Enter course modules and the expected average effort for each repeated content component.

2. Add specialized production work
Provide finished media hours and the labor hours associated with each.

3. Include assessment authoring
Enter the planned number of assessment items and average authoring time per item.

4. Add final shared work
Use final qa hours for work that is not naturally assigned to a single unit.

5. Review total and per-unit effort
Use the total for resource planning and the average per unit for scope comparisons.

Formula

Total hours = (Modules × Hours per module) + (Finished media hours × Production hours per media hour) + (Assessment items × Hours per item) + Final QA hours

The result is total labor effort. If several people work in parallel, elapsed calendar time will not equal the summed hours.

What the result means

The result is the summed labor effort for the production components entered, not the elapsed calendar duration of the project.

Use scenario ranges when content complexity or revision effort is uncertain.

Example calculation

Given: 12 modules at 9 hours each, 4 finished media hours at 6 production hours each, 40 assessment items at 0.35 hours each, plus 18 QA hours.

Calculation: Module work = 108 h; media work = 24 h; assessment work = 14 h; total = 108 + 24 + 14 + 18 = 164 h.

Result: Estimated production effort is 164 hours, or about 13.7 hours per module.

FAQ

Does the estimate represent project duration?

No. It is a sum of labor hours. Calendar duration depends on team size, parallel work, dependencies, review turnaround, and working schedules.

How should I estimate hours per repeated item?

Use records from similar work when available, or estimate a representative sample and average it. Run a higher-effort scenario when content complexity varies widely.

Should revision rounds be included?

Yes, if revisions are expected. Include them in the relevant per-unit averages or add them to the shared QA or integration allowance.

Can zero be used for a component that does not apply?

Yes. Set optional production components to zero when the project does not include them; the remaining terms will still be calculated.

How can I turn total hours into staffing needs?

Divide total effort by the productive hours one person can contribute during the target period. Account separately for meetings, leave, and other work rather than assuming every paid hour is available for production.

Related tools