Choose the right QA layer
Design a team QA policy
Compare Avellio, InDesign Preflight, GREP Find/Change, and human proofreading by task.
Assign ownership
| Quality layer | Suggested owner | Evidence |
|---|---|---|
| Asset and output rules | Production/prepress | Named Preflight profile and final result. |
| Style-system integrity | Designer/template owner | Avellio Style Audit, Override Report, accepted exceptions. |
| Typography and locale | Typographer/editor | Avellio Typography and Fix Reports plus visual review. |
| Deterministic transformations | Production specialist | Versioned GREP query, scope, before/after sample, undo checkpoint. |
| Meaning and final approval | Editor, designer, and accountable approver | Proofreading record and approved proof PDF. |
Define pass criteria
Do not write “all automated checks must be zero” unless every rule has been tested and every intentional exception is encoded. Better acceptance criteria are:
- the named Preflight profile has no unresolved blocking conditions;
- Avellio high-risk findings are corrected, accepted, or documented;
- the Fix Plan is current and all executed actions were visually verified;
- approved GREP queries were run on the intended version and scope;
- manual-only and editorial findings have an owner;
- the cleaned final PDF was independently inspected and approved.
Measure without misleading metrics
Useful measures include unresolved blocking conditions, high-risk style overrides, report freshness, accepted exceptions, time spent on repetitive search, and rework found after proof. Do not treat an Avellio health score, Preflight green light, match count, or proofreader speed as a standalone quality score for the publication.
Release sourceThis page was generated from the Markdown companion of the verified distribution PDF.