Glossary Follow
Field/Register: Custom Field
Source Case Reference
This is a reference field for historical data from Smartsheet, Globocol or Invoka - when populated this will indicate it is a historic record with core fields populated and remaining data attached as a pdf file - this will be blank on new records and doesn't need to be populated.
Field/Register: Entities
Entities
Entities in Clue are singular, identifiable objects encompassing people, places, locations, and more. Clue adheres to the principle of a single record for each entity, and each can be associated with multiple, separate core workflows.
Address
Store place information such as addresses, streets, and localities, or locations such as a field or a point within a park.
Communication
Log telephone numbers, email addresses, social media accounts, IP addresses, and IMEI numbers, etc.
Organisation
A Cricket Club is logged in Clue as an Organisation - this means each Club only exists once in Clue and is linked to Incidents, Persons, Addresses accordingly - this mitigates against multiple entries of Clubs and enables visibility into patterns, trends etc. Clubs will initially be uploaded/maintained by The Cricket Regulator Triage team in order to maintain the data quality
Person
Used to record individuals such as victims, the accused, subjects, and witnesses. Personal information, like passport details, nicknames and aliases, can also be added.
Field/Register: Operational Function
Global Search
The Search function automatically indexes data in almost all languages, including text within attachments. Subject to permissions, users can search all accessible data using familiar syntax and operators, fuzzy matching and proximity searching, and results can be filtered. See the Clue Support - Global Search for more information
Investigator Notes
Investigator Notes are used as your diary of activity to maintain a running narrative and provide a comprehensive operational audit trail on the activities you have carried out during the process/investigation. To provide integrity, notes are "read only" once they have been entered.
Linking
The link function is the foundation for establishing relationships and connections between records such as an Incident record linked to a Person record. When linking you should search to see if that record already exists and if you have multiple, possible Entities then you will need to decipher which Entity to select - for example if you have 2 John Smiths in Clue you might look at Date of Birth to decipher which to select. When linking you will be asked for a Link Reason. A Link Reason is what provides context as to why the two records are related i.e. A Person is linked to the Incident as the Subject or Accused
Tasking
Tasks are under Tools in the navigation - and are visible across all users in Clue and should not contain any personal/sensitive data or instruction. They are Clue's internal notification system and can be used to notify a colleague or a group of colleagues known as a 'Team' to a linked record. Tasks are a record in their own right and can be created from within an Incident with a recorded link to help direct the assignee to the correct place for the task at hand. Tasks can also be created as a standalone record, allocated to yourself, as a reminder to carry out a certain action on a given date. The Triage and Case Management teams will also use Tasks to alert Cricket Organisation/County Safeguarding Officers that there is something to review or action - i.e. a LLC has been received from a Club and Triaged to be assigned to the correct Cricket Organisation.
Decision
All decisions can be recorded, along with rationale justifying them, to demonstrate that you are operating in accordance with terms of reference, broader governing legislation or rules. Like all records, decisions can be linked to supporting documentation and other records to support your reasoning. The Case Management team(s) use the Decision to log acceptance as Threshold Concerns and any decisions that are made on those Investigations. You may have view only access to view the Decision Register so you are able to see where concerns have been accepted.
Field/Register: Operational Function/Reporting
Dashboard
Multiple Views can be pinned to the Dashboard for ready access, and selected Views can be presented graphically. For example, Tasks outstanding for a team as a bar chart, making it easy to see workload distribution or Outcomes by type for the previous quarter presented as a pie chart to provide a quick summary. As a Cricket Organisation/County Safeguarding Officer you will need a View on your Dashboard showing Incidents assigned to you/ your Cricket Organisation , and a View on your Dashboard showing Tasks assigned to you/ your Cricket Organisation - so that you can immediately see when you log in- any Concerns you raised, or any raised by a Club in your Cricket Organisation, that have been triaged and assigned to you/ your Cricket Organisation.
Views
Views are the primary reporting tool in Clue. They provide different ways to look at data in a list of records by specifying filters, columns, and sort order. They are easy to create and modify and are dynamically updated as data changes. Views can be employed for operational reporting or for management reporting and can draw data from a single record type (e.g. new Incidents for a team) or Incidents by status.
Field/Register: Output
Outcome
An Outcome is a particular type of record that records the results of a given workflow. For example, as you manage a Low-Level Concern to resolution you will need to record what the Outcomes were - An incident can have one or multiple Outcomes. They are purposefully defined to allow for consistent tracking and reporting on trends.
Field/Register: Principle
Golden Nominal
The Golden Nominal Rule is the principle that there be a single, unified, and accurate record for every Entity, achieved through master data management to resolve duplicate and inconsistent data held across different databases/ records - this means in Clue that a Person or Organisation or Address should exist only once and be linked to other Records
Field/Register: Record Permissions
Owner Team
The Owner Team within Clue controls what you have permission to see. Defining the Owner Team within the Clue Record Permissions dictates which Cricket Organisation / Team can see the Incident. A Cricket Organisation/County Safeguarding Officer you will not be able to change this Owner Team and can only see Low-Level Concern Incidents within their Cricket Organisation, unless there is a specific and intentional decision, from The Cricket Regulator, to share additional Incidents during the investigation process.
Field/Register: Register/Workspace
Incident
The Safeguarding Concerns Reporting Form is received into the Incident register. The Incident register is used for logging, progressing and managing a Low-Level Concern and the initial referral of a Threshold concern. The Incident Register allows users to develop incidents and referrals by recording additional information in a structured, linked, reportable and audited manner, thereby building a more comprehensive picture.
Field/Register: System Functions
Access Control
Clue enables the management of sensitive data by controlling what users can do and what they can see. Permissions Groups determine what users can do by and Teams are used to limit what records a user can see. If a user is not in a particular team, they will not see the records for that team. As a Cricket Organisation / County Safeguarding Officer you have permission to see Incidents within your Cricket Organisation/County only - but you will be able to see Persons,
Addresses
Organisations across the ECB
Edit
Opens up the record in Edit mode
Save
Will save what you have edited and take you out of Edit mode
Save and Continue
Will save what you have edited but keep you in Edit mode
Delete
Would delete the record however whilst you see the Delete button if you do not have permission to delete you will not be able to and you will be prompted by an alert
Cancel
Allows you to exit Edit mode without saving your edits