---
title: "forecasting | Skills We Assign For | Azendo"
description: "Business forecasting — intervals over point estimates, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/forecasting/"
---

[Skills](https://azendo.co/skills/) Analytics and BI 

# forecasting.

Forecasting projects a series forward from its history and known drivers. In business use it supports capacity, inventory and financial planning, and its value depends on honest uncertainty as much as on the central estimate.

## Where forecasting fits on a long engagement.

A point forecast is close to useless on its own. The planning question is not "what will demand be" but "what should we prepare for", and that needs a range. A forecast of a thousand units means something quite different if the interval is nine hundred to eleven hundred than if it is four hundred to two thousand.

Simple methods are a genuinely hard baseline to beat. Seasonal naive — this month equals the same month last year — outperforms elaborate models on many business series, and a project that does not check against it has no evidence that its complexity earned anything.

## What an assigned team does with forecasting.

Forecasts need monitoring after deployment, which is the step most often skipped. A model that was accurate at launch degrades as conditions change, and without tracked error nobody notices until a planning decision goes badly wrong.

That continuous evaluation is standing work rather than a delivery milestone, held within an agreed [committed monthly capacity](https://azendo.co/pricing/).

## What we use forecasting for.

* Intervals rather than point estimates A range to plan against, because the uncertainty is the decision-relevant part.
* Complexity justified against a naive baseline Checking that a model beats seasonal naive before it is trusted.
* Accuracy tracked after deployment Forecast error monitored, so degradation is caught before a plan depends on it.

## How forecasting capacity is assigned.

Forecasting capacity is assigned under [managed data services](https://azendo.co/services/data-engineering/), with post-deployment accuracy tracking treated as part of delivery.

## Roles we assign forecasting for

* [Data Scientist Data science](https://azendo.co/services/data-science/data-scientist/)

## Service lines it sits in

* [Data science](https://azendo.co/services/data-science/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in analytics and bi

* [Looker — skill we assign for](https://azendo.co/skills/looker/)
* [Power BI — skill we assign for](https://azendo.co/skills/power-bi/)
* [Tableau — skill we assign for](https://azendo.co/skills/tableau/)
* [semantic layers — skill we assign for](https://azendo.co/skills/semantic-layers/)
* [A/B testing — skill we assign for](https://azendo.co/skills/a-b-testing/)
* [experimentation design — skill we assign for](https://azendo.co/skills/experimentation-design/)
* [causal inference — skill we assign for](https://azendo.co/skills/causal-inference/)
* [cohort analysis — skill we assign for](https://azendo.co/skills/cohort-analysis/)

## Tell us what your roadmap needs forecasting for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)