Network SOPs: importing SOPs shared by your HQ

What this is

If your business belongs to a franchise or association network on Verinode | HQ, your HQ can share a written SOP into the network, and every membership that belongs to the same group can pick it up and use it. Network SOPs is the shelf where those shared procedures land inside your own Processes section: a source-filtered view of the SOP list that separates what you wrote yourself from what your HQ has shared, with a one-click Import that copies a network SOP into your own library as a draft you can then edit and activate.

Verinode does not write the SOP for you and does not decide which one you should adopt. Your HQ shares it, Verinode surfaces it alongside your own procedures with a clear source label, and you choose whether to import it. Nothing about the source SOP's underlying text is shown to you until you're a member of the same network group it was shared into, and the copy that lands in your library is anonymized before it ever leaves the group.

This article covers the Network source filter, the My SOP vs Network SOP badge, and the import flow end to end. For the rest of the SOP library, writing, editing, and the LEAN score, see Your SOP library. For the standards catalog SOPs get measured against, see Standards library.

Where to find it

Open Processes from the sidebar, under Operations, at /processes. (The Help Center groups this page under Excellence; visiting /excellence redirects you to the same workspace. See Excellence overview for why that name still exists.)

Inside the Processes card slider, click the All Processes tab (third across the top, after Findings and Flow). A row of kind pills sits at the top: All (N), My SOPs (N), Pending Confirmations (N), Standards (N). Click My SOPs to open the SOP view. Network SOPs only ever appear inside this view, they never show up under All, Pending Confirmations, or Standards.

The Source filter

Once at least one network SOP is available to you, a second filter row appears directly under the kind pills, labeled Source in small uppercase text, with three pills:

• All ({your SOP count} + {network SOP count}), the default. Shows your own SOPs and every importable network SOP together in one list.
• My SOPs ({your SOP count}), narrows the list to only the SOPs you've written or already imported. Network SOPs drop out of view.
• Network ({network SOP count}), narrows the list to only the SOPs shared into your account from your HQ network, hiding your own SOPs entirely.

Whatever you type into the Search processes… box on the same screen filters within whichever Source pill is active, matching against the SOP's title, subtitle or category (for your own SOPs), or title, service line, and the sharing operator's name (for network SOPs).

Reading a row: My SOP vs Network SOP

Every row in the SOP view carries a small badge next to its title so you always know whose SOP you're looking at:

• My SOP, in copper, on any SOP you've written, uploaded, dictated, adopted from a standard, or previously imported from the network. This is your platform's brand color, the badge simply means "this is yours now."
• Network SOP, in teal, on a SOP shared into your account by your HQ that you haven't imported yet.

Your own SOP rows show a copper dot, the SOP's title, a subtitle with its LEAN score and work type when scored, and a relative timestamp on the right ("14m ago," "3h ago," a plain date once it's over a week old).

Network SOP rows look similar but carry different information, because the row isn't about your own history, it's an offer to adopt someone else's structure:

• A teal dot instead of copper.
• The SOP's title, with the Network SOP badge beside it.
• A meta line combining, in order: "Shared by [operator name]", the service line in Title Case (if the SOP has one), "[N] adopted" (how many operators across the network have already imported this SOP), and the date it was shared ("Jun 12," for example).
• An Import button on the right, in place of the timestamp your own rows show.

Clicking a network SOP row itself does nothing, unlike your own SOPs, network rows don't flip into a detail card. The only interaction on a network row is the Import button.

Importing a network SOP

1. 1Find the SOP. Open All Processes, click the My SOPs kind pill, then either leave Source on All or click Network to see just what's importable.
2. 2Click Import. The button reads Import, then Importing… while the copy runs.
3. 3Wait for the toast. On success, a toast reads: "Imported as a draft SOP. Refine the steps and activate when ready." The button itself flips to a green Imported pill and stays that way for the rest of your session on this row.
4. 4Find it under My SOPs. The page refreshes in the background. Your new SOP appears in the My SOPs list as a draft, titled and categorized exactly as the network version was, with the anonymized steps already filled in. From there it behaves like any other SOP you own, open its detail card, edit the steps, and click Activate this SOP when you're ready for it to count toward peer benchmarks and link to jobs. See Your SOP library for the full draft-to-active walkthrough.

What actually happens behind that click: Verinode reads the shared SOP's title, its already-anonymized body, and its service line from the network record, decrypts the body (it's encrypted at rest under your HQ group's shared key), confirms you genuinely belong to the group it was shared into, and writes a brand-new row into your own SOP library, owned by you, starting as a draft. The source record is left untouched aside from its adoption count ticking up by one, so the same network SOP stays available for every other membership in the group to import too.

If Import doesn't go through

Two error messages can surface as a toast instead of the success message:

• "You already have an SOP with this title." You (or an earlier click) already imported this exact network SOP, or you separately have an SOP of your own with the identical title. This is a safeguard against creating duplicate drafts on an accidental double-click or a repeat visit after the page refreshed. Check your My SOPs list, your draft is very likely already there.
• "This SOP belongs to a network you're not part of." A membership-check failure. In normal use you should never see this, since the network SOPs shown to you are already scoped to the groups you belong to, but it guards the import action itself in case your group membership changed between loading the page and clicking Import.

If neither message appears and Import simply doesn't complete, the toast shows whatever underlying error was returned; treat it as a one-off and try again.

Empty state

If your Source and search combination matches nothing, whether that's an empty Network filter, an empty My SOPs filter, or a search term that hits neither list, the SOP view reads the same generic line every kind-and-search combination on this tab uses:

No processes match this filter yet.

Best-practice example

Say your HQ shares a newly refined mold-remediation SOP into your group, built from a peer that scored well on containment and documentation. It shows up under All Processes, My SOPs pill, Source: Network, with the meta line "Shared by [an HQ-network operator] · Mold Remediation · 6 adopted · Jul 2." Click Import. A moment later the toast confirms it landed as a draft, and it's now sitting in your own My SOPs list with the same title and category. Open its detail card, walk the step editor, adjust anything that doesn't match how your crew actually runs a mold job (a different drying vendor, a different documentation habit), and click Activate this SOP once it reads true. From that point it scores its own LEAN number, tracks its own Jobs Using count, and behaves exactly like a procedure you wrote from scratch, the network only supplied the starting point.

Related reading

• Excellence overview
• Your SOP library: writing, editing, and scoring SOPs
• Standards library: IICRC, LEAN, OSHA, EPA, and state rules
• Patterns to confirm: how Verinode captures your process steps
• Process findings and Take Action decisions
• The decision workspace
• Acting on decisions

Data sources