Skip to main content

How do I set up Strength Score in a workflow template?

Configure Strength Score for a workflow template using the Editor.

Written by Lauren Baird
Updated this week

Answer

Set up Strength Score in the workflow template so ANVL can measure how thoroughly the workflow is completed. Strength Score is configured at the workflow template level in Editor using a JSON formula made up of:

  • parameters — what behaviors to measure

  • weights — how much each behavior matters

Strength Score should not be turned on and rolled out broadly all at once. The best approach is to:

  1. add the formula

  2. publish to a small pilot production site or sites

  3. let real users complete the workflow for about two weeks

  4. validate results in Power BI

  5. tune the formula if needed

  6. then expand to more sites

Strength Score does not appear in Live Feed, so it must be validated using real workflow data in Power BI.


Steps

Add or update the Strength Score formula

  1. Open ANVL Insights.

  2. Go to MobilizeEditor.

  3. Open the workflow template.

  4. Find the Strength Score section.

  5. Review the current formula, if one exists.

  6. Update the formula using the approved JSON format.

  7. Save your changes.

Tip for editing
For easier editing:

  1. Copy the full Strength Score field.

  2. Paste it into a plain-text editor such as Notepad.

  3. Make your changes there.

  4. Copy the updated JSON back into the workflow template.

  5. Save again.

Choose a starter formula
Pick a starter formula that matches the workflow type.

Evidence-heavy
Best for JSAs, inspections, or workflows where photos, text, and time matter.

{
"strength": {
"weights": {
"averagePostedPhotos": 0.30,
"completedResponsePct": 0.20,
"hasLongerTextResponseCharacters": 0.20,
"consistentDetailedTextResponsesCharacters": 0.10,
"minimumRequiredTextQuestionCharacters": 0.10,
"minimumDurationSeconds": 0.10
},
"parameters": {
"averagePostedPhotos": 0.20,
"hasLongerTextResponseCharacters": 90,
"consistentDetailedTextResponsesCharacters": 30,
"minimumRequiredTextQuestionCharacters": 40,
"minimumDurationSeconds": 150
}
}
}

Question completion
Best for LPAs, audits, or workflows where broad completion matters most.

{
"strength": {
"weights": {
"completedResponsePct": 0.5,
"pctChecklistsAnswered": 0.5
},
"parameters": {}
}
}

Text quality
Best for observation or reporting workflows where written detail matters most.

{
"strength": {
"weights": {
"nonBlankTextPct": 0.40,
"hasLongerTextResponseCharacters": 0.30,
"consistentDetailedTextResponsesCharacters": 0.30
},
"parameters": {
"hasLongerTextResponseCharacters": 50,
"consistentDetailedTextResponsesCharacters": 25
}
}
}

Adjust the formula carefully

  1. Start by adjusting parameters first.

  2. Keep the formula simple.

  3. Use about 2 to 4 parameters when possible.

  4. Make sure the weights add up to 1.0.

  5. Avoid giving any one parameter more than 0.50 unless you have a strong reason.

Common safe starting thresholds

  • averagePostedPhotos: 0.20

  • minimumDurationSeconds: 120–180

  • hasLongerTextResponseCharacters: 50–100

  • consistentDetailedTextResponsesCharacters: 20–40

  • minimumRequiredTextQuestionCharacters: 30–60

Tag required open-text questions if needed
If your formula uses minimumRequiredTextQuestionCharacters, you must tag the required open-text questions.

  1. Open the workflow in Editor.

  2. Select the open-text question.

  3. In the Tags field, add:

{"strengthScore":"Required"}
  1. Save the question.

  2. Repeat for each required open-text question.

Question-level tag marking this open-text question as required for Strength Score calculation.

Publish and validate

  1. Publish the updated workflow to a small pilot production site or sites.

  2. Let real users complete the workflow for about two weeks.

  3. Review the results in Power BI.

  4. Compare the scores to what you expected.

  5. Adjust the formula if needed.

  6. Repeat until the scoring is reliable.

  7. Then roll it out more broadly.

Important notes

  • Strength Score is configured per workflow template.

  • Strength Score does not appear in Live Feed.

  • Tagging a question with {"strengthScore":"Required"} does not force the user to answer it. It only affects Strength Score.

  • Only open-text questions should be tagged as required for Strength Score.

  • Treat Strength Score like a small enhancement project, not a one-click setting.

  • Pilot first, validate, then expand.


Did this answer your question?