
Econometric Forecasting Advisor
Build economic forecasts with expert model selection and validation
What You Can Do
Receive actionable guidance on econometric model selection, specification testing, and uncertainty quantification for your economic forecasts. This skill helps you choose the right model (ARIMA, VAR, GARCH) based on your data characteristics, diagnose specification problems, validate assumptions, and communicate forecast uncertainty to stakeholders. You'll get structured workflows that turn raw economic data into defensible, statistically sound forecasts.
Features
Recommends ARIMA, VAR, GARCH, or state-space models based on data properties (stationarity, volatility, multivariate structure)
Tests for unit roots, cointegration, ARCH effects, and serial correlation. Identifies which assumptions your data violates
Out-of-sample testing, rolling windows, and residual diagnostics to confirm your model forecasts reliably
Constructs confidence intervals, fan charts, and density forecasts to communicate prediction uncertainty to decision-makers
Provides Python (statsmodels, scikit-learn) and R code templates you can adapt to your econometric workflow
Systematic validation of normality, homoskedasticity, no autocorrelation, and exogeneity assumptions
Explains impulse responses, Granger causality, forecast error variance decomposition in plain economic terms
Example Output
Example 1: Model Selection for Inflation Forecasting
Input: "I have 15 years of monthly CPI data with obvious seasonality. Should I use SARIMA or seasonal decomposition?"
Output:
- Recommended approach: Seasonal ARIMA (SARIMA) preserves statistical inference and forecast intervals
- Specification tests: Run ADF test on original and differenced series; test for seasonal unit roots (OCSB test)
- Model diagnostics: Compare SARIMA(1,1,1)×(1,1,1)₁₂ vs. X-13 seasonal adjustment; validate on out-of-sample 2023-2024
- Code snippet: Python template using
statsmodels.tsa.statespace.SARIMAX
Example 2: Multivariate Forecasting Validation
Input: "I built a VAR model for GDP, unemployment, and interest rates. How do I know it's working?"
Output:
- Granger causality tests: Identifies which variables predictively cause others
- Impulse responses: Shock scenarios (1% rate increase → unemployment effect path over 12 months)
- Forecast error variance decomposition: Attributes GDP variance to own shocks vs. rate shocks vs. unemployment shocks
- Validation protocol: Recursive forecasting 2020-2024; Diebold-Mariano test vs. benchmark AR(1) model
Example 3: Communicating Forecast Uncertainty
Input: "My stakeholders ask 'Is that 3.2% growth forecast confident?' How do I answer?"
Output:
- 68% confidence interval: [2.8%, 3.6%]
- 95% confidence interval: [2.1%, 4.3%]
- Fan chart: Visual probability distribution of outcomes
- Communication template: "We forecast 3.2% growth with a 2-in-3 chance of landing between 2.8–3.6%"
What's Included
- Model Comparison Framework: Structured checklist for comparing ARIMA, VAR, GARCH, dynamic factors, and ML alternatives for your use case
- Diagnostic Test Protocols: Complete workflows for unit root (ADF, KPSS), cointegration (Johansen), ARCH, autocorrelation, and normality testing
- Validation & Backtesting: Out-of-sample test design, rolling window procedures, Diebold-Mariano forecast accuracy tests, and loss function selection
- Uncertainty Communication: Methods for building confidence intervals, density forecasts, fan charts, and translating statistical intervals into business language
- Code Templates: Ready-to-adapt Python (statsmodels, scikit-learn) and R code for model fitting, testing, and interpretation
Who It's For
- Economists & Econometricians
- Central Bank & Treasury Analysts
- Financial Forecasters & Strategists
- Business Intelligence & Analytics Teams
- Academic Researchers
Best For
- GDP, inflation, unemployment, and macroeconomic forecasting
- Interest rate and foreign exchange projections
- Choosing between competing econometric models
- Validating and stress-testing forecast models
- Communicating forecast confidence to non-technical stakeholders







