Answer
Different workflows need different Strength Score formulas because “good completion” does not look the same in every program.
For example:
a JSA may need strong text detail, photos, and enough time to show the user really thought through the job
an LPA may need strong completion of required questions, but not a lot of writing
a Near Miss report may need good issue reporting and enough detail to explain what happened, but not a time requirement
Use the formulas below as starting points. You can copy and paste them into the workflow template tags, then test them with real workflow submissions and adjust if needed.
Steps
Field JSA / Service JSA
Use this when you want to encourage:
detailed task descriptions
photos where risk exists
enough time spent thinking through the job
{
"strength": {
"weights": {
"averagePostedPhotos": 0.3,
"completedResponsePct": 0.2,
"hasLongerTextResponseCharacters": 0.2,
"consistentDetailedTextResponsesCharacters": 0.1,
"minimumRequiredTextQuestionCharacters": 0.1,
"minimumDurationSeconds": 0.1
},
"parameters": {
"averagePostedPhotos": 0.2,
"hasLongerTextResponseCharacters": 90,
"consistentDetailedTextResponsesCharacters": 30,
"minimumRequiredTextQuestionCharacters": 40,
"minimumDurationSeconds": 150
}
}
}In-Shop / Warehouse / Parts JSA
Use this when you want to encourage:
consistent documentation
checklist completion
basic written detail
less reliance on photos
{
"strength": {
"weights": {
"completedResponsePct": 0.35,
"nonBlankTextPct": 0.25,
"pctChecklistsAnswered": 0.25,
"minimumDurationSeconds": 0.15
},
"parameters": {
"minimumDurationSeconds": 120
}
}
}Layered Process Audit (LPA)
Use this when you want to encourage:
completion of required questions
checklist discipline
issue identification when needed
{
"strength": {
"weights": {
"completedResponsePct": 0.5,
"pctChecklistsAnswered": 0.4,
"flagsWereRaised": 0.1
},
"parameters": {}
}
}Avoid heavy text or duration weighting for LPAs unless that truly matches the program design.
5S Audit
Use this when you want to encourage:
visual confirmation
checklist adherence
broad completion
{
"strength": {
"weights": {
"averagePostedPhotos": 0.4,
"pctChecklistsAnswered": 0.35,
"completedResponsePct": 0.25
},
"parameters": {
"averagePostedPhotos": 0.2
}
}
}Safety Observation / Near Miss / Concern Reporting
Use this when you want to encourage:
raising issues
useful written context
meaningful reporting
{
"strength": {
"weights": {
"flagsWereRaised": 0.4,
"nonBlankTextPct": 0.3,
"hasLongerTextResponseCharacters": 0.3
},
"parameters": {
"hasLongerTextResponseCharacters": 50
}
}
}Avoid duration-based penalties for reporting workflows unless there is a strong reason.
How to use these formulas
Copy the formula that best matches the workflow type.
Paste it into the workflow template tags.
Publish to Demonstration / UAT.
Test with real submissions.
Adjust weights or thresholds if the scores feel too strict, too easy, or misaligned.
Helpful notes
Start with the workflow purpose, not the formula.
Use fewer parameters, weighted intentionally.
Do not reuse the same Strength Score formula across every workflow type.
A good Strength Score should feel fair and reinforce the right behavior.