Reading the Fine Print

A contract that grants access is not the same as a contract that requires contribution. Almost every misunderstanding about this system starts by collapsing those two ideas. An agency can read the national pool without feeding it, feed it on narrow terms, or feed it in full. The documents decide which.

For a city, the practical question reduces to three outcomes. This guide shows where each one is written down.

There is rarely one document. A full agreement is a stack, and the layer that controls data sharing is usually the one most often missing from a public records return.

Three doors lead to the same room. Each can be reader-only or contributor, and each leaves a different paper trail.

A consortium adds a layer between the agency and the vendor: a lead agency, a fiscal agent, and usually a named data warehouse described as a private container. That structure can keep data regional, or it can route it straight to the national pool. The deciding factor is a single clause.

One agency's records response described its feed in unusual detail. It is a useful baseline for what a standard contribution contains.

Contribution is configured, not just signed. The data leaves the agency's records or dispatch system, passes through an integration, and lands in the national pool. The on-ramp varies by vendor.

Ask a city for the technical record of what it shares, and you may learn that it does not have one. In one records response, a city explained that it holds no interface specifications, field mapping, or data translation records, because those are created and kept by LexisNexis or the software vendor, not the city.

That gap is structural, not accidental. The data a city cares about lives in its records management system (RMS), its computer-aided dispatch system (CAD), or its jail management system (JMS), and each of those is run by a private company, not the city: LETG, Motorola, Tyler Technologies, CentralSquare, Spillman, and the like. The LexisNexis feed is then built between two of those private vendors. The city is effectively asking one third party to integrate with another, so the technical side of the arrangement (what fields map where, how the translation works, what actually goes out the door) is something Motorola is working out with LexisNexis, or CentralSquare with LexisNexis, and so on. The detail never sits inside city hall, because no part of it was ever built there.

The gap compounds the renewal problem. The contract renews itself, so there is no recurring vote, and the configuration lives with the vendor, so there is no local file. Meanwhile, at least one agency asserted in a records response that AVCC contributions could not be restricted at all.¹ Another agency, Oklahoma City, had already negotiated exactly that restriction. The claim and the counterexample sit in the public record at the same time.

The contribution model runs across an industry. The local records this page has tracked are a target for several vendors at once, and the database itself is operated by more than one of them. In at least one agreement, Motorola Solutions runs the LexisNexis pool and carries the same give-to-get clause under its own logo. SoundThinking, a competitor, sells the identical consolidation. Every vendor in the middle is one more layer between a city and a clear view of what leaves its systems.

Six agreements, side by side. Each row is a different answer to the same question: how far does this agency's data travel?