Statement Matrix

Use the statement matrix to quickly change the relationships between YES/NO assessment statements and event types.

Accessing the Statement Matrix

  1. Click on the 'Admin Tools' button (this is only visible to users with admin privileges enabled).
  2. Select the ‘Framework’ tab, then the ‘Statement Matrix’ sub-tab.

Changing Statement Relationships

The statement matrix gives you a visual representation of how each YES/NO statement is related to each event type. The relationships are displayed as follows:

Matrix Key

  • Green square containing a 'A' (ALWAYS) - The statement is considered to be always applicable to the Event Type and will be automatically recorded in the database as 'YES'. The user will not be asked to review the statement when recording this event type.
  • Green square (YES) - The statement is always presented to the user for review and the answer will be set as 'YES' by default.
  • Grey square (ASK) - The statement is always presented to the user but no default answer will be selected, requiring manual input from the user to answer the statement and be able to move on.
  • Red square (NO) - The statement is always presented to the user for review and the answer will be set as 'NO' by default.
  • Red square containing an 'N' (NEVER) - The statement is considered to be never applicable to the Event Type and will be automatically recorded in the database as 'NO'. The user will not be asked to review the statement when recording this event type.

Tips

You can use the statement matrix to streamline the 'Add an Activity' process for users by changing how statements are presented to them.

Before altering these relationships, you should consider the balance you want to strike between not presenting statements to users (which streamlines the process of adding an activity but reduces the flexibility of capturing potentially relevant data), through to presenting users with every statement for each event type (which is more time consuming for users to complete, but reduces the chances of data not being captured).

Statements which are set to 'ALWAYS' or 'NEVER' will never be displayed to the user when they add an activity with that event type, yet the corresponding value will still be recorded in the database.

Statements set to 'YES' or 'NO' will still be displayed to the user, but the highlighted answer will default to the corresponding value, making this option useful for statements which virtually always or virtually never apply to the event type, but still preserves the freedom for users to provide an alternative answer to the statement regardless.