Primary Role: Workflow Manager (Editor Admin)
Audience: EHS Leaders, Program Owners, Power Workflow Managers
Purpose: Orientation
What This Role Is About
As a Workflow Manager with Editor Admin access, you are responsible for alignment.
Not just building workflows, but ensuring that workflows across your organization or division:
Collect data consistently
Are easy for users to complete correctly
Support reliable reporting and analytics
Reinforce the right behaviors (quality, completeness, follow-up)
Your decisions affect every site using those workflows.
What You’re Responsible For
1. Workflow Design Alignment
You ensure workflows that serve the same purpose are designed consistently:
Similar questions are asked the same way
Required information is captured reliably
Workflow structure supports how the data will be used
This consistency is what enables meaningful comparisons across sites and time.
2. Tag Consistency (Workflow & Question Level)
You manage how workflows and questions are tagged so reporting works as intended:
Workflow template tags group related workflows correctly for reporting
Question-level tags determine how responses appear in reports
The same question must use the same
reportNametag across workflows and sites to support multi-site and cross-site reporting
Tags are not just metadata — they are how workflows become reportable data.
3. Scoring Strategy (When Used)
When scoring is enabled, you define what “good” looks like:
Custom Scoring for point-based evaluation and prioritization
Strength Score for completion quality and effort
Your responsibility is not to make scoring complex — but to make it useful and fair.
Scoring should:
Support decisions
Be explainable to users
Be validated before broad rollout
4. Reporting Readiness
You don’t build dashboards — but you make them possible.
By aligning:
Questions
Tags
Scoring logic
…you ensure reports and Power BI insights are trustworthy and actionable.
If reporting looks inconsistent, the root cause is almost always workflow design, not reporting tools.
How to Approach This Role Successfully
Think in terms of systems, not one-off workflows.
Start with pilot sites when changing tags or scoring
Test changes before applying them broadly
Treat scoring (especially Strength Score) as a small project that may require iteration
Adjust weights and thresholds based on real usage, not assumptions
Small changes at the template level can have organization-wide impact.
Where to Go Next
Depending on what you’re working on:
Aligning reporting and tags
→ Managing Workflow Template Tags
→ Managing Question-Level Tags
→ Question-Level Tags Reference