Guided workflow playbooks

These playbooks translate Avellio controls into common production goals. They are starting points, not rigid standards. Adjust the checks to the publication, editorial policy, and accepted design exceptions.

Proof a client document before approval#

Goal: catch clear copy and spacing defects without overwhelming the reviewer.

Start with: INSPECT Conservative Proofing, AUTO locale, All Pages for a small document or Page Range for a long one, Live Mode off.

1. Save a review copy.
2. Run Typography Audit.
3. Navigate Double Spaces, Repeated Words, Straight Quotes, Punctuation Spacing, Ellipsis, Non-breaking Spaces, Empty Paragraphs, and Trailing Spaces.
4. Open Fixes and inspect the Fix Plan.
5. Apply the six-action Safe Clean batch only if its candidate groups suit the document.
6. Use Review Queue for contextual findings.
7. Run Typography Audit again and export the Typography and Fix reports.

REVIEW Treat repeated words, punctuation in technical strings, and locale-sensitive quotes as editorial evidence. Do not assume every highlighted occurrence is an error.

Success looks like: the final audit is current, the obvious-defect count is reduced, remaining exceptions are understood, and the delivery copy contains no Avellio diagnostics.

Audit a book or long-form article#

Goal: review editorial consistency, line endings, rhythm, semantic conventions, and fragile manual breaks.

Start with: Editorial Strict, AUTO locale when paragraph languages are maintained, and a representative chapter or Page Range before All Pages.

1. Run a Style Integrity Audit first to understand paragraph-style usage and accumulated overrides.
2. Use Editorial Strict on a representative section.
3. Review Widows & Orphans, Short Last Lines, Hyphenation, Line-height Rhythm, Paragraph Spacing, Tracking Drift, Style Drift, dates, abbreviations, capitalization, and Break Audit findings.
4. Rivers detection is geometry-intensive. Use it on short stories or selected sections before enabling it across the publication.
5. Fix text-level problems conservatively, then resolve composition issues in InDesign.
6. Repeat the audit for each production milestone or complete chapter group.

REVIEW A soft return, short final line, or manual page break can be a deliberate editorial composition choice. Navigate before changing it.

Success looks like: headings and body styles behave consistently, manual composition choices are intentional, semantic conventions match the house style, and the final chapter-level audits use the same settings.

Audit a corporate or financial report#

Goal: protect data credibility and maintain a controlled style system.

Start with: Corporate Report and an explicit locale when the publication follows one regional standard.

1. Run Style Integrity Audit and examine dangerous local overrides, duplicate style patterns, and rogue fonts.
2. Run Typography Audit with Corporate Report.
3. Prioritize dates, number separators, currency logic, abbreviations, capitalization, paragraph spacing, indentation, alignment, column balance, hierarchy, and Break Audit findings.
4. Use Safe Clean for unambiguous whitespace and range/unit fixes.
5. Review dates, numbers, currency placement, and abbreviations manually; these conversions are intentionally preview-only.
6. Export the Typography and Override reports for the production record.

CAUTION A mechanically changed number separator or date order can change meaning. Confirm the locale and source data rather than normalizing by appearance alone.

Success looks like: financial conventions are consistent, headings and styles are controlled, the report schema explains locale findings, and no semantic value was changed without review.

Review a magazine or visual editorial layout#

Goal: combine design-system QA with composition and page-level typography.

Start with: Style Heatmap or Override Detection, followed by Magazine Layout.

1. Use Style Heatmap to locate dominant and rare styles.
2. Run Override Detection at Normal sensitivity and review Critical, Geometric, and Styling groups.
3. Run Style Integrity Audit and inspect Style Hygiene, Overrides, Duplicates, and Assets.
4. Run Typography Audit with Magazine Layout.
5. Prioritize rag quality, line-height rhythm, paragraph spacing, tracking drift, column balance, hierarchy, grid alignment, font saturation, short lines, and hyphenation.
6. Resolve layout findings visually in InDesign rather than attempting broad text normalization.

REVIEW Editorial layouts often contain intentional exceptions. Likely-intent and risk grouping in Style Hygiene helps separate deliberate design from design-system erosion.

Success looks like: exceptions are intentional and explainable, layout rhythm is coherent, style drift is controlled, and the clean proof PDF contains no diagnostic rendering.

Audit a multilingual publication#

Goal: apply language-aware typography without forcing one convention onto every paragraph.

Start with: Multilingual QA, AUTO locale, and correctly assigned InDesign paragraph languages.

1. Verify language assignments in representative paragraphs before the audit.
2. Run Typography Audit with Multilingual QA.
3. Review Resolved Locale, Locale Hint, Locale Source Rule, Specificity, and Locale Hint Confidence in the exported report.
4. Navigate quote, punctuation, date, number, currency, abbreviation, unit-spacing, and hyphenation findings by language.
5. Use Review Queue for exact Czech or Polish short-preposition spacing and locally unambiguous apostrophe or quote cases.
6. Keep ambiguous quote pairing, date order, number formats, currencies, and abbreviations manual.

REVIEW Brand names, quotations in another language, code, addresses, URLs, and unassigned text can produce a convention that differs from the surrounding paragraph. Read the evidence before correcting it.

Success looks like: paragraph language and resolved locale agree where expected, exceptions are deliberate, and the report provides enough explainability for a language reviewer.

Prepare a document for handoff or archive#

Goal: deliver a maintainable InDesign file with evidence of the final QA state.

Start with: the same profiles, locale, thresholds, and scope used by the production team.

1. Run Style Integrity Audit and export the Override Report.
2. Review Style Hygiene for overrides, duplicates, risk, likely intent, and assets.
3. Run the final Typography Audit.
4. Apply or document remaining corrections.
5. Run both authoritative audits again after the last change.
6. Export final reports and record the Avellio version and settings.
7. Use Erase Highlights, accept cleanup when closing Avellio, and inspect a proof PDF.
8. Package the clean InDesign project according to the team's production process.

CAUTION Do not use Reset Text to Style as a handoff cleanup shortcut. It can remove intentional local formatting throughout the document.

Success looks like: another operator can understand the style system, reproduce the audit settings, find accepted exceptions, and open a clean document without Avellio diagnostics.