ISO22301 (The new international ISO standard for Business Continuity) is expected to be published at some point in Q2 2012. Even though it will take time to bed in it definitely opens up some interesting questions in respect to the effective development of the BCM programme within corporate environments.
One key question is how effective companies are at actually taking plans right through to formal review and planned remedial action closure.
I know some of you are members but if you are not yet aware we have a LinkedIn group running discussing ISO22301 and there are lot of useful references on there now if you would like to join. The group is called “ISO22301”. There are now over 700 members from all over the world so please join in and get the discussions going if you want to help shape the standard as it emerges.
Over the last 9 years, NonVerba has been historically developing a wide portfolio of managed services and software solutions to help our clients address a lot of the challenges that ISO22301 is only now starting to present.
We totally appreciated the need for a Plan, Do, Check and Act approach to management systems as early as 2003, with the development of our Internal Audit system eInviso, so we feel we are well positioned to help you plug a lot of gaps you may have in an attempting to meet or align to the needs of this standard.
As the standard starts to come to life we will be looking to send “FYI” emails to people associated with NonVerba to keep them aware of some of the key developments emerging out of the new standard and to look to give case study detail on how we have addressed some of these issues in the past through the use of our managed services and online software tools.
If you want to be kept in the loop for these ISO22301 updates please email with the subject saying “Please keep me in the loop” to: email@example.com
We will not spam people and will only mail you if you agree to receive mails on this. Otherwise we will not disturb you again on the ISO22301 updates.
I know a lot of people are not that bothered about the standard itself but we will be aiming to look at the challenges this standard will bring up and then focus on some of these individually to show how we have already addressed a lot of these in the past with clients as early as 2003. These emails are therefore intended for all even if you are not looking to ultimately consider the standard once it comes on line.
Thanks for listening and I hope you want to be kept in the loop.
By CSARN member Peter Joyce: firstname.lastname@example.org