Your Processes home: coverage headline and KPI tiles

What Processes is for

Processes is where Verinode keeps everything that describes how your business actually operates: the standard operating procedures (SOPs) you have written down, the patterns Verinode has noticed in how your team works but that nobody has written down yet, and the outside reference standards (IICRC, LEAN, OSHA, EPA, and your state's own rules) that your SOPs get measured against. It is not a document library and it is not a task list. It is the coverage picture: which parts of your service mix have a written, repeatable process behind them, and which parts are running on tribal knowledge.

Open it from the sidebar under Processes, at /processes. The rest of this article covers the first thing you see: the hero panel at the top of the page, and the row of four tiles labeled Explore directly under it.

Where the numbers come from

Every number on this page is read from your own operator profile and your own records, nothing else:

• SOPs written counts every row in your SOP library, regardless of status.
• Service line coverage compares the service lines in your operator profile (the work types you told Verinode you perform) against which of those service lines have at least one active SOP attached. "Active" means not archived; an archived SOP does not count toward coverage.
• To Confirm counts the patterns Verinode's agents have observed in your team's work, still sitting in pending status, waiting for you to confirm or dismiss them.
• Standards in scope reads from a shared, global library of process research benchmarks (IICRC, LEAN, OSHA, EPA, and state-specific rules), filtered to your state plus every framework that applies everywhere.

There is no peer or benchmark data behind any of these numbers. Everything on this page is you versus your own service mix, not you versus other operators.

The hero panel

At the top of the page, one large number anchors everything else.

SOPs written, in large type, is the total count of SOPs in your library. Beside it, a pill reads your service-line coverage as a percentage, for example "67% Service Lines Documented." The pill's color tracks how complete that coverage is: green once most of your service mix is documented, amber in the middle band, and red (Analyse tone) when coverage is still low.

Underneath the headline, a line of supporting text adapts to your situation:

• If you have not written any SOPs yet, it reads "Upload your SOPs to get started."
• If you have SOPs but some service lines still lack one, it reads "N of your service lines have no SOP yet" (singular phrasing, "1 of your service lines has no SOP yet," when the gap is exactly one).
• Once every service line has an SOP, it reads "Every service line has an SOP."

To the right, two smaller numbers sit beside the headline:

• To Confirm, the count of pending observed patterns. When there are none, the line under it reads "Nothing Waiting"; when there are, it reads "Patterns Waiting On You."
• Lines Without An SOP, the same coverage-gap count as the subtext above. When the gap is zero, the line under it reads "All Covered"; otherwise it reads "Write One To Close It."

The hero panel is read-only: it summarizes state, it doesn't take clicks. To act, drop down into the Explore row.

The Explore row

Four tiles sit in the Explore row, directly under the hero (and under a Take Action row of decisions and quick launches, covered in acting on decisions). Each one restates a hero number as its own tile, with its own preview visual, and each one is a doorway into a filtered view of your process records.

My SOPs

Shows the same count as the hero's headline: how many SOPs you have written. The line under it reads "Written By You" once you have at least one, or "Upload One To Start" when the library is empty.

Under the number, when you have at least one service line configured, a dot grid shows one dot per active service line, with the documented ones lit. It is the same coverage ratio as the hero pill, just drawn as a grid instead of a percentage.

Tap the tile and it opens the All Processes tab of the process card slider, pre-filtered to your SOPs (labeled My SOPs inside that tab). That is the full list, one card per SOP, each opening into its own detail view with its steps, its LEAN score if one has been computed, and its work type.

To Confirm

Shows the count of pending observed patterns, the same number as the hero's "To Confirm" secondary metric. The line under it reads "Tap To Confirm" when there is a backlog, or "Nothing Waiting" when it's clear. A dot grid below the number fills every dot in amber/watch tone, one per pending pattern, so the size of the backlog reads at a glance without opening anything.

An observed pattern is something Verinode's specialists noticed you or your team doing repeatedly, inferred from conversations and documents, that has not yet been turned into a written step. It is not an SOP until you say so.

Tap the tile and it opens the All Processes tab filtered to Pending Confirmations, the label this record kind uses inside that tab. From there you review each captured pattern and confirm, edit, or dismiss it.

Standards (labeled with your state)

If Verinode knows your state, this tile's label swaps to <Your State> + Federal; otherwise it reads plainly "Standards." The number is a count of reference standards in the shared research library that are tagged specifically to your state, drawn from IICRC, LEAN, OSHA, EPA, and state-level sources. The line underneath, "IICRC · LEAN · OSHA · EPA · State," names the frameworks the library spans, not just the state-specific slice this tile counts.

This number is narrower than the full standards library available to you: it counts only the state-tagged rows, not the global (IICRC/LEAN) or federal (OSHA/EPA) standards that apply everywhere and sit alongside your state's in the underlying catalog. If Verinode doesn't have your state on file yet, this tile reads zero and the label stays generic until your profile fills in.

Tap the tile and it opens the By Standard tab of the process card slider, where you can browse and filter the complete catalog: All, IICRC, LEAN, OSHA, EPA, and State groupings, with a count next to each. That full catalog includes the global and federal frameworks this tile's own number doesn't count, so don't be surprised if the list you land on is longer than the tile you tapped.

Lines Without An SOP

The coverage-gap count again, this time as its own tile. Its accent color flips with the state of the gap: red (ember) while lines are missing an SOP, green once none are. The line underneath reads "Write One To Close It" while the gap is open, or "All Covered" once it's closed.

Below the number, a gauge shows your documented-coverage percentage as a filled arc against two zones: red below 60%, amber from 60% up to 90%, green at 90% and above. It's the same percentage as the hero pill, drawn as a gauge instead of a badge.

Tap the tile and it opens the Coverage tab of the process card slider: the full coverage matrix, service line by service line, showing which ones have an SOP, which have relevant certifications or program memberships on file, and which have neither.

Empty states

Every part of this page degrades honestly rather than showing a fake zero:

• With no SOPs at all, the hero reads "Upload your SOPs to get started," and the My SOPs tile reads "Upload One To Start."
• With no pending patterns, "To Confirm" reads "Nothing Waiting" in both the hero and the Explore tile, and no pattern-to-confirm cards appear in the row.
• With every service line documented, the coverage gap is 0, the hero reads "Every service line has an SOP," and the Lines Without An SOP tile reads "All Covered" with a green accent.
• If your operator profile has no service lines configured at all, the coverage percentage has nothing to divide by, so the pill and gauge simply don't render rather than showing a misleading 0% or 100%.

None of these states are broken screens. They mean the underlying data, your service mix, your SOPs, your team's captured patterns, hasn't caught up yet, and the page tells you exactly what's missing.

What this page is not

Processes home does not show peer or benchmark comparisons of your process coverage against other operators. The rows further down this same page, "How your work flows" and the Business Analyst runs, do bring in cycle-time mining and, where you've opted in, peer stage durations, but the hero and Explore tiles covered here are entirely about your own coverage against your own service mix. See how benchmarks work for how peer comparisons are built and gated elsewhere on the platform, and the decision workspace for how the adoption-gap and other process decisions in the Take Action row turn into something you can act on.