We made a certain change in our underwriting application that should simplify the process of filling in and submitting the underwriting test results form by the ally. This simplification should result in a shortening of the time it takes from the moment an applicant completes the underwriting tests and until the ally submits the form reporting on the test results. This change was applied on March 15, 2259 and we would like to test whether the change has achieved its purpose.
The data you will be using to answer the questions in this exercise is attached to the email message you got:
-
Applicants table - personal details of the applicants that scheduled an underwriting sessions
-
Sessions table - administrative details about the session and its status
-
Events table - events related to the underwriting session
-
Data dictionary - list of fields in each table and their description
| Table | Field | Description |
|---|---|---|
| Applicant | applicant_id | Unique identifier of the applicant |
| session_id | Unique identifier of the session | |
| first_name | Applicant’s first name | |
| last_name | Applicant’s last name | |
| agent_name | Name of agent who referred the applicant | |
| ally_name | Name of ally who conducted the session | |
| birth_date | Applicant’s gender: F, M, Other | |
| gender | Applicant’s date of birth | |
| Session | session_id | Unique identifier of the session |
| applicant_id | Unique identifier of the applicant | |
| session_status | Status of the session | |
| risk_class_decision_datetime | Timestamp of when the notification about the applicant’s risk class was sent to the agent | |
| Events | session_id | Unique identifier of the session |
| applicant_id | Unique identifier of the applicant | |
| event_type | Type of event | |
| event_user | What side triggered the event | |
| event_datetime | Timestamp of the event |