Complaints as product evidence

Figure 01 / 12

The population that monitoring actually sees

4,464 of 6,200 source items enter this monitoring calculation. The missing 1,736 items are a coverage gap, not evidence of low risk. Reconcile stable identifiers and amounts where appropriate before interpreting the alert rate.

Figure data and text version

Population state	Items
Included in monitoring	4,464
Absent from this run	1,736

Repeated complaints can reveal confusing labels, failed handoffs, or systematic defects. The count needs context about exposure, channel access, and classification quality.

A lower complaint count is credited to a fix that made reporting harder.

All amounts, rates, capacity limits, and outcomes in this case are synthetic. The three conditions are separate assumptions for comparison. A better result in the response condition is not measured proof that the proposed control causes that improvement. The figures expose the calculation and its limits; a real deployment needs its own evidence.

Read the result

The daily source population is 6,200 items, but 1,736 are outside the completed monitoring run. The included population creates 466 hits and 280 unique cases. With 52 cases already open and capacity for 232, the queue closes at 100. Coverage, duplicate work, and staffing are separate causes; reducing one number does not prove that the overall control improved.

Figure 02 / 12

From scenario hits to unique cases

466 raw hits become 280 cases after removing 186 repeated references to the same case under the stated merge rule. Deduplication should reduce duplicate work while retaining the underlying events and reasons. It must not merge unrelated activity merely because values look similar.

Figure data and text version

Stage	Count
Raw scenario hits	466
Duplicate references	186
Unique cases	280

Figure 03 / 12

The queue balance is an accounting identity

Opening backlog 52 + arrivals 280 − completed cases 232 = closing backlog 100. Completion is capped by both available work and the stated capacity. This identity is useful even when average handling times are uncertain.

Figure data and text version

Movement	Cases	Definition
Opening backlog	52	Unresolved at window start
New cases	280	Unique arrivals in this window
Completed	232	Reached a defined completion state
Closing backlog	100	Unresolved at window end

Figure 04 / 12

Backlog accumulates across uneven days

This deterministic six-day example applies a stated daily arrival multiplier and a constant completion capacity. Unused capacity does not carry forward as completed work. The series is a workload illustration; it omits variable case durations and specialist routing. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version

Day	Closing backlog
D1	100
D2	106
D3	210
D4	398
D5	474
D6	438

Figure 05 / 12

Arrivals and completions need separate plots

The service line cannot exceed the work available that day. A team can complete more cases than arrive while clearing an opening backlog. Conversely, stable staffing can coexist with a growing queue when arrivals remain higher than capacity. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version

Day	Arrivals	Completions
D1	280	232
D2	238	232
D3	336	232
D4	420	232
D5	308	232
D6	196	232

Figure 06 / 12

An illustrative age profile of open work

The closing backlog is 100 cases. The 50/30/remainder split is an explicit illustrative age allocation, not a distribution inferred from the arrival model. Production age buckets must come from each case’s actual receipt and status history.

Figure data and text version

Age bucket	Open cases
Under one day	50
One to three days	30
Over three days	20

Figure 07 / 12

Completion outcomes are not criminal labels

Of 232 completed review tasks, 39 are referred for further assessment, 28 need another evidence action, and 165 close under the stated procedure. These are operational outcomes. None is a probability of money laundering or a substitute for a reporting decision.

Figure data and text version

Review disposition	Tasks
Referred for assessment	39
Further evidence action	28
Closed under procedure	165

Figure 08 / 12

Known-event tests assess specific coverage

The injected test set contains 100 known test events designed to exercise use complaints as product evidence. The system surfaces 63. That 63% detection result measures this constructed test set only; it does not establish population-wide detection of illicit activity.

Figure data and text version

Measure	Count	Interpretation
Injected known events	100	Defined test population
Detected by the scenario	63	Expected evidence reached the control
Not detected	37	Investigate data, logic, and delivery
Real-world illicit prevalence	Unknown	Not inferred from this test

Figure 09 / 12

Data quality has several independent dimensions

Each row is a different field requirement over the same source population. Completeness alone does not establish that values are accurate or current. The case uses explicit illustrative missing counts to show how data quality can affect scenario coverage.

Figure data and text version

Field requirement	Present	Absent
Party reference	5,890	310
Event time	5,332	868
Counterparty context	4,340	1,860

Figure 10 / 12

Type the relationship before drawing an inference

This evidence map distinguishes a customer relationship, a transfer, and a case reference. The links support use complaints as product evidence; they do not imply common ownership or intent. A shared data point is a lead whose meaning depends on source, time, and context.

Figure data and text version

From	To	Relationship
Complaints as product evidence	Counterparty A	Observed transfer
Complaints as product evidence	Profile record	Declared business
Counterparty A	Case record	Evidence reference
Profile record	Case record	Context for review

Figure 11 / 12

Case clocks start from defined events

A legal deadline, an internal response target, and an evidence-expiry date can start from different events. The hours here are internal teaching targets only. They are not BSA, sanctions, consumer-protection, or other statutory deadlines.

Figure data and text version

Event	Relative time	Operational meaning
Source event	T0	Activity occurred
Data arrival	T0 + 2 hours	The monitoring system learned it
Case created	T0 + 3 hours	Work entered an owned queue
Internal review target	T0 + 27 hours	Illustrative 24-hour target from case creation
Disposition	Recorded separately	Use actual decision and reporting records

Figure 12 / 12

The end-to-end delivery contract

The scenario is incomplete until the intended evidence reaches an owned case. For use complaints as product evidence, verify source coverage, hit creation, queue acceptance, reviewer access, and final disposition separately. A green job status proves only that a job reported completion.

Figure data and text version

Boundary	Acceptance evidence
Source to scenario	4464 included source items; 1736 missing
Scenario to case	466 hits linked to 280 unique cases
Case to reviewer	Required evidence visible under the reviewer role
Reviewer to outcome	Disposition, rationale, and any separate reporting decision retained

Connect the result to the system

Compare customer access, issue rates, case findings, and the affected product population.

Check the population, evidence, permitted action, and actual effect together. A balanced calculation can still use the wrong population; a successful response can still leave an unknown financial outcome. The case’s numerical result applies only to its stated assumptions.