Operations detail tabs: the four-tab slide-over

What this is

Every row on the Operations home page shows a handful of tiles, six here, twelve there, however many fit comfortably in a horizontal scroll. The detail slide-over is where the full list behind two of those rows lives: a full-screen overlay of swipeable cards that opens on top of the Operations page, with four tabs across it, Capacity, Process Maturity, Shared SOPs, and Fleet.

This is a network read, not a single member's book. Every row in every tab is either a per-member rollup already computed by the network aggregator (a member's own utilization, cycle time, SOP coverage, and registered fleet count) or a network-wide roll-up (a shared SOP's adoption and view counts, an equipment class's network-wide unit and member counts). HQ never opens a franchisee's private job records, payroll, or line-item costs to build any of these tabs. For the full mechanics of how that boundary holds, see What HQ sees: the network privacy boundary.

Where to find it

Open Operations from the HQ sidebar at hq.verinode.ai/operations. The slide-over is not a separate page. It opens as an overlay when you tap a Shared SOPs tile (in the Shared SOPs row) or a Fleet tile (in the Bulk Buy row), and it opens already scrolled to that tab, focused on the specific row you tapped.

The cards-slider deck

The slide-over fills the screen between the sidebar and the AI agent panel, if it's open. Four cards sit side by side, one per tab, and you move between them by swiping, dragging, clicking the floating left/right arrows at the edges of the screen, or clicking a dot in the row of navigation dots pinned to the bottom of the screen. Each card carries its own accent color so the tab you're on is visible even mid-swipe:

• Capacity: Ember Red (the Analyse signal color)
• Process Maturity: Hard Hat Yellow (the Maintain signal color)
• Shared SOPs: Copper
• Fleet: a deep purple, distinct from the three signal-color tabs beside it

Every card header shows the section label (Operations) and the tab's own label, plus a close button. Closing the slide-over (the X, clicking outside the card, or pressing Escape) returns you to the Operations home underneath.

The four tabs

Capacity

What it is. Every member whose active job load is running hot enough to be worth a look, the same cohort behind the home page's Capacity Pressure row, sorted from most stretched to least. A member appears here only once their capacity utilization passes 80%.

What you see. One row per member, each showing:

• The franchisee's name as the title.
• "Avg cycle N.N days" as the body line, or "Cycle time unknown" if no cycle-time figure has come through for that member.
• A meta line combining utilization and SOP coverage: "N% utilized" (or "Utilization unknown" on the rare row that qualified without a live percentage), followed by "N% SOP coverage" when that member has a coverage figure on file. That second piece is omitted entirely, not shown as a dash, when there's no coverage figure yet.
• A trailing "N units" figure, that member's own registered fleet count, when one exists. This is the member's own equipment total, not a network-wide figure, don't confuse it with the totals in the Fleet tab.

Empty state. "No member is running over 80% capacity. Pressure points show up here when utilization tightens."

Process Maturity

What it is. Every member in your network, one row each, listing the same underlying figures as the Capacity tab, cycle time, utilization, SOP coverage, fleet count, but unfiltered: this tab is the full roster, not just the members running hot.

What you see. The same row layout as Capacity: franchisee name as title, "Avg cycle N.N days" (or "Cycle time unknown") as body, a meta line of utilization plus SOP coverage percentage, and a trailing fleet-unit count when available.

Empty state. "Process maturity surfaces as members log SOP-tagged jobs." This appears only when your network has no members at all; once a single member exists, that member's row shows here even if every figure on it reads "unknown."

Shared SOPs

What it is. The full list behind the home page's Shared SOPs row, every process a member has actively published to your network's shared library, newest first.

What you see. One row per shared SOP, each showing:

• The SOP's title as the row's title.
• The SOP's actual content as the body line, when the source member's write includes it. When there's no body text on file, the body line falls back to "Shared by {member name}" instead, so attribution still shows even without content.
• A meta line joining whichever of these apply: the service line it's tagged to, "N adopted" (how many members have pulled this SOP into their own process library), and "N views".
• A trailing date, when the SOP was shared, in your browser's local date format.

Empty state. "Shared SOPs land here when members publish a process to the network library."

Fleet

What it is. The full list behind the home page's Bulk Buy row, every equipment class your network tracks, with bulk-buy candidates sorted to the front.

What you see. One row per equipment class, each showing:

• The class name as the title, humanized from the underlying category (a "cube_van" record displays as "Cube Van", the same rule that governs every raw database label surfaced anywhere in Verinode).
• "N units across N members" as the body line, the network-wide unit total for that class and how many distinct members report equipment in it.
• A "Bulk-buy candidate" meta label on classes where enough members across the network are independently carrying that class that a group purchase or group rental agreement is worth pursuing. Verinode doesn't publish the exact number of members it takes to cross that line, the same qualitative posture as every collective-demand gate on the platform, because publishing the mechanics invites someone to game it. Classes below that line show no meta label at all, not a "below threshold" note.

Empty state. "Fleet categories appear once members log equipment by class."

How SOP and Fleet tiles open focused

Tapping a tile in the home page's Shared SOPs row or Bulk Buy row does two things at once: it opens the slide-over directly on the matching tab (Shared SOPs or Fleet), and it scrolls to and highlights that specific row inside the tab with a brief copper ring, so you land on the exact entry you tapped instead of a list you have to search. Swiping to a neighboring tab and back, or closing and reopening the slide-over, clears the highlight.

This highlight only ever applies inside the tab you opened into. If you swipe from Shared SOPs over to Capacity or Process Maturity to browse the wider roster, no row lights up there, the highlight is tied to the specific SOP or fleet class you tapped, not to any member row.

How member tiles route to Franchisees instead

Every franchisee tile on the Operations home, in Capacity Pressure or Process Maturity, behaves differently from a Shared SOPs or Fleet tile: tapping it does not open this slide-over at all. Instead it takes you straight to that member's page inside Franchisees, deep-linked to that specific member.

This is deliberate. A franchisee tile is already the summary; there's no richer per-member profile to drill into inside Operations itself, the fuller picture of that member, their directory status, certifications, contact history, lives in Franchisees. Operations exists to show you the network pattern, who's running hot, whose processes are documented, and to hand you to the right member record the moment you want to act on one name. See hq-overview for how the Franchisees section itself is laid out.

Because member tiles route out to Franchisees rather than opening a drilled card here, this is the only entry point into the Capacity and Process Maturity tabs at all: there is no home-page tile that opens the slide-over directly onto either one. To browse the full Capacity or Process Maturity list, open the slide-over from a Shared SOPs or Fleet tile, then swipe, drag, or use the arrows or dots to move over.

Why these four tabs list-only, with no deeper drill

Every row inside every one of these four tabs is a flat, read-only list item. Tapping a row does not flip it over into a fuller detail card the way an entity's own profile page might. That's consistent across every HQ card-slider on the platform, not a gap specific to Operations: HQ's card-slider surfaces are read-only network rollups by design, and none of them wire up a second-level detail adapter for an individual row.

Concretely, that means:

• A Capacity or Process Maturity row shows exactly the figures listed above, cycle time, utilization, SOP coverage, fleet count, and nothing more. There's no click-through from the row itself; the only way to reach more detail on that specific member is the franchisee tile on the home page, which routes to Franchisees.
• A Shared SOPs row already shows the SOP's full content inline when it exists, so there's nothing further to reveal by clicking into it.
• A Fleet row is a network-wide count with no single member's inventory behind it to drill into. Bulk-buy conversations happen with your equipment vendors, not inside another layer of this UI.

Keeping these tabs flat is what makes them safe as a pure network read: there's no per-row action that could pull a single member's underlying records into view. If you need to act on a specific member, whether that's an intervention, a compliance check, or a direct conversation, do it from their Franchisees profile, not from inside this slide-over.

The network privacy boundary, held throughout

Nothing in this slide-over exposes a single franchisee's underlying job records, payroll, or line-item costs to HQ. What you're seeing in every tab is one of two things:

• A member-level rollup (Capacity, Process Maturity): a franchisee's own utilization, cycle time, SOP coverage, and fleet count, computed by the network aggregator from that member's data. HQ sees the computed figure, not the underlying jobs or timesheets behind it.
• A network-wide roll-up (Shared SOPs, Fleet): a count or a piece of voluntarily published content aggregated or attributed across your own network's members, never a comparison built from operators outside your network.

Shared SOPs is the one row where a member's name is attached on purpose: sharing a process to the network library is an opt-in act, and the point of sharing is credit. That's not an exception to the privacy boundary, it's a separate, voluntary mechanism sitting on top of the same boundary that governs every other row here. Every other row on this page is your own network looking at its own members' rollups, not a cross-network comparison, so there's no anonymity gate to speak of on Capacity, Process Maturity, or Fleet: the members named here are your own.

Related reading

• hq-operations-overview, the Operations home page these four tabs are the full lists behind
• hq-overview, the HQ shell and the Franchisees section franchisee tiles route into
• hq-network-privacy-boundary, the full technical explanation of what HQ can and can't see
• hq-margin-cash-detail-tabs, the equivalent four-tab slide-over on the Margin & Cash home, built on the same pattern

Data sources