Great questions everyone. Let me provide a comprehensive breakdown of our implementation:
Dynamic Routing Rules Configuration:
We created a three-tier decision matrix in the workflow designer:
Tier 1 - Change Type Classification:
- Product/Process changes → Route through Engineering + Quality + Manufacturing
- Document-only changes → Route through Document Owner + Quality
- System/IT changes → Route through IT + Quality + affected department heads
- Supplier changes → Route through Procurement + Quality + Engineering
Tier 2 - Impact Level Assessment (automatically scored based on checkboxes in the change request form):
- Low Impact (score 1-3): Department Manager → Quality approval
- Medium Impact (score 4-6): Add Manufacturing/Engineering Manager to approval chain
- High Impact (score 7-10): Add VP Quality and Executive approval
Tier 3 - Department Involvement (based on multi-select field in the form):
- System automatically adds department heads for each selected department
- If more than 3 departments affected, adds cross-functional review committee
Conditional Workflow Logic Setup:
In the workflow designer, we created parallel approval paths with conditional triggers:
- Initial assessment step evaluates all three tiers simultaneously
- Workflow branches based on the combination of factors
- Each branch has pre-configured approval sequences
- Approvals can run in parallel where appropriate (e.g., department heads reviewing simultaneously)
Escalation Paths:
Carlos, great question. Our escalation works on two levels:
- First escalation (48 hours): Email notification to approver + their supervisor (no reassignment)
- Second escalation (72 hours): Notification to change control board + option for board to reassign or approve
We chose 48 hours based on analysis of our historical data - 80% of approvals that eventually completed happened within 2 days. The remaining 20% were often waiting for information, so the escalation prompts action.
Exception Handling:
David, you raised the most important practical concern. We built in a ‘Manual Routing Override’ option that’s available to the Change Control Board and Quality Directors. When selected:
- Automated routing is bypassed
- User manually selects approvers
- System requires justification comment (audit trail)
- About 8% of our changes use manual override, which is acceptable
We also created a ‘Complex Change’ type specifically for edge cases. These automatically route to the Change Control Board for routing determination rather than trying to fit them into the automated matrix.
Change Management and User Adoption:
The resistance issue was real. Here’s how we addressed it:
- Pilot Phase: Started with low-impact document changes only, proved the concept works
- Transparency: Published the routing logic matrix so everyone could see how decisions are made
- Override Authority: Gave senior managers the manual override capability, which they rarely use but appreciate having
- Metrics Dashboard: Created real-time dashboard showing approval cycle times, which demonstrated the improvement
- Training: Conducted sessions showing that automation handles routing, not decision-making - approvers still have full authority to approve/reject
Results After 3 Months:
- Average approval time: 12 days → 7 days (40% reduction)
- Routing errors: 15% → 2%
- Changes requiring manual routing intervention: 8%
- User satisfaction score: increased from 6.2 to 8.4 (out of 10)
- Time spent by change coordinators on routing: reduced by 75%
Key Success Factors:
- Start simple - we began with 3 change types and expanded to 8 over time
- Build in flexibility - the manual override was crucial for adoption
- Monitor and adjust - we refined the impact scoring criteria twice based on outcomes
- Clear audit trail - every routing decision is documented with the logic used
The configuration is entirely within MasterControl’s standard workflow designer capabilities in version 2022.2. No custom code required, which makes it maintainable by our QMS administrators without IT dependency.