Published 13 September 2026
QA should improve the production system
If reviewers repeatedly fix the same problem, the organisation does not only have a content-quality issue. It has a production-process issue.
An issue log turns review findings into operational data. Instead of correcting a defect and forgetting it, the team records what failed, why it failed and where the prevention action belongs.
Record defects in a useful way
An effective issue log does not need to be complicated. For each meaningful defect, capture:
- the content asset or version;
- the issue type;
- the evidence or example;
- the severity;
- the corrective action;
- the owner; and
- whether the fix belongs in the prompt, source pack, template, workflow or human review step.
Look for patterns, not isolated mistakes
One weak example may be a local defect. Five similar weak examples across different assets are a signal. Recurring problems can reveal that a prompt is too vague, the source material is incomplete, the template encourages unnecessary repetition, or the handoff between subject-matter expert and instructional designer is unclear.
The review team should periodically ask: Which defects are we paying to find again and again?
Push the correction upstream
Once a pattern is visible, change the earliest practical point in the workflow. For example:
- If AI invents references, restrict generation to an approved source set and require citation traceability.
- If assessments drift away from objectives, make objective-to-item mapping part of the input template.
- If content is consistently too long, add explicit scope and duration constraints before generation.
- If tone is inconsistent, add a short style specification and examples to the production brief.
The best QA system should reduce future QA effort
Quality assurance is often treated as a final inspection function. A stronger model treats it as a feedback loop. Review identifies defects, issue logs identify patterns, and the production system is changed so that fewer defects are created in the first place.
That is how QA becomes a productivity system rather than a permanent correction layer.