Understanding Compliant Workflow Enforcement SOPs
If it’s not documented, it didn’t happen. When it comes to compliance, if you’re doing the work, you need to prove it. That means having well-documented SOPs (standard operating procedures) in place for all your regulated workflows. It also means logging your efforts to enforce these SOPs. They show that you took appropriate action in any number of scenarios, which can be related to regulations, change requests, firing of an employee, logging an HR compliant, or anything else that needs a structured workflow. But when do you need to do this, and how do you go about it? In this webinar, Tom Totenberg, our Helix ALM senior solutions engineer, clarifies workflow enforcement SOPs, along with a walkthrough of how Perforce manages GDPR (General Data Protection Regulation) requests. He’ll cover: -What are SOPs? -Why is it important to have this documentation? -Example: walking through our internal Perforce GDPR process. -What to beware of. -Building the workflow in ALM.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Understanding Compliant Workflow Enforcement SOPs
Similar to Understanding Compliant Workflow Enforcement SOPs (20)
More from Perforce
More from Perforce (20)
Recently uploaded
Recently uploaded (20)
Understanding Compliant Workflow Enforcement SOPs
- 1. SOP Enforcement TOM TOTENBERG | SR. SOLUTIONS ENGINEER
- 2. 2 | To change this title: View > Master > Slide Master perforce.com What are SOPs? • SOP = Standard Operating Procedure • Complex procedures that need accountability and consistency Examples • Regulatory compliance • Tax codes; ISOs; GDPR; military standards; etc. • HR complaints / customer complaints • Firing of an employee • Any other workflow that needs documented enforcement
- 3. If it’s not documented, it didn’t happen.
- 4. 4 | To change this title: View > Master > Slide Master perforce.com Good vs. Bad SOP Enforcement • Automated workflow routing • Automated notifications • Assignment emails; escalating overdue notifications • Comprehensive documentation • Security permission controls • Electronic signatures, where appropriate • Manual / institutionalized routing • Manual notifications • “When I’m done, I just email it to the next person.” • No centralized documentation (emails; chats; etc.) • Free for all • Paper signatures, or no signatures
- 5. 5 | To change this title: View > Master > Slide Master perforce.com Yeah, but… why? • Reduce risks • Failing an audit • Negative press due to employee or customer complaints • Reduced chance of playing “catchup” on unmanaged processes • Reduce costs • Fines • Legal fees • Improve process efficiency • Lower time investment, due to automation • Consistent documentation
- 6. 6 | To change this title: View > Master > Slide Master perforce.com Haste Makes Waste If you don’t do it right, you’ll do it twice.
- 7. Example Time! Sanitized, high-level look at a process Perforce uses to manage GDPR Requests. DISCLAIMER: Your process may be different! This is just an example. Consult your own teams and legal counsel to determine the right approach for you.
- 8. 8 | To change this title: View > Master > Slide Master perforce.com Conclusion • Every organization needs process accountability for their SOPs • The right tool can assist with this, and keep costs down by: • Reducing risk • Reducing costs • Improving efficiency
- 9. Questions? Comments? Hopes? Dreams? Come talk to us at perforce.com! Consulting available to implement your SOPs efficiently and securely.