CIT STANDARD OPERATING PROCEDURE |
SOP Template (replace "SOP Template" with the title of this standard operating procedure) |
Procedure Number: |
Related Processes and Procedures: |
All text in "blue" should be removed from this document prior to release as final draft.
Revision History
Date |
Author |
Version |
Description |
|
|
0.0 |
New Document |
|
|
|
|
|
|
0.9 |
Final Draft |
|
|
1.0 |
Approved Document |
|
|
|
|
BACKGROUND AND PURPOSE
(Provide any applicable background information and purpose of this document. For example, what are we trying to accomplish?)
Provide background material and purpose in this section. What is actually being recovered?
(If this section is not required, indicate "Not Applicable" rather than removing this section from the document).
SERVICES
(Specifically what services are covered within this procedure? What other services do these services depend on?)
Services included within the scope of this document are indicated below: The Service Owner, Service Manager and services the included services depend on are also listed. (This is a required section for this document.)
Included Service |
Service Owner |
Service Manager |
Service Dependencies |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
SCOPE
(What is in scope and what is not in scope for this procedure?)
Describe the situation or problem or specific deliverables applicable to this standard operating procedure.
(This is a required section for this document.)
CARD (Contingencies, Assumptions, Requirements, Dependencies)
(Indicate contingencies, assumptions, requirements and dependencies not indicated elsewhere which are required for execution of this procedure.)
Any relevant Contingencies, Assumptions, Requirements or Dependencies should be included.
- Contingencies describe "what if" scenarios and how to accommodate them.
- Assumptions are things which are presumed to be valid or true. Many assumptions will have a risk related to them.
- Requirements are items which are necessary in order to successfully execute this procedure.
- Dependencies are related items which depend on this procedure. Alternatively, the converse may also be relevant.
(If this section is not required, indicate "Not Applicable" rather than removing this section from the document).
TASK DESCRIPTION
Provide a description of the individual tasks which constitute the SOP. Flow chart diagrams may be included for clarity.)
Task Number |
Task Description |
Responsible Party |
---|---|---|
1. |
Provide a description of each task and the individual or functional unit responsible for executing this task. |
|
1.1. |
Flow charts or other diagrams may be included. |
|
2. |
|
|
3. |
|
|
PEOPLE
(Indicate functional units, titles of individuals who are both responsible and accountable for this SOP. If applicable, indicate skill sets required to execute the SOP in the event that the assigned individuals are not in a capacity to do so.)
Roles and responsibilities should be included in this section. Accountable individual or functional group for this standard operating procedure should be indicated. In the event that individuals or functional units specified cannot perform their function as described in this procedure, what skill sets would be required to perform the standard operating procedure?
APPENDICES and ATTACHMENTS follow the approval block.
Approvals
Name |
Function |
Comments |
Signature |
Date |
---|---|---|---|---|
|
Director |
|
|
|
|
Service Owner |
|
|
|
|
Service Manager |
|
|
|
Appendix A: First Appendix
Include any material for Appendix A as referenced in the main document.
(If this Appendix is not required, remove this appendix from the document).
Appendix B: Second Appendix
Include any material for Appendix B as referenced in the main document.
Add additional appendices, as required.
(If this Appendix is not required, remove this appendix from the document).
(Add any attachments that may have been too large to include in the main text portion of this document. Label as Attachment 1, Attachment 2, etc.)