Choose by task · verify the result

Compare by task

Filter 16 practical tasks and compare evidence, actions and verification.

Build 2.0.5 source review30 October 2026Web comparison guide

Choose a category or search for a symptom. Each task identifies where to start, the role of all four tools, a practical route and the evidence that would make the result useful. Expand a card for the complete comparison.

Find your production task

Output & assets · OutputMissing images, links or resolutionStart: InDesign PreflightCompare roles & next steps

Start with InDesign PreflightStart with the output requirements, because a typographic inspection does not establish the state of linked artwork.

InDesign Preflight
Use the active profile and intended layer/page options to identify relevant asset problems.
Avellio 2.0
Outside asset validation; inspect typography after restoring the intended artwork.
GREP Find/Change
Text-pattern search does not validate linked artwork.
Human review
Confirm the right replacement, crop and appearance in the final proof.

A practical route

  1. Select the job’s Preflight profile and inspect the reported asset condition.
  2. Restore or update the intended link; check resolution against the job requirement.
  3. Recheck Preflight and view the affected page in the exported proof.
Verify the result

The intended asset is present, the relevant output checks pass and the proof shows the right crop and content.

Keep in mind: A green profile checks its configured conditions, not every possible output or design requirement.

Output & assets · StylesMissing fonts versus unexpected font useStart: InDesign PreflightCompare roles & next steps

Start with InDesign PreflightFirst establish font availability. Then distinguish an available but unintended font from a genuinely missing one.

InDesign Preflight
Start here for missing-font output conditions under the active profile.
Avellio 2.0
Use Styles evidence to investigate supported local formatting and the intended style baseline.
GREP Find/Change
Use Find/Change formatting criteria when a known font/formatting pattern needs locating.
Human review
Approve the intended font, licensed production choice and reflow.

A practical route

  1. Resolve missing-font conditions in InDesign before judging final composition.
  2. Inspect Styles and compare an unexpected font with the intended named styles.
  3. Make the intended native formatting/style decision, then check reflow and Preflight.
Verify the result

Required fonts are available and the intended style system and final layout have been reviewed.

Keep in mind: A font-name finding is not a promise of an eligible single-property Preview reset.

Output & assets · White SpaceOverset text and terminal-frame fitStart: Preflight + White SpaceCompare roles & next steps

Start with Preflight + White SpaceOverset is both an output risk and a layout problem; detection and choosing a good fit are separate decisions.

InDesign Preflight
Use configured overset checks to identify the technical output risk.
Avellio 2.0
Review Copyfit evidence; eligible targets can offer typographic alternatives or terminal-frame bottom expansion.
GREP Find/Change
A text pattern cannot determine an acceptable frame expansion or complete story fit.
Human review
Approve frame geometry, retained copy and surrounding layout.

A practical route

  1. Locate the real threaded story and confirm the intended frame geometry.
  2. Read the offered strategy. A frame-fit Preview in layout is a live change; typographic Review details is panel-only.
  3. Apply or Revert deliberately; reinspect and check native overset and the nearby page.
Verify the result

The intended story fits, relevant output checks pass and no unacceptable geometry or reflow remains.

Keep in mind: No safe candidate is a valid result. The solver does not promise arbitrary frame reshaping.

Composition · White SpaceWidows, orphans and short last linesStart: Avellio + designerCompare roles & next steps

Start with Avellio + designerThe concern depends on composed line and page/frame relationships, not just matching words.

InDesign Preflight
Technical checks do not replace visual paragraph-boundary review.
Avellio 2.0
Locate White Space / Copyfit evidence and review an eligible constrained alternative.
GREP Find/Change
Use only a deliberately authored narrow pattern; it cannot decide the final composed boundary.
Human review
Decide whether the ending suits the text role and design.

A practical route

  1. Inspect a representative scope and locate the actual paragraph boundary.
  2. Review Keep Options, the paragraph role and any offered Before/After evidence.
  3. Keep a justified result and inspect the neighbouring spread and full affected story.
Verify the result

The target ending improves without creating overset, worse neighbouring breaks or lost editorial intent.

Keep in mind: A short title can be intentional; minimum paragraph-length eligibility is not a widow definition.

Composition · White SpaceRivers, rag and text textureStart: Avellio + designerCompare roles & next steps

Start with Avellio + designerStart with composed-layout evidence, then judge the actual reading texture of the page.

InDesign Preflight
Output checks do not judge whether spacing texture looks acceptable.
Avellio 2.0
Read the relevant river/texture evidence and compatible target metrics, including unavailable coverage.
GREP Find/Change
Character matches do not measure a visual whitespace corridor across composed lines.
Human review
Judge rhythm, density, measure and the surrounding design.

A practical route

  1. Inspect comparable text under the intended profile, scope and settings.
  2. Locate the corridor or texture concern; compare target deltas and side effects of any offered alternative.
  3. Apply only a justified result, obtain fresh evidence and view nearby columns.
Verify the result

The relevant local measure and visible page improve together, with acceptable fit and reflow.

Keep in mind: A global score gain alone does not establish that the selected river improved.

Styles · StylesWhere styles are usedStart: Avellio Style catalogCompare roles & next steps

Start with Avellio Style catalogSeparate style identity, relative frequency and override diagnostics before reading the colours.

InDesign Preflight
Profile results are a different view from a style-distribution map.
Avellio 2.0
Use Style Map, Style Frequency Heatmap or Override Map for the specific supported question.
GREP Find/Change
Formatting searches can locate a known pattern, rather than explain the complete style distribution.
Human review
Confirm whether each role and apparent outlier belongs in the design.

A practical route

  1. Choose paragraph/character styles and a supported map scope in Style catalog.
  2. Show the intended map explicitly and read unavailable/capped counts.
  3. Clear Style Map with its own action before final delivery.
Verify the result

The map answers the intended question and retained document diagnostics are cleared deliberately.

Keep in mind: A heat colour is not severity or a permanent style identity. Showing a map replaces issue marks.

Styles · StylesUnintended local formattingStart: Avellio Styles + style ownerCompare roles & next steps

Start with Avellio Styles + style ownerFind the exact property and trusted baseline before deciding that a formatting difference is accidental.

InDesign Preflight
Some formatting conditions are profile-dependent; they do not decide editorial intention.
Avellio 2.0
Use supported baseline/override evidence; Preview reset is for one eligible exact local property.
GREP Find/Change
Use explicit formatting criteria only after the intended pattern is understood.
Human review
Protect deliberate emphasis and approve the canonical baseline.

A practical route

  1. Identify the intended paragraph/character styles and affected property.
  2. If eligible and unintended, choose Preview reset and inspect the live document change.
  3. Apply or Revert, then inspect again and check adjacent composition.
Verify the result

Only the intended local property changed; named styles and legitimate emphasis remain correct.

Keep in mind: Font names, ambiguous baselines and nested targets can remain review-only. Reset does not redefine styles.

Styles · StylesStyle families, definitions and apparent duplicatesStart: Style owner + Avellio evidenceCompare roles & next steps

Start with Style owner + Avellio evidenceCatalog differences need design ownership; similarity alone is not a reason to merge or delete styles.

InDesign Preflight
Configured technical text checks do not establish the intended style architecture.
Avellio 2.0
Use catalog and supported consistency evidence to prioritize manual review.
GREP Find/Change
Find/Change can target a known style or formatting condition after the owner decides.
Human review
Own definitions, inheritance, deliberate variants and any native consolidation.

A practical route

  1. Review style names, groups, definitions and their actual use in representative text.
  2. Separate a real design inconsistency from a deliberate variant or incomplete evidence.
  3. Make approved definition changes in InDesign, then inspect affected text and reflow.
Verify the result

The style system remains intentional and changes were verified in the layouts that use it.

Keep in mind: Do not infer a general merge/delete or document-wide cleanup command from a style finding.

Editorial & language · TypographyRepeated spaces, punctuation and ellipsisStart: Avellio for discovery; GREP for an approved patternCompare roles & next steps

Start with Avellio for discovery; GREP for an approved patternUse findings to discover the issue; use a narrowly defined transformation only after exceptions are understood.

InDesign Preflight
These editorial spacing decisions are outside ordinary output-condition review.
Avellio 2.0
Locate supported rule evidence, exact text where available and the intended language context.
GREP Find/Change
Useful for a precisely approved expression, replacement and run-time scope.
Human review
Review quotations, code, alignment and intended typography before changing copy.

A practical route

  1. Read representative occurrences and show nonprinting characters where helpful.
  2. Make a deliberate native edit or use a tested, scoped Find/Change query.
  3. Inspect again, compare text with the source and check the resulting line endings.
Verify the result

The intended patterns changed without altering code, quoted source or deliberate spacing structures.

Keep in mind: A finding does not imply a universal Avellio text-replacement action or a safe Change All.

DOUBLE_SPACESPACE_BEFORE_PUNCTUATIONELLIPSIS_SEQUENCE
Editorial & language · TypographyQuotes, apostrophes and language conventionsStart: Avellio + language editorCompare roles & next steps

Start with Avellio + language editorThe complete quotation, nesting and resolved locale matter more than the isolated glyph.

InDesign Preflight
A valid output profile does not establish the publication’s quotation convention.
Avellio 2.0
Surface supported quote/punctuation evidence under the actual inspection policy.
GREP Find/Change
Use only a narrow approved case; do not apply a universal straight-to-curly replacement.
Human review
Determine quote roles, literal primes, source fidelity and house style.

A practical route

  1. Check paragraph language, resolved scan policy and the complete quoted span.
  2. Compare the built-in locale guide with the actual team/publication convention.
  3. Make the justified targeted edit and reinspect nearby punctuation and line boundaries.
Verify the result

The intended quote roles and source meaning survive; the applicable convention is documented.

Keep in mind: The documentation’s locale comparison shows defaults, not a live reading of a custom profile.

STRAIGHT_QUOTESMART_QUOTE
Editorial & language · TypographyDates, amounts, currency and unitsStart: Avellio + source ownerCompare roles & next steps

Start with Avellio + source ownerA visual format difference must be separated from the factual value it represents.

InDesign Preflight
Output checks cannot determine whether a factual date or amount is correct.
Avellio 2.0
Review supported locale-sensitive dates, numeric formats, currencies, units and abbreviation evidence.
GREP Find/Change
Useful only after the intended source value and exact conversion rule are established.
Human review
Confirm original values, currencies, dates and publication convention.

A practical route

  1. Check the authoritative source and actual language policy before replacing punctuation.
  2. Review comparable values and exceptions; use a targeted native edit or approved controlled query.
  3. Recheck source values and fresh inspection, then inspect the resulting composition.
Verify the result

Values and dates retain their meaning while their intended typography is consistent.

Keep in mind: 03/04/2026 and an isolated currency symbol can be ambiguous. Never guess the fact from the separators.

DATE_FORMATNUM_FORMATCURRENCY_LOGICUNIT_SPACE
Editorial & language · TypographyA known project-specific text transformationStart: GREP Find/ChangeCompare roles & next steps

Start with GREP Find/ChangeWhen the exact expression and replacement are already approved, a saved query is direct and repeatable.

InDesign Preflight
Recheck output conditions affected by resulting reflow.
Avellio 2.0
Inspect supported consequences before/after; do not assume every custom pattern has a matching rule.
GREP Find/Change
Use a saved, tested query; choose the search range each time it runs.
Human review
Approve representative matches, exceptions, the transformation and the result.

A practical route

  1. Save a working copy and test the exact expression, replacement and formatting criteria.
  2. Set the actual search range and inspect representative matches before any broad operation.
  3. Review replacements, compare source meaning and rerun affected Avellio and output checks.
Verify the result

The approved transformation ran only in the intended scope and its text/formatting effects were verified.

Keep in mind: Saved queries do not save the search range. A correct match does not by itself justify a replacement.

Editorial & language · EditorialFacts, names, tone and editorial meaningStart: Human editor + authoritative sourceCompare roles & next steps

Start with Human editor + authoritative sourceThe publication owner must establish what is true and appropriate before automation locates instances.

InDesign Preflight
Technical output checks do not validate names, facts or tone.
Avellio 2.0
Can surface related supported typography or structural evidence; does not establish factual truth.
GREP Find/Change
Locate known spellings once the correct form has been established.
Human review
Own facts, names, clarity, audience, meaning and final editorial decisions.

A practical route

  1. Ask the responsible editor and verify the source.
  2. Find the relevant occurrences without assuming every similar string refers to the same thing.
  3. Make approved changes and proofread them in full context and in the final output.
Verify the result

A responsible reviewer approved the correct content against a suitable source.

Keep in mind: None of the compared automation is a complete spelling, grammar or factual authority.

Team & publication · All areasComparable team standards and review evidenceStart: Avellio Settings + team ownerCompare roles & next steps

Start with Avellio Settings + team ownerAn active policy revision and fresh scan provenance matter more than an identical profile name.

InDesign Preflight
Use the named job profile separately for technical output conditions.
Avellio 2.0
Use the profile library, active revision, Results from and compatible included modules.
GREP Find/Change
Retain the agreed query, expression and actual scope as separate transformation evidence.
Human review
Own policy changes, deliberate exceptions and acceptance criteria.

A practical route

  1. Confirm the intended saved/active Avellio profile and named output requirements.
  2. Apply authorized changes and inspect again with the agreed scope and modules.
  3. Record the policy revision, review decisions and evidence that belong to the same document version.
Verify the result

The team can identify which policy and scope produced the retained evidence.

Keep in mind: Viewing a library profile is not activation; profile rollback does not undo document corrections.

Team & publication · PublicationA Book or multi-document publicationStart: Avellio Publication + production ownerCompare roles & next steps

Start with Avellio Publication + production ownerExpected membership, successful scans and compatible evidence must all be checked separately.

InDesign Preflight
Check technical conditions of the intended documents with the appropriate profile and scope.
Avellio 2.0
Collect completed summaries or serially inspect selected already open documents; inspect integrity warnings.
GREP Find/Change
Choose explicit run scope; do not equate all open documents with the intended Book.
Human review
Reconcile chapters, intentionally different sections, missing work and final proofs.

A practical route

  1. Test one representative chapter, then confirm expected documents and compatible policy.
  2. Read active Book and queue eligible open chapters, or intentionally select the required open documents.
  3. Resolve failed/missing/partial evidence and report warnings before completing and sharing the collection.
Verify the result

The intended membership is accounted for and the report’s coverage and warnings are understood.

Keep in mind: Closed chapters are not secretly opened. FINAL records collection completion, not defect-free approval.

Team & publication · All areasFinal handoff and approvalStart: Production owner + human approverCompare roles & next steps

Start with Production owner + human approverA final decision requires matching technical, typographic and editorial evidence from the intended version.

InDesign Preflight
Use the final named profile and resolve its blocking output conditions.
Avellio 2.0
Fresh intended scope/modules, reviewed exceptions, appropriate JSON report and cleared active visualization.
GREP Find/Change
Retain any approved transformation record; a saved query alone proves no completed run.
Human review
Inspect a clean exported proof and explicitly approve the deliverable.

A practical route

  1. Finish any live preview; obtain fresh inspection and review omissions and accepted exceptions.
  2. Clear issue marks or the active Style Map with its own action; check the intended document and final Preflight.
  3. View the exported proof independently and obtain approval; review report labels before sharing.
Verify the result

A named approver accepts the clean proof and the retained reports describe the intended version and coverage.

Keep in mind: Counters, a green status, an addressed flag and a FINAL report are evidence, not approval.

Read the comparison fairly

“Start with” identifies the most useful first move, not a winner for every part of the job. An unsupported operation remains unsupported even when a related finding exists. Availability and actual coverage matter more than the number of visible results.

The dots identify current Typography rule colours, not severity. Composition, Styles and Publication tasks do not acquire a Typography ID merely because they appear in this comparison. Open the linked Colour Atlas for exact rule context.

For omitted nested structures and declared host/platform limits, read Compatibility & Known Limits and tables and footnotes.

Sources and current boundaries

Avellio guidance describes build 2.0.5 source review within the 2.0.0 documentation collection. Read the current delivery boundaries and compatibility evidence. This comparison does not claim fresh native-host acceptance.