Menü aufrufen
Toggle preferences menu
Persönliches Menü aufrufen
Nicht angemeldet
Ihre IP-Adresse wird öffentlich sichtbar sein, wenn Sie Änderungen vornehmen.
Version vom 2. Juli 2026, 15:30 Uhr von KoKl (Diskussion | Beiträge)
(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)
Create review – step 1

In the first step you record the master data of the review. Here we explain all fields:

Mandatory fields:

  • OrgUnit: The organizational unit responsible for the review, or the organizational unit being reviewed.
  • Name & description: Record here what the purpose of the review is.
  • Interview partner: These are the people who give you the answers to the questions in the review. If you set "Self-Assessment" for the type of review, the users in this field later receive the e-mails that request them to answer the questions. As with the responsible person, HITGuard fills this field with the responsible person from the organizational unit. However, you can also enter any number of other regular HITGuard users.

Further input fields:

  • Note: Further notes, e.g. on the execution.
  • Lead auditor: Main responsible person of a review. When you create the review, HITGuard automatically enters your user here.
  • Co-auditors / accompaniment: Subject matter experts who are brought in to the review for special topics.
  • Responsible persons: The responsible persons of the organizational unit or the area. Just as with the Interview partner field, HITGuard fills this field with the responsible person from the organizational unit.
  • Start and end date: Planned time span. Every review requires both dates. For self assessments (see below) the end date is called answering deadline.
  • Type: Controls how the review is carried out (see below). This setting can only be changed in the Draft status.
  • Workflow plans: Shows in how many workflow plans the review occurs as active or paused. Links can be set, removed or paused here.
  • Created by workflow plan: Refers to the triggering workflow, if the review was created automatically.
  • Change log: Records who edited, changed the status or completed it, and when.