Network SOPs: importing playbooks shared across your network

What a network SOP is

If your business belongs to a franchise or association group inside Verinode, some of your fellow members can share a documented procedure into the group's library for everyone else in the network to use. That shared procedure is a network SOP: a standard operating procedure written by another member, run through Verinode's anonymization pass to strip out anything identifying, and made available to import into your own process library in one click.

This is not the peer-benchmark cohort you see elsewhere on the platform, where individual operators are never named. A network SOP is shared inside a specific HQ group you already belong to, so the member who shared it is named (their business, not a peer number), while the procedure itself, the actual steps, has any identifying specifics stripped out before it ever leaves their account. You get the process, not their file.

Verinode never sells this data, or any operator data, to carriers or insurers. Sharing a SOP into your network is a decision the source operator makes; importing it is a decision you make. Nothing imports itself.

Where to find it

Open Processes from the sidebar (/processes). The section opens on a row of cards you scroll through: Findings, Flow, All Processes, By Standard, Coverage, Benchmarks. Network SOPs live inside All Processes.

Inside All Processes, a row of filter pills sits above the list: All, My SOPs, Pending Confirmations, Standards, each with a count in parentheses. Click My SOPs and, if your group has anything shared, a second row appears underneath: Source, with three pills, All, My SOPs, Network, each again showing a count. This Source row only appears when there's at least one network SOP available to you. If nobody in your group has shared anything yet, you'll never see it, the SOP list just shows your own documented procedures.

A search box sits to the right of the top filter row. It matches against title, subtitle, and category for your own records, and against title, service line, and the sharing member's name for network SOPs.

Reading a network SOP row

Each network SOP appears as its own row inside the SOP list, marked with a teal dot and a Network SOP tag beside the title. Your own SOPs, by contrast, carry a copper My SOP tag when you're inside the Source-filtered view. The color coding is deliberate: teal is Verinode's Monitor accent, used across the platform for things worth watching that come from outside your own operation.

Under the title, a single line of metadata reads left to right:

• Shared by [member name], the business that documented and shared this SOP.
• The service line, if the SOP is tagged to one (for example, Water Mitigation), title-cased.
• "N adopted," how many members across your network have already imported this SOP into their own library. A SOP nobody has imported yet reads "0 adopted," not a stronger claim than the data supports.
• The share date, when the procedure was added to the network library.

On the right edge of the row sits the action: an Import button, or, once you've imported it, an Imported badge in green.

Importing a network SOP

1. 1Open Processes → All Processes, click the My SOPs filter pill, then the Network pill under Source (or leave it on All to see both alongside your own).
2. 2Find the SOP you want and click Import. The button reads "Importing…" while the copy is created.
3. 3Verinode copies the anonymized body into a brand-new SOP in your own library, saved as a draft. A toast confirms: "Imported as a draft SOP. Refine the steps and activate when ready."
4. 4The button becomes an Imported badge. Once the list refreshes, that new draft shows up under My SOPs carrying the same copper My SOP tag as everything else you've written, it doesn't stay visually marked as a network import in the list. Open its own detail card if you need to confirm where it came from.
5. 5Open the new draft, review every step against how your crew actually works, and activate it when you're satisfied. Nothing in an imported draft goes live on its own.

The imported copy is fully yours from the moment it lands: rename it, add or remove steps, retag its category, or archive it, exactly as you would with anything you wrote from scratch. Verinode keeps no ongoing link back to the shared original, an import is a one-time copy, not a subscription to future edits the source operator makes.

Every imported SOP is saved with draft status and no activation date. Open it and its Status section carries an amber Draft badge with the line "Activate this SOP to contribute to peer benchmarks and surface in job process matches," next to an Activate this SOP button. Click it and a toast confirms: "SOP activated. It now contributes to peer benchmarks and links to jobs." Until you do, the imported procedure sits in your library as a reference only, it won't count toward your own adherence tracking or your peer-SOP benchmark comparisons. See the SOP detail card for what else lives on that screen.

What "anonymized" means here

Sharing a SOP into the network runs the source operator's original through an LLM anonymization pass before it's written to the shared library, and that pass runs once, at share time, not each time someone imports. What comes out the other side is the procedure: the steps, the sequence, the timing, with anything that would identify the source operator's specific business, crews, addresses, or named vendors removed. The source operator's own copy in their own account is never touched, they keep their original exactly as written; only the shared, cleaned copy lives in the network library.

That's a narrower kind of anonymization than the one behind Verinode's peer benchmarks elsewhere on the platform, where individual operators are never named to anyone, including HQ. Here, because you and the sharing member both belong to the same franchise or association group, you already know who's in your network, so the "Shared by" attribution stays visible. What's stripped is the operational detail inside the procedure itself, not the identity of who wrote it.

Empty states

If your account isn't part of any HQ group, or your group hasn't had anyone share a SOP yet, the Source row simply doesn't appear, there's no separate empty-state message for it. The SOP list under My SOPs just shows your own documented procedures (or, if you haven't written any yet, the general All Processes empty state: "No processes match this filter yet.").

If you search or filter down to nothing, the same message applies across the whole tab, whether the miss is on your own SOPs, network SOPs, or both.

Best-practice example

Say your business joins a regional restoration group inside Verinode, and three other members have already shared water-mitigation SOPs. Open Processes → All Processes, click My SOPs, then Network. You see four rows, each tagged Network SOP, each showing who shared it, the service line, an adoption count, and a share date. One reads "12 adopted," well ahead of the others, a signal that most of your network has already put it through its paces. You import that one. It lands as a draft under My SOPs. You open it, adjust two steps to match how your crew actually stages equipment, and click Activate this SOP. You now have a documented, network-tested starting point you got to in one click instead of writing from a blank page, and the member who shared it still owns their own original, untouched, in their own account.

Related help

• All Processes: browse, filter, and search your records
• The SOP detail card
• How work flows through your process library
• Confirming a pattern Verinode observed
• Acting on process decisions
• Connecting your data
• The decision workspace

Data sources