What an observation
can tell you.
RMD Lens tracks changes in public FCC Robocall Mitigation Database records. It does not decide whether a provider is compliant.
1. One source snapshot per cycle
A configured operator job fetches the public source once per cycle. It checks the response, exact expected headers, record count, completeness and identifiers before using the snapshot. A blocked response, malformed file or suspicious drop in records fails the whole check.
2. Exact identifiers, always
Provider names help you label a watchlist. Matching uses the exact RMD ID, preserving leading zeroes. Duplicate IDs are marked ambiguous and do not generate automatic change alerts.
3. A baseline before an alert
Your first observation establishes a baseline. Later valid observations can reveal field changes, a record no longer observed, or a reappearance. Failed source checks do not replace the last valid baseline.
4. Absence is an observation
“Not observed” means an exact ID was absent from a validated snapshot. It does not prove enforcement removal. A database listing does not itself demonstrate compliance. Missing dates do not establish an overdue filing.
5. Two different clocks
Observation time is when RMD Lens checked a snapshot. A filing or update date comes from the source, where present. We retain these separately and do not substitute one for the other.
Preview status
The public demo contains synthetic sample data only. Live source integration, delivery, and account setup require operator verification before launch. The application does not imply a regulatory requirement to check the database daily.