reference number |
attribute (an asterisk indicates a multi-value field) |
name |
tier听 |
category听 |
type |
notes for completion |
required |
1.1 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
name 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Name 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 1 |
Overview 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榥ame鈥 is the colloquial name used to identify the algorithmic tool. |
TRUE听 听 |
1.2 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
description听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Description听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 1 |
Overview 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙escription鈥 is a description to give a basic overview of the purpose of the algorithmic tool. It should include: - how the algorithmic tool is used - why the algorithmic tool is being used |
TRUE听 听 |
1.3 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
website听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
URL of the website 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 1 |
Overview 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
URL 听 听 听 听 |
The attribute 鈥榳ebsite鈥 is the URL reference to a page with further information about the algorithmic tool and its use. This facilitates users searching more in-depth information about the practical use or technical details.This could, for instance, be a local government page, a link to a GitHub repository or a departmental landing page with additional information. |
FALSE 听 |
1.4 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
contact_email听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Contact email听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 1 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榗ontact_email鈥 is the email address of the organisation, or team for this entry. For continuity and security purposes, we would advise using or creating a team email address instead of using an individual email address. 听听 |
TRUE听 听 |
2.1.1听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
organisation 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Organisation/ department 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榦rganisation鈥 is the full name of the organisation, department or public sector body that carries responsibility for use of the algorithmic tool. For example, 鈥楧epartment for Transport鈥.听 |
TRUE听 听 |
2.1.2听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
team 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Team 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榯eam鈥 is the full name of the team that carries responsibility for use of the algorithmic tool. |
TRUE听 听 听 听 |
2.1.3听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
senior_responsible_owner 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Senior responsible owner 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榮enior_responsible_owner鈥 is the role title of the senior responsible owner for the algorithmic tool. |
TRUE听 听 听 听 |
2.1.4听 |
external_supplier_involvement |
External supplier involvement |
Tier 2 |
Owner and responsibility |
UTF-8 string |
Have external suppliers been involved in the development and operation of the tool? Please choose: Yes; No |
TRUE听 |
2.1.4.1听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
external_supplier* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Supplier or developer of the algorithmic tool |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榮upplier鈥 gives the name of any external organisation or person that has been contracted to develop the whole or parts of or the algorithmic tool.听听 |
FALSE听 听 |
2.1.4.2听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
companies_house_number*听 听 听 听 听 听 听 听 听 听 听 听 |
Companies House Number 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榗ompanies_house_number鈥 gives, if available, the Companies House number of the external organisation that has been contracted to develop either the whole, or a part of the algorithmic tool. You can find a company鈥檚 Companies House number by searching the Companies House register or using the Companies House API. If multiple organisations have been contracted, the Companies House Number for all of the companies should be provided, specifying which number represents which organisation. |
FALSE 听 |
2.1.4.3听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
external_supplier_role*听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
External supplier role 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榚xternal_supplier_role鈥 gives a short description of the role the external supplier had in the development of the algorithmic tool.If multiple organisations have been contracted or there are multiple companies involved in the delivery of the tool, these relationships should be described clearly and concisely.听 |
FALSE听 听 |
2.1.4.4听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
procurement_procedure_type*听 听 听 听 听 听 听 听 听 听 听 听 |
Procurement procedure type 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榩rocurment_procedure_type鈥 details the procurement procedure through which the contract has been set up. For example, 鈥榦pen鈥, 鈥榬estricted鈥, or 鈥榗ompetitive procedure with negotiation鈥, or 鈥榗all-off from a dynamic purchasing system鈥, and 鈥榗all-off from a framework鈥 where a contracting authority has awarded to a supplier under a pre-established framework agreement.听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
FALSE 听 |
2.1.4.5听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
data_access_terms* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Terms of access to data for external supplier |
Tier 2 |
Owner and responsibility 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙ata_access_terms鈥 details the terms of access to (government) data applied to the external supplier. 听听 |
FALSE |
2.2.1 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
detailed_description 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Detailed description |
Tier 2 |
Detailed Description and Rationale 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙etailed_description鈥 gives a detailed description of how the algorithmic tool works. Compared to the high-level description in Tier 1, the detailed description should provide an explanation at a more granular and technical level, including the main rules and criteria used by the algorithm/algorithms. This field is optional and is very likely to include information required in other fields below. It is open to the organisation to decide whether they want to include a summary detailed description in addition to the information below. 听听 |
FALSE |
2.2.2听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
scope听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Scope听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Detailed Description and Rationale听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榮cope鈥 describes the purpose of the tool in terms of what it has been designed for and what it has not been designed for. This can include a list of potential purposes that the tool was not designed for: this can help to avoid听 misconceptions about the scope and purpose of the tool. 听 |
TRUE听 听 |
2.2.3听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
benefit听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Benefit听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Detailed Description and Rationale听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榖enefit鈥 describes the key benefits that the algorithmic tool is expected to deliver, and an expanded justification on why the tool is being used.听 |
TRUE听 听 |
2.2.4听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
previous_process听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Previous process听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Detailed Description and Rationale听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榩revious_process鈥 gives a description of the decision making process that took place prior to the deployment of the tool, where applicable. |
FALSE |
2.2.5听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
alternatives_considered听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Alternatives considered听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Detailed Description and Rationale听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榓lternatives_considered鈥 details, where applicable, a list of other algorithmic and non-algorithmic alternatives considered. It should explain why a certain algorithmic approach was chosen over other approaches, and why the chosen tool is the best available option given any known risks and shortcomings and trade-offs. |
FALSE |
2.3.1听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
process_integration听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Process integration听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Decision-making Process听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榩rocess_integration鈥 explains how the algorithmic tool is integrated into the decision-making process and what influence the algorithmic tool has on the decision-making process. It gives a more detailed and extensive description of the wider decision-making process into which the algorithmic tool is embedded.听 |
TRUE |
2.3.2听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
provided_information 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Provided information 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Decision-making Process听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榩rovided information鈥 details how much and what information the algorithmic tool provides to the decision maker. For example, this can include the prediction output and the form in which it is presented to the decision maker. This field should also detail any internal procedures that are in place to document the relationship between the output and the decision. Such procedures should, where applicable, include information on the extent to which decisions made have been influenced by the tool. |
TRUE |
2.3.3听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
human_decisions_and_review听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Human decisions and review 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Decision-making Process听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榟uman_decisions_and_review鈥 describes the decisions that people take in the overall process. It should also detail human review options. For example, specific details on when and how a person reviews or checks the automated decision. 听 听 听 听 |
TRUE听 听 |
2.3.4听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
required_training听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Required training听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Decision-making Process听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榬equired_training鈥 details the required training those deploying or using the algorithmic tool must undertake, if applicable. This can include training for operations, users, maintenance, compliance, or oversight personnel. For example, the person responsible for the management of the tool had to complete data science training. |
TRUE |
2.3.5听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
appeals_and_review 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Appeals and review 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Decision-making Process听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榓ppeals_and_review鈥 details the mechanisms that are in place for review or appeal of the decision available to the general public, where applicable.听听 |
FALSE |
2.4.1听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
method 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Method听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榤ethod鈥 indicates which types of methods or models the algorithm is using. For example, linear regression, expert system, different kinds of machine learning algorithms, and so on. This can also include a short description of the method(s) used and/or a link to resources providing further resources on the method(s).听 |
TRUE听 听 |
2.4.2听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
frequency_and_scale_of_usage听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Frequency and scale of usage 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榝requency_and_scale_of_usage鈥 gives information on how regularly the algorithmic tool is being used and the scale of use. For example, the number of decisions made per month, the number of citizens interacting with the tool, and so on.听听 |
TRUE |
2.4.3听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
phase听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Phase听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榩hase鈥 indicates in which of the following stages or phases the tool is currently in. Please choose: Idea; Design; Development; Beta/Pilot; Production; Retired. This field includes date and time stamps of creation and any updates.听听 |
TRUE听 听 |
2.4.4听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
maintenance听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Maintenance听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榤aintenance鈥 gives details on the maintenance schedule and frequency of any reviews. This includes information such as how often and in what way the tool is being reviewed post-deployment, and how it is being maintained if further development is needed. This can concern maintenance both by the supplier as well as by the operator/user of the tool. 听 |
TRUE |
2.4.5听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
model_performance听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Model performance 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榤odel_performance鈥 gives details on the model or tool鈥檚 performance. Useful metrics to consider are: accuracy metrics (such as precision, recall, F1 scores), metrics related to privacy, and metrics related to computational efficiency. It also gives details on any identified biases in the data and model. If applicable, it describes how bias and accuracy have been balanced in the model.听 |
TRUE |
2.4.6听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
system_architecture听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
System architecture听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 听 听 听 听 |
URL 听 听 听 听 |
The attribute 鈥榮ystem_architecture鈥 is the URL reference to documentation about the system architecture. For example, a link to a GitHub repository image or additional documentation about the system architecture. 听 听 |
听 听 听 听 |
2.4.7听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
source_data_name*听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Source data name 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榮ource_data_name鈥 gives, if applicable, the name of the datasets used.听听 |
TRUE听 听 |
2.4.8听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
source_data_description* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Source data听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榮ource_data_description鈥 gives an overview of the data used to train, test, configure and operate the algorithmic tool, specifying which data was used for which purpose. This should encompass data used by both the public sector team and the supplier, where applicable. It should include a description of the types of variables or features used to train, test or run the model - for example 鈥榓ge鈥 or 鈥榓ddress鈥. In certain cases, it might not be feasible for a team to disclose all the variables in a dataset. In this case, teams should disclose - at a minimum: whether the data contains personal and special category information; variables of interest, such as protected characteristics and potential proxies; and variables with high predictive power or that have a significant bearing on the model. 听 听 听 听 听 听 听 听 |
TRUE听 听 |
2.4.9听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
source_data_url* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Source data URL听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
URL 听 听 听 听 |
The attribute 鈥榮ource_data_url鈥 provides a URL to the openly accessible dataset wherever possible.听 听 听 听 听 |
FALSE 听 |
2.4.10听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
data_collection* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Data collection听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙ata_collection鈥 gives information on the data collection process. This can include details on the original purpose of data collection and the context in which it was initially collected. If the data was initially collected for different purposes and is now being repurposed, there should be consideration of to what extent the data transferable and suitable for the new context. 听 |
TRUE听 听 |
2.4.11听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
data_cleaning 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Data cleaning听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙ata_cleaning鈥 gives information on data cleaning, including a description of any pre-processing or cleaning of the data conducted by either the supplier or public sector customer.听 听 听 听 听 听 听 听 听 听 听 |
FALSE听 听 |
2.4.12听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
data_completeness_and_representativeness 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Data completeness and representativeness听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙ata_completeness_and_representativeness鈥 provides information on the completeness of the data, including missing data and on how representative the data is.听 听 听 |
TRUE听 听 |
2.4.13听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
data_sharing_agreements* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Data sharing agreements听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data听 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙ata_sharing_agreements鈥 provides further information on data sharing agreements in place.听听 |
TRUE听 听 |
2.4.14听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
data_access_and_storage* 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Data access and storage听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Technical Specification and Data 听 听 听 听 听 听 听 听 |
UTF-8 string |
The attribute 鈥榙ata_access_and_storage鈥 details: who has, or will have, access to this data; how long it is stored; under what circumstances; and who is responsible for its storage. Where personal and/or sensitive data is being stored and accessed, a description of the mechanisms used to protect the security and privacy of the data should be described, including technical (e.g. de-identification techniques, Privacy Enhancing Technologies) and operational (e.g. role-based access controls) methods. |
TRUE听 听 |
2.5.1听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
impact_assessments听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Impact assessments 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Risks, mitigations and impact assessments |
UTF-8 string |
The attribute 鈥榠mpact_assessments鈥 provides the names and a short overview of the impact assessments conducted, date of completion, and if possible a summary of the findings. If available, a publicly accessible link should be provided. If multiple impact assessments were completed, they should all be listed in this field. Examples of impact assessments are Data Protection Impact Assessments (DPIAs), Equality Impact Assessments, Algorithmic Impact Assessments. This field also provides an opportunity to list other monitoring and evaluation requirements under relevant legislation.听 |
TRUE听 听 |
2.5.2听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
risks听 听 听 听 听 听 听 听 听 听 听 听 听 听 听 |
Risks 听 听 听 听 听 听 听 听 听 听 听 |
Tier 2 |
Risks, mitigations and impact assessments |
UTF-8 string |
The attribute 鈥榬isks鈥 is an overview and a description of the possible risks that have been identified for the algorithmic tool. It also gives an overview of how the risks have been mitigated. 听 听 |
TRUE听 听 |