Network targets: setting a threshold that tags franchisee sliders

What a network target is

Every restoration program, an approved-vendor list, a fleet safety mandate, a reputation standard, eventually needs a number attached to it: a franchisee should carry no more than so many vehicles over five years old, or should sit at or above a 4.5-star Google rating, or should keep monthly rent under some ceiling. A network target is how a program admin declares that number once, at the program level, and has it show up automatically on every franchisee's own metric tile across the network, as a plain ✓ Meets target or ✗ Below target read.

The target lives on the program, not on the franchisee. You are not setting 60 individual thresholds for 60 locations, you are declaring one rule ("fleet age should average 5 years or under") and Verinode evaluates every enrolled franchisee against it, using the fleet, facilities, equipment, commercial, or reputation data that already flows into their section sliders. Nothing here is a new data source, it is a read against numbers HQ already sees in aggregate.

Where to find it

Open a program from Programs in the HQ sidebar at hq.verinode.ai/programs, then click into any individual program. That opens the program's detail page, built from the same shared adapter every program type uses (see Inside a program: the detail view and its rows for the full page layout).

The Network target row sits low on that page, after any type-specific authoring row (the audit rubric on a vendor-approval program, the KPI matrix on a carrier program, the co-op terms on a marketing co-op) and before Open violations, Recent audits, and Latest KPI snapshots. As an admin, this row is always present, whether or not a target has been declared yet, so you always have a way to set or clear one. If you are not an admin, the row only appears once a target has actually been set; with nothing declared, it is simply absent from the page.

Marketing co-op programs are the one exception. Co-op has its own purpose-built ledger page, not the shared detail view this row lives on, so co-op programs never carry a network target.

The metric registry: what you can target

The dropdown in the target modal is not free text. It is a fixed registry of the same metric keys the per-section sliders already track, grouped by section:

Facilities

• Facility count (higher is better)
• Total square footage (higher is better)
• Total monthly rent (lower is better, entered in cents, e.g. 12000 = $120.00)
• Facilities owned % (higher is better)
• Leases expiring within 90 days (lower is better)

Fleet

• Vehicle count (higher is better)
• Average vehicle age, years (lower is better)
• Vehicles owned % (higher is better)
• Accidents, last 36 months (lower is better)
• At-fault accidents, last 36 months (lower is better)
• Drivers with expired license (lower is better)
• Drivers with stale MVR (lower is better)
• Auto policies expiring within 90 days (lower is better)

Equipment

• Active equipment count (higher is better)
• Distinct equipment classes (higher is better)
• Average equipment age, years (lower is better)
• Equipment over 5 years % (lower is better)
• Maintenance overdue count (lower is better)
• Calibration overdue count (lower is better)
• Equipment in-service % (higher is better)

Commercial

• Commercial clients count (higher is better)
• Commercial jobs, last 36 months (higher is better)
• Commercial collected % (higher is better)
• Average days to pay, commercial (lower is better)
• Top-client concentration % (lower is better)

Reputation

• Reputation composite score, 0-5 (higher is better)
• Google rating, 0-5 stars (higher is better)
• Google review count (higher is better)
• Yelp rating, 0-5 stars (higher is better)
• Yelp review count (higher is better)

Each entry carries a default direction ("higher is better" or "lower is better"), an input step hint the value field snaps to, and a stored-unit description shown next to the value field, for example "percent 0-100," "cents (e.g. 12000 = $120.00)," "stars 0-5," or "score 0-5." You do not need to guess units: the modal tells you exactly what number to type once you pick a metric.

Declaring a target

With no target set, the row shows a single tile: + Declare a network target, labeled Target, subtext "Pick a section metric + value + direction. Compliance ✓/✗ tags appear on each franchisee's slider tile." (marked ADMIN). Clicking it opens the Network target modal.

1. 1Pick a metric. The select is grouped by section (Facilities, Fleet, Equipment, Commercial, Reputation) with the placeholder ", pick a metric, " until you choose one. Once you pick a metric, a line appears underneath reading "Stored as [unit]. Default direction: Higher is better / Lower is better."
2. 2Enter the target value. The field label updates to "Target value ([unit])" so you know exactly what to type, for example "Target value (percent 0-100)" or "Target value (cents (e.g. 12000 = $120.00))." The field is disabled until a metric is chosen.
3. 3Confirm or override the direction. Choosing a metric snaps the direction dropdown to that metric's usual reading (most metrics default sensibly, average vehicle age defaults to "lower is better," Google rating defaults to "higher is better"), but you can override it. The two options read exactly as: "Higher meets (≥ target)" and "Lower meets (≤ target)." A network might legitimately want a metric read the opposite of its usual sense; the direction is stored explicitly on the program rather than re-derived from the registry, so your intent stays intact even if the registry's usual reading later changes.
4. 4Set grace days (optional). A number field, default 0, with the note "Days a newly-enrolled franchisee has before compliance is evaluated. 0 = evaluate immediately."
5. 5Save. The button is disabled until a metric is chosen and a value is entered.

Once saved, the row's tile changes to show the live target: the section name plus "target" as the label (for example "Fleet target"), the headline reading the direction symbol and the formatted value (for example "≤ 5 yrs" or "≥ 4.5 ★"), the metric's full label and grace days on the sub-line (for example "Average vehicle age (years) · 30d grace"), and a meta line reading either "Franchisees meet at or above" or "Franchisees meet at or below" depending on direction. A second tile, Edit target, sits beside it (subtext "Change metric, value, direction, or grace days. Clear to remove tags.", marked ADMIN) so you can reopen the modal at any time.

Value formatting follows the metric's stored unit: _cents keys render as dollars (rounding to $Xk or $X.XM at scale), _pct keys render with a % sign, star-based metrics render as X.X ★, score-based metrics render to one decimal, day counts render as "X days," year counts as "X yrs," square footage with a thousands separator and "sqft," and everything else as a plain formatted number.

Editing or clearing a target

Reopening the modal from Edit target pre-fills every field with the currently saved metric, value, direction, and grace days. Change any of them and save to update the target in place; every franchisee's slider tile picks up the new threshold the next time that slider is read, no separate re-publish step.

Clear target removes the threshold entirely: it wipes the metric key, value, direction, and grace days back to null (grace days resets to 0), and every ✓/✗ tag for that program disappears from franchisee sliders on the next read. Only an admin can set, edit, or clear a target; a non-admin viewer who opens a program with no target simply sees the row's plain-text note: "No network target declared. Group admin can pick a metric + value from this row."

How the compliance tag reaches a franchisee's slider

Once a target is declared and active (the owning program's status is Active), every per-section slider (Facilities, Fleet, Equipment, Commercial, Reputation) checks whether any active program in the group has declared a target on the metric that tile is already showing. When one exists, the franchisee's own metric tile gains a line under the peer-comparison read:

• ✓ Meets target in green, when the franchisee's value satisfies the direction (at or above the target for "higher," at or below it for "lower").
• ✗ Below target in red, when it does not.

Either way, a small parenthetical shows the target value itself, for example "(target 5 yrs)," and hovering the tag surfaces which program declared it, "Network target from [Program name]: [value]." If two active programs happen to target the same metric, the one activated most recently wins, admins coordinating on the same metric across programs should expect the later one to take precedence.

A franchisee with no value on record for that metric (nothing entered or ingested yet) shows no tag at all, there is nothing to compare. The tag only ever compares a live number to a live target; it never infers a status from missing data.

Reading the row as an admin doing weekly review

The Network target row is a declaration surface, not a leaderboard. It shows you the one number you set, not how every franchisee stacks up against it, that comparison lives on each franchisee's own slider, one metric at a time, where you already look at peer medians and percentiles. Use this row to confirm what you have declared and adjust it; use the per-section sliders, or the Compliance surfaces, to see who is meeting it.

A sensible order for setting one:

1. Decide the metric from a real conversation, an insurance renewal that flagged fleet age, a brand audit that flagged facility standards, a franchisee complaint about lease terms.
2. Check the section's existing peer median first (open any franchisee's slider for that section) so your target is grounded in what the network actually looks like, not an arbitrary round number.
3. Set the direction deliberately, most defaults are correct, but double-check anything where "more" isn't obviously "better" for your network (concentration and expiring-policy metrics default to lower-is-better for a reason).
4. Leave grace days at 0 unless you specifically want the field recorded for a future onboarding-window policy, since it does not currently delay the tag.

Related reading

• Programs: how HQ codifies what the network adopts, the catalog page this program lives in, and how the eight program types differ.
• Inside a program: the detail view and its rows, the full detail-page layout this row is one part of.
• Audit rubrics: weighted criteria for vendor-approval programs, the sibling authoring row for vendor-approval programs.
• Franchisee enrollments, the enrollment row that appears above this one on mandatory and opt-in programs.
• Compliance by franchisee (worst-cert view), where certification-style compliance is read across the whole network at once.
• Standards conformance, the brand-standard equivalent of a network target, scoped to standards programs specifically.