23 rules for creating a Management System

Published by admin on

Management Systems authoring is not difficult, but it is time consuming. The following rules are designed to help you get it right first time and avoid some of the unnecessary wasted time that so many previous system administrators have spent.

  1. Only document in your management system:
    • knowledge you need to retain for intellectual purposes,
    • methods and procedures which demonstrate compliance and you want people to follow exactly,
    • the methods and procedures which are defined as required controls by your risks and opportunities, and
    • the need for records that prove your products, services and processes are compliant with requirements.
  2. System documents should consider the key attributes of a process to ensure the right people do the right thing, at the correct time, with the correct plant and equipment, in the correct environment and keep the right records, but only include this information where it is required to ensure conformance to a requirement.
  3. Acronyms can be barriers to understanding – only use them after you have established a system-wide approach for explaining what they stand for.
  4. Your system should allow easy location of relevant documents and records with the minimum of effort and with minimal prior knowledge or training.
  5. Minimum retention period policies should be established for all document and record types which considers statutory requirements and the needs of internal and external stakeholders, however any document’s retention time should be able to be extended to meet project or customer specific needs.
  6. All changes to records and management system documents should be traceable to a date, a person, the reason for the change and the approver, where required, unless that document or record has been destroyed following completion of the retention period.
  7. A mechanism to allow workers to make or propose changes to system documents must be available.
  8. Changes to management system documents must be controlled so that unauthorised amendment or deletion is not possible.
  9. Superseded documents must be withdrawn such that they don’t show up in the management system unless they are clearly marked as superseded.
  10. Ideally all requirements identified by the management system and all system records retained shall only have a single instance. Where multiple systems require the same data or content ideally this will be managed via data connections or cross references to prevent duplication and possible transposition errors or omissions.
  11. All regular reports should be able to be created in real-time from the data entered with minimal human intervention.
  12. Available Data capture methods must allow for all the expected environments workers are likely to experience.
  13. Electronic data capture methods should auto-complete as much data as possible (e.g. today’s date, automatic capture of the user completing the form, location, etc).
  14. No system document or record should ever be capable of being lost, being destroyed or becoming inaccessible or unreadable (unless via planned destruction after expiry of retention period).
  15. The process for the periodic reviewing of system documents should not be onerous (otherwise it is unlikely to occur), but should record who reviewed the document, when it was reviewed and any conclusion from the review.
  16. Changes to legal requirements should be managed such that each change is accompanied by data recording whether action was required or not, what the action was, who took it and when.
  17. A single register can be used to log and prioritise all actions associated with improvements, complaints, non-conformities and incidents as these all require a similar management process (identify issue, determine action, verify effectiveness of the action).
  18. A single register can be used to log and assess all risks and opportunities, although how they are prioritised will need careful consideration.
  19. A single register can be used to manage all plant and equipment as long as that register can manage records for servicing, maintenance, calibration, registration, etc.
  20. Often the organisation’s financial software can be used as the approved supplier register, providing you can effectively suspend a supplier and document the reason for the suspension in the software.
  21. The assessment and prioritising of environmental aspects and impacts should take your ability to influence each aspect into account.
  22. Hyperlinks between documents should be minimised unless you have a process and the appropriate resources to continuously manage them.
  23. If you plan to number your system documents make sure the document numbering system you adopt is flexible enough to allow a document to be slotted in between any two document numbers at any time as most methods of hosting management systems order documents by document name.


A word from the Managing Director: “We aim to establish long term, mutually beneficial working relationships, helping organisations850 grow and avoid the pitfalls that many fall into. Too many organisations feel their certification is a burden. We want to help organisations realise the benefits of effective management systems and certification”