Related SOPs: the process behind a vendor, client, or asset
Open a vendor, a team member, a piece of equipment, or a carrier/TPA client record, and Verinode has already gone looking for the answer to one question: which of your written Standard Operating Pr…
On this page
What it is
Open a vendor, a team member, a piece of equipment, or a carrier/TPA client record, and Verinode has already gone looking for the answer to one question: which of your written Standard Operating Procedures actually reference this thing? Related SOPs is the panel that surfaces the answer, a short list of the SOPs that touch the record you're looking at, so you're not digging through your SOP library by hand to remember which procedure governs that vendor, that technician, or that piece of gear.
Nothing here is a new document, and nothing is invented. It's a read on connections that already exist, either because you set them yourself in the SOP editor or because Verinode noticed the same vendor, person, or equipment named inside a procedure. Verinode surfaces the link; it never decides which SOP a job should follow or writes one on your behalf. You author the SOPs (see Your SOP library), and this panel just makes "where does this show up elsewhere" answerable from wherever you happen to be looking.
The same lookup quietly primes your AI Co-COO, too. Before you ask IQ a question about a vendor, a team member, or a piece of equipment, it has already resolved which of your SOPs mention that record, the same linkage that fills this panel.
Where to find it
Related SOPs isn't its own page. It's a panel folded into six kinds of record, opened from wherever that record already lives on the platform:
- Vendors. Open any vendor from the Vendors section: a dedicated Related SOPs tab sits on its detail card.
- Team. Open a team member from the Team section: a dedicated Related SOPs tab, for named people only. An open role slot on your roster (a headcount target, not a specific hired person) never carries this tab.
- Equipment. Open a piece of equipment from the Equipment section: a dedicated Related SOPs tab, scoped to that exact unit, not every item of that type you own, just this one.
- Clients: Carriers and TPAs. Open a carrier or TPA from Clients: the linkage is folded into that client's Processes tab, underneath the processes you run with them. Private Pay and Commercial clients don't carry this panel; the link this panel reads only exists for carrier and TPA relationships today.
Across all of these, the tab (or, for carriers and TPAs, the block inside Processes) appears only once Verinode has actually found at least one SOP that touches the record. A vendor, person, piece of equipment, or client with nothing linked yet simply doesn't show the tab at all.
Note
The panel is built to also render a resolving state, "Resolving linked SOPs…", and a plain no-match message, worded per entity, for example "No SOPs touch this vendor yet. Verinode links them automatically when a process is documented from a job, an upload, or the SOP editor." In day-to-day use you'll rarely land on either screen, because the surrounding tab only shows up once there's a result to display. Treat the tab's presence or absence as the empty state: no tab means no SOP references this record yet.
How the linkage is resolved
Verinode reads two different structures depending on which kind of record you're looking at:
- Carriers and TPAs link the older way: a single field carried directly on the SOP. When you open an SOP's Details tab and set Link to Carrier or TPA, that client's record gets stamped onto the SOP. The Related SOPs panel on the client's Processes tab reads that field back.
- Vendors, team members, and equipment link a newer way: a separate table for each kind, connecting one SOP to as many vendors, people, or equipment items as the procedure actually names. You set these from the same SOP's Details tab, under Link to Vendors, Team, or Equipment, three chip pickers, one per kind.
Either path, the panel only ever returns SOPs that belong to you, filters out anything you've archived, and stops at ten results so a heavily-linked vendor or a carrier with years of SOPs behind it doesn't turn into an unreadable wall.
Ordering differs slightly by kind. For carriers and TPAs, active SOPs surface ahead of anything still in Draft or Needs Review, then most recently updated first within that. For vendors, team, and equipment, the most recently linked SOP sits on top, regardless of its status.
What each row shows
Every row in the list carries:
- The SOP's title, the name you gave it when you wrote or adopted it.
- Category, one of Water, Fire, Mold, Reconstruction, Contents, or General.
- Status, shown only when it isn't the ordinary case: an SOP still sitting in Draft or flagged Needs Review says so right next to its category. An active SOP, the normal state, shows nothing extra here.
- How it got linked, shown only for the two kinds Verinode infers on its own: "Detected from a document" or "Detected from job execution." A link you set yourself through the SOP editor's pickers, or the carrier/TPA field, carries no extra note, since that's the ordinary, expected way an SOP gets connected and doesn't need calling out.
Above the list, a small label counts the results in plain language: "3 SOPs on file," or "1 SOP on file" for a single match.
Jumping into the SOP
Each row ends with an Open button. Click it and Verinode closes the record you're currently viewing, the vendor, team member, equipment item, or client card, and takes you to Processes. From there, use the All Processes tab (filtered to My SOPs) or the Most recent row on the Processes home to open that exact SOP and read its full detail card, LEAN score, steps, and links included. See Your SOP library for what that detail card shows once you're in it.
Linking an SOP to something yourself
Verinode links a vendor, team member, or piece of equipment to an SOP automatically once it recognizes the connection in a document or a job, but you don't have to wait for that. Open any SOP's detail card, go to the Details tab, and:
- 1Use Link to Carrier or TPA if the SOP is written around how you serve one specific carrier or TPA. It's a single-select dropdown, one client per SOP.
- 2Use Link to Vendors, Team, or Equipment for everything else the SOP names. Three chip pickers, one per kind, and you can add as many of each as the procedure actually calls for: the rental vendor, the lead technician's role, the specific extraction unit.
- 3Add or remove chips as your procedure changes. Each change saves on its own; there's no separate "save links" step to remember.
The moment you add a link, the record on the other end, the vendor, the team member, the equipment item, the carrier, or the TPA, starts showing this SOP in its own Related SOPs panel the next time you open it.
Best-practice example
Say your fire-mitigation SOP names a specific ozone generator you rent from one vendor and calls out your two lead fire technicians by role. Open that SOP, add the rental vendor under Link to Vendors, Team, or Equipment, then add both technicians under the same picker. The next time either technician's own Team detail card comes up, maybe you're reviewing a coaching note or checking a coverage gap, the Related SOPs tab already shows this procedure, so neither you nor IQ has to go hunting through the SOP library to confirm which written process actually governs how they're supposed to run that job.
Related reading
- Your SOP library: writing, editing, and scoring SOPs
- Excellence (Processes): the fractional-COO process coach
- Clients and carriers
- The decision workspace
- Acting on decisions
Data sources
- 1.Your SOPs and the vendor, team, equipment, and carrier/TPA links you set on them. Your business.
- 2.Vendor, team, equipment, and client records. Your business.