Purpose:
Section titled “Purpose:”The purpose of this WI is to detail the requirements needed to create a process in Knowledge - Halo. A process is a high-level description of a large tasks or a series of related tasks. Use the related articles as reference, if needed.
Naming Convention:
Section titled “Naming Convention:”Keep the name specific to the work being done. EX: New Client Onboarding Please DO NOT add the prefix. Pzzl script will add the prefix when the article is in “Review” status.
Section titled “Keep the name specific to the work being done. EX: New Client Onboarding Please DO NOT add the prefix. Pzzl script will add the prefix when the article is in “Review” status.”Scope:
Section titled “Scope:”How to request a process header affects the entire organization. The approval of a process creation is the responsibility of the CI/QA committee.
Responsibility:
Section titled “Responsibility:”All process owners will work together with the CI/QA Committee to ensure the work being performed falls into the process category. If so, the CI/QA Committee will approve creation of the process.
Completion Criteria:
Section titled “Completion Criteria:”The completion of a properly created process header and process outline.
Records:
Section titled “Records:”NA
Steps:
Section titled “Steps:”Decision Matrix:
Section titled “Decision Matrix:”- Does the work being done involve three or more medium to large tasks?
- Does the work being done rely on more than one person or department to complete?
- Is there typically a time delay of hours, days, or even longer between steps or completion?
- Will the work being done require multiple SOPs and WIs to complete the tasks? If you answered “yes” to one or more of these questions, please contact the CI/QA Committee to confirm that a process header is needed.
Once it has been approved to create a process, follow these steps:
- Open “Knowledge-Halo” and click on the “All CIT Articles” from the upper left corner.
- Click the “Create from template” icon in the upper right corner.
- Select “Process Template” from the list and fill it out and include the following informtion:
-
Title - the title should only include the name of the process, and stated as simply as possible.
-
Ex: New Client Onboarding (do not include how-to or any verbs in the title)
-
Summary - the summary should be a simple, one-sentence description of the task that is being done.
-
Reference the header of this article for an example.
-
Purpose - the purpose statement describes in more detail as to why the process is needed and what the outcome will be.
-
Ex: The purpose of this process is to outline the work required to successfully onboard a new client. It may include cross-references to articles related to offboarding or re-onboarding an existing client.
-
Scope - the scope statement should include the roles, departments or areas, that are affected by this Process along with any inclusions or exclusions.
-
Ex: The scope of this process includes the following (list all roles or departments), and what is responsible for completing…
-
Responsibility - the responsibility defines the role(s) of who owns the outcome of this process. Any additional roles and departments will be defined above in the scope.
-
Process References - list or attach any process maps created for the defined process. Author will also create relationships for any supporting SOPs, STs, and WIs required to complete the process.
Process References:
Section titled “Process References:”- Create a relationship back to related process. Note: Please add KB relationships to core process, process, SOPs or other WIs on the right.