← Back

The gap between a record request and an exposure map

From Anières

Pulling files is procurement. Mapping exposure is analysis. Most of what gets sold is the first dressed up as the second.

A record request answers what is on file. An exposure map answers what someone with a reason could put together. The two get sold under the same word, priced the same way, and delivered in binders that look almost identical from the outside, and that is most of why the market for this kind of work is confused.

An exposure map is something else; it is a structured view of where a person is reachable, by whom, through which channel, with what cost. Reachable by a counterparty running a standard check. Reachable by a writer with the usual tools. Reachable by someone with stronger tools and a reason. Reachable by a state-level inquiry; these are four different surfaces, and a person can be invisible on one and over-exposed on another.

The two reports are not the same category. The record request answers what is on file. The exposure map answers what someone with intent could put together. The first is a snapshot; the second is a small model of the person who might come looking.

Most of what gets sold as enhanced research is the first thing in a longer document. Pages of returned rows, a summary at the front, a risk score generated by a tool nobody on either side has read. The work the client actually needs; what is reachable, by whom. Is not in the record.

We treat the two as different products with different inputs. Record pulls run as a procurement pipeline with quality checks and provenance. Exposure maps run as analysis with a defined adversary in mind. The first feeds the second; a record dump is not an exposure map. Telling clients which one they actually need is half of the first call.

Written alongside work at Anières: exposure mapping, cross-reference, and standing-report systems for private clients.