<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OHSAS 18001 EXPERT &#187; OHSMS Documentation</title>
	<atom:link href="http://ohsas18001expert.com/category/ohsms-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://ohsas18001expert.com</link>
	<description>Developing, Implementing &#38; Maintaining Occupational Health &#38; Safety Management Systems</description>
	<lastBuildDate>Thu, 02 Feb 2012 19:34:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Checklists &amp; Christmas</title>
		<link>http://ohsas18001expert.com/2011/12/22/checklists-christmas/</link>
		<comments>http://ohsas18001expert.com/2011/12/22/checklists-christmas/#comments</comments>
		<pubDate>Thu, 22 Dec 2011 16:16:01 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Auditing]]></category>
		<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[checklists]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=930</guid>
		<description><![CDATA[Every year we do a Christmas dinner party – a three-course English Feast with Roast Beef and Yorkshire Pudding and a dessert we call “The Amy” (Butter Tarts with Stilton Cheese).   The menu is set and draws its inspiration from my husband’s heritage (England and Canada) and my Midwest upbringing (Iowa).  We have been doing [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://ohsas18001expert.com/wp-content/uploads/2011/12/small-table.bmp"><img class="alignleft  wp-image-945" title="small table" src="http://ohsas18001expert.com/wp-content/uploads/2011/12/small-table.bmp" alt="" width="236" height="181" /></a>Every year we do a Christmas dinner party – a three-course English Feast with Roast Beef and Yorkshire Pudding and a dessert we call “The Amy” (Butter Tarts with Stilton Cheese).   The menu is set and draws its inspiration from my husband’s heritage (England and Canada) and my Midwest upbringing (Iowa).  We have been doing the same meal for the last 15 years.</p>
<p>Once I started developing and implementing management systems, I could not resist applying management system theory to this event.  I developed a <a title="Christmas Party Checklist" href="http://ohsas18001expert.com/wp-content/uploads/2011/12/Christmas-Party-Checklist.pdf">Christmas Party Checklist</a>.  This checklist sets out the various tasks that need to be done and has blanks for assigning responsibilities and checking off each task when it is done.</p>
<h5><strong>Why do I use a checklist?</strong></h5>
<p>One year, I found the strawberries for the appetizer course still in the refrigerator when I put the leftovers away.  Another year, I had to scramble to find the meat platter while the guests watched from the table.</p>
<p>This checklist helps the party go smoothly and, more importantly, it helps me relax and actually enjoy the party because I know I am not going to forget anything important.</p>
<p>The morning after the party I make notes and additions to the checklist and file it away for the following year.</p>
<h5>So what does this have to do with OHSAS 18001?</h5>
<p>Checklists are an important part of a management system.  As with our Christmas party, they prevent you from missing important tasks.  They also help make your job more manageable and enjoyable – that is, if they are done right.</p>
<h5 style="text-align: left;"><strong>Want to learn more about creating effective checklists?</strong></h5>
<p><a title="Blog - 7 Steps to Creating Effective Checklists" href="http://ohsas18001expert.com/2011/09/15/7-steps-to-creating-effective-checklists/">Click here</a> to check out my previous blog and sign up for my mini-course (starting January 16, 2012) focused on checklist creation.</p>
<p>p.s.  It was a great webinar Tuesday on <em><strong>ISO 19011:2011 – The Impact on Management System Auditing</strong></em>. Thank you to those of you who participated and submitted questions for the Q&amp;A.  Come back here next week for a link you can use to view this presentation.</p>
<pre>© ENLAR Compliance Services, Inc. (2011)</pre>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2011/12/22/checklists-christmas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>7 Steps to Creating Effective Checklists</title>
		<link>http://ohsas18001expert.com/2011/09/15/7-steps-to-creating-effective-checklists/</link>
		<comments>http://ohsas18001expert.com/2011/09/15/7-steps-to-creating-effective-checklists/#comments</comments>
		<pubDate>Thu, 15 Sep 2011 13:24:01 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[checklists]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=868</guid>
		<description><![CDATA[In my last blog, I discussed the importance of checklists in saving lives.  Checklists are everywhere.   They are an integral part of many personal activities &#8211; from completing your tax return to communicating symptoms to your doctor.  Checklists also play an important role in managing many business processes.  Checklists will be an important part of your OHSMS documentation. In [...]]]></description>
			<content:encoded><![CDATA[<p>In my <a title="Checklists Save Lives" href="http://ohsas18001expert.com/2011/08/10/checklists-save-lives/">last blog</a>, I discussed the importance of checklists in saving lives. </p>
<p>Checklists are everywhere.  </p>
<p>They are an integral part of many personal activities &#8211; from completing your tax return to communicating symptoms to your doctor.  Checklists also play an important role in managing many business processes. </p>
<p>Checklists will be an important part of your OHSMS documentation.</p>
<p>In order to be effective, checklists need to be intelligently designed and routinely used.  They also need to be controlled.</p>
<p><strong><em>So how do you go about creating a great checklist?<span id="more-868"></span></em></strong></p>
<p>You need to follow 7 steps –</p>
<ol>
<li>Clearly define the purpose of your checklist.</li>
<li>Decide on the right content.</li>
<li>Utilize great design.</li>
<li>Test that the checklist works as intended.</li>
<li>Explain how and when the checklist is to be used (train users).</li>
<li>Monitor that the checklist is used as intended.</li>
<li>Ensure users are provided new versions when the checklist is changed.</li>
</ol>
<p><strong><em>Want to know more? </em></strong></p>
<p>Sign up below to receive additional information on learning to create great OHSMS documentation.</p>
<p><form name="form1" method="post" action="https://www.mcssl.com/app/contactsave.asp">
<input name="merchantid" type="hidden" id="merchantid" value="109511">
<input name="ARThankyouURL" type="hidden" id="ARThankyouURL" value="www.kickstartcart.com/app/thankyou.asp?ID=109511">
<input name="copyarresponse" type="hidden" id="copyarresponse" value="1">
<input name="custom" type="hidden" id="custom" value="0">
<input name="defaultar" type="hidden" id="defaultar" value="640942">
<input name="allowmulti" type="hidden" id="allowmulti" value="0">
<input name="visiblefields" type="hidden" id="visiblefields" value="Name,Email1,Company,Country">
<input name="requiredfields" type="hidden" id="requiredfields" value="Name,Email1,Company,Country">
<table>
    <tr>
      <td>Name</td>
      <td><input name="Name" type="text" size="40"></td>
    </tr>
    <tr>
      <td>Email</td>
      <td><input name="Email1" type="text" size="40"></td>
    </tr>
    <tr>
      <td>Company</td>
      <td><input name="Company" type="text" size="40"></td>
    </tr>
    <tr>
      <td>Country</td>
      <td><input name="Country" type="text" size="40"></td>
    </tr>
	<tr align="center">
		<td colspan="2">
			<input type="Submit" name="cmdSubmit" value="Submit">
		</td>
	</tr>
  </table>
</form></p>
<pre>© ENLAR® Compliance Services, Inc. (2011)</pre>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2011/09/15/7-steps-to-creating-effective-checklists/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Checklists Save Lives</title>
		<link>http://ohsas18001expert.com/2011/08/10/checklists-save-lives/</link>
		<comments>http://ohsas18001expert.com/2011/08/10/checklists-save-lives/#comments</comments>
		<pubDate>Wed, 10 Aug 2011 13:49:47 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[Emergency Preparedness]]></category>
		<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[Resources & Tools]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=762</guid>
		<description><![CDATA[Checklists are essential to successful business operations.  Checklists are an integral part of an occupational health and safety management system.  More importantly, checklists save lives.  This result is most obvious in medicine where the use of surgical checklists has saved thousands of lives and untold suffering. The importance of checklists in medicine was highlighted in a 2007 [...]]]></description>
			<content:encoded><![CDATA[<p>Checklists are essential to successful business operations.  Checklists are an integral part of an occupational health and safety management system.  More importantly, checklists save lives.</p>
<p><a href="http://ohsas18001expert.com/wp-content/uploads/2011/08/WHO-checklist.gif"><img class="alignleft size-thumbnail wp-image-856" title="WHO checklist" src="http://ohsas18001expert.com/wp-content/uploads/2011/08/WHO-checklist-150x150.gif" alt="" width="150" height="150" /></a></p>
<p> This result is most obvious in medicine where the use of surgical checklists has saved thousands of lives and untold suffering. The importance of checklists in medicine was highlighted in a 2007 article in the New Yorker Magazine, <strong><em><a title="New Yorker article - The Checklist" href="http://www.newyorker.com/reporting/2007/12/10/071210fa_fact_gawande" target="_blank">The Checklist</a></em></strong>. The most dramatic of these incentives is the international adoption of a one-page Surgical Safety Checklist developed, promoted and disseminated by the World Health Organization.</p>
<p><a title="WHO Surgical Safety Checklist" href="http://www.who.int/patientsafety/safesurgery/en/" target="_blank">Click here to download a copy of this checklist.</a> </p>
<p> </p>
<p>There are numerous uses of checklists in OH&amp;S management systems.  In fact, checklists are one of the most effective way of creating management system procedures and work instructions to meet the OHSAS 18001 requirements. </p>
<p>Some of the OH&amp;S uses of checklists include –</p>
<ol>
<li>Inspection checklists – for forklift trucks, fire extinguishers and other safety-critical devices, equipment and supplies.</li>
<li>Plans and permits – for confined space entry, hot work and equipment lockout where the sequence of tasks and adequacy of precautions are critical.</li>
<li>Emergency preparedness – for making sure equipment, materials and personnel will be ready and available when an incident occurs.</li>
<li>Risk assessments – for evaluating the hazards and risks associated with materials, equipment and tasks.</li>
<li>Internal audit protocols – for making sure that OHSMS audits are complete, inclusive and cost-effective.</li>
</ol>
<p>As regulations, activities and organizations become more complex, checklists become increasingly important for ensuring that nothing is missed.  This is why pilot checklists were developed in aviation in the 1930s.  This is why surgical checklists are being aggressively promoted in medicine today.  This is why most OH&amp;S management systems would benefit from the use of appropriately-designed checklists. </p>
<p>In my next blog, I will cover the 5 steps you should follow in order to develop good OHSMS checklists.</p>
<p>In the meantime, <a title="EHSMS Implementation Checklist" href="http://www.managementsystemexpert.com/resources/ehsms-implementation-checklist/">click here</a> to request a copy of my EHSMS Implementation Checklist.</p>
<pre>© ENLAR® Compliance Services, Inc. (2011)</pre>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2011/08/10/checklists-save-lives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Control of Documented Information</title>
		<link>http://ohsas18001expert.com/2011/04/15/control-of-documented-information/</link>
		<comments>http://ohsas18001expert.com/2011/04/15/control-of-documented-information/#comments</comments>
		<pubDate>Fri, 15 Apr 2011 16:02:07 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Standards & Certification]]></category>
		<category><![CDATA[document control]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[record control]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=394</guid>
		<description><![CDATA[In a previous blog, I discussed the new High Level Structure and identical text requirements that has been proposed for all ISO management system standards.  One of the proposed changes is to eliminate the document control and record control elements and replace them with a new provision requiring control of “documented information”.  Documented information is [...]]]></description>
			<content:encoded><![CDATA[<p>In a <a title="MSS High Level Structure" href="http://ohsas18001expert.com/2011/01/14/high-level-structure-for-ms-standards/">previous blog</a>, I discussed the new High Level Structure and identical text requirements that has been proposed for all ISO management system standards.  One of the proposed changes is to eliminate the document control and record control elements and replace them with a new provision requiring control of “documented information”.  Documented information is somewhat vaguely defined in this new scheme as “the information required to be controlled and maintained by an organization”.</p>
<p>Although this may be seen as progressive by those who developed this new management system structure, it is likely to create confusion on the part of users of the standards who are not information management experts.</p>
<p>There are important reasons for distinguishing between the documents that  need to be controlled in a management system and record retention requirements.  Even though both document control and record control are control of documented information, their purpose and use is very different.<span id="more-394"></span></p>
<p>Documents are controlled to ensure that individuals are using the correct information to guide them in accomplishing some task.  The information within a document changes over time as conditions and requirements change.  This is why approval processes and version control are critical for documents.</p>
<p>Records are controlled to ensure that the information contained within the document is available and accurate for reference in the future.  The information in records should <span style="text-decoration: underline;">not</span> change over time.  This is why preservation and data integrity are critical for records.</p>
<p>In honor of the upcoming tax return deadline, I will use preparation and retention of tax returns as an example of document and record control. </p>
<p>When you complete your tax return, it would be foolish to use last year’s forms and instructions. Instead, since tax forms typically change each year, you look for the most recent version. You want to ensure you use the right form so you meet the requirements set out in the tax code. Version control is what is important.</p>
<p>Once your tax return has been submitted to the IRS, it becomes a record.  Sometimes that record is requested by others to provide evidence of your financial stability.  It would be foolish to change the information contained in that record – and probably illegal as well.  Data preservation and integrity is what is important – not version control.</p>
<p>Both of these involve the control of “documented information” but they are hardly the same.</p>
<pre>© ENLAR® Compliance Services, Inc. (2011)</pre>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2011/04/15/control-of-documented-information/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Should I Write a Procedure?</title>
		<link>http://ohsas18001expert.com/2009/11/06/should-i-write-a-procedure/</link>
		<comments>http://ohsas18001expert.com/2009/11/06/should-i-write-a-procedure/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 22:14:55 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[decision making]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=274</guid>
		<description><![CDATA[One of the difficult questions that OH&#38;S managers face is &#8211; &#8220;Do we need a written procedure for [some process]?&#8221;  The dilemma is that although written procedures are a necessary part of an occupational safety and health management system &#8211; if you create too many formal procedures your OHSMS becomes complex, cumbersome and unwieldy.  I just got done reading an article in [...]]]></description>
			<content:encoded><![CDATA[<p>One of the difficult questions that OH&amp;S managers face is &#8211; &#8220;Do we need a written procedure for [some process]?&#8221;  The dilemma is that although written procedures are a necessary part of an occupational safety and health management system &#8211; if you create too many formal procedures your OHSMS becomes complex, cumbersome and unwieldy.</p>
<p> I just got done reading an article in the October 2009 <strong><em>Quality Progress Magazine</em></strong> that sets out a nifty tool for making this decision &#8211; a 2 x 2 matrix for deciding whether or not to standardize a process.  Although the example given in this article &#8211; <a href="http://www.asq.org/quality-progress/2009/10/one-good-idea/building-a-consensus.pdf" target="_blank">Building a Consensus</a> &#8211; is  for a quality system process, it can be easily adapted to making standardization decisions in an OH&amp;S management system.</p>
<p>Try it out for your OH&amp;S management system and let me know &#8211; &#8220;Did it work?&#8221; - by posting your comments below.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/11/06/should-i-write-a-procedure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Information Overload</title>
		<link>http://ohsas18001expert.com/2009/10/27/information-overload/</link>
		<comments>http://ohsas18001expert.com/2009/10/27/information-overload/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 20:43:59 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[OHSMS Implementation]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=266</guid>
		<description><![CDATA[One of the signfiicant tasks associated with implementing any management system is managing information &#8211; typically lots of information.  Usually, way too much information.  As I discussed in a previous post &#8211; Data Sprawl &#8211; Not Just an IT Problem, the fact that we are now managing &#8220;virtual information&#8221; leads us to believe that the [...]]]></description>
			<content:encoded><![CDATA[<p>One of the signfiicant tasks associated with implementing any management system is managing information &#8211; typically lots of information.  Usually, way too much information.  As I discussed in a previous post &#8211; <a href="http://ohsas18001expert.com/2008/07/21/data-sprawl-not-just-an-it-problem/" target="_self">Data Sprawl &#8211; Not Just an IT Problem</a>, the fact that we are now managing &#8220;virtual information&#8221; leads us to believe that the more information we have the better.</p>
<p>Not true. </p>
<p>As this video points out, at some point more information simply makes us stupid.</p>
<p> <object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="445" height="364" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/CXFEBbPIEOI&amp;hl=en&amp;fs=1&amp;rel=0&amp;color1=0xe1600f&amp;color2=0xfebd01&amp;border=1" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="445" height="364" src="http://www.youtube.com/v/CXFEBbPIEOI&amp;hl=en&amp;fs=1&amp;rel=0&amp;color1=0xe1600f&amp;color2=0xfebd01&amp;border=1" allowfullscreen="true" allowscriptaccess="always"></embed></object></p>
<p>This is an important point to remember as you are establishing, implementing and maintaining your OH&amp;S management system.  As you are developing your procedures, programs, forms, inspection sheets, training programs, meeting minutes, e-mail updates&#8230;&#8230; remember that the human brain only has so much capacity. </p>
<p>Use it wisely.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/10/27/information-overload/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating OHSMS Documentation</title>
		<link>http://ohsas18001expert.com/2009/09/30/creating-ohsms-documentation/</link>
		<comments>http://ohsas18001expert.com/2009/09/30/creating-ohsms-documentation/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 15:16:49 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[audit]]></category>
		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=244</guid>
		<description><![CDATA[A reader recently asked – Why is that OH&#38;S management system manuals so often repeat the language of the OHSAS 18001 standard – isn’t that redundant? Yes and No. During management system implementation, the constant repetition of the OHSAS 18001 language feels redundant.  You are referring to OHSAS 18001 constantly – in drafting procedures, discussing processes, [...]]]></description>
			<content:encoded><![CDATA[<p>A reader recently asked –</p>
<p><em>Why is that OH&amp;S management system manuals so often repeat the language of the OHSAS 18001 standard – isn’t that redundant?</em></p>
<p>Yes and No.</p>
<p><span id="more-244"></span>During management system implementation, the constant repetition of the OHSAS 18001 language feels redundant.  You are referring to OHSAS 18001 constantly – in drafting procedures, discussing processes, creating forms and developing training programs.  You probably feel – “enough already with the arcane standards speak.”  Since you are so close to the initial drafting of the manual and other procedures, it is clear in your mind what the OHSAS 18001 requirements are and how you are planning to meet them.</p>
<p>As with most things, memories and associations fade with time. </p>
<p>One of my favorite Christmas stories is that each year when we got together with my mother and my husband’s parents for Christmas, my Mother would start a question with “What year was it when we ….”  A lively discussion would ensue as we tried to remember exactly what year it was that we did some particular activity – &#8220;Was it 1997 or was it 2000?&#8221;  My mother has since passed away but we still discuss “What year was it when we …” at Christmas &#8211; and I am reminded of her presence.</p>
<p>A similar thing happens with your management system manuals and procedures.  Over time, people will forget both WHAT they need to do and WHY if you don’t actually include the requirements in your Manual.  The “shall clauses” in the OHSAS 18001 standard are unlikely to be remembered and may not actually be met if you don’t explicitly include them in your own OHSMS documentation.</p>
<p>One of the tests of the completeness of a management system manual is whether you can file the standard away (never refer to it again), and still have a management system that continues to be in conformance with the requirements of OHSAS 18001. </p>
<p>In fact, the hallmark of a good internal audit program is that audits are performed against the organization’s own OHSMS documentation – its manual and procedures – NOT against the OHSAS 18001 standard.  Conformance with the OHSMS manual IS conformance with OHSAS 18001.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/09/30/creating-ohsms-documentation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

