Training Materials Checklist
How an insurance learning-and-development lead builds, reviews, and ships a new training course — for producers, CSRs, adjusters, or underwriters — from audience scoping through compliance review through pilot to release.
Audience and Curriculum Scoping
-
Identify target roles and their job tasks
Producer, CSR, claims adjuster, underwriting assistant, and SIU each have different daily tasks and different state regulators looking over their shoulder. Name the role and the system they use day-to-day (Applied Epic, Guidewire, EZLynx) so scenarios can be drawn from their actual screens.
-
Confirm CE credit applicability for the audience
Producer-facing courses often need state-DOI-approved CE credit; internal claims or back-office training usually does not. CE-bearing courses require a provider number, course filing, and per-licensee reporting through NIPR — material scope and timeline implications before instructional design begins.
Collects list -
Define measurable learning objectives
Write objectives the learner can demonstrate on the job: "correctly populate the Additional Insured field on ACORD 25," not "understand certificates of insurance." Each objective ties to one assessment item later.
-
Draft the curriculum outline and module sequence
-
Assign SMEs and reviewers by line of business
P&C, workers comp, and group health each need a separate SME — generic "insurance" SMEs miss line-specific gotchas like NCCI vs. independent-bureau rules or HIPAA overlay on group health. Lock SME availability before drafting begins.
Compliance and Regulatory Review
-
Map content to state DOI CE filing requirements
CE hour requirements, line-specific topic mandates (ethics, flood, LTC, annuities), and provider-filing windows vary by state. Build the state matrix before writing — retrofitting a course to meet CA's annuity-suitability hour requirement after the fact is expensive.
-
Cross-check against NAIC models and NYDFS Part 500
For cybersecurity and privacy training, Part 500 §500.14(a)(3) requires annual cybersecurity awareness training for all personnel. NAIC Insurance Data Security Model Law adoptions in SC, OH, MS, and others have parallel requirements. Make sure the course as scoped will satisfy whichever regime applies to your covered entities.
-
Add required disclaimers and producer E&O language
Standard producer-training disclaimers: course content is educational and not legal advice; coverage examples are illustrative and policy language controls; producers must verify state-specific rules before binding. Compliance usually has approved boilerplate — use theirs rather than drafting fresh.
-
Route through compliance and legal reviewCollects list Collects paragraph Collects file
-
Revise content and resubmit for compliance review
Address each markup item in the compliance memo. Re-route only the changed sections rather than the full course — most legal teams will turn around a focused re-review faster than a fresh full review.
-
Schedule the annual regulatory refresh review
Insurance regs move. Add a calendar reminder for an annual content refresh; sooner if a major change hits (e.g., a new state Insurance Data Security Law adoption, NAIC model amendment, or significant case law). Stale CE content can fail a market-conduct exam audit of training records.
Instructional Design
-
Apply the ADDIE model to module structure
Analyze, Design, Develop, Implement, Evaluate. Adult-learner principles matter here — producers and adjusters are time-poor and resist abstract content. Anchor each module in a recognizable workflow (FNOL intake, COI issuance, renewal review) rather than a textbook concept.
-
Build scenarios from real ACORD forms and claim files
Use redacted real artifacts: ACORD 25 with a real-looking certificate holder, ACORD 130 with a real WC class code question, a redacted FNOL recorded statement transcript. Scrub all NPI before use — using live insured names in training material is a GLBA Safeguards Rule problem.
-
Design knowledge checks tied to each objective
-
Create job aids for forms and rating workflows
One-page references producers actually keep at their desk: Additional Insured vs. Certificate Holder cheat sheet, state cancellation/non-renewal notice windows, OFAC screening trigger points. Job aids drive on-job recall far better than module recall.
-
Build the final assessment with pass threshold
CE-bearing courses usually require a 70% or 80% passing score per state filing rules. Set the threshold to match the highest state's bar so a single assessment works across states. Lock question randomization to prevent answer-sharing.
Delivery Platform and Technology
-
Configure the LMS course shell and SCORM package
SCORM 1.2 or xAPI depending on the LMS — check whether it supports bookmarking, completion status, and quiz score reporting. Test the package upload before publishing; broken SCORM manifests are the most common LMS launch failure.
-
Test browser, mobile, and screen-reader compatibility
-
Configure CE credit reporting to NIPR
Most states accept CE roster filing through NIPR; a few (FL, TX) have their own state systems. Roster filings typically due within 10 to 30 days of course completion depending on state. Misreported NPNs are the #1 reason CE credits fail to post — validate the producer's NPN at enrollment, not at reporting.
-
Stage delivery to a pilot cohort
-
Monitor LMS analytics and completion telemetry
Watch for drop-off points (modules where 30%+ of learners exit) and questions with anomalous answer distributions. Both signal content problems — the former is usually pacing or relevance, the latter is usually an ambiguous stem or distractor.
Pilot, Evaluation, and Release
-
Run the pilot cohort and capture feedbackCollects list Collects number Collects file
-
Collect Kirkpatrick Level 1 and 2 data
Level 1 (reaction) from the post-course survey, Level 2 (learning) from the assessment scores. Level 3 (behavior) and 4 (results) come later — schedule a 60- and 90-day follow-up to measure on-job application before claiming the program works.
-
Revise content based on pilot gaps
Prioritize revisions hitting modules with both low pass rates and high drop-off — those are the failure points. Re-route revised modules through compliance only if the change is substantive; minor edits typically do not require a fresh legal review.
-
Release to the full audience after final sign-off
-
Schedule the annual content refresh
Calendar a 12-month refresh review at minimum. Trigger an off-cycle update if a state adopts a new data security law, a major NAIC model is amended, or material case law shifts E&O exposure. Document the refresh decision either way — "reviewed, no changes needed" is a valid audit artifact.
Use this template
Copy it to your account, customize the steps, and run it with your team in minutes.
Browse hundreds of free templates across every team and industry.
Back to template libraryRelated templates
More workflows your team can run.
Run Training Materials Checklist with your team
Customize the steps, assign roles, set a schedule, and keep a complete record for every run.