项目事 件记录表.docVIP

Project Name Document No. Rev status Issue Register 2000 ?  HYPERLINK http://www.trinitystudio.ltd.uk http://www.trinitystudio.ltd.uk Date printed:  DATE \@ M/d/yy 12/21/17 Project Name Project identifier ISSUE REGISTER Document Number: Revision: Revision date: Document Owner: 2000 ?  HYPERLINK http://www.trinitystudio.ltd.uk http://www.trinitystudio.ltd.uk  PAGE 5 of  NUMPAGES 9 Date printed:  DATE \@ M/d/yy 12/21/17 Revision History Revision No.Revision dateChanges made0First issue123 Approval The following are authorized to approve issue of this document TitleNameSignatureDate of signature The original signed copy of this document is stored:  Signed release forms for this document are stored in the Quality Section of the Project Library. Distribution List TitleNameLocation Purpose The Issue Register is a record of each identified issue. It is in two sections. The complete register should be contained within one ring binder. Section one is a list of the issues showing the current status of each one. Section two is a collection of issue monitoring sheets. The issue monitoring sheets are ‘living documents’ and are updated at each project planning meeting or whenever there is significant change of status. It is not necessary to update the revision status of the parent document every time an individual monitoring sheet is updated. It may be more effective/efficient to update the monitoring sheets by hand as each risk event is discussed. Document release forms are is used to control the issue and revision status of documents distributed electronically. A document release form is included as the last page of the document. Current Status Codes Keep the status categories to a minimum. The Issue is either ‘Open’, ‘Merged’ with another issue, or, ‘Closed”. Open – The Issue is identified, registered and owned by an individual. Merged – The Issue is closely linked to another issue