Mad Quality Plugin
Standards Exist — But Enforcement Is Manual and Inconsistent
Turn documentation quality into a system property.
Style guides don't enforce themselves
Your team has a style guide. Maybe it's based on Microsoft Manual of Style, maybe it's custom. Either way, enforcing it relies on reviewers catching every violation manually — across hundreds or thousands of topics. (Read more: The Hidden Cost of Manual QA in Technical Documentation.)
Reviewers miss things. Different reviewers catch different issues. Standards drift as the team grows. The gap between what the style guide says and what actually ships widens over time.
Quality as a system property
Encode your standards into the workflow itself. Mad Quality scans every topic against your rules — automatically. Writers see issues as they work, not weeks later in review. Quality becomes a system property, not a reviewer's burden.
Your style guide rules live in a spreadsheet. Add, modify, or remove rules without coding. The result: consistent quality at scale, with less review effort.
Key Features
Content & Structure Validation
Thorough checks against the Microsoft Manual of Style or your custom rules, ensuring both content quality and structural integrity.
Spreadsheet-Based Rules
Add, modify, or remove quality rules in a spreadsheet — no coding required. Default rules based on Microsoft Manual of Style included.
Bulk Scanning
Scan individual topics or entire projects, ensuring consistency at scale. Find every violation in seconds, not hours of manual review.
Guided Findings
Each finding links to the relevant style guide rule for context, helping writers learn and improve as they fix issues.
Pricing
See It In Action
Mad Quality Plugin Demo
Once we discovered just how powerful the Mad Quality plugin is, it's been our 'robo editor' of choice! We have mapped dozens of our style guide conventions to Mad Quality Plugin rules. Now, it quickly finds half of the issues in every single topic, whether it's topic type mismatches, topic structure, unwanted grammar, or non-breaking spaces — and saves hours we'd otherwise have to spend on language edits!
Free or relatively inexpensive tools like the Mad Quality plugin are invaluable. These tools check the topics in your MadCap Flare projects to make sure they comply with your corporate style guide and general best practices of technical writing.
Common Questions
Will this work with our Flare setup?
Mad Quality works with MadCap Flare 2020 and later on Windows. Rules are defined in a spreadsheet — no coding required. It integrates directly into Flare's ribbon and scans individual topics or entire projects.
What if we outgrow it?
Mad Quality scales with your content. Add unlimited custom rules, scan thousands of topics, and adapt the rule set as your style guide evolves. The spreadsheet-based rule management means your team can maintain and extend it without developer support.
How long until we see results?
Within the first scan. Install the plugin, point it at a project, and you'll immediately see which topics violate your style guide rules. Teams typically reduce review cycle time by 30–50% within the first month.
Questions?
30 minutes. No commitment.