Team workflow and handoff

Avellio is most valuable when the team agrees who interprets each kind of evidence. The product supplies findings and reports; the team owns the editorial and design decisions.

Role	Primary Avellio responsibility	Recommended handoff evidence
Designer / template owner	Style Heatmap, Override Detection, Style Hygiene, hierarchy, rhythm, grid and layout findings	Style Audit Summary and Override Report
Editor / proofreader	Copy, punctuation, quote, semantic, locale and repeated-word findings	Filtered Typography Report with decisions
Production specialist	Break Audit, scope, threading, report freshness, diagnostics cleanup and final proof	Final Typography and Fix Reports plus delivery checklist
Language reviewer	Paragraph language, resolved locale, quote, date, number, currency and abbreviation conventions	Locale-related CSV columns and accepted exceptions
Project lead	Consistent profile, scope and thresholds across milestones	Recorded audit settings, version and final report set

Record accepted exceptions

The production release does not include a complete user-facing occurrence-level suppression manager. For team work, keep a short external acceptance log containing:

issue type;
page or story;
affected style;
reason the finding is intentional;
reviewer and date;
whether the exception must be rechecked after reflow.

This prevents the next operator from “fixing” an intentional design choice and provides context when counts remain above zero.

Make reports useful to the recipient

Do not send an unfiltered CSV without explaining the audit conditions. Include:

Avellio version;
profile and semantic strictness;
locale mode;
analysis scope and threaded-story setting;
any changed thresholds;
whether the report comes from the final full audit;
which findings are resolved, accepted, or still awaiting review.

Performance planning

Choose the least expensive mode that answers the current question, then use the full audit at the production milestone.

Need	Efficient starting choice	When to expand
Quick local composition check	Current Spread, Native Shading, focused checks	Expand after the layout stabilizes.
Repeated editing feedback	Incremental Updates and Live Mode	Run a full audit before reports or fixes.
Style distribution overview	Style Heatmap with Co.Text	Add Override Detection when local formatting risk matters.
Local override QA	Normal sensitivity and relevant filters	Use Strict only for tightly governed templates.
River analysis	Selection, short story, or small Page Range	Expand only if geometry performance is acceptable.
Long publication QA	Representative chapter, then staged Page Ranges	Finish with the agreed full-document audit.
Maximum internal coverage	Deep Audit	Use after faster profiles have established the baseline.

Success looks like: every recipient understands what was checked, what remains a human decision, and whether the report is current enough to support delivery.

Record accepted exceptions#

Make reports useful to the recipient#

Performance planning#

Record accepted exceptions

Make reports useful to the recipient

Performance planning