Launchpad

Overview

The Launchpad serves as timveroOS's centralized operations interface for managing manual decision workflows. It provides department-based work queues, assignment management, and structured review processes for applications requiring human intervention during the underwriting process.

Business Purpose

During automated underwriting, certain conditions require expert review that cannot be fully automated. These include edge cases outside standard parameters, regulatory compliance requirements, and data quality issues requiring verification. The Launchpad transforms these manual touchpoints into structured, auditable workflows.

Configuration Components

Department Configuration

Departments must be configured to match your organizational structure and review responsibilities.

Configuration Location: Settings → Catalogs → Decision Departments

Required Fields:

• Department Code: System identifier

• Description: Department purpose

• Activity Status: Active/Inactive flag

Example Department Types, for example:

• Underwriting Department: Reviews debt obligations and credit history anomalies

• KYC Department: Handles identity verification and address confirmation issues

• AML Department: Investigates transaction patterns and money laundering concerns

• Financial Department: Analyzes complex financial metrics and accounting irregularities

User Assignment

Link users to departments to control access to specific warning types:

Available Permission Levels:

• Worker permissions: Basic operational access

• Supervisor permissions: Extended operational access with assignment capabilities

Interface Configuration

The Launchpad interface provides three primary views:

1. All Items View

Complete visibility of all subjects with unresolved warnings relevant to your department:

2. To Be Assigned View

Unassigned items requiring immediate attention from your department:

Unassigned warnings filtered by department

3. Assigned to Me View

Personal work queue of assigned reviews:

Warning Configuration

Linking Warnings to Departments

Configure warning routing in the workflow designer:

Warning fact configuration with department assignment

Form Scheme Integration

Link data collection forms to warnings requiring additional information:

Form scheme selection for structured data collection

Review Process Configuration

Assignment Workflow

Assignment Options (per documentation):

• Self-assign: Items from the unassigned queue

• Assign to colleagues: Within their department (with appropriate permissions)

• Reassign: Items as workload requires

• Unassign: Items to return them to the departmental queue

Resolution Actions

Approval Process

Approval Characteristics:

• Allow the subject to proceed despite the warning

• Can be reverted while other warnings remain unresolved

• Updates participant profile when forms are completed

Decline Process

Decline Characteristics:

• Uses predefined catalog of reasons for analytics

• Affects all warnings across all departments

• Declines the entire application (if participant role is borrower)

• Cannot be reverted

Status Management

Track warning resolution status:

Multi-Department Coordination

Multiple departments can process warnings simultaneously:

Coordination Logic (from documentation):

• If any department declines, the participant's application is immediately declined

• Full approval requires all assigned departments to approve all relevant warnings

• Users from different departments can work in parallel

Work Reassignment

According to the documentation:

• Users can relinquish assigned warnings using "Drop Assignment" action

• Another user can then self-assign the warnings

• Supervisors can reassign the warnings

• New assignees can view prior resolution decisions

• Approval decisions can be reverted if the new assignee disagrees

• Decline decisions remain permanent

Integration Points

Workflow Integration

When the automated decision engine encounters a condition requiring manual review:

• The system creates a warning fact linked to the appropriate department

• The warning appears in the Launchpad for authorized department members

• Form schemes determine what information reviewers need to collect

Document Management

• Access relevant files for review

• Supporting documents necessary for informed decision-making

Audit System

• Records all actions for compliance

• Maintains complete audit trail of decisions

Reporting Module

• Provides operational metrics and analytics

Configuration Best Practices

Based on the documented system capabilities:

Department Setup

• Assign warnings to the department with the most relevant expertise

• Avoid creating bottlenecks by over-concentrating warnings

• Regularly review assignment patterns for optimization opportunities

Queue Management

• Encourage prompt assignment of new items

• Monitor aging of unresolved warnings

• Implement escalation procedures for stalled items

Form Design

• Design forms that capture decision rationale

• Include fields for risk mitigation measures

• Ensure consistency in data collection across reviewers

Additional Resources

For detailed implementation guidance and technical support, consult your system administrator or implementation team.

Next Steps

With Launchpad configured, proceed to:

• Form Builder - Create custom data collection forms

• Catalogs - Set up reference data and departments

• Notification Configuration - Configure alerts and communications