Case 04 · Operations

Many records.
Decisions you can trust.

Problem
Missing, duplicate and outdated data weakened confidence in operational records.
Decision
Added execution locks, protected human entries and reconciled completed results.
Verified outcome
Recovered 23,590 missing operational records.
139,292Source rows reconciled · 136,852 creators1
My role
System design · AI-assisted development lead · direct operation
Evidence
Verified improvement and operational records

Trust in the records
comes before speed.

Collecting more data was different from making it useful. I reconciled records and distinguished corrected information from newly obtained information.

01

Use rules where they fit

Deduplication, reconciliation and preservation of human notes need reproducible rules. I kept these checks in code rather than generative AI.

02

Separate collection from completion

Collecting a list during sending left records missing. I added collection after completion and reconciled the results by invitation.

03

Make the result usable

Keep corrections, new contacts and recovered records distinct. Deliver the results in separate tabs for the people responsible.

Automation must preserve
the work of others.

Separate incidents—overlapping runs and mismatched delivery results—led to checks on both writes and completion.

01 / ISSUE

Two runs overlapped

Scheduled and manual runs wrote duplicate rows. Cleanup preserved rows containing human-entered information.

02 / DECISION

Control concurrent writes

Add an execution lock, protect review status and notes, and roll back if the before-and-after check of reviewed entries differs.

03 / VALIDATION

Check the actual outcome

A successful request did not always mean successful delivery. Re-query delivery counts before reporting completion and reconcile records again.

Recovered. Corrected.
Newly obtained.

These are separate improvement outcomes. They should not be summed or treated as a partition of the full dataset.

23,5902

Missing records recovered

Recovery result documented in the operational records.

4,5481

Existing email changes identified

Changes identified through the contact-data reconciliation.

8,0351

New email records obtained

Counted separately from changes to existing information.

Source rows and individual creators are different units.

Sources and scope

  1. Contact reconciliation and verification records. Source rows, unique creators, changes, and newly obtained records are counted separately.

  2. Verified recovery records. Missing-record recovery is a separate improvement from contact reconciliation.

  3. Operating and decision records describe concurrent-run duplicates, execution locking, preservation checks and delivery re-querying. These examples show operational safeguards; private selection rules and implementation details are omitted.