🎯 Why This Matters
Strength Score helps you quickly understand how thoroughly a workflow was completed, not just whether it was finished. It’s a scalable way to encourage quality without reviewing every submission manually.
📝 What Strength Score Is
Strength Score is one of ANVL’s core quality metrics.
It reflects the level of effort and completeness shown when a workflow is completed.
Strength Score looks at how a workflow was completed, such as:
Whether required questions were answered
Whether users provided meaningful evidence (photos or text)
Whether the workflow required real observation or interaction
Whether the workflow took a reasonable amount of time
Strength Score does not evaluate correctness of responses.
🧠 What Strength Score Is Not
Strength Score is not:
A performance rating for individuals
A compliance score
A replacement for professional judgment
It’s a signal, not a verdict.
🛠️ How Strength Score Is Used
Strength Score is tailored to the type of workflow and program goal.
For example:
Job Safety Assessments (JSAs) may emphasize detailed text, photos, and time spent
Layered Process Audits (LPAs) may emphasize answering required questions and identifying issues
Each workflow’s Strength Score reflects what “quality” means for that workflow, not a one-size-fits-all standard.
⚠️ When Strength Score Is Helpful
Strength Score is most useful when:
Workflows require careful inspection or observation
Data quality matters as much as completion
There is a risk of rushed or minimal-effort submissions
It works best alongside clear questions and good workflow design.
⚠️ When Strength Score May Not Be Needed
Strength Score may add little value when workflows are:
Short or informational
Focused on awareness or simple reporting
Primarily narrative or exploratory
Not every workflow needs a Strength Score.
🧩 How Strength Score Is Configured
Strength Score is configured at the workflow template level and can be adjusted to reflect program needs. Configuration is typically done by Workflow Managers with advanced permissions, often in collaboration with ANVL or internal administrators.
(Detailed configuration guidance is covered in Advanced Strength Score articles.)
🔑 Key Takeaways
Strength Score measures thoroughness, not correctness
It helps surface rushed or low-effort workflows
It should be applied intentionally, not by default
Strong workflow design matters more than scoring alone