Loyola University Chicago

Information Technology Services

Project Management Templates

The LUC ITS VPMO Methodology is based on a "best fit" approach, meaning there are required documents for a project, suggested documents (if needed for a larger project), and there are informational documents to help run each phase. 

As of April 2017, the Project Document Checklist assists Loyola's ITS project lead's to use specific types of documentation to use on projects. If some documents are not used, there is a section to document why they are not being used so future teams can learn from those decisions. 

Below are column header definitions for clarity on the graph below:

  • Phase = Which stage you are in the overall project management process of the project.
  • Required = These templates should be used for most projects.
  • Suggested = These templates are in addition to the “required” templates to help with managing many unknowns, communications for larger groups, etc.
  • Informational = These templates or documents are available for use at the discretion of the Project Manager or Project lead.




Project Document Checklist

Project Scope

PM Menu of Services

Status Report

Meeting Agenda

Meeting Minutes


Executive Status

Staffing Commitment

Initial Project Plan

Initiation Phase Agenda

Initiation Phase Review

Sponsor Feedback Form

Project Kickoff Presentation

Project Roles and Responsibilities

Project Checklist


High-Level Project plan (MS Excel)

High-Level Project plan (MS Project) 


Functional Specs Doc

Communication Plan

Risk Management

Work Breakdown Structure

Comprehensive Project Plan

RACI Template

Action Item List


Stakeholder Registry

Planning Phase Review

Advanced Risk Management 

Planning Phase Kickoff Agenda

MS Project Tutorial




Deliverable Acceptance Form

Execution Phase Kickoff Agenda

Defect Log Template

Execution Phase Review  


Close-Out Questionnaire

Closeout Metrics Template


Project Feedback

Closeout Meeting Agenda

Project Closeout Report

Process Modification Recommendation

Closeout Phase Review

Project Closeout Presentation



This policy covers all of Loyola University Chicago’s computing, networking, telephony and information resources. All members of the University community share in the responsibility for protecting information resources for which they have access or custodianship.


The purpose of this policy is to establish the University’s approach to information security and to establish procedures that will help identify and prevent compromises of information around the University’s computing, networking, telephony and information resources, as well as to create a secure baseline standard for the University’s computing, networking, telephony and information resources.


Individuals Covered

This policy applies to all persons accessing and using computing, networking, telephony and information resources through any facility of the University. These persons include students, faculty, staff, persons retained to perform University work, and any other person extended access and use privileges by the University given the availability of these resources and services, and in accordance with University contractual agreements and obligations.

Systems and Resources Covered

This policy covers all computing, networking, telephony and information resources procured through, operated or contracted by the University. This policy also covers any computing device connecting to and utilizing University information resources. Such resources include computing and networking systems including those that connect to the University telecommunications infrastructure, other computer hardware, software, databases, support personnel and services, physical facilities, and communications systems and services.  Authorized support personnel for high security systems are outlined in the ITS Roles and Responsibilities Matrix and Audit Calendar.

Information Classification & Protection

In order to ensure that information about members of the University community is properly protected, all information will be classified in accordance with the Data Classification Policy. Information that is classified as Loyola Protected or Loyola Sensitive data will receive additional protections as described in the Personally Identifiable Information (PII) Protection Policies. Data deemed PCI-DSS relevant must comply with all PCI-DSS requirements as outlined by the PCI Data Security Standard Version 3.2. All Personal Health Information (PHI) must be protected or properly redacted as outlined in the HIPAA Privacy Rule.

User Training and Awareness

Effective information security requires a high level of participation from all members of the University and all must be well informed of their responsibilities. To facilitate this, information security awareness materials and training will be provided to the Loyola community in accordance with the ITS Security Awareness Policy.

Physical and Environmental Security

Centralized computer facilities will be protected in physically secure locations with controlled access, in accordance to the ITS Access Control Policy. They will also have appropriate environmental safeguards. Departmental computers housing Loyola Sensitive or Loyola Public data may require physical and environmental security safeguards. All servers containing Loyola Protected data must be housed in an approved ITS data center.

Incident Response

Information security incidents have the potential to negatively impact members of the University community and to harm the University’s reputation. Therefore, it is important that all information security incidents are handled confidentially and appropriately. All information security incidents will be handled in accordance with the ITS Incident Response Plan.

Risk Assessment

Security incidents are more likely to occur when there are unknown and unaddressed risks and vulnerabilities in information systems. Therefore, risk assessments will be conducted in accordance with the ITS Risk Assessment Process. In addition, the IT Security Team will periodically perform vulnerability assessments, per the ITS Vulnerability Assessment Policy.

Network Security

All networking devices procured through, operated or contracted by the University will be configured in accordance with the ITS Router and Switch Security Standard, the ITS Network Firewall Policy, or the ITS Wireless Access Point Policy, depending on the type of device that it is.

Computer Security

All workstations, desktops and laptops procured through, operated or contracted by the University will be configured in accordance with the ITS Computer Security Standard and the ITS Password Standard.

Server Security

All servers procured through, operated or contracted by the University will be configured in accordance with the ITS Computer Security Standard and the ITS Password Standard.


Viruses and other malicious programs can compromise the confidentiality, integrity, and availability of information resources. All systems connected to University networks shall abide by the ITS Antivirus Policy.

Key Management

All systems that store Loyola Protected data will encrypt said data using appropriate encryption techniques, as defined within the Encryption Policy. This policy requires the use of private keys to encrypt the data.

Individuals who, because of their job function, are responsible for using a private key will be designated as “key custodians”. No key custodian will have knowledge of a majority of the private keys.

Any private keys created during the encryption process will be maintained via a key management procedure specific to that system. This procedure is determined by the key custodians, and must include the following items:

  • Require split knowledge and dual control of private keys, so that at least two key custodians are required to install a single key component or enter a passphrase, for the generation or installation of an encrypting private key.
  • An individual who is not serving as a key custodian must be present during the installation of the private key to witness the installation and sign the ITS Key Management Log. The witness will then submit the ITS Key Management Log to the ISO.
  • Require that key custodians sign the ITS Key Management Responsibilities Form, indicating they understand their key management procedures and responsibilities.
  • Restrict private keys to the fewest number of key custodians possible
  • Store private keys securely in the fewest possible locations
  • Generate strong keys and securely distribute them to the appropriate key custodians
  • Change private keys at least annually, or as deemed necessary, whichever comes first.
  • Replace all known or suspected compromised private keys immediately.
  • Securely destroy all private keys that are changed and re-encrypt the data with new private keys.

Log Management Standard

System logs are required to enable effective troubleshooting of system problems and are a required component of the incident response process. All systems that store, transmit or process Loyola Protected data shall abide by the ITS Log Management Standard.

Policy Adherence:

Failure to follow this policy can result in disciplinary action as provided in the Employee Staff Handbook, Student Worker Employment Guide, and Faculty Handbook.  Disciplinary action for not following this policy may include termination, as provided in the applicable handbook or employment guide.


Exceptions to this policy will be handled on a case-by-case basis and reviewed and approved by the University Information Security Office.


This policy, and all policies, standards, handbooks and supporting materials contained within, will be reviewed by the ISO on an annual basis.


In emergency cases, actions may be taken by the Incident Response Team in accordance with the procedures in the ITS Incident Response Handbook. These actions may include rendering systems inaccessible.


Server – a software program, or the computer on which that program runs, that provides a service to client software running on the same computer or other computers on a network


  • June 16, 2008: V 1.0, Initial Policy
  • October 6, 2011: V 1.1, Revised
  • June 17, 2015: V 1.1, Annual Review for PCI Compliance
  • June 18, 2015: V 1.1, Reformatted to standard policy format
  • December 5, 2013: V 1.2, Corrected reference to Incident Response Plan
  • April 14, 2016: V 1.2, Annual Review for PCI Compliance
  • June 23, 2017: V 1.2, Annual Review for PCI Compliance
  • July 21, 2017: V 1.3, Added HIPAA information, updated PCI-DSS version
  • June 14, 2018: V1.4, revised Exception section, Annual review for PCI Compliance
  • August 27, 2019: V1.4, Annual Review for PCI Compliance
  • August 10, 2020: V1.4, Annual Review for PCI Compliance