Turn a mini-course report into one useful improvement decision

Start with the question you need the report to answer

Choose a bounded question such as “Where do readers stop?” or “Which option attracts a mistaken interpretation?” Avoid opening a spreadsheet and searching for a flattering number. A report can guide an editorial decision even when it cannot establish why someone left or whether they can perform the workplace task.

Mini Course Generator documents an .xls download through Report → Download Report, with another route through course Analytics. The described data includes learner responses and completion information. This guide has not inspected a live learner export; column names and availability should be checked in your actual file.

Keep the original and make a working copy

1. Record the course, source version, export time and any report filters shown.
2. Preserve the unedited file in the appropriate restricted location. Work in a copy.
3. Identify what a row represents: person, attempt or another unit. Do not assume repeated rows are duplicates.
4. Check whether a blank means not reached, unanswered, unavailable or something else. Leave it unknown until the report supports a meaning.
5. Separate responses from different lesson versions before comparing answer patterns.
6. Remove names and addresses from any example you share outside the authorized review group.

These are analysis safeguards, not a claim that every export contains attempt IDs or version fields. If the file lacks the context needed for a comparison, record that limitation rather than constructing a precise-looking rate.

Work through a small fictional triage log

Suppose a synthetic review contains five cases: A answered the overlap question correctly; B and C chose “the request is listed, so confirm”; D reached the question but left it blank; E never reached it. These letters are invented labels, not learners or an actual product report.

• B and C: inspect whether the earlier explanation clearly separates request status from confirmation. Their matching wrong answer suggests a useful place to review, not proof of the cause.
• D: preserve the unanswered state. Do not silently count it as the same misconception.
• E: inspect the preceding path and access experience before rewriting the question.
• A: a correct response to this item remains narrower evidence than successful workplace performance.

You now have two possible improvements: clarify the status distinction and investigate a pre-question barrier. Keep them separate so a later comparison can show which material actually changed.

Choose a revision and define what would challenge it

A specific revision might replace “enter the booking” with “record the request; confirmation follows the overlap check” and add a contrasting status example. Leave unrelated wording alone. Note the source passage, changed lesson element and expected sign: fewer selections of the request-list option among comparable answered attempts.

The strongest counterexplanation is that a new audience or a changed assignment caused the difference. Use the same question version and a comparable group where possible; if those conditions differ, describe the observation rather than claiming the revision caused improvement. Small numbers should stay visible, not be hidden behind percentages.

Share the decision, not an unnecessary list of people

An editorial note can say “Two of three answered synthetic cases selected the request-list option; one additional case was unanswered and one did not reach the question.” That is more transparent than “most learners failed.” Keep the real report’s access limited to its legitimate purpose and avoid placing personal response data in public examples or unrelated AI tools.

Use the completion and denominator guide for careful interpretation and the revision map to track every answer explanation affected by a changed rule. A report is useful when it produces a justified action—or a justified decision not to change the lesson.