Blog › ICP guides

Instructional designer on retainer: learning objectives advisory, course architecture design, and LMS configuration guidance on monthly retainer

July 24, 2026 · ~19 min read

A financial services firm runs annual anti-money-laundering training for 2,300 employees. The training has been in the LMS for three years. Completion rates are consistently above 95%, the compliance team reports no exceptions, and the module passes every audit. The compliance officer considers it a solved problem. The instructional designer reviewing the module for the first time in 18 months finds something different: 14 of the module's 22 learning objectives use Bloom's Taxonomy knowledge-level action verbs — identify, recognize, list, recall — for skills that the firm's own job task analysis, conducted before the module was built, explicitly listed as requiring application-level performance. The bank tellers and relationship managers who take this training are expected to recognize suspicious transaction patterns in real customer interactions and file Suspicious Activity Reports. The module teaches them to recall the definition of structuring. These are not the same cognitive task.

The distinction matters for compliance reasons that go beyond audit completion rates. When a bank examiner from the Financial Crimes Enforcement Network reviews training records and asks whether training was effective at producing the behavior the regulation requires, completion percentage is not the answer. The answer is whether the training was designed to develop the performance the regulation requires — and a module that asks employees to recognize terms on a multiple-choice quiz cannot demonstrate that it developed the ability to identify structuring in an ambiguous, real-time customer conversation. The instructional designer identifies this gap and presents it to the compliance officer as a regulatory risk, not a training critique. The remediation is not a complete rebuild: it is a targeted redesign of the objectives, the scenario content, and the assessment items for the three modules covering transaction monitoring. It takes 80 hours of instructional design work. The completed redesign now addresses a defensible gap in the training program before an examiner identifies it first.

The compliance officer who commissioned the annual refresh sees the launch of the updated modules. The 80 hours of learning objectives audit, Bloom's Taxonomy analysis, scenario development, assessment redesign, and LMS QA testing that produced those updated modules is invisible between the launch event and the next compliance exam. A monthly retainer engagement makes that advisory layer visible, and makes it continuous rather than punctuated by annual refresh cycles that catch problems only after they have accumulated for twelve months.

An instructional designer or learning experience designer on monthly retainer operates in this analytical and architectural layer continuously. Between the visible course launches that appear in LMS dashboards lie a continuous cycle of learning objectives alignment, course architecture review, assessment quality analysis, LMS configuration monitoring, and accessibility compliance work that the client never directly observes — and that is exactly the work that prevents learning programs from accumulating the structural failures that require expensive program overhauls to correct.

Learning objectives design advisory

Learning objectives are the instructional design equivalent of requirements specifications: they define what the learner should be able to do after completing the course, and they determine every subsequent design decision about content, activity, and assessment. Objectives that are vague, misaligned to the required performance level, or inconsistently structured propagate their failures downstream into every element of the course that references them. The retainer's objectives advisory function catches those failures before they compound.

Bloom's Taxonomy alignment review

Bloom's Taxonomy provides a framework for classifying learning objectives by cognitive complexity level: remember, understand, apply, analyze, evaluate, create. Each level corresponds to a set of observable action verbs that describe what a learner at that level can do. The practical significance for instructional design is that the cognitive level of the objective determines the instructional method required to develop that level of performance. A learner who needs to apply a skill in practice needs practice activities and feedback, not a reading and a recognition quiz.

In a typical Bloom's Taxonomy audit of an existing course, an instructional designer reviewing objectives against the six-level taxonomy finds a consistent pattern: objectives written at the remember or understand level (using verbs like identify, describe, list, explain) for skills that the job task analysis describes as requiring application or analysis in context. A software implementation course whose objectives say “Identify the steps in the configuration wizard” and “Describe the difference between a primary and secondary server role” is designed to produce recognition, not configuration skill. A learner who completes that course can answer quiz questions about the wizard steps; whether they can configure a server under novel conditions without reference materials is not assessed and not developed by the current design.

Rewriting objectives to target the correct Bloom's level requires analysis of the job task documentation, the performance context (what conditions the learner will face on the job, what tools and resources will be available, what the acceptable performance standard is), and the gap between the current objective's cognitive demand and the required performance level. For a 20-objective module, that analysis takes 3 to 5 hours and produces a rewritten objective set with documented rationale for each change. The rationale documentation is particularly important: when the subject matter expert or stakeholder reviews the revised objectives, the rationale explains why “Describe the company's harassment prevention policy” was changed to “Apply the harassment prevention policy to ambiguous workplace interactions” — because the performance requirement is judgment under ambiguity, not recitation of policy language.

Objective-to-assessment alignment mapping

Every learning objective in a well-designed course should be covered by at least one assessment item that evaluates whether the learner achieved the objective. In practice, objectives and assessment items frequently drift out of alignment during the iterative development process: assessment items get revised for clarity without checking whether the revision changed the cognitive level being assessed; new content gets added without corresponding assessment coverage; old objectives are updated without corresponding assessment item updates.

An objective-to-assessment alignment mapping is a systematic cross-reference of each objective against the assessment item or items that cover it. The output is a coverage matrix: rows are objectives, columns are assessment items, and cells indicate which items cover which objectives. Gaps (objectives with no assessment coverage) indicate content that is taught but not evaluated — a compliance risk when the objective covers a regulatory requirement. Clusters (multiple items covering the same single objective with no items covering other objectives) indicate imbalanced assessment design that inflates scores on well-covered content while leaving other content unmeasured. Misalignments (items that test a lower cognitive level than the objective requires) indicate assessment that cannot confirm the learner achieved the objective as written.

For a module with 15 objectives and 40 assessment items, building the coverage matrix, identifying gaps, clusters, and misalignments, and drafting revision recommendations takes 4 to 7 hours. The deliverable is the matrix plus a prioritized recommendation list. This work is conducted before any assessment revision begins — it is the diagnostic that determines which assessment items need revision and why, preventing the common pattern of revising items based on gut feel rather than coverage analysis.

Course architecture advisory

Course architecture advisory is the instructional design retainer's strategic layer: the decisions about how content is organized across modules, how modules sequence and relate to each other, how prerequisite logic is structured, and how the cognitive load of the learning experience is managed across the duration of the engagement. These decisions are made once at the design stage and persist for the life of the course, making architectural errors the most expensive type of instructional design problem to correct after launch.

Cognitive load management and micro-module design

Cognitive load theory describes the finite capacity of working memory and its implications for instructional design: learners who are presented with more information than working memory can process at one time either fail to encode the material or encode it incorrectly. The practical implication is that course modules should be designed with working memory limits in mind, not with content volume as the primary organizing principle.

The most common cognitive load problem in enterprise learning programs is the compliance megacourse: a single module covering four to six distinct regulatory requirements, designed as a linear sequence of 45 to 90 minutes of content followed by a 20-question cumulative assessment. The design is driven by content coverage needs (all the required topics must be covered) and administrative convenience (one completion record per learner per year) rather than learning effectiveness. Learners who encounter a 90-minute module with six distinct topic areas and a comprehensive assessment must hold content from the first section in working memory while processing content from the fourth section — a working memory demand that exceeds human cognitive capacity for most adult learners.

A cognitive load audit of a 4-hour annual compliance training program produced a recommendation to split the single module into six distinct micro-modules of 20 to 35 minutes each, organized around single regulatory domains. The redesign also incorporated a spaced repetition schedule: instead of one annual completion event, learners received the six modules in two-week intervals over a 12-week period, with a brief knowledge refresher before each new module that reviewed key concepts from the previous one. The spaced repetition schedule was implemented through the LMS using a learning path with time-locked release dates. The compliance officer's concern about administrative tracking was addressed by a completion summary report that aggregated micro-module completions into a single annual compliance status per learner. The redesign produced a measurably higher score on the knowledge retention assessment administered 90 days after completion (62% correct vs. 41% on the single-module format) and a lower learner-reported difficulty rating despite covering identical content.

The architectural analysis that produced this redesign — reviewing the existing module structure, conducting a cognitive load audit, mapping content to regulatory domains, designing the micro-module architecture, specifying the LMS learning path configuration, and documenting the spaced repetition schedule rationale — took 18 hours over six weeks. The client saw the launch of a redesigned compliance program. The advisory work that designed that program was not visible in the launch.

Prerequisite logic and learning path design

Prerequisite logic in an LMS defines the conditions a learner must meet before gaining access to a given module or learning path. Correctly designed prerequisite logic ensures learners encounter content in the sequence the instructional design requires, prevents learners from accessing advanced content before completing foundational modules, and creates a structured progression that mirrors the intended learning sequence. Incorrectly designed prerequisite logic either blocks learners who have legitimate reasons to access content out of sequence or fails to enforce prerequisites that the learning design depends on.

In one learning path audit, an instructional designer reviewing a new hire onboarding curriculum found that the LMS prerequisite configuration for a six-module sequence had been set to require completion of Module 1 before accessing Module 2, but no prerequisite had been configured between Modules 2 through 6. A learner who completed Module 1 could access Modules 3, 4, 5, and 6 without completing Module 2 — a gap that was not caught during the initial LMS configuration because the QA testing protocol checked only whether Module 1 blocked Module 2, not whether the remaining prerequisites were in place. Module 2 covered the product knowledge foundation that Modules 3 through 6 applied in practice. Learners who skipped Module 2 were completing hands-on product configuration exercises without the foundational conceptual framework that the exercises assumed. The fix was a prerequisite chain configuration that could be implemented in the LMS in two hours. Identifying the gap, understanding its consequences for the learning sequence, and specifying the corrected configuration took four hours of audit work.

Assessment design advisory

Assessment design advisory is the instructional design retainer function that most directly affects whether a learning program can demonstrate its effectiveness. An assessment that measures the wrong cognitive level, uses implausible distractors, or contains items with technical flaws produces scores that cannot be interpreted as evidence of learning — they are evidence of assessment completion. A well-designed assessment produces scores that correlate with actual post-training performance, which is the evidence that justifies the learning investment.

Knowledge check item quality and distractor analysis

Multiple-choice items — the most common assessment format in e-learning — depend on the quality of their distractors (the incorrect answer choices) to function as valid measures of learning. Implausible distractors are incorrect options that no informed learner would select, making the item trivially easy regardless of whether the learner understood the content. Items with implausible distractors inflate assessment scores without measuring learning, creating the appearance of high performance while failing to discriminate between learners who understood the material and those who guessed correctly.

In a distractor analysis of a 40-item compliance assessment, an instructional designer reviewing each item against distractor quality criteria found 11 items with at least one implausible distractor. The pattern was consistent: distractors that used obviously non-technical language in a technical context, distractors that were clearly grammatically inconsistent with the stem, and distractors that described behaviors explicitly prohibited rather than plausibly confused behaviors. One item asked what a relationship manager should do when a customer requests to split a $15,000 cash deposit into three separate $4,900 deposits on the same day. The distractors included “Call the customer's employer to verify employment status,” “Offer the customer a complimentary fee waiver,” and “File a Currency Transaction Report and a Suspicious Activity Report immediately.” The correct answer was to file a Suspicious Activity Report. A learner who had no knowledge of the Bank Secrecy Act could eliminate three distractors without knowledge of the subject matter, leaving the correct answer as the only plausible option. The item measured the ability to exclude obviously wrong options, not the ability to identify structuring.

Rewriting 11 items with improved distractors requires understanding the domain well enough to generate plausible wrong answers — options that reflect common misconceptions, overgeneralizations, or partial understanding rather than arbitrary wrong answers. That requires SME consultation, review of learner error data if available, and knowledge of the regulatory domain. The analysis and revision of 40 items took 6 hours. The revised assessment produced a score distribution with meaningfully higher discrimination between high- and low-performing learners on the post-assessment, confirming that the original assessment's high completion scores were not evidence of learning but of easily-guessed items.

Formative vs. summative assessment balance

Formative assessment is assessment that occurs during the learning process and provides feedback to the learner and the instructor about current understanding before the summative evaluation. Summative assessment is the end-of-course evaluation that produces the completion record. A well-designed e-learning course uses formative assessment (knowledge checks, scenario responses, reflection prompts) throughout the content to give learners feedback on their understanding before the final quiz, and uses summative assessment to confirm whether the learning objectives were achieved.

In a course architecture where formative and summative assessment are not distinguished, learners may encounter a single cumulative quiz at the end of the course as their only assessment experience — a design that provides no feedback during the learning process and gives the instructional designer no information about where learners are encountering difficulty. An instructional designer reviewing a leadership development program with 12 modules and a single 60-item final assessment recommended distributing formative knowledge checks after each module's key concepts, with immediate corrective feedback (the learner sees why a wrong answer is wrong, not just that it is wrong), and preserving the summative assessment for certification purposes. The formative check data, captured by the LMS at the xAPI statement level, provided module-by-module performance data that identified Module 7 (conflict resolution frameworks) as the topic with the highest error rate — information that triggered a content revision of Module 7 that was not possible to identify from the cumulative final assessment scores alone.

LMS configuration advisory

LMS configuration advisory is the instructional design retainer function that is most consistently treated as a technical problem rather than an instructional design problem. LMS configuration decisions about completion tracking logic, SCORM vs. xAPI protocol selection, suspend_data handling, and learner progress visibility directly determine what evidence of learning the LMS can capture and report. An LMS configured to track completion by slide advancement produces completion records for learners who clicked through every slide without reading them. An LMS configured to track completion by assessment score produces completion records only for learners who demonstrated measured competence.

Completion tracking logic design

Completion tracking in SCORM (the most common e-learning interoperability standard) is controlled by the lesson_status field, which can be set by the course to one of several values: passed, failed, completed, incomplete, not attempted, or browsed. The choice of which status value to send, and under what conditions, is an instructional design decision with compliance implications: if the LMS reports “completed” when a learner reaches the last slide regardless of assessment performance, and the organization's compliance documentation requires evidence of learning (not just content viewing), the completion record is not the evidence the compliance requirement demands.

In one LMS configuration audit, an instructional designer reviewing completion tracking settings for a medical device training program found that 23 of the 31 modules were configured to report “completed” when the learner advanced to the final slide, with no assessment score threshold required. The remaining 8 modules required a passing score on the summative assessment (80% minimum). The inconsistency was introduced over three years of piecemeal module development by multiple external developers who had used different completion logic in their Articulate Storyline configurations. From the LMS completion dashboard, all 31 modules showed consistent completion records. From a regulatory audit perspective, the 23 modules were generating completion records that could not be defended as evidence of competency demonstration — only evidence that employees had opened and advanced through the content. The remediation required opening each of the 23 Storyline files, identifying the completion reporting trigger in the Storyline player settings, changing it from “last slide viewed” to “quiz result,” republishing, and re-uploading. The audit that identified the problem took 8 hours. The remediation was 14 hours of development work.

SCORM vs. xAPI protocol selection and suspend_data advisory

The choice between SCORM and xAPI (also called Tin Can) as the communication protocol between a course and an LMS is a technical decision with instructional design implications. SCORM, in its 1.2 and 2004 versions, provides standardized communication for completion status, score, and a data field called suspend_data that stores the learner's progress state between sessions. xAPI provides a more granular event-level communication layer: the LRS (Learning Record Store) receives individual statements describing learner actions (“Actor completed Activity at timestamp with Result”), enabling analytics at the interaction level rather than the module level.

The suspend_data field in SCORM 1.2 has a critical limitation: the maximum field size is 4,096 characters. Courses with complex branching logic, adaptive pathways, or a large number of interaction states store learner progress in suspend_data. When the accumulated progress state exceeds 4,096 characters, the field truncates — and the truncation behavior is not always obvious in testing. A learner who suspends a module mid-way through, returns to resume it, and finds the module has reset to the beginning rather than resuming from the suspension point is experiencing a suspend_data overflow. The learner typically attributes the reset to a technical error or LMS problem and reports it to IT support. IT support often cannot diagnose a SCORM suspend_data overflow without instructional design knowledge of the issue.

In one LMS QA engagement, an instructional designer testing a newly published 45-minute customer service training module identified a suspend_data overflow when testing a resume scenario in which the learner had completed 38 of 52 slides (including 12 branching decision slides with recorded interaction states). The module reset to slide 1 upon resumption rather than slide 39. Investigation found that the suspend_data field was reaching approximately 4,200 characters at slide 38 in that specific interaction path. The recommendation was to migrate the module from SCORM 1.2 to SCORM 2004 (which supports a 64,000-character suspend_data field) or to reduce the interaction state being stored by consolidating branching decision records. The organization chose SCORM 2004 migration. The QA testing that identified the issue took 2.5 hours; the fix required developer republication and took 1 hour.

Accessibility compliance advisory

E-learning accessibility advisory covers the application of WCAG 2.1 (Web Content Accessibility Guidelines) standards to course content, including keyboard navigation requirements, closed captioning standards for audio and video content, alt text specifications for instructional images and diagrams, color contrast requirements for on-screen text, and timing requirements for timed interactions. Accessibility requirements in e-learning are not optional in most organizational contexts: Section 508 of the Rehabilitation Act requires federal agencies and federal contractors to make electronic and information technology accessible to people with disabilities, and many organizations apply these standards regardless of federal contractor status.

Keyboard navigation and interaction accessibility

Keyboard navigation accessibility requires that every interactive element in a course be operable by keyboard alone, without requiring mouse or touch input. For e-learning courses built in Articulate Storyline, Rise, or Adobe Captivate, this means every button, drag-and-drop interaction, tab interaction, and custom JavaScript element must have a keyboard-accessible equivalent. In practice, custom interactions built by instructional developers or visual designers who are not accessibility-trained are the most common source of keyboard navigation failures.

In one accessibility audit of a 6-module leadership development program, an instructional designer conducting a WCAG 2.1 keyboard navigation review identified three modules with click-to-reveal accordion interactions that were not operable by keyboard. The interactions had been built as custom Storyline layers triggered by clicking on graphic elements rather than Storyline buttons with native focus and keyboard handling. A screen reader user or keyboard-only user could not expand the accordion items to reveal the content. The remediation required rebuilding the interactions using native Storyline button objects with proper tab order and enter-key trigger assignment. The accessibility audit across 6 modules took 7 hours; the developer remediation was 4 hours per affected module. The audit identified the problem before the program was deployed to 1,800 employees; deployment followed by accessibility complaint and remediation would have required the same remediation effort plus compliance incident documentation.

Closed captioning standards and audio description advisory

Closed captioning for e-learning video content must meet WCAG 2.1 Success Criterion 1.2.2 (Captions Pre-recorded): all pre-recorded audio content in synchronized media must have captions. The captioning standard requires synchronization with audio (not just a transcript delivered separately), verbatim or close-verbatim accuracy (not paraphrased summaries), and identification of non-speech audio elements that carry instructional meaning (sound effects that signal correct or incorrect responses, audio indicators that distinguish feedback from content).

In a captioning audit of a technical skills training library, an instructional designer reviewing 14 video modules found that 9 had captions generated by automatic speech recognition without human review. The ASR-generated captions contained an average of 12 accuracy errors per minute for the technical domain content — domain-specific terminology (API endpoint names, configuration parameter names, product-specific UI element names) was consistently misrecognized. In one case, a configuration step demonstrating how to set a parameter called “maxRetryAttempts” was captioned as “max retry attempts” in some places and “max re-try at temp is” in others. A learner relying on captions would not be able to follow the configuration instruction. Remediating 9 modules of ASR captions to human-reviewed accuracy standards, at an average of 3.5 hours per module for review, correction, and re-synchronization, represents 31.5 hours of captioning remediation work that was identified and quantified in a 4-hour audit.

Tracking instructional design retainer hours with HourTab

Instructional designers and learning experience designers on monthly retainer face the same invisible-work billing problem that affects every knowledge-intensive advisory engagement: the visible outputs are small (a revised objective set, a new assessment item, a republished SCORM package) while the analytical work that produced those outputs is large. A 3-hour Bloom’s Taxonomy audit of 23 objectives produces a one-page document. An 8-hour LMS configuration audit of 31 modules produces a two-page findings report. The ratio of advisory hours to visible deliverable size can run 4:1 or higher in a month where the work is primarily audit and advisory rather than content authoring.

When the monthly invoice arrives, L&D managers and CLOs who evaluate the retainer against visible output volume apply a calculation that systematically undervalues instructional design advisory: “what did we receive this month?” If the answer is “a revised objective set for Module 4 and a distractor analysis report for the compliance assessment,” the invoice feels expensive relative to the visible deliverables — even though the revised objective set prevented a regulatory audit finding and the distractor analysis identified 11 items producing inflated completion scores. The advisory hours are the majority of the retainer value; the deliverable documents are the summary of that analysis.

HourTab is built for exactly this billing challenge. Import your time-tracker CSV, and HourTab generates a public retainer-hours URL that your client can bookmark. The URL shows a live view of hours logged against the monthly retainer allocation, with the work log entries visible in chronological order. The client does not need a login or a portal to see where the retainer hours stand. When the invoice arrives, the client has already seen the objectives audit session, the distractor analysis work, the LMS QA testing log, and the accessibility review. The hours are not a surprise; they are a record of the instructional design advisory engagement the client has been following in real time.

The Free plan handles one active retainer: a public share URL, CSV import, and a work log with a progress bar showing hours consumed against the monthly allocation. The Solo plan at $9 per month supports up to 10 active retainers with a custom URL slug, no HourTab branding, CSV export, and email-a-summary for month-end reporting. The Studio plan at $19 per month supports unlimited retainers, a branded subdomain, two team seats, per-client headers, and rollover rules for engagements where unused hours carry forward.

Try HourTab free →