Primary Role: Workflow Manager
Learning Focus: Learn
Where: Workflow Editor & Mobilize AI
🎯 Why This Matters
Reports are only as good as the data behind them. When workflows are designed with reporting in mind, insights are easier to trust, compare, and act on.
📝 What Actually Drives Reporting Quality
Reporting quality is shaped by three workflow design decisions:
1️⃣ Question Design
How questions are worded
Whether the same question uses the same question-type and similar wording across different workflows
Whether questions collect discrete (not free-form) data
Consistent questions = reliable comparisons.
2️⃣ Tags
reportNamedefines how questions and workflows appear in reportsThe
reportNametag must be the same across different workflow templates in order to compare the results across those templates
Tags are how workflows become reportable data.
Only questions with a correctly configured reportName tag appear in the Workflow Drilldown report.
3️⃣ Scoring (When Used)
Custom Scoring enables comparison and prioritization
Strength Score highlights completion quality and effort
Scoring only works when it aligns with workflow intent.
Example of Custom Scoring of a Layered Process Audit.
👉 Design Rule
If you expect to report on something, make sure:
The question is designed consistently
The tag is applied consistently
Any scoring supports a real decision
🔑 Key Takeaways
Reporting starts in the workflow, not the dashboard
Question design, tags, and scoring determine insight quality
Consistency matters more than sophistication
Job Role: Workflow Manager | Permission Level: Admin / ANVL Web + ANVL Workflows | Special Rights: Workflow Management (Create)