Training Plan Version: Error! Unknown document property name.
Summary Report Module
Version: Error! Unknown document property name.
Summary Report – Module
[In a real-world scenario, you would include a title that lets the reader know what the report covers.]
Version
Prepared By: <Jude Akassap
Date: 11/22/21
VERSION HISTORY
[Provide information on how the development and distribution of the was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version. For example, the reason for the first version could be ‘document creation’ or ‘initial document’ and subsequent reasons could be things like ‘updated ’.]
Version #
Implemented
By
Revision
Date
Approved
By
Approval
Date
Reason
1.0
Jude akassap
11/22/21
John A
11/28/21
This section involves the description of the report’s purpose, the executive summary, detailed summary, recommendations, and suggested actions which will later be presented to the executive management of XYZ Technology Services.
Note to the Author
[This document is a template. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the report.
Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.
Blue italicized text enclosed in angle brackets () indicates a field that should be replaced with information specific to a particular project. When replacing text, be sure to change the font so that it is no longer blue and italicized. You want the final report to look professional and clean.
Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.
When using this template, it is recommended that you follow these steps:
Replace all text enclosed in angle brackets (e.g., ) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):
Select File>Properties>Summary and fill in the Title field with the Document Name and the Subject field with the Project Name.
Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields with the appropriate information for this document.
After you click OK to close the dialog box, update the fields throughout the document with these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update an individual field by clicking on it and pressing F9. This must be done separately for Headers and Footers.
Modify boilerplate text as appropriate to the specific project.
To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.
To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”
Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which appear throughout the document as blue italicized text enclosed in square brackets.]
TABLE OF CONTENTS
1 Introduction 5
1.1 Purpose 5
2 Executive Summary 5
3 Detailed Summary 5
3.1
3.2
3.3
4 Recommendations 5
5 SuggEstED aCTIONS 5
Appendix A: Approval 6
APPENDIX B: REFERENCES 7
APPENDIX C: KEY TERMS 8
Introduction
Purpose
The main aim of a risk register is identifying, recording, and tracking potential risks in a particular project. A chance is the occurrence of unexpected situations that would have a negative or a positive impact on a project. Whenever team members identify something that could affect the project, it should be evaluated and logged in the risk register. As projects get complex, more extensive and more extended, it becomes difficult for management to keep up with everything; therefore, a risk register is a necessity for managers. If managers fail to track and review risks regularly, a thing may be neglected and forgotten. Although some dangers may appear unlikely or small, at first, they may have a more significant impact later on the project.
Executive Summary
The risk register includes main discussion topics like risk identification, risk evaluation and risk control, under risk identification; the subtitles have business units, operational risks and possible outcomes. The business units include accounting, human resources, information technology, manufacturing and marketing. The operational risks involved include; accounting software fails, limited staffing, email viruses, tariff wars and advertisement misquote prices. Possible outcomes of the risks involve an inability to process payroll, overworking employees and infected servers. Risk identification consists in identifying an existing risk control measure, if any and remarks. Under risk control, I have elaborated on additional risk control measures, follow-ups and comments.
detailed Summary
An operational risk involved in the accounting department is a failure in software used in accountancy practices and shortcomings in information technology systems, creating critical business failures. The accounting department fails to monitor spending made by other departments, which results in losses due to high expenditure. Tax documents may be received late by the accounting department, resulting in offences and penalties by the government and the inability of employees to file taxes. The human resource department may encounter limited staffing of employees due to unqualified personnel applying for the job. Coronavirus may also be a risk in human resources as it requires social distancing, which may not be possible in an open office layout. Moreover, human resource systems may go down, causing a loss in employee files and a delay in hiring.
In addition, the department of information technology may experience software failures due to corrupted computers in the organization which may in turn cause delays in processing payrolls to the employees. Some computers may have email viruses acquired after visiting some sites causing the servers to be infected. Furthermore, too much network traffic might cause slow network speeds. The manufacturing department may experience tariff wars in the industry, which might cause higher prices for international trade. A stinking talent pool where a lot of employees might be unqualified may cause limitations during staffing. In the stakes and marketing department, advertisement misquotes prices caused by carelessness might cause a loss in revenue. During marketing, a product recall may cause failure in production and income from memory.
Recommendations
I recommend creating an assessment team involving security analysts who will update, install and manage software on the networks and systems they monitor. In addition, creating a post for the chief information officer will ensure technologies and processes within a firm’s IT organization ensure the deliverance of outcomes that support business goals. The human resource department will employ qualified personnel, therefore, ensuring smooth flow of operations. Moreover, the finance department will ensure efficient management of the firm’s finances.
SuggEstED aCTIONS
The manufacturing department should ensure they produce quality goods at all times through the employment of qualified personnel. In addition, the marketing department should widely advertise the firm’s product using media platforms to capture a greater audience.
Appendix A: Approval
The undersigned acknowledge they have reviewed the above and agree with the approach it presents. Changes to this will be coordinated with and approved by the undersigned or their designated representatives.
[For this section, consider who would need to approve this Summary Report. For your submission, you only need the Role of the individuals whose signatures are desired. Examples of such individuals are Quality Manager or Tester. Add additional lines for signature as necessary. Although signatures are desired, they are not always required to move forward with the practices outlined within this document. Think about who might need to approve your recommendations and suggested actions. For the purposes of this class, you can simply make up names for the various titles (for example, Mickey Mouse, CEO etc.)]
Signature:
Date:
Print Name:
Title:
Role:
Signature:
Date:
Print Name:
Title:
Role:
Signature:
Date:
Print Name:
Title:
Role:
APPENDIX B: REFERENCES
[Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary. This is where you would want to reference your Risk Register and any other documents that you need to. For the purposes of this class, please include references to course material or outside sources that you are using in your work.]
The following table summarizes the documents referenced in this document.
Document Name and Version
Description
Location
[Provide description of the document]
APPENDIX C: KEY TERMS
[Insert terms and definitions used in this document. Add rows to the table as necessary. Keep in mind that you are typically writing a summary report for someone who is not familiar with information technology. Be sure to define any terms here that might need to be explained.]
The following table provides definitions for terms relevant to this document.
Term
Definition
[Insert Term]
[Provide definition of the term used in this document.]
[Insert Term]
[Provide definition of the term used in this document.]
[Insert Term]
[Provide definition of the term used in this document.]
Revision Date: Error! Unknown document property name. Page 2 of 10
NOT DONE – CDC_UP_Training_Plan_Template.doc
Page 2 of 8
1
Revision Date: Error! Unknown document property name.
The post Training Plan Version: Error! Unknown document property name. Summary appeared first on PapersSpot.
