Recession Forecast Scorecard: Methodology

By Swoopr Editorial Team Published 2026-09-17 Research-assisted analysis. Verify sources before acting.

--- title: "Recession Forecast Scorecard: Methodology" slug: "forecast-scorecard-recession-methodology" content_type: "Forecast Scorecard" content_type_id: "forecast_scorecard" priority: "P0" status: "draft-ready" canonical_path: "/research-lab/forecast-scorecard-recession-methodology/" primary_hub: "/research/forecast-scorecards/" audience: ["beginner","intermediate","advanced"] educational_only: true ai_assisted: true sources: - "https://fred.stlouisfed.org/" - "https://www.bea.gov/data/gdp" ---

Key Takeaways

• A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast.
• A forecast scorecard should grade what was actually predicted, at the time it was predicted, using a metric declared before seeing the outcome.
• The Swoopr implementation should preserve the evidence path: claim → source → calculation or interpretation → limitation.
• Do not collapse uncertainty into a buy/sell score; expose the variables that change the answer.
• Where current rates, limits, rules, or market data matter, link to the authoritative source and timestamp the value.

Why This Format Exists

Forecast Scorecard pages solve a different problem from a conventional explainer. A normal article can teach the concept; this format makes the reader inspect the structure of the decision or evidence. For this topic, the goal is to turn a vague question into a sequence that can be checked, challenged, and updated. The page should work for a beginner who needs the plain-language mechanism and for an advanced reader who wants to trace the conclusion back to a source.

Federal Reserve Bank of St. Louis is used here as a primary or authoritative reference point for fred economic data. U.S. Bureau of Economic Analysis is used here as a primary or authoritative reference point for gross domestic product. Those sources are not included as decoration. They define the authoritative baseline for claims that can change over time or depend on a formal rule, methodology, or product structure. Swoopr should add interpretation around them, not replace them.

The Analytical Framework

1. Forecast Timestamp

For Recession Forecast Scorecard: Methodology, forecast timestamp is a separate analytical dimension rather than a box to check. A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast. Scorekeeping should reward calibrated probabilities rather than only dramatic yes/no calls. The practical task is to document what evidence would support this dimension, what evidence would weaken it, and whether the conclusion changes when the assumption moves. That prevents one attractive statistic or one alarming headline from becoming the whole analysis.

2. Target Definition

For Recession Forecast Scorecard: Methodology, target definition is a separate analytical dimension rather than a box to check. A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast. Scorekeeping should reward calibrated probabilities rather than only dramatic yes/no calls. The practical task is to document what evidence would support this dimension, what evidence would weaken it, and whether the conclusion changes when the assumption moves. That prevents one attractive statistic or one alarming headline from becoming the whole analysis.

3. Horizon

For Recession Forecast Scorecard: Methodology, horizon is a separate analytical dimension rather than a box to check. A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast. Scorekeeping should reward calibrated probabilities rather than only dramatic yes/no calls. The practical task is to document what evidence would support this dimension, what evidence would weaken it, and whether the conclusion changes when the assumption moves. That prevents one attractive statistic or one alarming headline from becoming the whole analysis.

4. Error Metric

For Recession Forecast Scorecard: Methodology, error metric is a separate analytical dimension rather than a box to check. A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast. Scorekeeping should reward calibrated probabilities rather than only dramatic yes/no calls. The practical task is to document what evidence would support this dimension, what evidence would weaken it, and whether the conclusion changes when the assumption moves. That prevents one attractive statistic or one alarming headline from becoming the whole analysis.

5. Revision Policy

For Recession Forecast Scorecard: Methodology, revision policy is a separate analytical dimension rather than a box to check. A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast. Scorekeeping should reward calibrated probabilities rather than only dramatic yes/no calls. The practical task is to document what evidence would support this dimension, what evidence would weaken it, and whether the conclusion changes when the assumption moves. That prevents one attractive statistic or one alarming headline from becoming the whole analysis.

6. Calibration And Bias

For Recession Forecast Scorecard: Methodology, calibration and bias is a separate analytical dimension rather than a box to check. A recession forecast is not a single number unless the forecaster specifies the recession definition, horizon, probability, and date of the forecast. Scorekeeping should reward calibrated probabilities rather than only dramatic yes/no calls. The practical task is to document what evidence would support this dimension, what evidence would weaken it, and whether the conclusion changes when the assumption moves. That prevents one attractive statistic or one alarming headline from becoming the whole analysis.

Worked Example

Imagine a forecaster publishes a 12-month estimate on January 1, then revises it four times. The scorecard should preserve the January 1 forecast as its own observation rather than grade only the last revision. That prevents hindsight from entering the dataset and allows separate questions: Was the initial forecast accurate? Did revisions add information? Was confidence calibrated?

Swoopr Lens: Question, Evidence, Failure Condition

Question. State the exact decision or claim in one sentence. For this page, avoid substituting a broader topic label for the actual question.

Evidence. Prefer primary sources for rules, filings, product terms, and official data. Secondary research can add context, but it should not outrank the source that defines the underlying fact.

Failure condition. Write down what observation would make the current interpretation weaker or wrong. If the page cannot name a failure condition, it is probably describing a belief rather than performing analysis.

Update rule. Record which parts are evergreen and which are date-sensitive. A methodology change, regulatory change, new filing, or material data revision should trigger a content review; a passing calendar date alone should not.

What to Verify Before Publishing

• The title and direct answer describe the same question.
• Every time-sensitive factual claim has an authoritative source and an as-of date.
• Any hypothetical example is labeled as hypothetical and does not imply historical performance.
• The page distinguishes a mechanism from a prediction.
• Internal links point to the canonical Swoopr concept, hub, comparison, or tool rather than creating a duplicate explanation.
• The conclusion exposes uncertainty, exceptions, and failure conditions.

Common Mistakes

• Using the final revised forecast as the original. This can make the page sound more certain than the evidence allows or cause the reader to optimize the wrong variable.
• Changing the scoring rule after the outcome. This can make the page sound more certain than the evidence allows or cause the reader to optimize the wrong variable.
• Grading different definitions together. This can make the page sound more certain than the evidence allows or cause the reader to optimize the wrong variable.
• Rewarding confidence without calibration. This can make the page sound more certain than the evidence allows or cause the reader to optimize the wrong variable.

Limitations

This page is designed as educational research infrastructure. It cannot know a reader's complete financial situation, tax position, liquidity needs, legal constraints, or tolerance for loss. Historical relationships may change, product terms can change, and regulations can be amended. Where the question depends on current rules or market values, verify the linked primary source before acting. The page should also resist false precision: if the evidence supports a range, condition, or set of scenarios, publishing a single number would make the output less accurate rather than more useful.

Is this page a recommendation?

No. It is an educational research format designed to make assumptions, evidence, and failure conditions explicit. It does not tell a reader to buy, sell, hold, or select a particular investment.

What is the first thing to verify?

Start with the definition of the question and the primary source. A forecast scorecard should grade what was actually predicted, at the time it was predicted, using a metric declared before seeing the outcome. A correct source attached to the wrong definition, period, benchmark, or unit can still produce a wrong conclusion.

What would make the conclusion change?

The conclusion should change when a material assumption, constraint, source fact, or failure condition changes. The page should state those variables explicitly so updates are analytical rather than cosmetic.

How should this page be updated?

Refresh source-dependent facts on a declared schedule, preserve the prior version when the change is material, and record what changed. Evergreen explanations should not be rewritten simply to create artificial freshness.

• Primary hub: /research/forecast-scorecards/
• Research Workbench: /research/
• Compare: /compare/
• Tools: /tools/
• Glossary: /glossary/

• Federal Reserve Bank of St. Louis: FRED Economic Data, Federal Reserve Bank of St. Louis.
• BEA: Gross Domestic Product, U.S. Bureau of Economic Analysis.