Skip to main content

Recommended Strength Score Formulas by Program (Workflow Manager – Advanced)

Use proven Strength Score patterns aligned to common EHS workflow types.

Lauren Baird avatar
Written by Lauren Baird
Updated this week

Primary Role: Workflow Manager (Advanced – Editor Admin)
Learning Focus: Apply
Where: Workflow Editor


🧭 Before You Start
These examples are starting points, not universal defaults.
Always validate scores using real workflow submissions.


🎯 Why This Matters
Different workflows require different definitions of quality. A one-size-fits-all Strength Score creates friction and false signals.


🧩 Program-Based Strength Score Formulas

Below are example formulas showing:

  • Which parameters to use

  • Typical threshold values

  • Practical weight distribution


🔹 Field JSA / Service JSA

Primary Behaviors to Encourage

  • Detailed task descriptions

  • Photos where risk exists

  • Sufficient time-on-task

Recommended Parameters

  • averagePostedPhotos

  • completedResponsePct

  • hasLongerTextResponseCharacters

  • consistentDetailedTextResponsesCharacters

  • minimumRequiredTextQuestionCharacters

  • minimumDurationSeconds

Example Formula

{   "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

Primary Behaviors

  • Consistent task documentation

  • Less reliance on photos

  • Checklist discipline

Recommended Parameters

  • completedResponsePct

  • nonBlankTextPct

  • pctChecklistsAnswered

  • minimumDurationSeconds

Example Formula

{   "strength": {     "weights": {       "completedResponsePct": 0.35,       "nonBlankTextPct": 0.25,       "pctChecklistsAnswered": 0.25,       "minimumDurationSeconds": 0.15     },     "parameters": {       "minimumDurationSeconds": 120     }   } }

🔹 Layered Process Audits (LPAs)

Primary Behaviors

  • Completion of required questions

  • Identification of issues

Recommended Parameters

  • completedResponsePct

  • pctChecklistsAnswered

  • flagsWereRaised (low weight)

Example Formula

{   "strength": {     "weights": {       "completedResponsePct": 0.5,       "pctChecklistsAnswered": 0.4,       "flagsWereRaised": 0.1     },     "parameters": {}   } }

⚠️ Avoid heavy text or duration weighting for LPAs.


🔹 5S Audits

Primary Behaviors

  • Visual confirmation

  • Checklist adherence

Recommended Parameters

  • averagePostedPhotos

  • pctChecklistsAnswered

  • completedResponsePct

Example Formula

{   "strength": {     "weights": {       "averagePostedPhotos": 0.4,       "pctChecklistsAnswered": 0.35,       "completedResponsePct": 0.25     },     "parameters": {       "averagePostedPhotos": 0.2     }   } }

🔹 Safety Observations / Near Miss / Concern Reporting

Primary Behaviors

  • Raising issues

  • Narrative context

Recommended Parameters

  • flagsWereRaised

  • nonBlankTextPct

  • hasLongerTextResponseCharacters

Example Formula

{   "strength": {     "weights": {       "flagsWereRaised": 0.4,       "nonBlankTextPct": 0.3,       "hasLongerTextResponseCharacters": 0.3     },     "parameters": {       "hasLongerTextResponseCharacters": 50     }   } }

⚠️ Avoid duration penalties for reporting workflows.


🔑 Key Takeaways

  • Quality looks different by workflow type

  • Use fewer parameters, weighted intentionally

  • Let workflow purpose drive scoring design

Did this answer your question?