How EPRScope turns public records into reviewable work.

The three questions the product answers

1. What company names appear in the available state EPR records?
2. What changed in an approved official source since the previous successful check?
3. What does the customer’s team need to review, document or assign?

Customer-supplied entity scope

The customer supplies the entities that belong in its account. EPRScope does not silently invent a corporate family or decide that a similarly named company belongs to the customer.

The monitored name set may include:

• Exact legal entity names
• DBAs and operating names
• Known abbreviations and legacy names
• Brands and licensed names
• Parent and subsidiary relationships
• Customer-provided registration or account identifiers

Coverage is labeled by capability

State programs do not publish equivalent data. A regulator page, a PRO registration page and a downloadable producer list are not interchangeable. EPRScope uses separate coverage labels so a research page is never presented as a company-level registry search.

Current state capability

How name matching works

EPRScope compares the customer-supplied legal name and aliases with the published record text. The matching process can account for capitalization, punctuation, spacing and common corporate-suffix differences. A result is stored with the published text, source, retrieval date, match type and reason.

Result categories

• Match found: the published name and monitored name align under the validated matching rules.
• Possible match: the names are similar enough to require confirmation, but the system does not treat them as the same legal entity automatically.
• No obvious match: no qualifying name was found in the currently searchable record.
• Name search unavailable: the state source does not provide a validated company-level record for automated searching.

A no-obvious-match result is never converted into “unregistered,” “exempt,” “not obligated” or “noncompliant.”

Immediate rechecking

Adding or editing a legal entity must trigger a check against the latest retained searchable records. The customer should not have to wait for an official webpage to change before a newly added entity is evaluated.

Official-source monitoring

For each approved source, EPRScope records the check time, HTTP result, retained content version and content hash. When the normalized content changes, EPRScope stores the prior and current versions and creates a review item.

Automated classifications—such as deadline, fee, exemption, producer definition, enforcement or rulemaking—are triage aids. They are not legal conclusions.

Human review

Possible matches and source changes remain review items until a permitted user records a decision. The expected match decisions are:

• Confirm same entity
• Not the same entity
• Need more information

The reviewer, decision, time and supporting evidence remain in the history. Technical source differences remain available, but the main interface leads with what happened, why it was flagged and what the team should do.

Evidence and closure

Tasks can be linked to evidence URLs, notes or securely stored documents when that capability is enabled. Closing a task without evidence requires an authorized user to record a reason. The evidence gap is not silently deleted.

Customer deliverables

• Initial entity baseline: monitored names, enabled states, available public-record results, source coverage and open review items.
• Event alert: a new match, changed name, source update, source failure or overdue review that requires attention.
• Monthly monitoring summary: current entity results, source changes, tasks, evidence, decisions and monitoring health across the states enabled for the account.

Quality controls

• Approved source inventory with explicit jurisdiction and capability
• Immutable retained source snapshots
• Explainable match reasons instead of unexplained confidence scores
• False-positive and generic-name suppression
• Customer review before a possible match becomes confirmed
• Organization and role scoping on customer data
• Audit history for material changes and decisions
• Coverage labels that prevent research content from inflating product claims

Expansion rule

A state does not become “live entity monitoring” because a law exists or because EPRScope has written a state guide. The capability is promoted only after an authoritative record is identified, structured ingestion is repeatable, match behavior is tested, limitations are documented and the customer workflow works end to end.