Dismiss Notice
You must be a registered member in order to post messages and view/download attached files in this forum.
Click here to register.

Logo Change

Discussion in 'ISO 9001:2008 - Quality Management Systems' started by Mr. Bungle, Mar 30, 2016.

  1. Mr. Bungle

    Mr. Bungle New Member

    Joined:
    Mar 30, 2016
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    We are changing the name log of our company and is on most of the documents we use. Do I need to create a Document Change Request for every document that needs the new name and logo?
     
  2. Sidney Vianna

    Sidney Vianna Well-Known Member

    Joined:
    Jul 30, 2015
    Messages:
    127
    Likes Received:
    172
    Trophy Points:
    42
    What would be the value of doing that?
     
    Andy Nichols likes this.
  3. Candi1024

    Candi1024 Well-Known Member

    Joined:
    Jul 30, 2015
    Messages:
    129
    Likes Received:
    83
    Trophy Points:
    27
    Location:
    Pennsylvania
    I'm going to say that depends on your company. Technically you don't need any document change requests but that is obviously in your procedures.

    Is it possible to make one document change request that will cover any document that comes through a revision change, and that also allows for documents to be allowed to use the old logo for a period of time?
     
  4. Golfman25

    Golfman25 Well-Known Member

    Joined:
    Nov 6, 2015
    Messages:
    715
    Likes Received:
    352
    Trophy Points:
    62
    I'm sure the paper company sees value. :).
     
  5. Miner

    Miner Moderator Staff Member

    Joined:
    Jul 30, 2015
    Messages:
    392
    Likes Received:
    295
    Trophy Points:
    62
    Location:
    Greater Milwaukee USA
    There may be betters ways of doing this, but our document control procedure listed several situations where the documents could be revised without formal revision and approval. One of these was for a logo change.
     
  6. MarkMeer

    MarkMeer Well-Known Member

    Joined:
    Dec 3, 2015
    Messages:
    138
    Likes Received:
    62
    Trophy Points:
    27
    Agreed with Miner.

    You can include a caveat in your documentation control procedure to allow for variations that are inconsequential to the content. Examples might be: logo change, minor grammatical corrections, different formatting (e.g. fonts), different print mediums...etc.

    Some people use a major/minor version system (e.g. 1.0, 1.1, 1.2, 2.0...) to identify such minor changes. Minor revision updates can bypass formal approval and re-distribution (QA is authorized to unilaterally make such minor changes), whereas major revisions must go through formal change-control. As long as everyone has the same major version, it's all good!
     
  7. Mr. Bungle

    Mr. Bungle New Member

    Joined:
    Mar 30, 2016
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Not by choice. Merger with another will cause for a change in name and logo.
     
  8. Sidney Vianna

    Sidney Vianna Well-Known Member

    Joined:
    Jul 30, 2015
    Messages:
    127
    Likes Received:
    172
    Trophy Points:
    42
    So, that's business. Being concerned about a bureaucratic "approval" of (potentially) hundreds of documents because of a logo and name change should be the least of the worries.

    Chances are, due to the merger, business processes will have to be revised. THAT is something worth worrying about, in my opinion.
     
  9. RoxaneB

    RoxaneB Moderator Staff Member

    Joined:
    Jul 31, 2015
    Messages:
    858
    Likes Received:
    978
    Trophy Points:
    92
    Location:
    Ontario, Canada
    Depending on the politics of the merger, I'd suggest only changing the logo on a document when it comes due for review...if the logo is the only change needed to a document. Changing all of them now will result in a heavy workload on authors and approvers right now and on reviewers this time next review cycle...changing the logo right now on everything adds little value. If, as Sidney indicated, there is a process change, then the document should be revised as soon as possible, including the logo update.
     
    Miner likes this.
  10. Miner

    Miner Moderator Staff Member

    Joined:
    Jul 30, 2015
    Messages:
    392
    Likes Received:
    295
    Trophy Points:
    62
    Location:
    Greater Milwaukee USA
    Good point Roxane. Also, consider removing the logo from all internal QMS documents. I did that after the first logo change. The only document that retained a logo was the quality manual that was provided to external parties.
     
  11. ncwalker

    ncwalker Well-Known Member

    Joined:
    Sep 21, 2015
    Messages:
    260
    Likes Received:
    165
    Trophy Points:
    42
    Location:
    North Carolina
    Take a few minutes and check the kb size of the new logo. We were purchased 3 years ago and they said "Here's the new logo, use it" and gave us a file. That were you to print to full resolution would have needed a C size piece of paper for a logo that was supposed to be maybe 1/2" wide in the upper left hand corner of 8.5x11. Anyhoo ... everyone started putting this logo in and nobody thought to "compress pictures". Next thing you know, the servers started struggling.

    It's the little things.... :)
     
  12. Nick1

    Nick1 Member

    Joined:
    Jan 27, 2016
    Messages:
    49
    Likes Received:
    20
    Trophy Points:
    7
    You only have to create a Document Change Request if that is part of your procedures. You can just changed the document based on your "document control" procedure. If this procedure dictates you to create a Document Change Request per document, I am afraid you have to work accordingly. Or don't, create an NCR (non-compliant on procedure) included a request for change on procedure "Document Control" and change the procedure accordingly (include the option to change multiple files at once under certain circumstances).

    However, do keep in mind that you should request a new certificate and maybe include a new scope due to the merger.
     

Share This Page