Reviewing a module
When you click a course card on the kanban, you land on the course detail page in review mode. This page is the reviewer’s main workspace.
What the review page shows
For each module in the course:
- Title and description (read-only at this stage)
- Cover image (read-only)
- Status pill — Draft / Pending / Approved / Published / Archived
- Flashcards — every card in the deck, in order
- Quiz — every question, fully rendered
You can scroll the whole course in one page, or click into individual modules for a focused review.
The big difference: you can see correct answers
When a trainer is editing a quiz, they see the correct answers (they’re writing them). When a learner is taking a quiz, they see the question and options but NOT which is correct.
When you’re reviewing, Wisteria shows the correct answers in green so you can verify them. This sounds obvious but it wasn’t always the case — early versions of Wisteria hid correct answers from reviewers too, which made it impossible to verify a quiz was accurate. We fixed it.
What you see per question type:
| Type | What’s highlighted |
|---|---|
| MCQ | Correct option in green with a ✓ marker |
| Fill in blank | Green box below the question showing ”✓ Answer: [the answer]“ |
| Matching | Each pair shown with the correct right value next to the left |
| Oral | Model answer, keywords, and pass threshold all displayed |
Question type and difficulty pills are also visible — useful when a course was AI-generated and you want to verify the mix matches what the trainer intended.
How to review effectively
A focused review pass takes 5–15 minutes per module. Things to check:
Flashcards
- Accuracy — is every front/back factually correct?
- Clarity — is the back actually understandable by a new hire?
- Voice — does it match your team’s tone?
- Hidden assumptions — does a card assume prior knowledge a learner won’t have?
- Duplicates / contradictions — do any two cards contradict each other?
Quiz
- Correct answers actually correct? Sounds obvious; AI sometimes generates plausible-looking wrong answers.
- Questions answerable from the flashcards? A quiz that tests knowledge not covered in the cards is unfair.
- Difficulty appropriate? Is the question testing something useful or something trivial?
- MCQ distractors plausible? Wrong options should be wrong-but-tempting, not obviously absurd. (Otherwise it’s a one-option quiz.)
- Fill-in-blank: is the answer exact enough? Wisteria’s matching is case-forgiving but spelling-exact. “Paris” matches; “the city Paris” doesn’t.
- Matching: are the pairs unambiguous? No “this term could match either right value.”
- Oral: model answer realistic? A model answer that reads as scripted will reject most natural phrasings.
Where to leave feedback
You don’t comment on individual cards or questions directly. The granularity is at the module section level (Details / Flashcards / Quiz).
If the issue is at the question level, write it in the section feedback: “Question 3: the correct answer is wrong — should be B, not C.”
Trainer sees this in the Queries tab.
Decisions per module
Three actions:
- Approve — module moves to
approved(ready to publish when the trainer says so) - Reject — module returns to
draft; trainer addresses feedback and resubmits - Ask a query — open a question without rejecting yet
See Approving, rejecting, querying for the full action flow.
Step-by-step vs whole-course review
Two patterns work:
- Module-by-module — review one module fully, decide, move on. Faster total time; downside is you might find an issue in module 3 that means module 1 needs to change too.
- Whole course first — scan all modules quickly, then decide. Slower total time; better at catching cross-module inconsistencies.
For complex compliance content, prefer the whole-course pattern. For routine training, module-by-module works fine.
Notifications you’ll send
Each decision fires a notification to the trainer:
- Approve — email “Module X approved”
- Reject — email with your comment
- Query — email with your question
Don’t worry about being too noisy — trainers expect feedback, that’s the whole point.
What if you’re not sure
Use Ask a query instead of Reject. The trainer responds; you decide afterwards. See The rejection-and-resubmit cycle.
Time per review
Typical per-module review time:
- Simple modules (5 cards, 5 quiz questions) — 5–10 minutes
- Medium (15 cards, 10 questions) — 15–25 minutes
- Complex (30+ cards, 15+ questions, with oral) — 45–60 minutes
If you’re consistently spending more than an hour on a module, the content might be too dense for one module — flag it to the trainer.