The document provides a template for reviewing project documentation and tracking any requested changes. It details the process the project manager will follow: 1) acquiring draft documents from authors, 2) determining reviewers, 3) scheduling reviews, 4) documenting any decisions or issues during reviews. The project manager will have authors update documents based on reviews and seek final approval before storing final versions or using them for training. The log excerpt shows a review was held on 1/27/17 for a Statement of Work, and requested changes were documented for the project manager to track.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
100%(1)100% found this document useful (1 vote)
288 views2 pages
Document Review and Change Log
The document provides a template for reviewing project documentation and tracking any requested changes. It details the process the project manager will follow: 1) acquiring draft documents from authors, 2) determining reviewers, 3) scheduling reviews, 4) documenting any decisions or issues during reviews. The project manager will have authors update documents based on reviews and seek final approval before storing final versions or using them for training. The log excerpt shows a review was held on 1/27/17 for a Statement of Work, and requested changes were documented for the project manager to track.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2
Document Review and Change Log
Document Instructions and Use:
This template is used when project artifacts are reviewed by a review team and certain changes are being requested. The project manager will do the following:
1. Acquire draft documentation from the author/creator.
2. Determine what members of the project team will need to review; include the author/creator. 3. Schedule review meeting and review team, and pre-send the document(s) that will be reviewed. 4. Review date: Review each document(s) with the review team and use this log for each document(s). Document any decisions/issues related to content changes so that they are tracked. 5. Author/creator updates the draft documentation for final review and then asks for final approval. 6. If approved, document is stored in Project folder until ready to transfer to gold source or needed for training. 7. If not approved, same process revisited. Document Review and Change Log Document XXX SOW dated 1/22/17 Review 1/27/17 Review Team: MiXXX, NXXX, BXXX, TrXXXs and LoXXX Name: Date: Version: Author/Creator: Sara SXXXXX, SHI
Page Section Title/Bullet Requested Change Published Version Approved/
and Date Complete/ Follow-up 4 2.1 In Scope First sentence; need a period and space between engagement and The engagement 4 2.1 In Scope/2nd Envisioning Workshops How many will there be, and what will the topics be? Need to require the they are scheduled in advance to ensure team is available 5 2.5 Key Cust Pre-Engagement Questionnaire, need to have a specific period of time Act that we will have to review and complete and finalize with vendor 5 2.5 Key Cust Sessions What are these? Are these the Knowledge Transfer sessions, Act / 5 & 6 training sessions, what specifically? Need to ensure scheduled in advance 5 3.1 R&R Nick will be the POC for XXX to coordinate FF Staff; Travis and Lonnie share technical expert hats, Travis IT Supervisor, Brett Project Sponsor
Copywriting Successful writing for design advertising and marketing Third Edition by Gyles Lingwood, Mark Shaw 9781529420258 1529420253 - Get the ebook in PDF format for a complete experience