Matter Management Data Entry Enforcement via Dynamic Field Requirements

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Matter management systems face inaccuracies due to incomplete data entry, particularly in fields like potential liability estimates, leading to unreliable reports and non-compliance with regulatory requirements, as users often must choose between entering inaccurate information or omitting critical details.

Innovation Solution

A software facility that designates certain fields as 'required' at a future time, leveraging processes to ensure their completion, such as blocking data entry or document posting until necessary information is provided, and differentiating between 'hard-required' and 'soft-required' fields to allow flexibility while ensuring data accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If required fields are made mandatory for matter creation, then data completeness is improved, but ease of operation deteriorates because users cannot create matters when information is not yet available

Engineering Contradiction:
Improvedata completenessVSAvoidease of matter creation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies dynamics by making field requirements change over time. Fields that are optional at matter creation can become required later through scheduled reminders and automated communications, allowing the system to adapt requirements based on the matter lifecycle stage rather than enforcing static requirements

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by sending automated reminders and communications to users before deadlines to prompt them to complete required fields. This advance notification allows users to prepare and complete data entry before the fields become mandatory, maintaining ease of operation while ensuring eventual data completeness

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If required fields are made optional, then ease of operation is improved, but data completeness deteriorates because users may forget or be too busy to enter information

Engineering Contradiction:
Improveease of matter creationVSAvoiddata completeness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements feedback mechanisms through automated reminders, notifications, and communications that continuously prompt users to complete required fields. This feedback loop ensures users are aware of incomplete data and are motivated to provide it, maintaining high data completeness while keeping fields optional throughout the matter lifecycle

Inventive Principle:
Principle #23Feedback

3Measurement precision

If data entry is delayed until information is available, then data accuracy is improved, but productivity deteriorates because matters cannot be created immediately

Engineering Contradiction:
Improvedata accuracyVSAvoidspeed of matter creation
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent segments data entry into multiple phases: initial matter creation with available information, followed by subsequent data entry prompted by automated reminders. This segmentation allows matters to be created immediately with partial data while ensuring accurate information is entered later when available, resolving the conflict between immediate productivity and eventual accuracy

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9767435B1Ensuring the entry of certain data in a matter management system by leveraging another process
Publication Date: 2017.09.19 THOMSON REUTERS ENTERPRISE CENTRE GMBH
  • US9767435B1 patent drawing
  • US9767435B1 patent drawing
  • US9767435B1 patent drawing

AI summary

A facility for collecting distinguished information relating to an engagement of a first organization by a second organization is described. The facility provides an interface usable by at least one user affiliated with the second organization to provide the distinguished information. Only after the interface is used by a user affiliated with the second organization to provide the distinguished information, the facility permits at least one user affiliated with the second organization to perform a distinguished process.