• Home
  • About Us
    • Managing Director
    • IMS White Paper Exec Sum
  • What is an IMS?
  • Why do we need an IMS?
  • Common IM Issues
  • Solution Insights
    • 1. Initial Engagement
    • 2. Innovative Approach
    • 3. Optimising Content
    • 4. Clarifying Ownership
    • 5. Info. Architecture
    • 6. Transferring Knowledge
    • 7. Managing Change
    • 8. The Role of Software
    • 9. Defining Content Types
    • 10. Version Control
    • 11. Simplifying Access
    • 12. Records Management
  • News
  • Contact Us
  • More
    • Home
    • About Us
      • Managing Director
      • IMS White Paper Exec Sum
    • What is an IMS?
    • Why do we need an IMS?
    • Common IM Issues
    • Solution Insights
      • 1. Initial Engagement
      • 2. Innovative Approach
      • 3. Optimising Content
      • 4. Clarifying Ownership
      • 5. Info. Architecture
      • 6. Transferring Knowledge
      • 7. Managing Change
      • 8. The Role of Software
      • 9. Defining Content Types
      • 10. Version Control
      • 11. Simplifying Access
      • 12. Records Management
    • News
    • Contact Us
  • Home
  • About Us
    • Managing Director
    • IMS White Paper Exec Sum
  • What is an IMS?
  • Why do we need an IMS?
  • Common IM Issues
  • Solution Insights
    • 1. Initial Engagement
    • 2. Innovative Approach
    • 3. Optimising Content
    • 4. Clarifying Ownership
    • 5. Info. Architecture
    • 6. Transferring Knowledge
    • 7. Managing Change
    • 8. The Role of Software
    • 9. Defining Content Types
    • 10. Version Control
    • 11. Simplifying Access
    • 12. Records Management
  • News
  • Contact Us

Managing Change

Benefits must be clear

Key Controls

A case for change has to be agreed with stakeholders before any updates to IMS content are made.

Once the updated document is ready only the IMS Administrator can implement IMS content updates in the system.

Always ask questions.

Challenge the Need for Documents

Embedding instructions and advice on the 'ways-of-working' within the applications used day-to-day rather than having stand-alone procedure documents is preferable to the majority of end-users.

An optimal IMS is not overflowing with content!

Risk based rather than planned scheduled reviews.

Use Risk-based Reviews

Rather than fixed-term, periodical reviews and revalidations of IMS content, we recommend a risk-based approach. This significantly reduces the number of IMS content updates (and the associated change management effort) needed to keep your management system content up-to-date.

Copyright © 2025 Alianna Consulting Limited - All Rights Reserved.

  • Privacy Policy
  • Terms&Conditions
  • News

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

DeclineAccept