# Analytics Metric Period Consistency Check

Check that a channel analytics metric matches its stated reporting period before it is quoted.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Analytics metric value, its reporting period and the period the report claims.

## Workflow
1. Record the metric value and its actual reporting period.
2. Record the period the report claims.
3. Normalize both to the same period length.
4. Return the consistency check without changing the report.

## Output contract
metric | actual_period_days | claimed_period_days | value | normalized_value | match

## Fictional acceptance test
Fictional analytics shows 120 new followers over 30 days, which is 4 per day; the report quotes 40 per day for the same metric, so the figure is inconsistent with the period and gets flagged.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715231495196-Planable-Analytics

Checked October 20, 2026. Oct17 live AIS Search Console (sc-domain property, tej@groweasy.ai, Saturday audit): Oct 9-15 complete week 22 clicks, 937 impressions, 2.3% CTR, position 10.6, day-row verified. Top queries: Muse India 125i (3-month), Planable/Claude social agent 45i, marketing Copilot 37i, Planable/ChatGPT 24i, investor agents 19i, Copilot investment-committee 14i, cash flow forecasting 13i, campaign brief 12i. Google Trends verified Oct 17: muse glimmer/spark rising. Site impressions are query leads, not monthly volumes; exact topic volume is unmeasured.