Regulations and the Regulatory Autofeed

What this covers

Restoration operators sit under a moving stack of rules: state licensing, EPA and OSHA requirements, carrier-program conditions, and local ordinances, and the stack changes throughout the year without anyone emailing you a summary. The Regulations tile and Regulatory Autofeed tile on the Compliance page are how Verinode keeps that stack visible: which rules actually apply to your business, where you stand on each one, and which ones just changed. Verinode reads your state, your service mix, and your recorded status on each rule, and lays out what's live and what's coming. It never files anything on your behalf and it never decides your status for you: you record where you stand, Verinode tracks it against the calendar.

Where to find it

Open Compliance from the sidebar (/compliance). The page is built from three rows: a hero panel at the top, a Take Action row, and an Explore row of tiles. Regulations and Regulatory Autofeed are two of the seven tiles in the Explore row, sitting alongside Shield Score, Cross-Domain Stacks, Open Exposures, and Next Audit. Clicking either tile opens the Regulations tab of the Compliance card slider, which lists every applicable regulation. A Frameworks row (HazCom, OSHA recordkeeping, EPA RRP) and a Most recent row of the newest compliance records sit further down the page.

The Regulations tile

What it shows. The tile's headline number is a fraction: compliant regulations / total applicable regulations, for example "3/5". If nothing applies yet, it reads a plain dash (", ") instead of "0/0".

Underneath the fraction, the subtext tells you what's driving the number:

• If any regulations were added by the autofeed in the last 30 days, it reads "N new via autofeed · N exposed."
• Otherwise, if any applicable regulations are unresolved, it reads "N exposed."
• If everything applicable is either compliant or exempt, it reads "compliant / applicable."

Below that, a segmented bar breaks the applicable set into three bands: compliant (green), exposed (red), and everything else, meaning regulations that are upcoming or in progress (neutral). Segments with zero count are simply omitted from the bar.

The tile's accent color tracks the worst state present: copper (an accent tied to attention-needed states) when anything is exposed, teal when the count is healthy, amber when nothing applies yet. Clicking the tile opens the Regulations tab.

The Regulatory Autofeed tile

What it is. A weekly automated scan (a cron job internally called the regulatory-scan) watches for new state, federal, and local regulatory changes and writes them into Verinode's regulation catalog on your behalf. You don't request these, they arrive on their own schedule, tagged by source so you can tell an autofeed-sourced regulation apart from ones Verinode's research team curated directly.

What the tile shows. The headline number is the count of regulations the autofeed has added in the last 30 days, counted from the point they were ingested (not their effective date). If that count is zero, the value reads "0" and the subtext reads "system is watching, none new this month", which is a genuine empty state, not a sign anything is broken: it means no relevant changes have been detected in your applicability window this month. When the count is above zero, the subtext reads "new regulations in last 30d." A small sparkline below the number gives a quick visual sense of the pace of change (one mark per new regulation, up to eight).

The tile's accent is teal when there's been recent autofeed activity and violet when the feed is quiet. Clicking the tile opens the same Regulations tab as the Regulations tile above.

Applicability filtering: why you don't see every regulation in the country

Verinode's regulation catalog spans every state and covers a wide range of restoration-adjacent rule categories. You never see the whole catalog. Every regulation record is filtered down to what actually applies to your business, using two signals from your operator profile:

1. Your state. A regulation tagged as state-level jurisdiction only appears if it's tagged for your operator's recorded state. Federal and local-jurisdiction regulations aren't filtered by state in the same way, they pass through this check by definition.
2. Your service mix. If a regulation is tagged with one or more applicable service lines (for example, mold remediation, water mitigation, fire and smoke), it only surfaces if at least one of those service lines overlaps with your recorded service mix. A regulation with no service-mix tags attached applies broadly and isn't filtered on this axis.

Both checks have to pass for a regulation to reach your Regulations tab. This is why two operators in the same state can see a different Regulations count: the filter is reading each operator's actual footprint, not showing a single generic state list.

Regulations tab: reading the list

Open the Regulations tab (via either tile, or directly from the card slider). Each row shows:

• Title of the regulation.
• A subtitle combining the source, the jurisdiction (federal, state, or local), and, for state-level rules, the state abbreviation, for example "State Licensing Board · state TX."
• A status label on the right, one of: Compliant, Exempt, In progress, Effective, adopt, or a countdown like "14d to effective" for regulations that haven't taken effect yet.
• A colored badge for autofeed-sourced rows: a copper "NEW · Autofeed" pill when the regulation was ingested by the autofeed within the last 14 days, or a plain "Autofeed" pill (no "NEW") once that window has passed. Regulations added by Verinode's research team directly, rather than the autofeed, carry no badge at all.

Clicking any row opens its detail card.

Regulation status vocabulary

Every applicable regulation carries one of five statuses, entered or updated by you as you work through it:

• Pending, recorded but not yet acted on.
• Acknowledged, you've reviewed it.
• In progress, you're actively working toward compliance.
• Compliant, you've met the requirement.
• Exempt, this rule has been determined not to apply to your operation, despite matching the filter.

Regulations also carry a computed posture based on status plus timing relative to the effective date. Verinode uses a five-state posture vocabulary across the whole Compliance page (hedged, drift, exposed, breaching, watching); for regulations specifically:

• Compliant or Exempt and past its effective date reads as fully resolved (hedged), no action needed.
• Within 30 days of the effective date and not yet resolved reads as drift, the "adopt now, before it's mandatory" window.
• Past its effective date with adoption in progress reads as exposed, meaning partial adoption is treated the same as non-compliance on most audits, so finish the remaining steps.
• Past its effective date with no adoption started reads as breaching, the highest-urgency state: citation risk is live.
• More than 30 days out and untouched reads as watching, nothing to do yet, revisit closer to the date.

Regulation detail card

Opening a regulation shows its full record: Source, Jurisdiction (with state if applicable), Category, Effective date, a full Summary of the change, the Action required to come into compliance, your current Operator status, and, when the regulation catalog links one, a Source URL you can open directly to the original text.

The hero stats at the top of the card repeat the essentials at a glance: Status, Effective (with a delta reading either "Nd out" for a future date or "Nd in effect" for a past one), Jurisdiction, and Source.

Empty states

• No applicable regulations. If your state and service mix don't overlap with anything in the catalog yet, the Regulations tab reads: "No applicable regulations in the catalog for your state + service mix."
• No compliance data at all. If you haven't surfaced any compliance records yet (no exposures, audits, or regulations acknowledged), the Take Action row above the tiles reads: "Get your compliance posture on the radar," with three prompts: upload a recent certificate of insurance or carrier-program audit, forward an audit-notice or regulator email so future notices land automatically, or paste a regulation update or compliance memo (state licensing, EPA, OSHA, anything that changes how you operate). Further down, the Most recent row reads: "Compliance records will appear as you forward audit notices, drop COIs, or acknowledge regulations."
• Everything resolved. Once you've worked through every open compliance signal and nothing new has surfaced, the Take Action row instead reads "All clear on your compliance posture," noting how many signals you've worked through, with new items to appear as audits, exposures, or regulation changes come up.

How Regulations relates to Shield Score and the rest of Compliance

Regulations is one input among five into the Shield Score, the headline number in the hero panel at the top of the Compliance page. Shield Score blends training, insurance, carrier-program, regulatory, and safety posture into a single 0–100 read on overall compliance health. A thin or exposed Regulations set pulls that composite score down; a fully compliant one is one of five things it takes to sit at the top of the range. The Regulations tile and the Shield Score are two different lenses on the same underlying gaps: Regulations is the itemized list, Shield Score is the rollup.

Regulations also feeds the Benchmarks tab of the Compliance slider, where your framework completeness and audit pass rate are read against a peer cohort where the cohort is large enough to protect anonymity, and against industry research otherwise. Regulations compliance is one of the inputs to that peer comparison.

Best-practice example

Your operator profile lists Texas as your state and water mitigation plus mold remediation as your service mix. The autofeed picks up a new Texas mold-remediation licensing requirement and ingests it. Because it's a state-level regulation tagged Texas, and mold remediation overlaps your service mix, it clears both applicability filters and lands in your Regulations tab, badged "NEW · Autofeed." It's 45 days out from its effective date, so its status reads "45d to effective" and its posture sits at watching, nothing urgent yet. You forward the notice to your ops manager, and 20 days later, as the effective date closes in, its posture shifts to drift and the countdown badge turns amber. You mark it In progress while your team completes the required training, then flip it to Compliant once it's done, which moves both the Regulations fraction and the Shield Score in the right direction.

Related reading

• How benchmarks work
• Reading a benchmark
• Benchmarks overview
• The decision workspace
• Forwarding documents
• Connecting your data

Data sources