| Templates | Question and answer structure that is set up in Iristrace for the collection of information by the user. The result of answering a template is a checklist. |
| Checkslits | Entity generated by answering a template. A checklist contains the set of questions, answers, comments, images, attached files, etc., recorded during the process of answering it. |
| Dashboard | A group of graphs, tables or cards that are configured based on the data recorded in Iristrace. You can configure different panels with different information. |
| Notifications | Functionality that allows the configuration of automatic notifications by email to users of the platform based on a series of actions related to a checklist. |
| Departments | A department is the entity that allows users and checklists to be organised in Iristrace. By default, they are called departments, but they can be named as establishments, customers, shops, teams, locations... whatever aspect you use to organise your controls and audits. |
| Users | Access to Iristrace is secure and requires a username and password to access. The user corresponds to an email address. Users can be configured with different roles to ensure proper access to information and to define secure processes with Iristrace. |
| Action plan | An action plan is a small checklist created from another checklist (parent) where an incident has been identified and requires the notification and participation of a user registered on the platform. |
| Workflow | Functionality that allows the configuration of automatic notifications by email to platform users, or the automatic creation of checklists, based on a series of conditions associated with the result of a checklist. |
| Reports | Reports composed with the information recorded from one or several checklists. They can be generated in different formats (PDF, Word, Excel) and for an individual checklist or a group of them. There are different configurable aspects to adapt the format to your needs (cover page, images, header and footer, etc). |
| Issues | Error or anomaly that you want to register in Iristrace in order to treat it. It has specific reports and dedicated management to facilitate its identification and the implementation of an action plan to mitigate its effect. |
| Advanced scoring | Scoring method that allows defining a more complex structure for counting points at template level than the usual method by category. It is configured through tags and requires the configuration of a specific scheme that can accommodate two levels. The summary score table of the checklist is displayed in the reports. |
| Scoring group | Group that is defined to structure on another level the cumulative score according to the tags defined for the advanced scoring of the template. |
| Threshold score | Threshold scoring method that you can configure for multiple-answer questions, being able to define rules that evaluate the points of several answers to determine the final score to be applied. |
| Valuation unit | Method used to calculate the score of weighted questions applied per category and defined at template level. There are different options based on the calculation by percentage or by the sum of the weights of the answers. |
| Audit | Report usually associated with certifications (quality, safety, etc.) that includes a group of checklists under an audit code that groups them together. |
| Tag | Literal used in association with the different functional entities in Iristrace (departments, users, templates) that allows information to be classified and filtered in order to optimise its management. |
| Offline | Method of answering checklists without the need for connectivity on the device on which the process of answering it is being carried out. The checklist is previously created when connectivity is available, all the information is downloaded to the terminal and allows the checklist to be operated without the need for connection to the server. Subsequently, all the checklist data (answers, comments, images, etc.) are synchronised when connectivity is restored. |
| Status | Situations through which the process of completing a checklist in Iristrace can pass. The statuses can mark obligatory milestones in the completion of questions, as well as being associated with user permissions to configure their accessibility. |
| Status group | Ordered grouping of states through which the execution of a checklist can pass, which allows the definition of the workflow to be followed during its operation. |
| Administration panel | Configuration panel of options applied to the private instance of the client. This panel is accessed from the "Customisation" option of the administrator user. |
| Categories | Question grouping that serves not only to group and structure the questions in a template, but also allows the calculation of subtotals (in % or by sum) in questions with assigned weights. |
| Predefined answers | Answer structure that can be stored and reused in other questions at a later date to speed up the configuration of the templates in Iristrace. |
| Default answers | Answers marked by default in the configuration of a question and which are already answered with that value when a new checklist is created. This option allows you to speed up the checklist response process. |
| Conditional answers | Iristrace allows the configuration of conditional tags associated with the answers so that certain questions only appear in the checklist if the appropriate answer has been marked (marked with the selected tag). |
| Metadata | Internal data of certain Iristrace functional entities that are made available to the user for inclusion in the configuration of the template to enrich the information managed in the checklists. |
