Has any CE improved your underwriting accuracy — especially cash-flow sensitivity, DSCR breakpoints, and CRE stress testing? I’m weighing an 8-hour RMA financial statement analysis course against a Moody’s RiskCalc session; looking for what genuinely translated to better risk grading or faster write-ups, and I’ll do my own research since results vary.
RMA’s 8-hour session helped most for me: I built a one-tab sensitivity — ‘rate +200 bps, revenue -10/-20%’ — with a DSCR breakpoint tied to fixed vs. variable debt, and it now lives in my template so write-ups got faster and my grading tightened. RiskCalc is a solid PD benchmark, but it didn’t change my cash-flow spreads much compared to the RMA cases (https://www.rmahq.org/). Do you standardize a DSCR breakpoint blurb in every CRE credit?
For pure speed-to-grade, Moody’s RiskCalc tightened my consistency more than the 8-hour RMA, but it didn’t improve ‘cash-flow sensitivity’. What moved accuracy for me was bolting a lease-roll/NOI haircut tab onto my template (5–10% vacancy shock, refi test at exit cap +50–100 bps, debt rate +150 bps) and mapping coverage thresholds to grade notches. Are you modeling expirations or just margin shocks, @OP? https://www.moodysanalytics.com/product-list/riskcalc.
, most CE glosses over the DSCR breakpoint math… Between the eight-hour RMA FSA and RiskCalc, I’d pick RiskCalc for faster write-ups, then bolt on a tiny model: a single “DSCR at reset” line that uses actual amortization, a rate step-up (+200 bps), and an IO toggle, plus a simple lease rollover ladder for CRE. If you want hands-on with shocks, RMA’s CRE Lending School had more reps than the general FSA, @kelli_roberts86.
I’m with @w_harris58: for consistency, RiskCalc plus a tiny Excel “coverage breakeven” tab moved the needle more than the RMA FSA day — set fixed charges, link the floating-rate piece, Goal Seek NOI/revenue to your covenant (say 1.20x), and add a toggle for IO rolling to amortizing with a simple rent/occupancy haircut for CRE. , CE rarely forces that IO-to-amortizing hit, which is where accuracy slipped for me. If your gap is statement adjustments, the RMA workshop helps, but otherwise this combo sped my write-ups — are you modeling the IO roll right now?