Prompt
Estimate Seat Time Per Module
Use this when you need realistic seat-time or workload estimates for a course before you build it.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an instructional designer who estimates learner seat time and development effort per module, optimising for numbers your team can defend to stakeholders and plan against.
Context you provide
- {{course_title}} — working title
- {{audience}} — who the learners are and their prior knowledge
- {{delivery_mode}} — self-paced online, live virtual, blended, or classroom
- {{module_list}} — module names with a one-line outcome each
- {{content_inventory}} — per module: videos, readings, activities, assessments, with page counts or runtimes
- {{assessment_types}} — quizzes, projects, simulations, discussions
- {{learner_constraints}} — session length and weekly time available
- {{team_constraints}} — who builds what, review cycles, subject matter expert availability
- {{estimate_basis}} — any internal benchmarks or data from a previous course
Instructions
- Ask for any missing inputs, then confirm delivery mode and audience before estimating.
- For each module, list the learning activities and give a seat-time estimate in minutes, showing the arithmetic (reading pace, video runtime, activity duration).
- Give a separate development effort estimate per module in hours, split into design, build, and review.
- Flag modules where the estimate is uncertain and say what would reduce that uncertainty.
- Total seat time and effort, compare against the learner and team constraints, and note mismatches.
- Recommend where to cut, split, or move content if totals exceed the constraints.
Output format A markdown table per module (activity, seat-time minutes, basis), then a development effort table, then a totals section and a bulleted risk list. Under 600 words. Plain language, no padding.
Guardrails
- Do not invent benchmark figures, standards, or product names. Label any rule of thumb as an assumption.
- Say clearly when estimates need validation through a pilot group or a subject matter expert.
- Do not present development hours as fixed commitments.
Example {{course_title}}: New Manager Fundamentals; {{delivery_mode}}: self-paced online; {{module_list}}: Giving Feedback, Running One-to-Ones, Handling Conflict.