> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprova.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Provalytics in Your Workflow

> Learn a practical rhythm for using Provalytics across weekly, monthly, and planning conversations.

## Overview

Provalytics works best when it is part of your operating rhythm, not just a report you open after the fact.

The strongest teams use it across three cadences:

* weekly performance review
* monthly budget and pacing review
* quarterly planning and scenario work

## Weekly rhythm

Use the weekly rhythm to answer:

* What changed?
* Which channels or campaigns are creating incremental impact?
* Are we seeing unusual softness, timing delays, or efficiency pressure?

The most useful pages here are:

* [Home Dashboard](/using-provalytics/home-dashboard)
* [Incrementality Report](/using-provalytics/incrementality-report)
* [Campaign Performance](/using-provalytics/campaign-performance)
* [Trending](/using-provalytics/trending)

## Monthly rhythm

Use the monthly rhythm to answer:

* Are we allocating enough budget to the right places?
* Are costs or efficiency moving in the wrong direction?
* Are we still comfortable with model quality and data health?

The most useful pages here are:

* [Spend Headroom](/using-provalytics/spend-headroom)
* [CPM Report](/using-provalytics/cpm-report)
* [Proof Report](/using-provalytics/proof-report)
* [Opportunity Days](/using-provalytics/opportunity-days)

## Planning rhythm

Use the planning rhythm when the question becomes:

* What should we do next?
* What happens if budget changes?
* Where should we press harder and where should we protect efficiency?

The most useful pages here are:

* [Budget Recommendations](/planning/budget-recommendations)
* [Scenario Planner](/planning/scenario-planner)
* [Days to Conversion Report](/using-provalytics/days-to-conversion-report)

## A practical team pattern

A strong operating pattern is:

1. Start with impact
2. Pressure-test with validation
3. Move into campaign or channel detail
4. Decide whether the next move is timing, allocation, or investigation

That keeps the team focused on business movement instead of getting lost in isolated metrics.