Process Maturity: SOP coverage across every member

What the Process Maturity row shows

A restoration business runs on repeatable process: written SOPs for mitigation, for documentation, for the handoff from estimate to production. A member with process on paper closes jobs more consistently than one running on tribal knowledge, and closes them faster when the crew changes. Process Maturity is where Verinode HQ reads that, one gauge per member, so leadership can see at a glance which memberships have real process discipline behind their numbers and which are still building it.

This is a network rollup, not a file review. Verinode does not read a member's actual SOP documents to build this row. Each member's own operator-side data already tells Verinode which of their jobs are tagged to a written, on-file SOP; that gets rolled into a coverage percentage on the member's own side of the privacy boundary, and only the resulting percentage, never the underlying jobs or documents, crosses into the aggregate HQ reads. HQ sees the score. Members own the process behind it.

Where to find it

Open Operations from the HQ sidebar, in the Operations group (it sits alongside Assets, Vendors, and Materials, mirroring IQ's own Operations band). The page lives at hq.verinode.ai/operations and its header reads OPERATIONS. The Process Maturity row is the second row of tiles on that page, directly under Capacity Pressure.

The hero band at the top of the page

Before the tile rows, a hero panel anchors the page on cycle time:

• Eyebrow: "Cycle time · Group median (days)."
• Headline: your network's median cycle time, in days, rounded to a whole number.
• Pill beside the headline: normally reads "P\<n\> (lower is better)", the percentile your network's median cycle time ranks at against the broader industry (lower cycle time is faster, so a lower percentile here is the good direction). When there isn't yet enough comparison data to place that percentile, the pill falls back to a sample-size marker instead, "n=\<members\>/\<industry\>", so you can see a comparison is building without a number being invented for it. The pill also tints: green when your network's median cycle time is at or faster than the industry median, red when it is slower.
• Subtext: names the industry median in days and repeats two network-wide figures, "Industry median \<n\>d · \<n\>% Process Maturity · \<n\>% Capacity." If your network has no cycle-time data on file yet, the whole hero instead reads "Cycle time appears as members share job data."

Below the headline, three secondary stats sit in a row:

• Process maturity: your network's overall percentage, labeled "Above SOP coverage threshold." This is the single network-wide figure the per-member row below breaks apart.
• Capacity utilization: your network's active jobs against capacity, labeled "Network active jobs vs cap." It tints when the network overall is running hot.
• Fleet items: total equipment registered across the network, a plain count.

These three are network averages. The tile rows below them are where you see which specific members are driving those averages up or down.

The Process Maturity row, tile by tile

Each tile in this row is one active membership. Up to twelve show directly on this home row, ordered the same way your member directory is ordered; the full list, uncapped, is one click away (see "Seeing every member" below). Every tile carries:

• A banner label: Mature (green), Partial (yellow), Low (red), or Pending (gray).
• Headline: the member's location name, exactly as it appears in your directory.
• Sub-line: their SOP coverage percentage, written as "\<n\>% SOP coverage," or "Awaiting data" when Verinode does not yet have a coverage figure for that member.
• Meta line: that member's own average cycle time, "\<n\>d cycle," when known; blank when it isn't. This is the member's individual cycle time, a different number from the network median in the hero band above.
• A gauge visual: an arc filled to the coverage percentage and colored to match the banner, unfilled when the member is Pending.

The three bands are:

| Band | SOP coverage | Reads as | |---|---|---| | Mature | 80% or higher | Process is written down and the crew is working from it on most jobs. | | Partial | 40% up to 80% | Some process exists; sizable share of jobs still run without a documented SOP behind them. | | Low | Under 40% | Mostly undocumented process, whatever the reason, new membership, no SOP program yet, or a program that has stalled. | | Pending | No figure yet | Verinode has not received enough SOP-tagged job data from that member to compute a coverage percentage. Not a red flag by itself, just not yet measurable. |

Clicking a tile opens that member's profile in Members, focused on them, so you can follow up with the specific location rather than staring at a percentage in isolation. This still respects the privacy boundary: you land on that member's aggregate profile, not their job files or SOP text.

Empty state. If your directory has no active memberships yet, the row reads: "Process maturity will appear as members are added."

How this relates to Capacity Pressure, right above it

The row directly above Process Maturity is Capacity Pressure: members running over 80% utilization, sorted worst first, banded Stretched or Maxed Out. It draws from the same per-member data set (each tile there also shows that member's cycle time in its meta line) but it is a different lens on the same person. A member can be Mature on process and still Stretched on capacity, or Low on process while running comfortably under capacity. Read the two rows side by side rather than assuming one predicts the other. When no member is over 80% utilization, that row reads: "All members operating with healthy capacity headroom."

Seeing every member: the full card panel

The home row caps at twelve tiles so the page stays scannable. To see every active membership's Process Maturity gauge, open the full card panel: click into a Shared SOP tile or a Fleet tile further down the Operations page (either opens the panel), then use the tab bar across the top of the panel to switch to Process Maturity. The panel has four tabs: Capacity, Process Maturity, Shared SOPs, Fleet; tap between them, or use the arrow controls, to move across all four without closing the panel.

On the Process Maturity tab, every active member appears as a row, not just the twelve on the home page. Each row shows the member's name, their average cycle time ("Avg cycle \<n.n\> days," or "Cycle time unknown" when not yet available), and a meta line combining utilization ("\<n\>% utilized," or "Utilization unknown") and SOP coverage ("\<n\>% SOP coverage," omitted when unknown), separated by a middle dot. A trailing figure shows fleet item count when known.

Empty state. If there is no member data at all yet, this tab reads: "Process maturity surfaces as members log SOP-tagged jobs."

1. 1Open Operations from the HQ sidebar.
2. 2Read the hero band first: your network's cycle-time percentile against the industry, and the three network-wide averages underneath it.
3. 3Scan the Process Maturity row for outlying tiles, Low or Pending members worth a conversation, and Mature members worth using as an internal reference.
4. 4Click a tile to open that member's profile in Members and follow up directly.
5. 5To review the whole network at once rather than the top twelve, open the card panel from a Shared SOP or Fleet tile and switch to the Process Maturity tab.

What "process maturity" rolls up from

Every number on this page, the hero's network averages and each member's coverage percentage, cycle time, and utilization, comes from a periodic group aggregation snapshot (the network data), keyed under an "operations" evidence block. That snapshot is built by reading each member's own operator-side data on their side of the privacy boundary and rolling it up before HQ's view is ever built: SOP coverage from jobs tagged to a written, on-file SOP; cycle time from how long jobs take from open to close; capacity utilization from active jobs against that member's stated capacity; fleet items from registered equipment. HQ receives the output aggregate. It does not receive the underlying jobs, SOPs, or documents that produced it. In newer snapshots that evidence block is also encrypted at rest under the group's own key and only decrypted for the HQ user viewing the page.

The same evidence block feeds beyond this page, too. On Network Health, a member whose SOP coverage or cycle time falls into a range calibrated against restoration-industry norms also surfaces as a reason chip on that member's card there, banded by severity, so a maturity problem shows up again in whichever HQ view a leader happens to be working from, not just here.

Best-practice example

Say the hero band reads a network cycle-time median of 24 days, at the 35th percentile against the industry (faster than most, tinted green), with 68% Process Maturity and 74% Capacity underneath it. Scanning the Process Maturity row, three members sit Low, two of them also appear in Capacity Pressure as Stretched. That combination, low process discipline and high utilization at the same locations, is the pattern worth a call before it worth a program: a stretched crew with no written SOP to fall back on is the most likely place for cycle time to slip next quarter, even while the network median still looks strong overall. Open the card panel and switch to Process Maturity to confirm there isn't a fourth member quietly Pending rather than genuinely Low, then follow up with each from their Members profile.

Related reading

• HQ overview: where Operations sits among the rest of the HQ shell.
• Network Health: the same operations evidence feeding into per-member reason chips and quartile standing.
• HQ Compliance: where the Process Standards and SOPs editors that feed a member's own coverage live on the operator side.
• HQ Benchmarks: the broader percentile-against-industry framing used for the cycle-time pill here.

Data sources