Skip to content
RiskTemplates · The Daily Brief Wednesday, November 18, 2026
Wire FINRA's Spartan Capital Case: The Private-Placement Diligence File That Wasn't There NOV 17

Feature Compliance Strategy

Third-Party Risk Board Metrics That Survive a Follow-Up Question

Five third-party risk board reporting metrics with definitions, paired evidence, and gaming vectors — built for a board that asks who signed.

By Rebecca Leung · November 16, 2026 ·
Table of Contents

TL;DR

  • The comment period on the interagency third-party risk proposal closed November 16. Its board-reporting language is softer than the 2023 guidance it would replace: reporting “as appropriate,” not a fixed oversight duty.
  • Five metrics survive a director’s follow-up because each one ships with the artifact that proves it — a function map, a contract extract, a test sample, a signed acceptance, a reopen count.
  • Vendor counts, assessment-completion percentages and tier distributions are management metrics wearing board clothes. Send them upstairs and a director will find the seam in one question.

The comment period on the interagency third-party risk management proposal closed November 16, 2026. Read the Federal Register notice and you will find a governance section that asks banks to “establish appropriate reporting to senior management and the board,” and a monitoring section that tacks on the qualifier “as appropriate, in line with the banking organization’s size, complexity, and risk profile.”

Compare that to the guidance the proposal is built to rescind. The 2023 Interagency Guidance on Third-Party Relationships (OCC Bulletin 2023-17, SR 23-04, FIL-29-2023) stated that a banking organization’s “board of directors has ultimate responsibility for providing oversight for third-party risk management and holding management accountable.”

Ultimate responsibility, or reporting as appropriate? Both, if the program is real. The agencies are not lowering the board’s duty — they are refusing to prescribe the packet. That puts the design burden on the person who builds it, and it means the packet has to hold up when a director leans in.

What the OCC Actually Did to Blue Ridge

In August 2022 the OCC hit Blue Ridge Bank with a formal agreement that opened with a finding of unsafe or unsound practices “including those relating to third-party risk management.” Article III of that agreement required the board, within 60 days, to adopt a written third-party risk management program covering fintech partners, with criteria for board review and approval built into the program itself.

The board did not get a dashboard. It got an obligation with a deadline. That is the difference between reporting on third-party risk and governing it, and it is the standard a metric set should be judged against: would this number have told the board something before the order arrived?

Five Metrics With Their Evidence Attached

Each metric below passes one test — improving the number requires improving the condition. Each ships with the artifact that proves it. The right-hand column is what a director or examiner asks to see next.

MetricDefinitionThe follow-up questionPaired evidenceFailure mode it exposes
Critical-function concentrationShare of critical activities supported by the largest provider, and count of functions with no alternate provider”Which two functions fail if this vendor is dark for 72 hours?”Function-to-vendor map with a named accountable business owner per rowTiering that rates vendors instead of functions, so a “low-risk” payroll tool hides inside a critical dependency
Exit feasibilityShare of high-risk contracts with termination for convenience plus transition assistance inside 12 months; deconversion fee exposure in dollars”What is the check we write to leave, and who approved that number?”Contract term extract per high-risk relationship, fee figure sourced to the clauseContracts scored on renewal, not on exit; fees discovered during a negotiation
Monitoring evidence coverageShare of high-risk relationships with control testing completed inside the interval the monitoring plan sets”Show me last quarter’s actual test, not the SOC report they emailed.”Test workpaper with tester initials and date; SOC bridge letter reconciled to the test”Reviewed annually” standing in for testing, with a vendor-supplied report as the only proof
Unaccepted residual riskCount of relationships where residual risk exceeds appetite and no signed, dated, expiring acceptance exists”Who signed, when does it expire, and what condition reopens it?”Acceptance memo naming the acceptor, the limit, and the expiryResidual risk scored in a spreadsheet and never formally accepted by anyone
Finding closure velocityMedian days from third-party finding to independently validated closure, plus 90-day reopen rate”How many of those closures rested on the vendor’s own word?”Reopen log; validation sample that re-performed a closed itemClosure counted when the vendor replies, not when the control is retested

Take the third row seriously, because it is where programs quietly rot. A monitoring plan states that a high-risk vendor gets control testing twice a year. A quarterly report says 94% of high-risk vendors are “current.” The 6% shows up as a small red cell, and everyone moves on. Then a director asks for the actual test on the vendor supporting the payments switch, and the workpaper turns out to be a cover memo forwarding a SOC 2 report with an exceptions section nobody read. The metric was accurate. The program was not.

The Four Numbers That Sound Like Board Metrics

Vendor count. Directors like it because it is concrete and it trends the right way when you cut tail spend. It says nothing about exposure. A bank can cut 300 vendors and increase risk by consolidating the remaining 40 into two platforms.

Assessment-completion percentage. The most gameable number in TPRM. Closing an assessment is an administrative act; the vendor risk can be identical before and after. Pair it with a count of assessments whose conclusions changed a relationship’s tier, contract terms, or monitoring plan. That number tells the board whether the assessments did anything.

Risk-tier distribution. A well-shaped pyramid is a comfort object. Push one level: how many vendors moved down a tier in the last year, and what evidence justified each move? Tier migration in one direction only is a sign the tiers are being managed, not the vendors.

“100% of critical vendors reviewed annually.” True and nearly meaningless on its own, because “reviewed” is undefined. Break it into tested versus attested, and the number gets smaller and more honest.

Which of these belong in the packet depends on the audience. As covered in the earlier piece on separating management and board TPRM reporting, the failure pattern is a single dashboard serving both audiences badly. The five metrics above are board metrics precisely because each one has a management-level feeder underneath it that the committee never sees unless it asks.

Build the Evidence Before the Slide

Sequence matters. A metric without its artifact is a hostage.

Days 1–30. Build the function-to-vendor map. Start from the critical activities list in the business impact analysis, not from the vendor inventory, because the inventory is organized by legal entity and the risk is organized by function. Every row needs an accountable business owner who will defend the dependency in a committee meeting. Expect two fights: product teams that consider the map an admission of fragility, and procurement, which will want to know why contract data is leaving the contract system.

Days 31–60. Pull four quarters of history for concentration and exit feasibility and calibrate the amber lines against it. Set them where your own record shows monitoring capacity already strained — a concentration ratio that has historically produced quarterly escalation is the honest threshold, not a round number borrowed from a conference slide. Publish the method beside the number. Add one anti-gaming control per metric: ticket-to-request mapping for monitoring coverage, independent sample re-test for closures, clause-level citation for every fee figure.

Days 61–90. Run the packet through the risk committee once as a dry run before it reaches the full board. The dry run’s job is to find the row where the presenter cannot answer the follow-up. Fix that row or drop it.

Ownership splits cleanly if you let it. The second-line TPRM function owns definitions, thresholds and the anti-gaming controls. Relationship owners supply data and defend it. The CRO signs the packet. The board risk committee receives it quarterly and gets out-of-cycle notice on three triggers: any critical vendor incident breaching an impact tolerance, any concentration breach above the approved limit, and any supervisory action against a critical provider.

What the Core Provider Statement Adds

The joint statement on community banks’ engagement with core service providers issued September 11, 2026 is the most useful board document of the year, and almost nobody has put it in a packet. It names the practices the agencies weigh when deciding how closely to supervise a provider: opaque pricing, back-billing windows that permit retroactive charges, deconversion fees that are “unsupported or contractually undefined,” and excessive limits on unaffiliated providers integrating with the platform.

Read against the exit-feasibility metric, that list converts contract hygiene into a supervisory variable. A board that sees dollar-denominated deconversion exposure next to the name of the provider holding its deposit platform is having a different conversation than a board that sees a green “contract current” cell. The September analysis of the OCC’s core provider control expectations goes deeper on what the examiners will test, and the concentration risk analysis walkthrough covers the portfolio math behind the first table row.

So What?

The proposal’s risk-based turn rewards banks that can prove their packet is proportionate, and punishes banks whose packet is decorative. Every metric in the table above can be built from records you already own — the BIA, the contract repository, the monitoring workpapers, the issue log. None of them require a new platform. What they require is a decision about which questions the board is allowed to ask, and the discipline to have the answer sitting in an appendix before the meeting starts.

The TPRM Kit includes the function-to-vendor map, contract term extract, monitoring coverage tracker, residual risk acceptance memo and the board packet template with the evidence appendix already laid out.

FAQ

Should the concentration metric count vendors or functions? Functions. Vendors are how exposure arrives; functions are what fails. Counting vendors produces a tidy chart and loses the two-functions-one-provider case that actually hurts.

What if the board asks for a metric we cannot evidence yet? Say so and give a date. A metric promised for next quarter is credible. A metric hand-entered this quarter and unsupported next quarter is worse than absent, because the board will start trusting it.

Do we need the same five metrics at a $900 million bank and a $40 billion bank? Same five, different weights and different thresholds. A community bank’s packet might carry the concentration and exit rows quarterly and the other three annually with a narrative. The evidence pairs do not shrink with asset size.

How does residual risk acceptance interact with risk appetite? Acceptance should cite the specific appetite statement it deviates from, name a limit, and carry an expiry. An acceptance without an expiry never gets revisited, which is how a tolerated condition becomes a permanent one.

◆ Need the working template?

Start with the source guide.

These answer-first guides summarize the required fields, evidence, and implementation steps behind the templates practitioners search for.

◆ Immaterial Findings · Weekly

Sharp risk & compliance insights. No fluff.

◆ FAQ

Frequently asked questions.

How many third-party risk metrics should go to the board?
Four to six, and every one of them needs a paired artifact the board can request on the spot. The binding constraint is not the dashboard, it is the follow-up question. If a director asks 'which functions break?' or 'who signed that?' and the answer requires a two-week project, the metric belongs in management reporting until the evidence exists. A workable starting point is three exposure metrics, one acceptance metric, and one remediation metric — then calibrate the count against how much time the risk committee actually spends on third-party risk.
Does the September 2026 interagency proposal require board reporting on third parties?
It requires less explicitly than the 2023 guidance it is designed to replace. The proposal's governance section lists establishing 'appropriate reporting to senior management and the board' as one of six elements of third-party risk management, and the ongoing monitoring section says reporting should happen 'as appropriate, in line with the banking organization's size, complexity, and risk profile.' The 2023 Interagency Guidance on Third-Party Relationships (OCC Bulletin 2023-17, SR 23-04, FIL-29-2023) was blunter: the board has 'ultimate responsibility for providing oversight for third-party risk management and holding management accountable.' The proposal shifts the emphasis from a fixed oversight duty to a risk-proportionate one.
What is a gaming-resistant TPRM metric?
A metric whose input cannot be improved without improving the underlying condition. Assessment-completion percentage fails this test because a team can close assessments without changing vendor risk. A concentration ratio tied to a named function-to-vendor map holds up because reducing it requires actually moving a function off a provider. Every board metric should be paired with the artifact that proves it was not hand-entered: a database pull, a contract term extract, a signed acceptance memo, or a re-test sample.
How should concentration thresholds be set for board reporting?
There is no regulatory number. The September 2026 proposal ties risk assessment to 'magnitude of harm' and 'likelihood' without prescribing limits, so institutions set their own against risk appetite. A defensible approach: build the function-to-vendor map first, compute the last four quarters of concentration, and set the amber line where your history shows the relationship already strains monitoring capacity. Revisit after two cycles. Publish the calibration method next to the threshold so an examiner can see the number was derived, not decorated.
What does the joint statement on core providers change for community bank boards?
It gives the board a specific, citable list of contract features to ask about: opaque pricing, back-billing windows, undefined deconversion fees, and integration restrictions on unaffiliated providers. Issued September 11, 2026 by the Federal Reserve, FDIC and OCC, the statement says the agencies weigh those features when deciding how closely to supervise a provider. For a board, that converts exit cost from a procurement detail into a supervisory variable worth a line in the packet.
Rebecca Leung

Author

Rebecca Leung

Rebecca Leung has 8+ years of risk and compliance experience across first and second line roles at commercial banks, asset managers, and fintechs. Former management consultant advising financial institutions on risk strategy. Founder of RiskTemplates.

◆ Related framework

Third-Party Risk Management (TPRM) Kit

Tier every vendor with one documented rule, run due diligence and AI vendor reviews, find contract gaps against the 2023 Interagency Guidance, and track SOC reports, issues, concentration and exits. Excel workbook, guide, Word policy and offboarding checklist.

Immaterial Findings · Newsletter

The brief, in your inbox.

Enforcement of the week, a framework breakdown, and the prompts that are actually worth running. Delivered to your inbox. Free.