---
title: Producing the monthly scorecard
slug: distribution-performance/producing-the-monthly-scorecard
icon: {"lucideIcon":"FileCog"}
docTags: 
createdAt: 2026-08-17T11:14:26.163Z
---

## 🎯 Purpose

Instruction for the analyst producing the Distribution monthly scorecard. Due at the monthly ops review on working day 8; data cut is close of business on working day 3.

:::hint{type="success"}
**✅ Operational effectiveness**

Publication deadlines are measured against the operational governance calendar. Consistent on-time delivery is reported as part of monthly operational effectiveness tracking.
:::

## 🔄 Operational publishing flow

```mermaid
flowchart LR
    A[Source Extract] --> B[Validation]
    B --> C[Reconciliation]
    C --> D[Executive Review]
    D --> E[Publication]
    C -->|Failure| F[Operational Escalation]
```

## ✅ Steps

::::WorkflowBlock
:::WorkflowBlockItem
Run the extract pack on working day 4: production extract (policy admin system), pipeline and referral extracts (CRM), persistency file (actuarial shared area).
:::

:::WorkflowBlockItem
Load extracts into the scorecard workbook. Do not edit extract files by hand — if a source number is wrong, fix it at source and re-extract, or footnote it.
:::

:::WorkflowBlockItem
Refresh the workbook and check the reconciliation tab: GWP must tie to the finance flash report within 0.5%. Outside tolerance, stop and resolve with **Finance Operations** before distributing anything.
:::

:::WorkflowBlockItem
Apply RAG statuses per the thresholds in the KPI pack. The thresholds are formula-driven — never hand-colour a cell.
:::

:::WorkflowBlockItem
Chase commentary for red/amber measures from the accountable owners (per the RACI in **Roles and Responsibilities**). Commentary must state cause, action, owner, date.
:::

:::WorkflowBlockItem
Publish to the distribution leadership channel by working day 8, 12:00, and archive a copy in the scorecard library with the naming convention `SC_YYYY-MM.xlsx`.
:::
::::

## ⚠️ Reporting controls and risks

::::Tabs
:::Tab{title="Data controls"}
- Validate all source extracts against prior month totals
- Reconcile finance-linked metrics before publication
- Confirm no missing commentary fields for red/amber measures
:::

:::Tab{title="Operational risks"}
- Delayed extract delivery from upstream systems
- Manual intervention in intermediary onboarding records
- Version control conflicts during executive review
:::

:::Tab{title="Publishing standards"}
- Apply the approved naming convention
- Archive prior month outputs in the reporting library
- Ensure all executive commentary is final before release
:::
::::

## ✅ Quality checks before publishing

- [ ] Reconciliation tab green
- [ ] No measure missing a value (gaps are recorded as "no data", never blank)
- [ ] Every red/amber has commentary
- [ ] Version and data-cut date on the cover page

