Description

A focused course, tailored for you

The LOB Risk Lead's Quarterly Risk Profile Playbook

Turn issue logs, KRI breaches, and control test fails into a one-page LOB risk profile your business head will defend in the ERC.

Your business head reads the LOB risk profile the night before the Enterprise Risk Committee and calls you because it does not tell him something he can defend. Three KRIs in amber, two open issues from prior cycles, a Heightened Standards MRA aging into supervisory range, and a control-test failure rate that has crept up two quarters running. Each artefact has its own owner, its own cadence, and its own narrative. The profile is supposed to reconcile them and surface the two risks that actually moved. Most quarters it lists them all and ranks none.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

LOB Risk Leads sit between the first-line business heads who own the risk and the enterprise risk function that aggregates across the bank. The quarterly LOB risk profile is the single artefact that bridges them. It has to satisfy the business head (so he will defend it in the ERC without going off-script), the CRO and ERC (so the aggregation up to enterprise heat map is defensible), and the regulator review of the bank's risk reporting (so the methodology is traceable). When KRI ambers, control-test fails, issue aging, and emerging risks each tell a different story, the profile collapses to a list of everything and a ranking of nothing. The business head improvises in the ERC. The CRO asks why two open MRAs are not in the top three. The internal audit team flags the methodology gap in the next risk reporting review. The fix is a reconciliation method that takes the four input streams, applies a consistent aggregation logic, and produces a one-page profile with the two risks named, the one risk moving, and the talk-track the business head walks in with.

What you walk away with

Build a quarterly LOB risk profile that reconciles KRI breaches, control-test results, issue aging, and emerging risks into a single one-page read.
Run an issue aggregation method that surfaces the two MRAs aging into supervisory range without burying them under fifteen lower-rated findings.
Apply a KRI threshold review that distinguishes thresholds that fire on noise from thresholds that miss the risk that actually moved.
Triangulate control-test failure rates with issue volume and KRI breach pattern so the profile names the one risk genuinely on the move.
Hand the business head a two-sentence talk-track he will defend in the ERC without going off-script.

The 12 modules

Module 1. The four input streams and why they contradict each other

KRI dashboard, control test results, issue management log, and emerging risk inputs each run on a separate cadence with a separate owner. Module one walks through why the four streams produce contradictory readings of the same LOB quarter, where the methodology gaps sit between them, and what the reconciliation work actually involves. Worked example: a commercial LOB where KRIs read green, control tests read amber, and the issue log shows three aging MRAs.

Module 2. The KRI threshold review that distinguishes noise from movement

Most KRI portfolios contain thresholds calibrated when the LOB was a different size, in a different rate environment, and serving a different customer mix. Module two covers the threshold review method: how to identify thresholds firing on noise, thresholds masking the movement, and the small set of KRIs that actually move with the underlying risk. Includes a threshold recalibration worksheet and a decision log template for the LOB risk committee.

Module 3. Issue aggregation under the bank's RCSA and Heightened Standards

Issue logs accumulate findings from internal audit, regulatory exams, control self-assessments, and incident reviews. Module three covers the aggregation method that maps each finding to risk type, root cause, and aging band, then surfaces the small set that genuinely changes the LOB profile. Specific attention to Heightened Standards MRA aging, internal audit issue closure rate, and the difference between issue count and issue weight.

Module 4. Control test failure rate as a leading indicator

Control test failure rates move ahead of incidents and ahead of KRI breaches when read correctly. Module four covers how to triangulate test failure rate against issue volume, KRI movement, and control design changes to identify whether the LOB is genuinely degrading or whether a single batch of poorly-designed tests is generating noise. Includes a test-failure analysis template and a control owner conversation script.

Module 5. Emerging risk inputs and the LOB-level horizon scan

Emerging risks arrive through enterprise risk function memos, regulator speeches, peer-bank incidents, and business head conversations. Module five covers how to filter the enterprise-level horizon scan down to the small set that genuinely changes the LOB profile this quarter. Includes a horizon-scan-to-profile translation worksheet and a business head briefing template for emerging risk discussions.

Module 6. The one-page LOB risk profile template

The profile lives or dies on the front page. Module six provides the one-page template: top-two risks named, the one risk moving with direction and magnitude, the supporting evidence summarised in two lines per risk, and the change-since-last-quarter call-out. Includes the template, the populated worked example for a commercial LOB, and the rationale for every element on the page.

Module 7. The supporting pack that defends the front page

Behind the one-page profile sits a supporting pack that the CRO, the ERC, and internal audit will read in detail. Module seven covers the pack structure: KRI movement summary, issue aging detail, control test triangulation, emerging risk note, and the methodology page that documents the aggregation logic. Includes the pack template and the two-line rationale required for every section.

Module 8. The business head talk-track for the ERC

The business head walks into the Enterprise Risk Committee with the profile in hand and two minutes to defend it. Module eight covers the talk-track structure: the two-sentence opener that names the top risk and the movement, the supporting line that anticipates the CRO's likely follow-up, and the close that names what the LOB is doing about it. Includes worked talk-tracks for three common scenarios and a pre-ERC briefing call template.

Module 9. Reconciling the LOB profile to the enterprise heat map

The enterprise heat map aggregates the LOB profiles into a bank-wide view. Module nine covers how the LOB profile maps onto the enterprise risk taxonomy, where the aggregation logic typically loses fidelity, and how to surface to the enterprise risk function the LOB-specific risks that the bank-wide heat map needs to retain. Includes a mapping worksheet and a quarterly enterprise risk function note template.

Module 10. Worked examples across LOBs

Module ten walks through three full worked examples: a commercial banking LOB with concentration concerns, a retail LOB with operational loss trend, and a capital markets LOB with market-risk and conduct-risk overlay. Each example takes the four input streams, applies the reconciliation method, and produces the one-page profile plus the supporting pack. Each example includes the methodology decisions made and the rationale for them.

Module 11. Quarterly cadence and the reconciliation calendar

The reconciliation method only works if the LOB risk team runs it on a predictable calendar that lines up with the ERC date, the business head's review window, and the enterprise risk function's aggregation cycle. Module eleven covers the quarterly cadence template, the input-cutoff dates, the review-window structure, and the escalation path if a stream is late. Includes a quarter-calendar template and an escalation script.

Module 12. Defending the methodology under internal audit and regulatory review

The aggregation methodology will be tested by internal audit and reviewed by the regulator. Module twelve covers how to document the methodology so it survives both: the decision log, the threshold rationale, the aggregation weights, and the change-control trail. Includes a methodology binder template and a self-assessment checklist the LOB risk team runs before internal audit walks in.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Top of the cycle: input cutoffs hit, KRI dashboard locks, control test results land, issue log is frozen. Modules 1-4 give the reconciliation method that produces a defensible read of all four streams.

Middle of the cycle: emerging risk inputs filter in, the LOB risk team drafts the profile, the business head reads it. Modules 5-8 give the one-page profile template, the supporting pack, and the talk-track the business head walks into the ERC with.

Aggregation to enterprise: the LOB profile rolls into the bank-wide heat map. Module 9 covers the mapping and the LOB-to-enterprise note that preserves fidelity.

Audit and regulatory review: internal audit tests the profile methodology, the regulator reviews the bank's risk reporting under Heightened Standards. Modules 10-12 give worked examples, the quarterly calendar, and the methodology binder.

What you get with this course

Twelve written modules with worked examples for commercial, retail, and capital-markets LOBs.
Downloadable templates: one-page LOB risk profile, supporting pack structure, KRI threshold review worksheet, issue aggregation matrix, control test triangulation template, business head talk-track, methodology binder.
Hand-built implementation playbook tailored to the LOB the buyer covers, delivered alongside course access.
Quarter calendar template and escalation script for late input streams.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.

Modules 1-4 are designed to be worked through in the first week, covering the four input streams and the KRI threshold review.

Modules 5-8 in week two, building the one-page profile, supporting pack, and business head talk-track.

Modules 9-12 in week three, covering enterprise mapping, worked examples across LOBs, quarterly cadence, and the methodology binder for internal audit and regulatory review.

Before and after

Before

The LOB risk profile reads as a long list of everything: every KRI in amber, every open issue, every aging MRA, every control test fail. The business head reads it the night before the ERC and calls because he cannot defend it in two sentences. The CRO asks why the top-two risks the profile names are not the two MRAs aging into supervisory range. Internal audit flags the methodology gap. The next quarter looks the same.

After

The one-page profile names the top-two risks with the supporting evidence in two lines each, calls out the one risk genuinely moving with direction and magnitude, and gives the business head a two-sentence talk-track he defends without going off-script. The supporting pack documents the aggregation methodology. The mapping note preserves LOB-specific fidelity into the enterprise heat map. Internal audit and the regulator review the methodology binder and find it traceable.

What happens if you do not address this

The next quarter the LOB risk profile still reads as a list of everything. The business head goes off-script in the ERC. The CRO follows up with the LOB Chief Risk Officer about the missed MRAs. Internal audit's next risk reporting review surfaces the methodology gap as a finding. The regulator's next review of the bank's risk reporting under Heightened Standards flags the inconsistency between the LOB profile and the enterprise heat map. The LOB risk function spends the following quarter responding to the issue rather than running the cycle.

Who it is for

LOB Risk Lead in a US regional or national bank, second-line risk function, partnering with a single business line (commercial banking, retail banking, corporate and institutional banking, capital markets, or wealth). Five to fifteen years in bank risk management. Owns the quarterly LOB risk profile that rolls into the enterprise heat map. Reports to the LOB Chief Risk Officer or the enterprise Head of Operational Risk. Sits in front of the business head and the Enterprise Risk Committee. Has a working knowledge of OCC Heightened Standards, the bank's RCSA methodology, and the issue management system, but spends most of the cycle reconciling artefacts rather than building the reconciliation method.

Who this is NOT for. First-line business risk officers who own controls execution rather than aggregation. Enterprise Risk Management leads who own the bank-wide heat map rather than a specific LOB profile. Internal Audit professionals who test the profile rather than build it. Model Risk specialists. Compliance officers focused on specific regulations rather than enterprise risk reporting.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly three to four hours per week across three weeks for the written modules. The implementation playbook is built to be used inside one quarterly cycle, so a working buyer can apply it to the next LOB risk profile they own.

Why $199 is the right number

Enterprise risk training from large bank consultancies covers the bank-wide heat map but does not get into the LOB profile reconciliation method. Operational risk certifications cover risk taxonomy and methodology principles but stop short of the one-page artefact and the business head talk-track. Internal bank-run training tends to be calibrated to the bank's current methodology and does not give the LOB Risk Lead a method to reconcile a methodology that is itself drifting. This course sits at the LOB Risk Lead's specific artefact: the quarterly profile that has to satisfy the business head, the ERC, and the regulator at once.

FAQ

Does this work for any LOB or do I need to be in a specific business line?

The method is the same across LOBs. The worked examples cover commercial, retail, and capital markets. The implementation playbook is tailored to the LOB the buyer covers, so the templates land already populated with the risk taxonomy, KRI categories, and issue types that fit the LOB.

What if the bank's RCSA methodology is in flight?

Most banks are running an RCSA methodology refresh on a rolling basis. The reconciliation method is methodology-agnostic. It works with the current methodology while the refresh is in flight, and it is designed to absorb the methodology change at the next cycle boundary.

How does this fit with the Heightened Standards framework?

The course treats Heightened Standards MRA aging as one of the four input streams and gives explicit attention to how MRAs map into the LOB profile and the enterprise heat map. The methodology binder documents the treatment in the way a regulator review of the bank's risk reporting will look for.

Will the business head actually use the talk-track?

The talk-track is structured around what business heads typically say in the ERC: a two-sentence opener, a follow-up line that anticipates the CRO's question, and a close that names the action. It is a starting point that the business head adjusts to his own voice, not a script he reads.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.