Fin Maverick
Foundations VocabularyAccounting & ReportingEconomics & MacroQuant Methods & ProgrammingBusiness & Company AnalysisCorporate Finance & ValuationBehavioural Finance
Banking & Market InfrastructureFixed Income & RatesDerivatives & Structured ProductsPublic EquitiesTransactions & DealsPortfolio ConstructionFunds & AMCs
Private Markets & AlternativesRisk, Treasury & ControlAI & Digital FinanceStochastic Calculus & PricingWealth & Personal FinanceIndian Markets & RegulationProfessional Practice
CalculatorComparison
Frameworks
Explore Bootcamps
Equity ResearchPortfolio ManagementMutual Fund MasteryFinancial LiteracyInvestment Banking Analyst
Private Equity AnalystHedge Funds AnalystBreaking Into VCBreaking Into QuantsAI For Finance
Financial Analyst ProgramRisk Management ProgramPrivate Wealth ManagementDebt Capital MarketsDerivatives Foundation
Explore Internships
Equity Research InternMutual Fund Intern
Portfolio Management InternFinancial Literacy Intern
Explore Micro Courses

Equity Research6

Writing an Investment ThesisBuilding a Discounted Cash FlowReading an Annual Report FastReading a Sector Before a CompanySpotting Quality of Earnings Red FlagsBuilding a Revenue Forecast From Drivers

Portfolio Management3

Rebalancing: When, Why and What It CostsStrategic and Tactical Asset AllocationMeasuring Risk in a Portfolio

Mutual Fund Mastery3

Comparing Funds Without Being FooledHow a NAV Is Struck and Which Day You GetReading a Fund Factsheet Properly

Derivatives Unlocked4

Hedging a Real ExposureThe Greeks, PracticallyFutures, the Basis and What Moves ItReading an Option Payoff

AI For Finance2

Retrieval and Grounding for FinanceDocument Extraction in Finance

Breaking Into Quants4

Backtesting a StrategyHypothesis TestingCleaning Financial DataRegression for Finance

Breaking Into VC3

Sizing a MarketReading a Term Sheet as a FounderHow a Venture Round Actually Works

Financial Analyst Program4

Common Size and Trend AnalysisReading a Cash Flow StatementRatio Analysis That Says SomethingBuilding a Working Capital Schedule

Risk Management Program2

Credit Exposure and How It Is ReducedValue at Risk and What It Hides

Investment Banking Analyst3

Precedent Transactions and Why They DifferReading a Term Sheet StructurallyBuilding a Comparable Companies Table

Private Wealth Management3

Tax Aware Portfolio DecisionsBuilding a Client Risk ProfileGoal Based Planning Arithmetic

Debt Capital Markets3

Analysing an Issuer's CreditDuration and What It Does Not Tell YouBond Pricing and Yield Mechanics

Private Equity Analyst2

Fund Waterfalls and CarryThe LBO in Structure

Hedge Funds Analyst2

Short Selling MechanicsLong Short Mechanics
Courses
Explore Career Roadmaps
Investment Banking AnalystEquity Research AnalystVC AnalystPrivate Equity AnalystHedge Funds Analyst
Quant AnalystAI For FinanceFinancial Analyst ProgramPrivate Wealth ManagementDebt Capital Markets
Risk Management ProgramDerivatives FoundationPortfolio ManagementMutual Fund Mastery
PartnershipsShowdown
Log inSign up
Quantitative Methods, Financial Data & Programming
1Probability
Probability in FinanceRandom VariableProbability DistributionsThe Normal DistributionNormal Distribution ProbabilityThe Lognormal DistributionRandomness vs Uncertainty
2Statistics and Inference
Population and SampleMean, Median and ModePrecision and AccuracyVariable TypesVariance, Standard Deviation and…Dispersion MeasuresStatistical BiasEffect SizeHypothesis TestingThe Sampling DistributionSkewnessKurtosisCovarianceConfidence IntervalArithmetic Mean vs Geometric MeanStatistical Significance vs Economic…Confidence Interval vs Prediction IntervalHow to Summarise a…
3Correlation and Regression
RegressionCorrelation and CausationOrdinary Least SquaresInteraction TermsRegression CoefficientsRegression vs ClassificationHow to Build a…Spurious CorrelationRegression, Correlation and FitResidualsMulticollinearityAutocorrelation and Partial Autocorrelation
4Time Series
Time Series in FinanceSimple, Weighted and Exponential…Moving Average CalculatorPrice, Return and Level SeriesHow to Prepare Time-Series…LagFrequencySeasonalityTimestampsTrendStationarity and the Unit RootHeteroskedasticityLeadRolling WindowsDifferencing
5Simulation and Numerical Methods
SimulationMonte Carlo SimulationHow to Run a…Numerical MethodsIterationResampling and the BootstrapPseudorandom Numbers and the SeedConvergence and ToleranceNumerical Stability
6Optimisation
OptimisationLocal and Global OptimaConstraintsConvex OptimisationThe SolverLinear ProgrammingThe Objective FunctionConstraint ViolationThe Feasible SetLagrange MultipliersQuadratic Programming
7Modelling Practice
Linear, Logistic, Ridge and…Training, Validation and Test…The ModelModel ErrorDependent and Independent VariablesThe ROC Curve and AUCWhat a Model HoldsMSE, RMSE, MAE and MAPEPrecision and RecallCross Validation and RegularisationOverfitting and UnderfittingReturn Series MeasuresSimple, Compound and Log Return
8Backtesting and Research Integrity
BacktestingBacktest vs Live PerformanceHow to Document a…How to Prevent Backtest…Out-of-Sample TestingWalk-Forward AnalysisMultiple TestingP-HackingData Snooping
9Data Quality and Structure
Data QualityThe DatasetSelection and Survivorship BiasVersioned DatasetsData Structures in FinanceData CleaningMissing Data and Null ValuesStructured Data vs Unstructured DataMissing Data vs ZeroData Validation vs Data CleaningOutliersDuplicate Records
10Programming for Finance
Data PipelinesAPIs for Financial DataAPI vs CSV FileDatabases in FinancePython for FinanceJoinsSQL for FinanceThe Analysis Workflow
11Quantitative Research
Research DesignThe Data Generating ProcessReproducibilityPeer Review in Analytical WorkThe Research HypothesisRobustness and Sensitivity

Precision and Recall: Two Views of the Same Classifier

Precision is the share of the months called up that really were up. Recall is the share of the real up months caught. On ten invented months relabelled up or down, a calling threshold of one half gives precision of 57.14 per cent and recall of 80.00 per cent, and every move of that threshold pushes one of them up and the other down.

Two numbers, one model, one set of ten months. The model is fitted once and never refitted, and no second record is built. Only one thing changes: which slice of one small table is being read. The slice chosen decides what can be said.

What arrives already settled, and what is left to do here?

Three things are carried in and none of them is explained a second time. The ten paired monthly readings of the Nakshatra unit and the Vasant unit are carried in already made, along with the relabelling of the outcome into up months and down months, five of each. The score attached to each month, a number between nought and one standing for how strongly the rule leans towards up, comes from the same place. And the thresholdThe cut-off a score has to reach before the rule commits to saying up. The threshold is set by a person after the model is built, not learned from the readings, and every score at or above it becomes an up call., together with the way a whole run of thresholds is stepped through in order, is covered under the threshold sweep.

One question is left, it has two answers, and most reports give only one of them. Given a table of calls against outcomes, how well did the rule do? There is no single honest number. There are two, they point in opposite directions, and a reader handed either one alone cannot tell a working model from a rule that says yes to everything.

Everything below reads one small table: the four cellsThe two by two count of calls against outcomes. Across the top, what the rule said; down the side, what actually happened. Every measure below is four whole numbers arranged in a square and nothing more. that record how many months were called up and turned out up, called up and turned out down, called down and turned out up, and called down and turned out down. At a threshold of one half those four counts are 4, 3, 1 and 2. Four counts of that kind are enough to rebuild every percentage below from scratch.

The ten invented months, their scores and their calls at a threshold of one half. The scores arrive already made, and no coefficient moves at any threshold.
MonthNakshatra changeVasant changeReallyScoreCalled at one halfWhich cell
11.00 per cent3.00 per centup0.50upcalled up and up
26.00 per cent18.50 per centup0.75upcalled up and up
3minus 4.00 per cent2.50 per centup0.25downcalled down and up
411.00 per cent17.00 per centup1.00upcalled up and up
51.00 per centminus 3.00 per centdown0.50upcalled up and down
6minus 9.00 per centminus 13.00 per centdown0.00downcalled down and down
76.00 per cent6.50 per centup0.75upcalled up and up
81.00 per centminus 1.00 per centdown0.50upcalled up and down
9minus 4.00 per centminus 7.50 per centdown0.25downcalled down and down
101.00 per centminus 3.00 per centdown0.50upcalled up and down
Seven months called up, three called down. Five months really up, five really down.4, 3, 1 and 2

What is precision, on its own?

The question in its plainest form: of the months the rule stuck its neck out on, how often was it right? Precision answers exactly that, and its arithmetic is a single fraction. Count the months called upA month the rule committed to. Its score reached the cut-off, so the rule said up out loud. Whether the month then went up or down is a separate fact and lives in a different column of the same table.. Count how many of those really were up. Divide the second by the first.

At a threshold of one half, seven of the ten months were called up. Four of those seven really were up. Four divided by seven is 0.571428 and onwards. Cut to two places that reads 57.14 per cent. The calculation stops there, and it has a shape worth naming: the denominator is chosen by the model, not by the world. A rule that says up less often has a smaller denominator, and a smaller denominator is easier to keep clean.

Precision never looks at the months that were not called. Nothing it stayed silent about can embarrass it. Take that seriously, because it is the crack the measure can fall through. Push the threshold all the way to one, and this same rule calls exactly one month up, month 4, and month 4 really was up. One right out of one call. Precision reads 100.00 per cent. Nine months went by, four of them genuinely up months, and not one of them appears anywhere in that fraction.

There is a street version of this that lands faster than the arithmetic. Picture a vendor outside a station who only calls out to a passer by when he is completely certain of a sale. He is right every single time he opens his mouth. The people he let walk past do not appear in his hit rate at all, so his hit rate is perfect and his takings are almost nothing. Perfect precision and an empty till are entirely compatible, and no amount of staring at the hit rate will reveal it.

A RULE THAT CALLS ONE MONTH UP AND GETS IT RIGHT SCORES 100.00 PER CENT the same rule at a calling threshold of one, where only month 4 reaches the cut-off 1 2 3 4 5 6 7 8 9 10 called up not called nine months the rule never committed to, and four of them really were up PRECISION 1 right of 1 call = 100.00 per cent RECALL, ON THE SAME RULE 1 caught of 5 = 20.00 per cent
At a calling threshold of one this rule commits to a single month and gets it right, so precision reads 100.00 per cent while the four real up months it stayed silent about pull recall down to 20.00 per cent.

What is recall, on its own?

The table turned the other way answers the opposite question. Of the months that really were up, how many did the rule catch? Recall answers that one: the number of real up months the rule called up, divided by the number of real up months.

Five of the ten months really were up: months 1, 2, 3, 4 and 7. Month 3 scored 0.25 and the cut-off was 0.50, so at a threshold of one half the rule caught four of them and let month 3 slip past. Four divided by five is 80.00 per cent exactly. Recall never looks at how many wrong calls it took to catch what it caught, so it cannot be embarrassed by noise.

And that is its own crack, the mirror image of the first. A rule that simply calls every single month up, with no thinking involved whatsoever, catches all five real up months and scores a recall of 100.00 per cent. The same rule also makes five wrong callsA month the rule committed to that then went the other way. A wrong call costs nothing in recall. Recall counts only the real up months and never the calls, which is exactly why recall alone can be fooled. along the way, and recall does not know they happened.

The everyday version: a household that answers every unknown number that rings will never miss a call from the hospital. Recall of one hundred per cent, and eleven sales calls a day to pay for it. Nobody would describe that as a good system, and yet described only by recall it is flawless.

A RULE THAT CALLS EVERY MONTH UP SCORES 100.00 PER CENT RECALL no model, no threshold worth the name, and nothing learned from anything 1 2 3 4 5 6 7 8 9 10 right right right right wrong wrong right wrong wrong wrong every month committed to, so no real up month can possibly be missed RECALL 5 caught of 5 = 100.00 per cent PRECISION, ON THE SAME RULE 5 right of 10 calls = 50.00 per cent
Calling every month up catches all five real up months for a recall of 100.00 per cent, which is why recall on its own cannot separate a working rule from one that says yes to everything.

Put the two side by side and the shape of the thing appears. The two measures are cut from the same four numbers, but one reads across the calls and the other reads down the outcomes. Precision and recall share one cell, the four months that were called up and really were up, and everything else about them is different.

ONE TABLE, TWO SLICES, AND THEY SHARE EXACTLY ONE CELL the ten invented months at a calling threshold of one half REALLY UP REALLY DOWN CALLED UP 7 months CALLED DOWN 3 months 4 caught, and right 3 called up, went down 1 missed, month 3 2 left alone, and right PRECISION reads across the top row: 4 right out of 7 called up, 57.14 per cent RECALL reads down the left column: 4 caught out of 5 that really were up, 80.00 per cent
Precision reads across the months that were called up and recall reads down the months that really were up, so the two measures are different slices of one four cell table.
Try it out

Which of the two measures never looks at the months that were not called up?

Try it out

A rule calls every single month up, thinking about nothing at all. What does it score on recall?

Breaking Into Quants Bootcamp — Fin Maverick Rebalancing: When, Why and What It Costs — free micro-course from Fin Maverick

What happens to each as the calling threshold moves?

The model is finished. The scores are fixed. The only thing left to choose is where the cut-off sits, and that choice belongs to a person rather than to the fitting arithmetic. Step it through the five distinct scores this record contains and watch what the two measures do. A run of settings of that kind is the sweepRunning the same finished model at one cut-off after another and writing down the result each time. Nothing is refitted between steps, so every difference in the readings comes from the cut-off and from nothing else., and building one is covered under the threshold sweep.

The same ten months read at five thresholds. Every row uses the identical model; only the cut-off moves.
ThresholdFour cellsPrecisionRecallAccuracyF1
0.005, 5, 0, 050.00 per cent100.00 per cent50.00 per cent0.6667
0.255, 4, 0, 155.56 per cent100.00 per cent60.00 per cent0.7143
0.504, 3, 1, 257.14 per cent80.00 per cent60.00 per cent0.6667
0.753, 0, 2, 5100.00 per cent60.00 per cent80.00 per cent0.7500
1.001, 0, 4, 5100.00 per cent20.00 per cent60.00 per cent0.3333

Precision never falls as the threshold rises, recall never rises, and neither of those was assumed here: both were checked at every one of a hundred and one cut-off settings from nought to one in steps of a hundredth, and neither ever broke. That distinction matters. A claim that has been verified across the whole run is a different kind of statement from a claim that sounded right and was written down.

Read the two rows of numbers straight through. Precision climbs 50.00, 55.56, 57.14, 100.00, 100.00. Recall slides 100.00, 100.00, 80.00, 60.00, 20.00. Somewhere between the threshold of one half and the threshold of three quarters the two cross over, and after that the measure that looked weaker is the strong one. Nothing about the model changed anywhere in that story. Not one coefficient moved.

ONE UNCHANGED MODEL, ONE MOVING CUT-OFF, TWO OPPOSITE SLOPES 0 20 40 60 80 100 they cross somewhere in this band 50.00 55.56 57.14 100.00 100.00 100.00 100.00 80.00 60.00 20.00 0.00 0.25 0.50 0.75 1.00 THE CALLING THRESHOLD PRECISION, which never falls as the cut-off rises RECALL, which never rises as the cut-off rises
As the calling threshold rises precision climbs from 50.00 per cent to 100.00 per cent while recall falls from 100.00 per cent to 20.00 per cent, and the two lines cross between one half and three quarters.
Try it out

The threshold rises from one half to three quarters. What happens to precision, and what happens to recall?

Play with it

Drag the calling threshold and watch two measures on one unchanged model pull apart.

One control moves: the cut-off a score has to reach before the rule says up. The model is never refitted and the ten months never change, so everything that moves on this panel is a consequence of the cut-off alone. The strip redraws with the cut-off line sliding through the scores, the four cells recount, and the two bars rescale in opposite directions. The tick marks under each bar show where that measure sits at the other four settings, so the whole run is visible without leaving the current setting. At the opening setting the threshold is 0.50, seven months are called up, the four cells read 4, 3, 1 and 2, precision is 57.14 per cent and recall is 80.00 per cent.

Jump to a setting:
Months called up
7
Precision
57.14 per cent
Recall
80.00 per cent
Accuracy
60.00 per cent
F1
0.6667

Educational illustration, built entirely on invented figures. The scores are held fixed throughout and the model is never refitted, so the cut-off is the only moving part. Four months share a score of 0.50 and two share 0.25, so several markers change hands at once at those settings rather than one at a time.

Value at Risk and What It Hides teaches you to compute value at risk three ways, interpret the figure, and say precisely what it refuses to describe.

Why can the two never be raised together?

Because of what raising a threshold physically does, and it does only one thing. Lift the cut-off and some months that used to reach it no longer do. No month can newly reach a cut-off that has just been raised. So every step upward removes up calls and adds none, and that single fact settles the whole question.

Now think about what removal does to each measure. Removing a wrong call takes a month out of precision's denominator and leaves the numerator alone, so precision goes up or stays put. Recall's denominator is the count of real up months, and no threshold can change that. Removing a right call therefore takes a month out of recall's numerator and leaves the denominator where it was. So recall goes down or stays put. There is no third kind of removal available, and there is no move that only ever removes the wrong ones.

The step from one half to three quarters on this record shows it happening. At one half, seven months are called up: 1, 2, 4, 5, 7, 8 and 10. At three quarters, three are: 2, 4 and 7. Four calls were removed. Three of them, months 5, 8 and 10, were wrong calls, and losing them lifts precision from 57.14 per cent all the way to 100.00 per cent. One of them, month 1, was a right call, and losing it drops recall from 80.00 per cent to 60.00 per cent. Three good removals and one bad one in a single step, and the good ones cannot be ordered without the bad.

RAISING THE CUT-OFF REMOVES CALLS, AND IT CANNOT PICK WHICH ONES CALLED UP AT A THRESHOLD OF ONE HALF: 7 MONTHS 1 2 4 5 7 8 10 4 right, 3 wrong RAISE IT TO THREE QUARTERS AND FOUR CALLS ARE REMOVED 5 8 10 1 a wrong call gone a wrong call gone a wrong call gone a RIGHT call gone WHAT SURVIVES: 3 CALLS, ALL OF THEM RIGHT 2 4 7 and 2 real up months now sit outside every call PRECISION 57.14 to 100.00 per cent RECALL 80.00 to 60.00 per cent
Raising the cut-off from one half to three quarters removes four calls, three wrong and one right, so precision climbs to 100.00 per cent while recall drops to 60.00 per cent in the same single move.

The argument leans on almost nothing. No sentence in it mentions the Nakshatra unit, the Vasant unit or any of the ten readings. Two facts carry the whole of it: raising a cut-off subtracts calls, and one measure counts calls in its denominator while the other counts outcomes. The trade-off is not a property of this record. The trade-off is a property of what the two measures are built out of, so it holds on any record at all.

Try it out

Why is it mechanically impossible to raise both measures by moving the threshold?

What does F1 do with the two, and what does it hide?

The obvious wish, once there are two numbers that will not both go up, is for a single number that settles the argument. F1 is the usual answer. F1 combines precision and recall in a way that is dragged down hard by whichever of the two is worse, so a rule cannot buy a good F1 by being brilliant at one and hopeless at the other. On the counts themselves F1 is twice the right calls divided by twice the right calls plus the wrong calls plus the missed months. The arithmetic stays in whole numbers until the final division.

Across the sweep it reads 0.6667, 0.7143, 0.6667, 0.7500 and 0.3333. Look at the first and the third. The two readings are the same number, and they come from confusion tables that have nothing in common. At no threshold at all the four cells are 5, 5, 0 and 0: everything called up, every real up month caught, five wrong calls, nothing left alone. At one half the four cells are 4, 3, 1 and 2: a rule making an actual distinction, catching most of what mattered, wrong three times and correctly quiet twice. F1 puts both at 0.6667 and cannot say which of the two is in front of the reader.

The collision is not a defect anybody can fix. There are more pairs of measures than there are values to give them, so any single number built out of two will land on the same value from more than one place. The one available remedy is to refuse to let the single number travel alone.

ONE F1, TWO COMPLETELY DIFFERENT TABLES BEHIND IT THRESHOLD THE FOUR CELLS PRECISION RECALL F1 0.00 5, 5, 0, 0 50.00 100.00 0.6667 0.25 5, 4, 0, 1 55.56 100.00 0.7143 0.50 4, 3, 1, 2 57.14 80.00 0.6667 0.75 3, 0, 2, 5 100.00 60.00 0.7500 1.00 1, 0, 4, 5 100.00 20.00 0.3333 SAME F1 Everything called up with five wrong calls, against a rule that makes a real distinction. One number standing for two cannot tell the two apart.
F1 reads 0.6667 at a threshold of nought and again at one half, from four cells of 5, 5, 0, 0 and 4, 3, 1, 2, so one number standing for two can be reached from more than one place.
Try it out

F1 reads 0.6667 at no threshold at all and again at one half, from cells of 5, 5, 0, 0 and cells of 4, 3, 1, 2. What does that say about F1?

Why is accuracy a poor summary on its own?

Accuracy is the friendliest of the four and the least informative. Accuracy counts everything the rule got right, of either kind, over all ten months. At a threshold of one half that is four right up calls plus two months correctly left alone, six out of ten, 60.00 per cent. Most readers hear sixty per cent and think of a pass mark.

Now put a baselineThe dullest rule available instead, written down so a result has something to be measured against. Here the baseline is the rule that calls every month up without looking at anything. Half the months went up, so that rule gets half of them right. next to it. The rule that calls every month up, having learned nothing from anything, gets five of the ten right and scores 50.00 per cent. So the model bought 10.00 per cent over doing nothing whatsoever, and 10.00 per cent is the real size of the claim, not 60.00 per cent.

Accuracy has a second silence that is worse than the first. Accuracy never says which kind of mistake was made. Three wrong up calls and one missed month score exactly the same as one wrong up call and three missed months, and on almost any record where the two mistakes cost different amounts, those are two different situations. And when one label is much rarer than the other, accuracy stops working altogether: if only one month in ten had been up, calling every month down would have scored 90.00 per cent while catching nothing at all.

SIXTY PER CENT SOUNDS LIKE A LOT UNTIL THE BASELINE IS DRAWN THE MODEL AT A THRESHOLD OF ONE HALF 60.00 per cent CALL EVERY MONTH UP, HAVING LEARNED NOTHING 50.00 per cent 0 25 50 75 100 10.00 per cent: everything the model bought 4 right up calls plus 2 correctly left alone 5 right purely because 5 went up
Accuracy of 60.00 per cent at a threshold of one half sits only 10.00 per cent above the 50.00 per cent a rule calling every month up would have scored without learning anything.
Try it out

Accuracy is 60.00 per cent and a rule calling every month up scores 50.00 per cent. What did the model actually buy?

Three numbers here look related to each other and are not

The ten months throw up some awkward coincidences, and they are worth naming rather than tripping over. Recall at a threshold of one half is 80.00 per cent, and accuracy at a threshold of three quarters is also 80.00 per cent. Accuracy at one half is 60.00 per cent, and recall at three quarters is also 60.00 per cent. A single summary of the same run of thresholds, set out under the threshold sweep, comes out at 0.8000, and 0.8000 looks like the two eighties above without being connected to either. Every one of those matches is a coincidence of this particular ten month record, and no sentence anywhere should read one of them off another. They are different fractions with different denominators that happen to land on the same digits.

Which of the two matters?

Here is the honest answer, and it is not the one a table of numbers can give. Nothing in the ten months decides it. Not the fit, not the scores, not the counts, not the sweep. The choice is made by whoever bears the cost of being wrong, and it depends entirely on which kind of wrong is expensive.

If a wrong up call is the expensive mistake, precision is what matters, and the cut-off is pushed up until the calls that are made are clean. A smoke alarm that empties an office building works that way: every false alarm costs an hour of everybody's day, so the alarm is set to be sure. If a missed up month is the expensive mistake, recall is what matters, and the cut-off drops until almost nothing gets past. A hospital screening test ahead of a serious one works the other way: a missed case is far worse than an extra check, so the test is tuned to be jumpy.

The data cannot make that call, and a threshold chosen without stating which mistake is more expensive has made the decision silently and hidden it inside a number. That is the real reason both measures belong in every report. Quoting one is quoting a conclusion about costs that was never argued.

Try it out

Which of precision and recall matters more on this record of ten months?

Risk Management Program Bootcamp — Fin Maverick

What belongs in a report, and in what order?

Somebody reading a written result, an analyst checking a colleague, a lender looking at a scoring rule somebody else built, all face the same problem: they have to work out whether the numbers in front of them can be trusted, and they usually cannot rerun anything. The order the figures are given in decides whether that is possible.

Put the four cells first. Everything else in the report is derived from them, and nothing else lets a reader recompute anything. Four whole numbers, 4, 3, 1 and 2, and the reader can build precision, recall, accuracy and F1 without asking a single question. Then the threshold. Every measure below it depends on where the cut-off was set, and a measure quoted without its cut-off is a measure quoted without half its meaning. Then precision and recall together, never one without the other. Then the baseline, so the reader can see what doing nothing would have scored on the same months.

The ordering protects against a specific, common failure: a summary figure travelling on its own, arriving somewhere far from the table it came from, and being read as a description of a model when it is a description of a choice. A reader with four whole numbers can rebuild the argument. A reader with one percentage can only accept or reject it.

THE SAME RESULT, REPORTED TWO WAYS WHAT USUALLY GETS WRITTEN The model achieved a recall of 80.00 per cent. A rule calling every month up would have reported 100.00 per cent on this line. WHAT LETS A READER CHECK THE RESULT 1. Four cells: 4 called up and up, 3 called up and down, 1 missed, 2 left alone. 2. Threshold: a month was called up at a score of 0.50 or above. 3. Precision 57.14 per cent AND recall 80.00 per cent, quoted together. 4. Baseline: calling every month up scores 50.00 per cent accuracy. Line 1 alone lets a reader rebuild lines 3 and 4 without asking anybody anything.
A report quoting recall of 80.00 per cent and stopping describes a model that could equally well be calling every month up, while the four cells let any reader rebuild every other figure.
Try it out

What should sit above precision and recall in any written result?

Where this goes wrong in practice

Somebody reports a recall of 80.00 per cent and stops there. The figure sounds strong. The figure is even true: the rule was right about the up months four times in five. The sentence leaves out two things. Seven months had to be called up to catch those four, so more than two calls in five were wrong. And a rule calling every month up without thinking would have reported a recall of 100.00 per cent on that same line and looked better still.

Recall on its own cannot separate a working model from a rule that says yes to everything, and neither can precision, in the opposite direction. The failure is not arithmetic. Every number in that sentence is correct. The failure is that one number was allowed to leave the table it came from.

The habit that fixes it is small and mechanical. Never quote one of the two without the other, and put the four cells above both. A reader holding 4, 3, 1 and 2 can compute every figure above in under a minute. A reader holding a single percentage can compute nothing at all, and has no way of knowing that.

Debt Capital Markets Bootcamp — Fin Maverick

What is covered elsewhere?

The curve produced by plotting a threshold sweep, and the single number that measures the area beneath it, are covered under the threshold sweep. The measures used when the answer is a size rather than a yes or no are covered separately.

How to price one kind of mistake against the other is a judgement about consequences and about who carries them, not a calculation, and nothing in a table of counts can settle it. Whether any call here would be worth acting on is a question about money at risk, and no count of months answers it.

What is behind each figure here, and what could be checked?

Every figure above is a count of ten invented months, so checking it means recounting rather than looking it up. The table below says which count produced which figure, in enough detail that a reader with a sheet of paper can redo any row.

Quantity quotedHow it was arrived atHow to check it in a minute
The ten monthly readings and the up or down label against eachWritten for teaching when these two units were made up, and carried in without alterationCount the labels: five up, five down, matching the signs in the table near the top
The score against each month, running 0.00 to 1.00Read off the straight line on the label at 0.4500 plus 0.0500 times the Nakshatra changePut a Nakshatra change of 1.00 per cent through it and confirm the score lands on 0.50
The four cells at each of the five thresholdsEvery month compared with the cut-off in turn and dropped into one of four boxesEach row of four adds to ten, and the two right-hand entries move as the cut-off climbs
Precision, recall, accuracy and F1 at each thresholdOne division each, taken from those four whole numbers and from nothing else4 over 7 gives 57.14 per cent, 4 over 5 gives 80.00 per cent, 6 over 10 gives 60.00 per cent
The claim that precision never falls and recall never risesWorked at a hundred and one cut-off settings from nought to one in steps of a hundredth, not assertedWalk the five distinct scores upward and watch the count of calls only ever shrink

The Nakshatra unit and the Vasant unit are invented.
Educational material. Not advice on any investment, tax, budget or market position.

← PreviousNext →
Fin Maverick Micro CoursesExplore Micro Courses
Fin Maverick BootcampsExplore Bootcamps
Fin Maverick

Finance education that ends in a job, not a certificate that gathers dust. Built for young India.

LEARN
CalculatorsFrameworksComparisonsCareersShowdown
RESOURCES
All CoursesMicro CoursesBootcampsInternships
COMPANY
AboutJob openingPartnership
LEGAL
Privacy PolicyTerms & ConditionsContent LicenseReturn & Refund Policy
© 2026 FIN MAVERICK / BUILT FOR INDIA.DO FINANCE, DO NOT JUST READ ABOUT IT.