Comparison Quick Reference
Choose a task, get a useful first action and know what to verify before moving on.
A desk reference for choosing your next move. Output conditions → Preflight. Supported typography, styles and composition → Avellio. An approved exact transformation → GREP. Meaning and acceptance → people. Use the layers together when the task needs them.
What do you need to solve?
Choose a task for a concrete first step, a short route and a way to verify the result. The advice describes 2.0.5 source review, within the Avellio 2.0.0 documentation collection.
Choose a task to show a route below.
Missing images, links or resolution
Start with InDesign PreflightStart with the output requirements, because a typographic inspection does not establish the state of linked artwork.
A practical route
- Select the job’s Preflight profile and inspect the reported asset condition.
- Restore or update the intended link; check resolution against the job requirement.
- Recheck Preflight and view the affected page in the exported proof.
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.
Compare all four roles and open the detailed controls
- 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.
Missing fonts versus unexpected font use
Start with InDesign PreflightFirst establish font availability. Then distinguish an available but unintended font from a genuinely missing one.
A practical route
- Resolve missing-font conditions in InDesign before judging final composition.
- Inspect Styles and compare an unexpected font with the intended named styles.
- Make the intended native formatting/style decision, then check reflow and Preflight.
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.
Compare all four roles and open the detailed controls
- 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.
Overset text and terminal-frame fit
Start with Preflight + White SpaceOverset is both an output risk and a layout problem; detection and choosing a good fit are separate decisions.
A practical route
- Locate the real threaded story and confirm the intended frame geometry.
- Read the offered strategy. A frame-fit Preview in layout is a live change; typographic Review details is panel-only.
- Apply or Revert deliberately; reinspect and check native overset and the nearby page.
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.
Compare all four roles and open the detailed controls
- 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.
Widows, orphans and short last lines
Start with Avellio + designerThe concern depends on composed line and page/frame relationships, not just matching words.
A practical route
- Inspect a representative scope and locate the actual paragraph boundary.
- Review Keep Options, the paragraph role and any offered Before/After evidence.
- Keep a justified result and inspect the neighbouring spread and full affected story.
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.
Compare all four roles and open the detailed controls
- 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.
Rivers, rag and text texture
Start with Avellio + designerStart with composed-layout evidence, then judge the actual reading texture of the page.
A practical route
- Inspect comparable text under the intended profile, scope and settings.
- Locate the corridor or texture concern; compare target deltas and side effects of any offered alternative.
- Apply only a justified result, obtain fresh evidence and view nearby columns.
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.
Compare all four roles and open the detailed controls
- 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.
Where styles are used
Start with Avellio Style catalogSeparate style identity, relative frequency and override diagnostics before reading the colours.
A practical route
- Choose paragraph/character styles and a supported map scope in Style catalog.
- Show the intended map explicitly and read unavailable/capped counts.
- Clear Style Map with its own action before final delivery.
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.
Compare all four roles and open the detailed controls
- 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.
Unintended local formatting
Start with Avellio Styles + style ownerFind the exact property and trusted baseline before deciding that a formatting difference is accidental.
A practical route
- Identify the intended paragraph/character styles and affected property.
- If eligible and unintended, choose Preview reset and inspect the live document change.
- Apply or Revert, then inspect again and check adjacent composition.
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.
Compare all four roles and open the detailed controls
- 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.
Style families, definitions and apparent duplicates
Start with Style owner + Avellio evidenceCatalog differences need design ownership; similarity alone is not a reason to merge or delete styles.
A practical route
- Review style names, groups, definitions and their actual use in representative text.
- Separate a real design inconsistency from a deliberate variant or incomplete evidence.
- Make approved definition changes in InDesign, then inspect affected text and reflow.
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.
Compare all four roles and open the detailed controls
- 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.
Repeated spaces, punctuation and ellipsis
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.
A practical route
- Read representative occurrences and show nonprinting characters where helpful.
- Make a deliberate native edit or use a tested, scoped Find/Change query.
- Inspect again, compare text with the source and check the resulting line endings.
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.
Compare all four roles and open the detailed controls
- 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.
Quotes, apostrophes and language conventions
Start with Avellio + language editorThe complete quotation, nesting and resolved locale matter more than the isolated glyph.
A practical route
- Check paragraph language, resolved scan policy and the complete quoted span.
- Compare the built-in locale guide with the actual team/publication convention.
- Make the justified targeted edit and reinspect nearby punctuation and line boundaries.
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.
Compare all four roles and open the detailed controls
- 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.
Dates, amounts, currency and units
Start with Avellio + source ownerA visual format difference must be separated from the factual value it represents.
A practical route
- Check the authoritative source and actual language policy before replacing punctuation.
- Review comparable values and exceptions; use a targeted native edit or approved controlled query.
- Recheck source values and fresh inspection, then inspect the resulting composition.
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.
Compare all four roles and open the detailed controls
- 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 known project-specific text transformation
Start with GREP Find/ChangeWhen the exact expression and replacement are already approved, a saved query is direct and repeatable.
A practical route
- Save a working copy and test the exact expression, replacement and formatting criteria.
- Set the actual search range and inspect representative matches before any broad operation.
- Review replacements, compare source meaning and rerun affected Avellio and output checks.
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.
Compare all four roles and open the detailed controls
- 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.
Facts, names, tone and editorial meaning
Start with Human editor + authoritative sourceThe publication owner must establish what is true and appropriate before automation locates instances.
A practical route
- Ask the responsible editor and verify the source.
- Find the relevant occurrences without assuming every similar string refers to the same thing.
- Make approved changes and proofread them in full context and in the final output.
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.
Compare all four roles and open the detailed controls
- 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.
Comparable team standards and review evidence
Start with Avellio Settings + team ownerAn active policy revision and fresh scan provenance matter more than an identical profile name.
A practical route
- Confirm the intended saved/active Avellio profile and named output requirements.
- Apply authorized changes and inspect again with the agreed scope and modules.
- Record the policy revision, review decisions and evidence that belong to the same document version.
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.
Compare all four roles and open the detailed controls
- 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 Book or multi-document publication
Start with Avellio Publication + production ownerExpected membership, successful scans and compatible evidence must all be checked separately.
A practical route
- Test one representative chapter, then confirm expected documents and compatible policy.
- Read active Book and queue eligible open chapters, or intentionally select the required open documents.
- Resolve failed/missing/partial evidence and report warnings before completing and sharing the collection.
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.
Compare all four roles and open the detailed controls
- 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.
Final handoff and approval
Start with Production owner + human approverA final decision requires matching technical, typographic and editorial evidence from the intended version.
A practical route
- Finish any live preview; obtain fresh inspection and review omissions and accepted exceptions.
- Clear issue marks or the active Style Map with its own action; check the intended document and final Preflight.
- View the exported proof independently and obtain approval; review report labels before sharing.
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.
Compare all four roles and open the detailed controls
- 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.
Browse all 16 tasks in the full comparison
- Missing images, links or resolution — InDesign Preflight
- Missing fonts versus unexpected font use — InDesign Preflight
- Overset text and terminal-frame fit — Preflight + White Space
- Widows, orphans and short last lines — Avellio + designer
- Rivers, rag and text texture — Avellio + designer
- Where styles are used — Avellio Style catalog
- Unintended local formatting — Avellio Styles + style owner
- Style families, definitions and apparent duplicates — Style owner + Avellio evidence
- Repeated spaces, punctuation and ellipsis — Avellio for discovery; GREP for an approved pattern
- Quotes, apostrophes and language conventions — Avellio + language editor
- Dates, amounts, currency and units — Avellio + source owner
- A known project-specific text transformation — GREP Find/Change
- Facts, names, tone and editorial meaning — Human editor + authoritative source
- Comparable team standards and review evidence — Avellio Settings + team owner
- A Book or multi-document publication — Avellio Publication + production owner
- Final handoff and approval — Production owner + human approver
Four questions at a glance
Will the file meet our output conditions?
Check the job’s configured technical requirements and intended coverage.
Where should we inspect typography, styles and composition?
Locate supported evidence, understand context and verify a justified decision.
Do we already know the exact pattern and change?
Run a tested expression with deliberate formatting criteria and scope.
Is the result correct, appropriate and ready to approve?
Own meaning, intentional design, source accuracy and the final proof.
The six-step handoff check
- Identify the version. Save a working copy and confirm the intended document or publication membership.
- Choose the checks. Use the job’s output profile, appropriate Avellio modules/scope and actual language policy.
- Discover before changing. Inspect representative evidence. Use GREP only for an approved expression and deliberately chosen run-time scope.
- Decide and verify. Make an eligible supported change, a deliberate native edit or an intentional review decision. Finish Apply/Revert and inspect again after edits.
- Clean and record. Clear issue marks or the active Style Map with its own action. Retain the matching report and accepted exceptions; review export labels before sharing.
- Approve the proof. Resolve final technical blockers and inspect the clean exported PDF. The responsible human approves it.
Before you trust a status
- Green Preflight: the active profile and coverage found no relevant condition; check the actual job requirements.
- Fewer Avellio findings: check filters, review states, scope, included modules and freshness before claiming an improvement.
- GREP match: the expression matched; verify that this context needs the approved change. A saved query does not save its search range.
- Preview: read whether it is panel-only or a live document change; finish the applicable Apply/Revert workflow.
- Queued proposal: retained for later revalidation, not applied in a batch.
- FINAL publication report: collection completed; check intended membership, warnings and independent approval.
Need the full reasoning?
Comparison Guide explains the tools and includes 16 task comparisons, eight worked examples, current action effects and team acceptance gates. Solutions provides complete practical routes. Typography Rules explains the principles and exact rule colours.
Typography recommendations explain findings and sometimes propose replacement text. Found / Suggested are read-only evidence, not Apply commands. Verify meaning and locale before manual edits; rescan afterwards.
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.